[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fCTu_NJELYJQjyvDD7_oI6ljEI5wPMDy8fkxfF0PsHX8":3},{"article":4,"iocs":51,"iocs_total":64,"watch_terms":65,"solutions":66,"lesson":156},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":28,"category":29,"article_tags":33},"d2ca4536-0f3f-4817-b7f5-27bc74c788d9","Rackspace Spot breach let hackers access customer Kubernetes secrets","rackspace-spot-breach-let-hackers-access-customer-kubernetes-secrets-1fa387","Rackspace warned customers that hackers breached its Rackspace Spot cloud platform using compromised credentials, allowing them to deploy unauthorized workloads and access Kubernetes secrets in customer clusters. [...]","Rackspace disclosed a breach of its Rackspace Spot cloud platform, where hackers used leaked credentials to access customer Kubernetes secrets and deploy unauthorized workloads. The incident, which occurred on November 17, 2026, allowed attackers to read sensitive information like passwords and API keys stored in customer clusters. Rackspace has since revoked tokens, rotated keys, and strengthened access controls, while advising affected customers to reissue tokens and rotate credentials.","Rackspace Spot platform breached via compromised credentials, exposing customer Kubernetes secrets.","https:\u002F\u002Fwww.bleepingcomputer.com\u002Fnews\u002Fsecurity\u002Frackspace-spot-breach-let-hackers-access-customer-kubernetes-secrets\u002F","https:\u002F\u002Fwww.bleepstatic.com\u002Fcontent\u002Fhl-images\u002F2022\u002F12\u002F09\u002FRackspace.jpg","2026-11-21T22:59:58+00:00","2026-11-21T23:00:17.130304+00:00",8,[17,20,23,26],{"name":18,"type":19},"Rackspace Spot","product",{"name":21,"type":22},"Kubernetes","technology",{"name":24,"type":25},"Rackspace","vendor",{"name":27,"type":25},"Platform9","2e06f76c-d5b9-4f54-9eef-4d3447b10730",{"id":28,"icon":30,"name":31,"slug":32},null,"Breaches","breaches",[34,39,41,46],{"category":35},{"id":36,"icon":30,"name":37,"slug":38},"26b0b636-0e31-4db1-bffb-61bdf9f20a58","Supply Chain","supply-chain",{"category":40},{"id":28,"icon":30,"name":31,"slug":32},{"category":42},{"id":43,"icon":30,"name":44,"slug":45},"c70f3a41-2f0c-4608-870d-b8cbcd8be076","Cloud Security","cloud-security",{"category":47},{"id":48,"icon":30,"name":49,"slug":50},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[52,56,58,60],{"type":53,"value":54,"context":55},"malware","probe","Suspicious Kubernetes pod and object prefixes",{"type":53,"value":57,"context":55},"i1",{"type":53,"value":59,"context":55},"glm-",{"type":61,"value":62,"context":63},"ip","23.224.79.106","Listed under \"Indicators of compromise\" in the article",4,[24,27,18],{"controls":67,"vendors":155},[68,97,126],{"slug":69,"name":70,"problem":71,"products":72},"identity-threat-detection","Identity threat detection and response (ITDR)","Attackers who log in with real, stolen credentials get noticed.",[73,81,89],{"vendor_slug":74,"vendor_name":75,"vendor_logo":76,"product_slug":77,"product_name":78,"url":79,"description":80},"microsoft","Microsoft","\u002Fvendor-logos\u002Fmicrosoft.png","defender-for-identity","Microsoft Defender for Identity","https:\u002F\u002Fwww.microsoft.com\u002Fen-us\u002Fsecurity\u002Fbusiness\u002Fsiem-and-xdr\u002Fmicrosoft-defender-for-identity","Detects attacks against on-premises Active Directory and hybrid identities.",{"vendor_slug":82,"vendor_name":83,"vendor_logo":84,"product_slug":85,"product_name":86,"url":87,"description":88},"huntress","Huntress","\u002Fvendor-logos\u002Fhuntress.png","managed-itdr","Huntress Managed ITDR","https:\u002F\u002Fwww.huntress.com\u002Fplatform\u002Fmanaged-itdr","Managed detection of suspicious activity in Microsoft 365 and Entra ID.",{"vendor_slug":90,"vendor_name":91,"vendor_logo":92,"product_slug":93,"product_name":94,"url":95,"description":96},"acalvio","Acalvio","\u002Fvendor-logos\u002Facalvio.png","shadowplex-identity-protection","ShadowPlex Identity Protection","https:\u002F\u002Fwww.acalvio.com\u002Fproducts\u002Fidentity-protection\u002F","Decoy accounts and credentials that expose identity attacks and credential misuse early.",{"slug":98,"name":99,"problem":100,"products":101},"secrets-management","Secrets management","API keys, tokens and passwords stop leaking from code, chat and configuration files.",[102,110,118],{"vendor_slug":103,"vendor_name":104,"vendor_logo":105,"product_slug":106,"product_name":107,"url":108,"description":109},"github","GitHub","\u002Fvendor-logos\u002Fgithub.png","advanced-security","GitHub Advanced Security","https:\u002F\u002Fgithub.com\u002Fsecurity\u002Fadvanced-security","Dependency review, code scanning and secret scanning with push protection.",{"vendor_slug":111,"vendor_name":112,"vendor_logo":113,"product_slug":114,"product_name":115,"url":116,"description":117},"gitguardian","GitGuardian","\u002Fvendor-logos\u002Fgitguardian.png","gitguardian-platform","GitGuardian Secrets Detection","https:\u002F\u002Fwww.gitguardian.com\u002F","Finds and helps remediate secrets leaked in repositories, CI pipelines and chat tools.",{"vendor_slug":119,"vendor_name":120,"vendor_logo":121,"product_slug":122,"product_name":123,"url":124,"description":125},"hashicorp","HashiCorp","\u002Fvendor-logos\u002Fhashicorp.png","vault","HashiCorp Vault","https:\u002F\u002Fwww.hashicorp.com\u002Fen\u002Fproducts\u002Fvault","Secrets management with short-lived credentials and encryption as a service.",{"slug":127,"name":128,"problem":129,"products":130},"endpoint-detection-response","Endpoint detection and response (EDR and XDR)","Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped.",[131,139,147],{"vendor_slug":132,"vendor_name":133,"vendor_logo":134,"product_slug":135,"product_name":136,"url":137,"description":138},"sophos","Sophos","\u002Fvendor-logos\u002Fsophos.png","sophos-endpoint","Sophos Endpoint","https:\u002F\u002Fwww.sophos.com\u002Fen-us\u002Fproducts\u002Fendpoint-security","Endpoint protection with Intercept X anti-ransomware technology and EDR.",{"vendor_slug":140,"vendor_name":141,"vendor_logo":142,"product_slug":143,"product_name":144,"url":145,"description":146},"bitdefender","Bitdefender","\u002Fvendor-logos\u002Fbitdefender.png","gravityzone","GravityZone","https:\u002F\u002Fwww.bitdefender.com\u002Fen-us\u002Fbusiness\u002Fgravityzone-platform\u002F","Endpoint protection, detection and response platform.",{"vendor_slug":148,"vendor_name":149,"vendor_logo":150,"product_slug":151,"product_name":152,"url":153,"description":154},"palo-alto-networks","Palo Alto Networks","\u002Fvendor-logos\u002Fpalo-alto-networks.png","cortex-xdr","Cortex XDR","https:\u002F\u002Fwww.paloaltonetworks.com\u002Fcortex\u002Fcortex-xdr","Endpoint detection and response with extended detection across network, cloud and identity.",[],{"slug":157,"title":158,"body":159,"framework_refs":160,"framework_notes":166},"leaked-credentials-expose-kubernetes-secrets-in-rackspace-spot-breach","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.",[161,162,163,164,165],"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)":167,"NIS2 Article 21(2)(j)":168,"CIS Control 6: Access Control Management":169,"NIST SP 800-53 SC-28: Protection of Information at Rest":170,"NIST CSF 2.0 PR.AA-05: Access permissions and authorizations":171},"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."]