TGViewer
Kubesploit Kubesploit @kubesploit · 2.13K subscribers
Post #1902 175

Forwarded from KubeFM

Moving to Kubernetes doesn't replace your security practices, but it adds a layer on top.

Rodrigo Bersa at AWS breaks down what carries over and what must change.

What stays: least privilege, perimeter security, network access control, authentication and authorization.

What changes:

- Supply chain security — you're managing hundreds of images, not just VMs
- Multi-tenancy by default — workloads share nodes; namespace isolation and network policies keep them separate
- In-cluster auth needs its own model, separate from infrastructure-layer controls





Watch the full interview: https://ku.bz/dB7PDNt0v
More from @kubesploit
  1. Sep 22, 2026This article explains what an attacker can really do with leaked Kubernetes credentials, f…
  2. Sep 22, 2026"When an agent goes loose, you might find yourself: your S3 bucket has been deleted by mis…
  3. Sep 21, 2026This article walks through making a container image safe before it ever reaches the cloud,…
  4. Sep 21, 2026We just published Kubernetes Architecture in Financial Services, a free technical book abo…
  5. Sep 18, 2026This case study shows how a team ran ServiceNow's MID Server on EKS as a StatefulSet and f…
  6. Sep 17, 2026Kogaro continuously validates Kubernetes config with 60+ checks across reference, resource…
Threads Profile ViewerView any public Threads profile without an account.Open ThreadLook →Writing with AI? Make it sound human.Metric37 rewrites AI drafts so they read naturally. Free AI detector, 1,500 words free.Try Metric37 →