[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fU0FuZUxNix80Y--ar20vy78wg7oyakQDxmrDRqok-_4":3},{"article":4,"iocs":54,"iocs_total":58,"watch_terms":59,"solutions":60,"lesson":147},{"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":31,"category":32,"article_tags":36},"68dac357-42b3-4b1f-b1d3-b555cb4740c4","Vendor data breach exposes Chase, Visa, Mastercard customer info","vendor-data-breach-exposes-chase-visa-mastercard-customer-info-c3a9fb","J.P. Morgan Chase warned it suffered a data breach after a cyberattack at a third-party service provider exposed customers' personal information and marketing data. [...]","J.P. Morgan Chase, Visa, and Mastercard have reported data breaches stemming from a cyberattack on a third-party service provider, Qubole. The n0n ransomware group claimed responsibility, alleging they accessed customer marketing data, including names and email addresses, and stole 53.9 GB of data from Qubole. The attackers reportedly used compromised Qubole credentials to access customer AWS environments via IAM roles.","Third-party vendor breach exposes customer data from Chase, Visa, and Mastercard.","https:\u002F\u002Fwww.bleepingcomputer.com\u002Fnews\u002Fsecurity\u002Fvendor-data-breach-exposes-chase-visa-mastercard-customer-info\u002F","https:\u002F\u002Fwww.bleepstatic.com\u002Fcontent\u002Fhl-images\u002F2022\u002F10\u002F28\u002Fhand-sifting-data.jpg","2026-11-20T15:58:06+00:00","2026-11-20T16:00:14.247153+00:00",8,[17,20,22,24,26,28],{"name":18,"type":19},"J.P. Morgan Chase","vendor",{"name":21,"type":19},"Visa",{"name":23,"type":19},"Mastercard",{"name":25,"type":19},"Qubole",{"name":27,"type":19},"Idera",{"name":29,"type":30},"n0n ransomware","threat_actor","2e06f76c-d5b9-4f54-9eef-4d3447b10730",{"id":31,"icon":33,"name":34,"slug":35},null,"Breaches","breaches",[37,42,44,49],{"category":38},{"id":39,"icon":33,"name":40,"slug":41},"26b0b636-0e31-4db1-bffb-61bdf9f20a58","Supply Chain","supply-chain",{"category":43},{"id":31,"icon":33,"name":34,"slug":35},{"category":45},{"id":46,"icon":33,"name":47,"slug":48},"7d8b5ab8-ea0b-4ced-ae97-ec251b86993a","Ransomware","ransomware",{"category":50},{"id":51,"icon":33,"name":52,"slug":53},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[55],{"type":56,"value":29,"context":57},"malware","Group claiming responsibility for the attack on Qubole.",1,[18,21,23],{"controls":61,"vendors":146},[62,91,117],{"slug":63,"name":64,"problem":65,"products":66},"identity-threat-detection","Identity threat detection and response (ITDR)","Attackers who log in with real, stolen credentials get noticed.",[67,75,83],{"vendor_slug":68,"vendor_name":69,"vendor_logo":70,"product_slug":71,"product_name":72,"url":73,"description":74},"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":76,"vendor_name":77,"vendor_logo":78,"product_slug":79,"product_name":80,"url":81,"description":82},"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":84,"vendor_name":85,"vendor_logo":86,"product_slug":87,"product_name":88,"url":89,"description":90},"vectra-ai","Vectra AI","\u002Fvendor-logos\u002Fvectra-ai.png","vectra-ai-platform","Vectra AI Platform","https:\u002F\u002Fwww.vectra.ai\u002Fplatform","Detection of attacker behaviour across network, identity and cloud.",{"slug":92,"name":93,"problem":94,"products":95},"cloud-security-posture","Cloud security posture management (CSPM and CNAPP)","Misconfigured cloud storage and over-permissive roles get caught before they leak.",[96,104,112],{"vendor_slug":97,"vendor_name":98,"vendor_logo":99,"product_slug":100,"product_name":101,"url":102,"description":103},"crowdstrike","CrowdStrike","\u002Fvendor-logos\u002Fcrowdstrike.png","falcon-cloud-security","Falcon Cloud Security","https:\u002F\u002Fwww.crowdstrike.com\u002Fen-us\u002Fplatform\u002Fcloud-security\u002F","Cloud posture management and workload protection.",{"vendor_slug":105,"vendor_name":106,"vendor_logo":107,"product_slug":108,"product_name":109,"url":110,"description":111},"palo-alto-networks","Palo Alto Networks","\u002Fvendor-logos\u002Fpalo-alto-networks.png","cortex-cloud","Cortex Cloud","https:\u002F\u002Fwww.paloaltonetworks.com\u002Fcortex\u002Fcloud","Cloud security platform covering posture management and runtime protection.",{"vendor_slug":68,"vendor_name":69,"vendor_logo":70,"product_slug":113,"product_name":114,"url":115,"description":116},"defender-for-cloud","Microsoft Defender for Cloud","https:\u002F\u002Fwww.microsoft.com\u002Fen-us\u002Fsecurity\u002Fbusiness\u002Fcloud-security\u002Fmicrosoft-defender-cloud","Cloud posture management and workload protection for Azure, AWS and Google Cloud.",{"slug":118,"name":119,"problem":120,"products":121},"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.",[122,130,138],{"vendor_slug":123,"vendor_name":124,"vendor_logo":125,"product_slug":126,"product_name":127,"url":128,"description":129},"upguard","UpGuard","\u002Fvendor-logos\u002Fupguard.png","upguard-vendor-risk","UpGuard Vendor Risk","https:\u002F\u002Fwww.upguard.com\u002Fproduct\u002Fvendor-risk","Supplier security questionnaires, ratings and continuous monitoring.",{"vendor_slug":131,"vendor_name":132,"vendor_logo":133,"product_slug":134,"product_name":135,"url":136,"description":137},"securityscorecard","SecurityScorecard","\u002Fvendor-logos\u002Fsecurityscorecard.png","security-ratings","SecurityScorecard Ratings","https:\u002F\u002Fsecurityscorecard.com\u002Fsolutions\u002Fuse-cases\u002Fsecurity-ratings\u002F","Outside-in security ratings and monitoring of suppliers.",{"vendor_slug":139,"vendor_name":140,"vendor_logo":141,"product_slug":142,"product_name":143,"url":144,"description":145},"bitsight","Bitsight","\u002Fvendor-logos\u002Fbitsight.png","bitsight-tprm","Bitsight Third-Party Risk Management","https:\u002F\u002Fwww.bitsight.com\u002Fproducts\u002Fthird-party-risk-management","Supplier assessments and continuous monitoring based on security ratings.",[],{"slug":148,"title":149,"body":150,"framework_refs":151,"framework_notes":157},"third-party-vendor-breach-exposes-major-financial-institutions-via-compromised-iam-credentials","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.",[152,153,154,155,156],"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)":158,"NIST SP 800-53 AC-6: Least Privilege":159,"CIS Control 6: Access Control Management":160,"NIST SP 800-53 SA-9: External System Services":161,"ISO\u002FIEC 27001:2022 A.5.19: Information security in supplier relationships":162},"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."]