[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fSKMsZmbvBOLzHSq-32oHQxVmWxo40-3NNdfuH4J_6rQ":3},{"article":4,"iocs":55,"watch_terms":56,"solutions":57,"lesson":145},{"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":32,"category":33,"article_tags":37},"4dbff3ed-0355-475c-a3f8-779984e6bb8b","AI company Fireworks says hackers stole data, billing info during October breaches","ai-company-fireworks-says-hackers-stole-data-billing-info-during-october-breache-266c19","Fireworks said the incident affected a “limited number of customer accounts” — all of whom were notified of the attack.","AI infrastructure company Fireworks experienced two data breaches in October, resulting in the theft of customer account and billing information, as well as AI-specific data. The first incident, discovered on October 6, was attributed to a financially motivated cybercriminal group. A second incident on October 23 involved a third-party cloud provider being attacked, which then led to unauthorized access to Fireworks' development machines and further customer data impact. Digital workspace company Notion confirmed some of its customers were impacted by the Fireworks breaches.","AI company Fireworks reports data and billing info stolen in two October breaches.","https:\u002F\u002Ftherecord.media\u002Fai-company-fireworks-says-hackers-stole-data-in-oct-attacks","http:\u002F\u002Fcms.therecord.media\u002Fuploads\u002Ffireworks_1_9c80b2da5e.jpg","2026-11-10T16:08:00+00:00","2026-11-10T17:00:21.893359+00:00",7,[17,20,23,25,27,29],{"name":18,"type":19},"Palo Alto Networks","vendor",{"name":21,"type":22},"Unit 42","product",{"name":24,"type":22},"Notion",{"name":26,"type":19},"Google",{"name":28,"type":22},"Mandiant",{"name":30,"type":31},"LLMJacking","technology","2e06f76c-d5b9-4f54-9eef-4d3447b10730",{"id":32,"icon":34,"name":35,"slug":36},null,"Breaches","breaches",[38,43,45,50],{"category":39},{"id":40,"icon":34,"name":41,"slug":42},"26b0b636-0e31-4db1-bffb-61bdf9f20a58","Supply Chain","supply-chain",{"category":44},{"id":32,"icon":34,"name":35,"slug":36},{"category":46},{"id":47,"icon":34,"name":48,"slug":49},"839da5c1-3c34-47e2-9499-f7201640e3ac","AI Security","ai-security",{"category":51},{"id":52,"icon":34,"name":53,"slug":54},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[],[18,26,21],{"controls":58,"vendors":141},[59,85,112],{"slug":60,"name":61,"problem":62,"products":63},"encryption-key-management","Encryption and key management","Stolen data stays unreadable, and the keys stay under your control.",[64,72,80],{"vendor_slug":65,"vendor_name":66,"vendor_logo":67,"product_slug":68,"product_name":69,"url":70,"description":71},"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.",{"vendor_slug":73,"vendor_name":74,"vendor_logo":75,"product_slug":76,"product_name":77,"url":78,"description":79},"thales","Thales","\u002Fvendor-logos\u002Fthales.png","luna-hsm","Thales Luna HSM","https:\u002F\u002Fcpl.thalesgroup.com\u002Fencryption\u002Fhardware-security-modules","Hardware security modules for protecting cryptographic keys.",{"vendor_slug":73,"vendor_name":74,"vendor_logo":75,"product_slug":81,"product_name":82,"url":83,"description":84},"ciphertrust","CipherTrust Data Security Platform","https:\u002F\u002Fcpl.thalesgroup.com\u002Fencryption\u002Fdata-security-platform","Data discovery, encryption and central key management across on-premises and cloud.",{"slug":86,"name":87,"problem":88,"products":89},"incident-response-retainer","Incident response retainer","Experts are on call before the worst day, not searched for during it.",[90,97,105],{"vendor_slug":91,"vendor_name":26,"vendor_logo":92,"product_slug":93,"product_name":94,"url":95,"description":96},"google","\u002Fvendor-logos\u002Fgoogle.png","mandiant-incident-response","Mandiant Incident Response","https:\u002F\u002Fcloud.google.com\u002Fsecurity\u002Fconsulting\u002Fmandiant-incident-response-services","Incident response services from Mandiant, available on retainer.",{"vendor_slug":98,"vendor_name":99,"vendor_logo":100,"product_slug":101,"product_name":102,"url":103,"description":104},"truesec","Truesec","\u002Fvendor-logos\u002Ftruesec.png","truesec-incident-response","Truesec Incident Response","https:\u002F\u002Fwww.truesec.com\u002Fservice\u002Fincident-response","Incident response team with a retainer option.",{"vendor_slug":106,"vendor_name":18,"vendor_logo":107,"product_slug":108,"product_name":109,"url":110,"description":111},"palo-alto-networks","\u002Fvendor-logos\u002Fpalo-alto-networks.png","unit-42-retainer","Unit 42 Retainer","https:\u002F\u002Fwww.paloaltonetworks.com\u002Funit42\u002Fretainer","Incident response retainer with Unit 42, including preparation services.",{"slug":113,"name":114,"problem":115,"products":116},"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.",[117,125,133],{"vendor_slug":118,"vendor_name":119,"vendor_logo":120,"product_slug":121,"product_name":122,"url":123,"description":124},"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":126,"vendor_name":127,"vendor_logo":128,"product_slug":129,"product_name":130,"url":131,"description":132},"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":134,"vendor_name":135,"vendor_logo":136,"product_slug":137,"product_name":138,"url":139,"description":140},"onetrust","OneTrust","\u002Fvendor-logos\u002Fonetrust.png","third-party-management","OneTrust Third-Party Management","https:\u002F\u002Fwww.onetrust.com\u002Fsolutions\u002Fthird-party-management\u002F","Supplier inventory, risk assessments and monitoring across privacy and security.",[142],{"slug":106,"name":18,"logo_path":107,"roles":143},[144],"reported_by",{"slug":146,"title":147,"body":148,"framework_refs":149,"framework_notes":155},"dual-breaches-at-fireworks-ai-expose-supply-chain-and-access-control-gaps","Dual Breaches at Fireworks AI Expose Supply Chain and Access Control Gaps","Fireworks AI suffered two separate data breaches in October, with the second stemming from an attack on a third-party cloud provider that cascaded into unauthorized access to Fireworks' own development machines and customer data. This illustrates a critical supply chain risk: an organization's security posture is only as strong as its least-secure vendor or partner. When third-party access is not tightly scoped, monitored, or segmented, attackers can pivot from a compromised supplier directly into a customer's core infrastructure. The theft of billing and AI-specific data amplifies the harm, as customers face both financial and intellectual property exposure.",[150,151,152,153,154],"NIS2 Article 21(2)(d)","ISO\u002FIEC 27001:2022 A.5.19: Information security in supplier relationships","CIS Control 15: Service Provider Management (v8)","NIST SP 800-53 AC-3: Access Enforcement","NIST CSF 2.0 GV.SC-04: Suppliers and third-party partners are routinely assessed",{"NIS2 Article 21(2)(d)":156,"NIST SP 800-53 AC-3: Access Enforcement":157,"CIS Control 15: Service Provider Management (v8)":158,"ISO\u002FIEC 27001:2022 A.5.19: Information security in supplier relationships":159,"NIST CSF 2.0 GV.SC-04: Suppliers and third-party partners are routinely assessed":160},"This point specifically requires organizations to manage security risks arising from supplier and third-party relationships, which is exactly the vector used in the second Fireworks breach.","This control requires that access to systems and data be enforced based on least-privilege principles, which would have limited the lateral movement from the compromised third-party cloud provider into Fireworks' development machines.","This control requires organizations to establish policies and procedures to evaluate, monitor, and limit the access and security posture of third-party service providers, directly addressing the third-party cloud pivot in this incident.","This control requires organizations to define and implement processes to manage information security risks associated with suppliers, which would have governed the security obligations of the third-party cloud provider involved.","This category explicitly calls for ongoing assessment of supplier and partner security practices, which could have identified the third-party cloud provider's weaknesses before they were exploited."]