[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f51vPFI8cF8dENdzp5NBspED8AJPMjAef7wRQYoc1Zyg":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":17,"status":23,"created_at":24,"published_at":25,"article":26,"tags":30,"podcasts":43,"controls":50},"ea3b958e-67f7-43c4-bce7-93c9bbf4cdc7","leaked-credentials-expose-kubernetes-secrets-in-rackspace-spot-breach","d2ca4536-0f3f-4817-b7f5-27bc74c788d9","Leaked Credentials Expose Kubernetes Secrets in Rackspace Spot Breach","Attackers leveraged leaked credentials to authenticate into Rackspace's Spot platform and read sensitive Kubernetes secrets — including passwords and API keys — stored within customer clusters. The root issue was that valid credentials provided unrestricted access to highly sensitive secret objects without additional authentication layers or anomaly detection to flag the unusual access. This matters because Kubernetes secrets, if left unencrypted at rest and inadequately access-controlled, become a single point of failure that can expose an entire cloud workload's credentials. Cloud providers managing multi-tenant Kubernetes environments carry an elevated duty to enforce least-privilege access, detect credential misuse, and ensure secrets are protected beyond basic RBAC.","**Immediate actions:**\n- Revoke and rotate all potentially exposed credentials, tokens, and API keys stored in affected Kubernetes secrets immediately.\n- Audit Kubernetes RBAC policies to ensure no role grants broad read access to secrets across namespaces.\n- Enable Kubernetes audit logging and review logs for unauthorized access to secret objects.\n\n**Long-term improvements:**\n- Encrypt Kubernetes secrets at rest using a dedicated key management service (e.g., AWS KMS, HashiCorp Vault) rather than relying on default base64 encoding.\n- Enforce multi-factor authentication (MFA) on all cloud platform accounts that can access cluster control planes or secret stores.\n- Apply least-privilege principles so that service accounts and users can only access the specific secrets required for their function.\n\n**Detection measures:**\n- Deploy behavioral monitoring to alert on anomalous credential use, such as access from unusual IPs or bulk secret enumeration.\n- Integrate secrets scanning into CI\u002FCD pipelines to prevent credentials from being committed or stored insecurely in cluster manifests.\n- Establish regular third-party reviews of cloud platform access controls and secrets management configurations.",[12,13,14,15,16],"CIS Control 6: Access Control Management","NIST SP 800-53 SC-28: Protection of Information at Rest","NIST CSF 2.0 PR.AA-05: Access permissions and authorizations","NIS2 Article 21(2)(i)","NIS2 Article 21(2)(j)",{"NIS2 Article 21(2)(i)":18,"NIS2 Article 21(2)(j)":19,"CIS Control 6: Access Control Management":20,"NIST SP 800-53 SC-28: Protection of Information at Rest":21,"NIST CSF 2.0 PR.AA-05: Access permissions and authorizations":22},"This point requires human resources security, access control, and asset management policies that, if enforced, would have ensured leaked credentials could not be freely used to access sensitive cluster resources.","This point mandates multi-factor authentication and secured communications, which if required for Rackspace Spot platform access would have blocked attackers from authenticating with leaked credentials alone.","This control requires enforcing least-privilege and regularly reviewing access rights, which would have limited the attacker's ability to read secrets across customer clusters using a single set of leaked credentials.","This control mandates encryption of sensitive data at rest, which applied to Kubernetes secrets would have rendered the exfiltrated data unreadable even after unauthorized access was achieved.","This category calls for managing access permissions based on least-privilege, which if applied to the Kubernetes API server would have prevented a single leaked credential from exposing all customer secrets.","published","2026-11-21T23:20:20.492322+00:00","2026-11-21T23:20:20.378+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fwww.bleepingcomputer.com\u002Fnews\u002Fsecurity\u002Frackspace-spot-breach-let-hackers-access-customer-kubernetes-secrets\u002F","rackspace-spot-breach-let-hackers-access-customer-kubernetes-secrets-1fa387","Rackspace Spot breach let hackers access customer Kubernetes secrets",[31,37],{"id":32,"name":33,"slug":34,"description":35,"color":36},"1ec88fde-2d0f-4ed8-932a-33f5ccc0fdc7","Access Control","access-control","Excessive privileges, missing MFA, weak auth","#f97316",{"id":38,"name":39,"slug":40,"description":41,"color":42},"c8b843a5-d5a7-41d1-8d3b-cabded09d2ef","Data Protection","data-protection","Unencrypted data, missing DLP, poor classification","#3b82f6",[44],{"id":45,"date":46,"edition":47,"title":48,"audio_url":49},"43288d5f-06ee-493d-a621-ec9347fca688","2026-11-22","morning","ThreatNoir Weekend Brief — November 22","https:\u002F\u002Fcdn.threatnoir.com\u002Fpodcasts\u002F2026-11-22\u002Fthreatnoir-morning-brief-2026-11-22.mp3",[51,55,59],{"slug":52,"name":53,"problem":54},"identity-threat-detection","Identity threat detection and response (ITDR)","Attackers who log in with real, stolen credentials get noticed.",{"slug":56,"name":57,"problem":58},"secrets-management","Secrets management","API keys, tokens and passwords stop leaking from code, chat and configuration files.",{"slug":60,"name":61,"problem":62},"endpoint-detection-response","Endpoint detection and response (EDR and XDR)","Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped."]