[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fkuWzLfLhw6ZbOVID84hG3PvpDlErSySHm9RgwNZpfSo":3},{"article":4,"iocs":49,"watch_terms":50,"solutions":51,"lesson":140},{"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":26,"category":27,"article_tags":31},"51b82c79-f26b-42cf-88b1-867f3d4f65c7","BAE Systems Security Incident Stalls Notices From US Bankruptcy Courts","bae-systems-security-incident-stalls-notices-from-us-bankruptcy-courts-58cf5a","A cyber incident affecting contractor BAE Systems has knocked out the Bankruptcy Noticing Center, halting notices nationwide for a week. The post BAE Systems Security Incident Stalls Notices From US Bankruptcy Courts appeared first on SecurityWeek.","A cybersecurity incident affecting BAE Systems' infrastructure has caused a nationwide outage of the Bankruptcy Noticing Center (BNC), halting all bankruptcy court notices for over a week. The BNC, managed by BAE as a contractor for the US judiciary, is responsible for sending notices to all federal bankruptcy courts. The incident has disrupted services including the National Creditor Registration Service, preventing users from generating creditor mailing lists. The cause and data compromise status remain unknown.","BAE Systems cyber incident halts US bankruptcy court notices nationwide.","https:\u002F\u002Fwww.securityweek.com\u002Fbae-systems-security-incident-stalls-notices-from-us-bankruptcy-courts\u002F","https:\u002F\u002Fwww.securityweek.com\u002Fwp-content\u002Fuploads\u002F2023\u002F04\u002Flaw-court-order-lawsuit-e1782819788980.jpg","2026-10-16T11:46:40+00:00","2026-10-16T12:00:17.901823+00:00",7,[17,20,23],{"name":18,"type":19},"BAE Systems","vendor",{"name":21,"type":22},"Bankruptcy Noticing Center","product",{"name":24,"type":25},"National Creditor Registration Service","technology","2e06f76c-d5b9-4f54-9eef-4d3447b10730",{"id":26,"icon":28,"name":29,"slug":30},null,"Breaches","breaches",[32,34,39,44],{"category":33},{"id":26,"icon":28,"name":29,"slug":30},{"category":35},{"id":36,"icon":28,"name":37,"slug":38},"6cbdd207-aaa1-4176-9534-e156b125e917","Nation-state","nation-state",{"category":40},{"id":41,"icon":28,"name":42,"slug":43},"c5c77cdb-f7d7-4990-9436-c81dcbff1163","Policy","policy",{"category":45},{"id":46,"icon":28,"name":47,"slug":48},"c5eccf7c-abbc-4bd3-bbed-e6da5cba8e73","Incident Response","incident-response",[],[18,21],{"controls":52,"vendors":139},[53,82,111],{"slug":54,"name":55,"problem":56,"products":57},"security-monitoring-siem","Security monitoring (SIEM)","Logs from everywhere end up in one place, with alerts that someone actually sees.",[58,66,74],{"vendor_slug":59,"vendor_name":60,"vendor_logo":61,"product_slug":62,"product_name":63,"url":64,"description":65},"abstract-security","Abstract Security","\u002Fvendor-logos\u002Fabstract-security.png","abstract-composable-siem","Abstract Composable SIEM","https:\u002F\u002Fwww.abstract.security\u002Fplatform","SIEM built from separate parts for collection, AI-assisted detection and tiered retention, which can be adopted one at a time.",{"vendor_slug":67,"vendor_name":68,"vendor_logo":69,"product_slug":70,"product_name":71,"url":72,"description":73},"elastic","Elastic","\u002Fvendor-logos\u002Felastic.png","elastic-security","Elastic Security","https:\u002F\u002Fwww.elastic.co\u002Fsecurity","SIEM and endpoint security built on Elasticsearch, with open detection rules.",{"vendor_slug":75,"vendor_name":76,"vendor_logo":77,"product_slug":78,"product_name":79,"url":80,"description":81},"splunk","Splunk","\u002Fvendor-logos\u002Fsplunk.png","enterprise-security","Splunk Enterprise Security","https:\u002F\u002Fwww.splunk.com\u002Fen_us\u002Fproducts\u002Fenterprise-security.html","SIEM for detection, investigation and response, on premises or in the cloud.",{"slug":83,"name":84,"problem":85,"products":86},"immutable-backup","Immutable backup and recovery","Ransomware cannot delete or encrypt your way back.",[87,95,103],{"vendor_slug":88,"vendor_name":89,"vendor_logo":90,"product_slug":91,"product_name":92,"url":93,"description":94},"commvault","Commvault","\u002Fvendor-logos\u002Fcommvault.png","commvault-cloud","Commvault Cloud","https:\u002F\u002Fwww.commvault.com\u002Fplatform","Backup and recovery platform with immutable storage and recovery testing.",{"vendor_slug":96,"vendor_name":97,"vendor_logo":98,"product_slug":99,"product_name":100,"url":101,"description":102},"rubrik","Rubrik","\u002Fvendor-logos\u002Frubrik.png","zero-trust-data-protection","Rubrik Zero Trust Data Protection","https:\u002F\u002Fwww.rubrik.com\u002Fproducts\u002Fdata-protection","Air-gapped, immutable backup for on-premises, cloud and SaaS data, with threat detection in backups and orchestrated recovery.",{"vendor_slug":104,"vendor_name":105,"vendor_logo":106,"product_slug":107,"product_name":108,"url":109,"description":110},"veeam","Veeam","\u002Fvendor-logos\u002Fveeam.png","veeam-data-platform","Veeam Data Platform","https:\u002F\u002Fwww.veeam.com\u002Fproducts\u002Fveeam-data-platform.html","Backup and recovery for virtual, physical, cloud and SaaS workloads, with immutable storage options.",{"slug":112,"name":113,"problem":114,"products":115},"incident-response-retainer","Incident response retainer","Experts are on call before the worst day, not searched for during it.",[116,124,131],{"vendor_slug":117,"vendor_name":118,"vendor_logo":119,"product_slug":120,"product_name":121,"url":122,"description":123},"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":125,"vendor_name":126,"vendor_logo":127,"product_slug":48,"product_name":128,"url":129,"description":130},"crowdstrike","CrowdStrike","\u002Fvendor-logos\u002Fcrowdstrike.png","CrowdStrike Incident Response","https:\u002F\u002Fwww.crowdstrike.com\u002Fen-us\u002Fservices\u002Fincident-response\u002F","Incident response services, available on retainer.",{"vendor_slug":132,"vendor_name":133,"vendor_logo":134,"product_slug":135,"product_name":136,"url":137,"description":138},"google","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.",[],{"slug":141,"title":142,"body":143,"framework_refs":144,"framework_notes":155},"bae-systems-contractor-incident-cripples-us-bankruptcy-court-notifications","BAE Systems Contractor Incident Cripples US Bankruptcy Court Notifications","A cybersecurity incident at BAE Systems, a third-party contractor managing critical US judiciary infrastructure, caused a nationwide outage of the Bankruptcy Noticing Center for over a week. This incident highlights the systemic risk of outsourcing mission-critical government services to external vendors without robust continuity safeguards. When a contractor's systems fail — whether from a breach, ransomware, or misconfiguration — the downstream impact can halt essential public services with no clear recovery timeline. The fact that the cause and data compromise status remain unknown after more than a week underscores serious gaps in incident detection, communication, and response planning. Government agencies must treat third-party contractors as an extension of their own risk surface.",[145,146,147,148,149,150,151,152,153,154],"NIST SP 800-161 (Supply Chain Risk Management)","NIST IR-6 (Incident Reporting)","NIST CP-2 (Contingency Plan)","CIS Control 15 (Service Provider Management)","CIS Control 17 (Incident Response Management)","NIST SP 800-53 SA-9 (External Information System Services)","FedRAMP Third-Party Authorization Requirements","FISMA Section 3554 (Agency Responsibilities)","ITIL Service Continuity Management","ISO\u002FIEC 27036 (Supplier Relationships)",{"NIST CP-2 (Contingency Plan)":156,"NIST IR-6 (Incident Reporting)":157,"ITIL Service Continuity Management":158,"ISO\u002FIEC 27036 (Supplier Relationships)":159,"CIS Control 15 (Service Provider Management)":160,"FISMA Section 3554 (Agency Responsibilities)":161,"CIS Control 17 (Incident Response Management)":162,"FedRAMP Third-Party Authorization Requirements":163,"NIST SP 800-161 (Supply Chain Risk Management)":164,"NIST SP 800-53 SA-9 (External Information System Services)":165},"Contingency planning helps keep bankruptcy notices flowing when a contractor goes down.","Incident reporting requirements ensure contractors tell agencies quickly about incidents.","Service continuity management helps maintain critical services during supplier incidents.","Supplier relationship guidance covers managing risks of outsourced services.","Service provider management sets security and resilience requirements for contractors.","Requires agencies to ensure security of systems operated by contractors.","Incident response plans should cover third-party outages.","Third-party authorisation requirements set security standards for cloud services used by agencies.","Supply chain risk management covers assessing contractors like BAE Systems running critical services.","Requires oversight of external services, including contractor-run notification systems."]