Cloud Foundry Through the Eyes of a Hacker
summary
Cloud Foundry instances often expose API endpoints and vhosts that reveal versions and domains, enabling attackers to run credential stuffing via rented proxy botnets and bypass IP rate limits; common outcomes are pushed Bitcoin miners or stolen app databases. Practical defenses shown: put APIs behind VPNs or load‑balancer filters, enable multi-factor authentication (hard to configure today but effective), monitor CPU/disk for noisy apps, and keep UAA and stemcells patched against recent CVEs discovered by honeypots and automated scans.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:38Round 1 The Hacker
- 3:35Round 2 The Hacker
- 4:50Round 3 The Hacker
- 9:02Update Your Cloud Boundaries
- 11:39The Hacker
- 13:56Update Cloud Foundry
- 16:53Honeypot Windows
- 17:30Bluekeep
- 19:25Balance
- 21:27How big is the problem
- 22:37Password recommendations
- 24:36Security of other sites
- 24:52Multifactor authentication
- 26:42The hackers
- 27:09Cloud Foundry and Kubernetes
- 27:57Denial of Service
- 28:39Password reuse
- 29:59Pink slides
- 30:24Recent attacks
- 34:32Resources
related talks
35mBuilding Security In: Using Cloud Foundry to Secure CF Apps
30mCloud Foundry: The Gaps
36mCloud Hacking Scenarios
36mCatch Me If You Can – Leveraging Cloud Foundry, SDN, BOSH and Predictive Analytics
31mStranger Danger: Addressing Vulnerable CF Application Dependencies
11mOpening Remarks - Chip Childers, CTO, Cloud Foundry Foundation
29mGraphQL Security Best Practices and Hardening
39mReal-World Detection Evasion Techniques in the Cloud