[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fGWivknNqT5q7M9QWvklOnOiGDoOuck7XYB56v2GblyE":3},{"article":4,"iocs":41,"watch_terms":42,"solutions":43,"lesson":132},{"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":23,"category":24,"article_tags":28},"b6f37ce1-88e7-4cf9-b006-d7beeaa7409d","Quest Diagnostics confirms data breach exposed patient records","quest-diagnostics-confirms-data-breach-exposed-patient-records-5d9f1f","American clinical laboratory company Quest Diagnostics disclosed that patient records have been exposed after a threat actor gained unauthorized access to its Quanum LSM system. [...]","Quest Diagnostics has disclosed a data breach affecting its Quanum LSM system, which is used by clients to place test orders and receive results. The company learned of the unauthorized access on October 21, 2026, and has launched an incident response protocol. While the full scope is still under investigation, patient records are believed to have been exposed, though the specific data types are yet to be determined. The incident has not disrupted customer-facing operations, but access to other systems has been temporarily paused.","Quest Diagnostics confirms patient records exposed after threat actor accessed Quanum LSM system.","https:\u002F\u002Fwww.bleepingcomputer.com\u002Fnews\u002Fsecurity\u002Fquest-diagnostics-confirms-data-breach-exposed-patient-records\u002F","https:\u002F\u002Fwww.bleepstatic.com\u002Fcontent\u002Fhl-images\u002F2026\u002F10\u002F23\u002Fquest.jpg","2026-10-23T16:40:07+00:00","2026-10-23T17:00:11.842896+00:00",8,[17,20],{"name":18,"type":19},"Quanum LSM","product",{"name":21,"type":22},"Quest Diagnostics","vendor","2e06f76c-d5b9-4f54-9eef-4d3447b10730",{"id":23,"icon":25,"name":26,"slug":27},null,"Breaches","breaches",[29,31,36],{"category":30},{"id":23,"icon":25,"name":26,"slug":27},{"category":32},{"id":33,"icon":25,"name":34,"slug":35},"c5c77cdb-f7d7-4990-9436-c81dcbff1163","Policy","policy",{"category":37},{"id":38,"icon":25,"name":39,"slug":40},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[],[21,18],{"controls":44,"vendors":131},[45,74,102],{"slug":46,"name":47,"problem":48,"products":49},"identity-threat-detection","Identity threat detection and response (ITDR)","Attackers who log in with real, stolen credentials get noticed.",[50,58,66],{"vendor_slug":51,"vendor_name":52,"vendor_logo":53,"product_slug":54,"product_name":55,"url":56,"description":57},"okta","Okta","\u002Fvendor-logos\u002Fokta.png","identity-threat-protection","Okta Identity Threat Protection","https:\u002F\u002Fwww.okta.com\u002Fproducts\u002Fidentity-threat-protection\u002F","Continuous risk assessment of sessions after login, with automatic actions such as ending sessions.",{"vendor_slug":59,"vendor_name":60,"vendor_logo":61,"product_slug":62,"product_name":63,"url":64,"description":65},"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":67,"vendor_name":68,"vendor_logo":69,"product_slug":70,"product_name":71,"url":72,"description":73},"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.",{"slug":75,"name":76,"problem":77,"products":78},"asset-inventory","Cyber asset inventory","You cannot patch, monitor or protect the devices, cloud resources and accounts you do not know you have.",[79,87,95],{"vendor_slug":80,"vendor_name":81,"vendor_logo":82,"product_slug":83,"product_name":84,"url":85,"description":86},"runzero","runZero","\u002Fvendor-logos\u002Frunzero.png","runzero-platform","runZero Platform","https:\u002F\u002Fwww.runzero.com\u002Fplatform\u002F","Finds and fingerprints everything on the network and in the cloud, including IoT and OT devices, without agents or credentials, and flags exposures.",{"vendor_slug":88,"vendor_name":89,"vendor_logo":90,"product_slug":91,"product_name":92,"url":93,"description":94},"axonius","Axonius","\u002Fvendor-logos\u002Faxonius.png","axonius-cyber-assets","Axonius Cyber Assets","https:\u002F\u002Fwww.axonius.com\u002Fplatform\u002Fcyber-assets","A continuously reconciled view of every asset, who owns it, which security controls cover it and where it drifts from policy.",{"vendor_slug":96,"vendor_name":97,"vendor_logo":98,"product_slug":99,"product_name":97,"url":100,"description":101},"lansweeper","Lansweeper","\u002Fvendor-logos\u002Flansweeper.png","lansweeper-asset-inventory","https:\u002F\u002Fwww.lansweeper.com\u002Fproduct\u002Fasset-inventory\u002F","Discovery with and without agents that keeps one central, always-updated inventory of devices, software and their details.",{"slug":103,"name":104,"problem":105,"products":106},"incident-response-retainer","Incident response retainer","Experts are on call before the worst day, not searched for during it.",[107,115,123],{"vendor_slug":108,"vendor_name":109,"vendor_logo":110,"product_slug":111,"product_name":112,"url":113,"description":114},"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.",{"vendor_slug":116,"vendor_name":117,"vendor_logo":118,"product_slug":119,"product_name":120,"url":121,"description":122},"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":124,"vendor_name":125,"vendor_logo":126,"product_slug":127,"product_name":128,"url":129,"description":130},"palo-alto-networks","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":133,"title":134,"body":135,"framework_refs":136,"framework_notes":144},"quest-diagnostics-breach-exposes-patient-records-via-quanum-lsm-system","Quest Diagnostics Breach Exposes Patient Records via Quanum LSM System","Quest Diagnostics suffered unauthorized access to its Quanum LSM system, a platform handling sensitive patient test orders and results, exposing an undetermined scope of patient health records. The breach highlights the critical risk of inadequate access controls and monitoring on systems that store protected health information (PHI). Healthcare organizations are high-value targets precisely because patient data commands a premium on the black market and carries heavy regulatory obligations. The temporary suspension of access to other systems suggests the attacker may have had broader lateral movement potential, underlining the importance of network segmentation and least-privilege access principles.",[137,138,139,140,141,142,143],"NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control","CIS Control 17: Incident Response Management","NIST SP 800-53 SI-2: Flaw Remediation","GDPR Article 32","ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities","CIS Control 7: Continuous Vulnerability Management","NIS2 Article 21(2)(b)",{"GDPR Article 32":145,"NIS2 Article 21(2)(b)":146,"NIST SP 800-53 SI-2: Flaw Remediation":147,"CIS Control 17: Incident Response Management":148,"CIS Control 7: Continuous Vulnerability Management":149,"ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities":150,"NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control":151},"Article 32 requires appropriate technical measures to ensure a level of security appropriate to the risk, including encryption and access controls that would have protected the patient records exposed in this breach.","NIS2 mandates incident handling policies for operators of essential services; Quest's delayed understanding of the breach scope indicates gaps in monitoring and response capabilities that this article directly addresses.","If the breach stemmed from an unpatched vulnerability in the Quanum LSM platform, a disciplined flaw remediation process would have ensured timely patching to close the attack vector.","Quest launched an incident response protocol after discovery, but a pre-established, rehearsed IR plan would have accelerated containment, reduced exposure duration, and guided timely patient notification.","Regular vulnerability scanning and remediation of internet-facing or client-accessible systems like Quanum LSM would have identified and addressed exploitable weaknesses before attackers could leverage them.","This control requires organizations to identify, assess, and remediate technical vulnerabilities in a timely manner, which would have reduced the attack surface on the Quanum LSM system.","Unauthorized access to the Quanum LSM system suggests insufficient identity verification and access controls; enforcing MFA and least-privilege would have limited or prevented the attacker's entry."]