[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fxxepqeKwedO_Uj9dKfyn2ev9UvbiWlTSbD8SKzpqAyw":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},"34c56244-b863-4e0f-9488-36dc16563917","third-party-vendor-breach-exposes-major-financial-institutions-via-compromised-iam-credentials","68dac357-42b3-4b1f-b1d3-b555cb4740c4","Third-Party Vendor Breach Exposes Major Financial Institutions via Compromised IAM Credentials","The breach at Qubole demonstrates how a single compromised third-party vendor can cascade into exposure for multiple high-profile clients, in this case Chase, Visa, and Mastercard. Attackers leveraged stolen Qubole credentials to pivot into customer AWS environments through IAM role trust relationships, effectively using legitimate access pathways as an attack vector. This highlights a critical gap in third-party risk management: vendors with broad cloud access permissions represent a significant inherited risk surface. Financial institutions cannot outsource accountability for customer data, even when that data resides in a vendor-managed environment.","**Immediate actions:**\n- Revoke and rotate all IAM roles and credentials associated with Qubole or any other third-party vendor with access to your AWS environments.\n- Audit all third-party IAM role trust policies to enforce least-privilege access and remove unnecessary cross-account permissions.\n- Enable AWS CloudTrail and GuardDuty to detect anomalous IAM role usage and unauthorized lateral movement in affected environments.\n\n**Long-term improvements:**\n- Establish a formal third-party risk management program requiring vendors to meet minimum security standards before being granted cloud environment access.\n- Implement just-in-time (JIT) access provisioning for vendor IAM roles so credentials are only active during approved, time-bounded sessions.\n- Require contractual obligations for vendors to report credential compromises or security incidents within a defined SLA window.\n\n**Detection measures:**\n- Deploy continuous monitoring of all IAM role assumption events across AWS accounts linked to third-party vendors.\n- Conduct periodic access reviews of all vendor-held credentials and IAM permissions to detect privilege creep or stale accounts.",[12,13,14,15,16],"NIST SP 800-53 SA-9: External System Services","NIST SP 800-53 AC-6: Least Privilege","CIS Control 6: Access Control Management","NIS2 Article 21(2)(d)","ISO\u002FIEC 27001:2022 A.5.19: Information security in supplier relationships",{"NIS2 Article 21(2)(d)":18,"NIST SP 800-53 AC-6: Least Privilege":19,"CIS Control 6: Access Control Management":20,"NIST SP 800-53 SA-9: External System Services":21,"ISO\u002FIEC 27001:2022 A.5.19: Information security in supplier relationships":22},"NIS2 Article 21(2)(d) explicitly requires security measures addressing supply chain risks, including the security of relationships with direct suppliers, which applies directly to the unvetted trust placed in Qubole's access to customer cloud environments.","AC-6 mandates that access rights be limited to the minimum necessary; enforcing least-privilege IAM roles for Qubole would have restricted the blast radius when their credentials were compromised.","CIS Control 6 calls for managing and limiting access credentials, including third-party accounts, which would have prevented the compromised Qubole credentials from being used to assume powerful IAM roles in customer AWS environments.","SA-9 requires organizations to define and enforce security requirements for third-party providers and monitor their compliance, which would have surfaced Qubole's excessive IAM permissions and inadequate credential protections before the breach.","A.5.19 requires that agreed information security controls be implemented and maintained across supplier relationships, meaning Qubole's credential hygiene and cloud access scope should have been contractually governed and audited.","published","2026-11-20T16:20:24.23247+00:00","2026-11-20T16:20:24.197+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fwww.bleepingcomputer.com\u002Fnews\u002Fsecurity\u002Fvendor-data-breach-exposes-chase-visa-mastercard-customer-info\u002F","vendor-data-breach-exposes-chase-visa-mastercard-customer-info-c3a9fb","Vendor data breach exposes Chase, Visa, Mastercard customer info",[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},"f0c2a0af-58aa-4128-87c9-6acd30f2dc48","Supply Chain","supply-chain","Third-party risk, compromised dependencies","#8b5cf6",[44],{"id":45,"date":46,"edition":47,"title":48,"audio_url":49},"779bd2ab-1c69-4627-9085-156837e3055c","2026-11-21","morning","ThreatNoir Weekend Brief — November 21","https:\u002F\u002Fcdn.threatnoir.com\u002Fpodcasts\u002F2026-11-21\u002Fthreatnoir-morning-brief-2026-11-21.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},"cloud-security-posture","Cloud security posture management (CSPM and CNAPP)","Misconfigured cloud storage and over-permissive roles get caught before they leak.",{"slug":60,"name":61,"problem":62},"third-party-risk-management","Third-party risk management (TPRM)","You know which suppliers could hurt you, and you hear quickly when one of them is breached."]