Do you conduct security tests or code analysis during system development, before go-live and after N/A Yes No system changes take place?
This is application question 80 of 121 on the Munich Re MRS Insurance Application Cyber Risk. It is a control question and reaches 14 controls. The wording is the carrier's, quoted verbatim.
Held from the Insurance Application - Cyber Risk (UK) (read 2026-10-11), jurisdiction United Kingdom. All Munich Re questions.
Facets: control: Do you conduct security tests or code analysis during system development, before go-live and after N/A Yes No system changes take place?
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 CC8.1: Managing changes to procedures, software, data and infrastructure (supporting)
Establishes the development or change control asked about; it does not establish the security of every release.
Evidence to have on file: the secure-development standard and the checks a change goes through before release; a sample of a code review or security test for a recent release - 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 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 Munich Re page, the controls index, the island and the answers.