Does the Applicant have a report phishing email add-in enabled for all email users?
This is application question 44 of 79 on the AXIS Insurance AXIS 1012985. It is a control question and reaches 11 controls. The wording is the carrier's, quoted verbatim.
Held from the AXIS Cyber Application for Small Business (read 2026-10-11), jurisdiction United States. All AXIS Insurance questions.
Facets: control: Does the Applicant have a report phishing email add-in enabled for all email users?; population: users
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 CC2.2: Internal communication of objectives and control responsibilities (COSO principle 14) (supporting)
Establishes how users report suspected messages; it does not establish that every report was actioned.
Evidence to have on file: the user-reporting route for suspicious mail and how reports are triaged; a sample of a reported message and the action taken - 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.AT-01: Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind (supporting)
Establishes how users report suspected messages; it does not establish that every report was actioned.
Evidence to have on file: the user-reporting route for suspicious mail and how reports are triaged; a sample of a reported message and the action taken - 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, RLI Q17.
Map your own answers in the tool. See the AXIS Insurance page, the controls index, the island and the answers.