Does the Company have in place procedures to identify and detect network security weaknesses?
This is application question 11 of 79 on the AIG AIG CyberEdge Proposal Form (FullForm 0413), CyberEdge Proposal Form (Hong Kong 2012) and Cyber Insurance Application Form (group revenue up to 500M). It is a control question and reaches 14 controls. The wording is the carrier's, quoted verbatim.
Held from the AIG CyberEdge Insurance Proposal Form (Asia Pacific, form 0413) and CyberEdge Proposal Form (Hong Kong, 2012) and Cyber Insurance Application Form (group revenue up to 500M) (read 2026-10-12), jurisdiction Singapore, Hong Kong and the United Kingdom and Europe. All AIG questions.
Facets: control: Does the Company have in place procedures to identify and detect network security weaknesses?
What this question reaches
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities (direct)
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 - ISO 27001:2022 A.8.19: Installation of software on operational 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 - ISO 27001:2022 A.8.29: Security testing in development and acceptance (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 CC7.1: Detecting configuration changes and new vulnerabilities (direct)
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.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 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-02: Software is maintained, replaced, and removed commensurate with risk (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 PATCHAPP: Patch applications (direct)
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 (direct)
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 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 - PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly (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: 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 AIG page, the controls index, the island and the answers.