Are blocked emails classed as incidents and remediated?
This is application question 66 of 121 on the Munich Re MRS Insurance Application Cyber Risk. It is a control question and reaches 11 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: Are blocked emails classed as incidents and remediated?
What this question reaches
- ISO 27001:2022 A.8.23: Web filtering (direct)
Establishes the email control the question names; it does not establish that every malicious message was caught or reported.
Evidence to have on file: the email-filtering configuration and the checks it applies to inbound mail; a sample of blocked or quarantined messages and their handling - ISO 27001:2022 A.8.7: Protection against malware (supporting)
Establishes the email control the question names; it does not establish that every malicious message was caught or reported.
Evidence to have on file: the email-filtering configuration and the checks it applies to inbound mail; a sample of blocked or quarantined messages and their handling - ISO 27001:2022 A.5.14: Information transfer (supporting)
Establishes the email control the question names; it does not establish that every malicious message was caught or reported.
Evidence to have on file: the email-filtering configuration and the checks it applies to inbound mail; a sample of blocked or quarantined messages and their handling - SOC 2 CC6.8: Preventing and detecting unauthorised or malicious software (direct)
Establishes the email control the question names; it does not establish that every malicious message was caught or reported.
Evidence to have on file: the email-filtering configuration and the checks it applies to inbound mail; a sample of blocked or quarantined messages and their handling - SOC 2 CC6.4: Restricting physical access to facilities and assets (supporting)
Establishes the physical or environmental control named; it does not establish the security of every site.
Evidence to have on file: the physical-access record for the site the question names; the rule on who may enter which area, and how visitors are handled - NIST CSF 2.0 PR.PS-05: Installation and execution of unauthorized software are prevented (direct)
Establishes the email control the question names; it does not establish that every malicious message was caught or reported.
Evidence to have on file: the email-filtering configuration and the checks it applies to inbound mail; a sample of blocked or quarantined messages and their handling - NIST CSF 2.0 PR.AA-06: Physical access to assets is managed, monitored, and enforced commensurate with risk (supporting)
Establishes the physical or environmental control named; it does not establish the security of every site.
Evidence to have on file: the physical-access record for the site the question names; the rule on who may enter which area, and how visitors are handled - CIS Controls v8 9.5: Implement DMARC (direct)
Establishes the email control the question names; it does not establish that every malicious message was caught or reported.
Evidence to have on file: the email-filtering configuration and the checks it applies to inbound mail; a sample of blocked or quarantined messages and their handling - CIS Controls v8 9.4: Restrict Unnecessary or Unauthorized Browser and Email Client Extensions (supporting)
Establishes the email control the question names; it does not establish that every malicious message was caught or reported.
Evidence to have on file: the email-filtering configuration and the checks it applies to inbound mail; a sample of blocked or quarantined messages and their handling - CIS Controls v8 9.7: Deploy and Maintain Email Server Anti-Malware Protections (supporting)
Establishes the email control the question names; it does not establish that every malicious message was caught or reported.
Evidence to have on file: the email-filtering configuration and the checks it applies to inbound mail; a sample of blocked or quarantined messages and their handling - PCI DSS 4.0 Requirement 5: Protect All Systems and Networks from Malicious Software (supporting)
Establishes the email control the question names; it does not establish that every malicious message was caught or reported.
Evidence to have on file: the email-filtering configuration and the checks it applies to inbound mail; a sample of blocked or quarantined messages and their handling
Subject: email_security. Owner a broker routes it to: Email and messaging owner.
The same control on other applications
Beazley Q5, Beazley Q6, Beazley Q10, Beazley Q19, Great American Insurance Group Q15, Great American Insurance Group Q16, Tokio Marine HCC Q20, Tokio Marine HCC Q29, AXIS Insurance Q31, AXIS Insurance Q42, AXIS Insurance Q43, AXIS Insurance Q44.
Map your own answers in the tool. See the Munich Re page, the controls index, the island and the answers.