When did the Applicant last have a comprehensive (i.e. inclusive of vulnerability scanning and penetration testing) network security assessment completed?
This is application question 23 of 43 on the Great American Insurance Group F.37009. It is a control question and reaches 14 controls. The wording is the carrier's, quoted verbatim.
Held from the Risk E-Business Cyber Loss and Liability Insurance Policy Application (read 2026-10-11), jurisdiction United States. All Great American Insurance Group questions.
Facets: control: When did the Applicant last have a comprehensive (i.e. inclusive of vulnerability scanning and penetration testing) network security assessment completed?
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 CC6.6: Protection against threats from outside the system boundary (supporting)
Establishes the network control asked about; it does not establish the full architecture or that no path bypasses it.
Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path - 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 - 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 Q24, Great American Insurance Group Q25, AXIS Insurance Q29, AXIS Insurance Q32, AXIS Insurance Q35, AXIS Insurance Q79.
Map your own answers in the tool. See the Great American Insurance Group page, the controls index, the island and the answers.