Does the applicant proactively address system vulnerabilities, including regular updates to anti-virus/malware protection and critical security patches?
This is application question 11 of 31 on the USLI Cyber APP 11/16. It is a control question and reaches 14 controls. The wording is the carrier's, quoted verbatim.
Held from the Cyber Liability and Data Security + application (form Cyber APP 11/16) (read 2026-10-15), jurisdiction United States. All USLI questions.
Priority underwriting question: a "no" here is a subject a cyber underwriter weighs most. A carrier may still accept a compensating-controls explanation, so it is not a binary decline.
Facets: control: Does the applicant proactively address system vulnerabilities, including regular updates to anti-virus/malware protection and critical security patches?
What this question reaches
- ISO 27001:2022 A.8.7: Protection against malware (direct)
Establishes the endpoint or malware control the question names; it does not establish coverage of every endpoint or that the tool was effective in an incident.
Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling - ISO 27001:2022 A.8.1: User end point devices (supporting)
Establishes the endpoint or malware control the question names; it does not establish coverage of every endpoint or that the tool was effective in an incident.
Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling - ISO 27001:2022 A.8.8: Management of technical vulnerabilities (supporting)
Establishes the patching or vulnerability practice asked about; it does not establish that every critical asset was patched within the stated window.
Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window - SOC 2 CC6.8: Preventing and detecting unauthorised or malicious software (direct)
Establishes the endpoint or malware control the question names; it does not establish coverage of every endpoint or that the tool was effective in an incident.
Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling - SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities (supporting)
Establishes the patching or vulnerability practice asked about; it does not establish that every critical asset was patched within the stated window.
Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window - NIST CSF 2.0 PR.PS-05: Installation and execution of unauthorized software are prevented (direct)
Establishes the endpoint or malware control the question names; it does not establish coverage of every endpoint or that the tool was effective in an incident.
Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling - NIST CSF 2.0 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events (supporting)
Establishes the endpoint or malware control the question names; it does not establish coverage of every endpoint or that the tool was effective in an incident.
Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling - ACSC Essential Eight PATCHAPP: Patch applications (supporting)
Establishes the patching or vulnerability practice asked about; it does not establish that every critical asset was patched within the stated window.
Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window - ACSC Essential Eight PATCHOS: Patch operating systems (supporting)
Establishes the patching or vulnerability practice asked about; it does not establish that every critical asset was patched within the stated window.
Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window - CIS Controls v8 7.3: Perform Automated Operating System Patch Management (supporting)
Establishes the patching or vulnerability practice asked about; it does not establish that every critical asset was patched within the stated window.
Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window - CIS Controls v8 7.4: Perform Automated Application Patch Management (supporting)
Establishes the patching or vulnerability practice asked about; it does not establish that every critical asset was patched within the stated window.
Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window - CIS Controls v8 7.7: Remediate Detected Vulnerabilities (supporting)
Establishes the patching or vulnerability practice asked about; it does not establish that every critical asset was patched within the stated window.
Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window - PCI DSS 4.0 Requirement 5: Protect All Systems and Networks from Malicious Software (supporting)
Establishes the endpoint or malware control the question names; it does not establish coverage of every endpoint or that the tool was effective in an incident.
Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling - PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software (supporting)
Establishes the patching or vulnerability practice asked about; it does not establish that every critical asset was patched within the stated window.
Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window
Subject: endpoint_edr. Owner a broker routes it to: IT endpoint and vulnerability owner.
The same control on other applications
Chubb Q7, Beazley Q5, Beazley Q6, Beazley Q7, Beazley Q10, Beazley Q11, Beazley Q19, Hiscox Q22, Great American Insurance Group Q15, Tokio Marine HCC Q4, Tokio Marine HCC Q19, Tokio Marine HCC Q20.
Map your own answers in the tool. See the USLI page, the controls index, the island and the answers.