Do you have a secure coding baseline in place (e.g. peer reviews & maintenance requirements?
This is application question 78 of 121 on the Munich Re MRS Insurance Application Cyber Risk. It is a control question and reaches 8 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 have a secure coding baseline in place (e.g. peer reviews & maintenance requirements?
What this question reaches
- ISO 27001:2022 A.8.25: Secure development life cycle (direct)
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 - ISO 27001:2022 A.8.26: Application security requirements (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 - ISO 27001:2022 A.8.28: Secure coding (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 - SOC 2 CC8.1: Managing changes to procedures, software, data and infrastructure (direct)
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 - SOC 2 PI1.3: Controls over system processing (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 PR.PS-06: Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle (direct)
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-09: The authenticity and integrity of hardware and software are assessed prior to acquisition and use (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 - PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software (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
Subject: secure_development. Owner a broker routes it to: Engineering change owner.
The same control on other applications
Hiscox Q57, Munich Re Q79, Arch Insurance Q95, Aspen American Insurance Company Q38, Markel Q45, Markel Q48.
Map your own answers in the tool. See the Munich Re page, the controls index, the island and the answers.