Do you (yourself or by engaging an outside vendor) regularly scan critical systems for security vulnerabilities? These scans may include security and penetration testing.
This is application question 28 of 33 on the The Hartford Steam Boiler Inspection and Insurance Company 6952. It is a control question and reaches 17 controls. The wording is the carrier's, quoted verbatim.
Held from the HSB Total Cyber Cyber Risk Insurance Application (form 6952 REV 6/20) (read 2026-10-15), jurisdiction United States. All The Hartford Steam Boiler Inspection and Insurance Company questions.
Facets: control: Do you (yourself or by engaging an outside vendor) regularly scan critical systems for security vulnerabilities? These scans may include security and penetration testing.
What this question reaches
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities (direct)
Establishes that a vulnerability-scanning programme is conducted, with its scope and dated results; it does not establish patch management or that every finding was remediated within a stated window.
Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised - ISO 27001:2022 A.8.19: Installation of software on operational systems (supporting)
Establishes that a vulnerability-scanning programme is conducted, with its scope and dated results; it does not establish patch management or that every finding was remediated within a stated window.
Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised - ISO 27001:2022 A.8.29: Security testing in development and acceptance (supporting)
Establishes that a vulnerability-scanning programme is conducted, with its scope and dated results; it does not establish patch management or that every finding was remediated within a stated window.
Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised - SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities (direct)
Establishes that a vulnerability-scanning programme is conducted, with its scope and dated results; it does not establish patch management or that every finding was remediated within a stated window.
Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised - SOC 2 CC9.2: Assessing and managing vendor and business partner risk (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded (direct)
Establishes that a vulnerability-scanning programme is conducted, with its scope and dated results; it does not establish patch management or that every finding was remediated within a stated window.
Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised - NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk (supporting)
Establishes that a vulnerability-scanning programme is conducted, with its scope and dated results; it does not establish patch management or that every finding was remediated within a stated window.
Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised - ACSC Essential Eight PATCHAPP: Patch applications (supporting)
Establishes that a vulnerability-scanning programme is conducted, with its scope and dated results; it does not establish patch management or that every finding was remediated within a stated window.
Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised - ACSC Essential Eight PATCHOS: Patch operating systems (supporting)
Establishes that a vulnerability-scanning programme is conducted, with its scope and dated results; it does not establish patch management or that every finding was remediated within a stated window.
Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised - APRA CPS 234 para 16: Assess the security capability of related and third parties (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - APRA CPS 234 para 22: Evaluate the design of third-party controls (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - APRA CPS 234 para 28: Assess reliance on third-party control testing (supporting)
Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review - CIS Controls v8 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets (direct)
Establishes that a vulnerability-scanning programme is conducted, with its scope and dated results; it does not establish patch management or that every finding was remediated within a stated window.
Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised - CIS Controls v8 7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets (supporting)
Establishes that a vulnerability-scanning programme is conducted, with its scope and dated results; it does not establish patch management or that every finding was remediated within a stated window.
Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised - CIS Controls v8 7.1: Establish and Maintain a Vulnerability Management Process (supporting)
Establishes that a vulnerability-scanning programme is conducted, with its scope and dated results; it does not establish patch management or that every finding was remediated within a stated window.
Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised - PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly (supporting)
Establishes that a vulnerability-scanning programme is conducted, with its scope and dated results; it does not establish patch management or that every finding was remediated within a stated window.
Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised - PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software (supporting)
Establishes that a vulnerability-scanning programme is conducted, with its scope and dated results; it does not establish patch management or that every finding was remediated within a stated window.
Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised
Subject: patching. Owner a broker routes it to: IT endpoint and vulnerability owner.
The same control on other applications
CFC Underwriting Q8, CFC Underwriting Q9, CFC Underwriting Q10, Beazley Q9, Hiscox Q23, Great American Insurance Group Q12, Great American Insurance Group Q23, Great American Insurance Group Q24, Great American Insurance Group Q25, AXIS Insurance Q29, AXIS Insurance Q32, AXIS Insurance Q35.
Map your own answers in the tool. See the The Hartford Steam Boiler Inspection and Insurance Company page, the controls index, the island and the answers.