Cyber Insurance Application Scannermap an application to controls

CFC Underwriting cyber policy application, held

10 questions, 37 controls reached, 0 flagged as priority underwriting questions and 0 flagged warranty (answers the carrier relies on). Renewal and change view.

The questions of the Cyber private enterprise Insurance application form (US), mapped to the ISO 27001:2022 controls, the SOC 2 criteria, the NIST CSF 2.0 outcomes, the ACSC Essential Eight requirements, the APRA CPS 234 paragraphs, the CIS Controls v8 safeguards and the PCI DSS 4.0 requirements each one reaches. The source document (read 2026-10-11). The date shown is the date this copy was read, not a version the form itself states. This page quotes only the question each mapped row needs and states its source; it does not publish the carrier's form. A complete form would be held only under a stated policy for copyrighted forms. CFC Underwriting is a source document, never a customer.

This document

Form identifierCyber private enterprise US application
Edition or versionundated
JurisdictionUnited States
ProductCyber private enterprise
Application typenew business application with an optional supplementary form
Scope conditionscompanies under $50m revenue seeking limits of $5m or below
Page referencesthe base form and the optional supplement

This document's questions reach 37 of 487 controls. Whether an applicant is offered cover is the carrier’s underwriting decision. 0 questions here are flagged as a priority underwriting question and 0 flagged warranty (an answer the carrier relies on, which can affect underwriting or cover if wrong).

Application question Do you anticipate spending more, the same or less in this financial year?
CFC Underwriting application question

This is a financials question, not a control requirement. It reaches no control.

No mapping identified for this line in the documents. That is not a statement that a document does not ask it.

Application question Is your IT infrastructure primarily operated and managed in-house or outsourced?
CFC Underwriting application question

Facets (activity, control, population, threshold, frequency, exception): control: Is your IT infrastructure primarily operated and managed in-house or outsourced?

ISO 27001:2022 A.5.19 Information security in supplier relationships
Direct mapping: this control is what the question asks about. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
ISO 27001:2022 A.5.20 Addressing information security within supplier agreements
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
ISO 27001:2022 A.5.21 Managing information security in the information and communication technology (ICT) supply chain
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
SOC 2 CC9.2 Assessing and managing vendor and business partner risk
Direct mapping: this control is what the question asks about. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
SOC 2 P6.4 Privacy commitments from vendors and third parties
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
NIST CSF 2.0 GV.SC-01 A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders
Direct mapping: this control is what the question asks about. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
NIST CSF 2.0 GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
APRA CPS 234 para 16 Assess the security capability of related and third parties
Direct mapping: this control is what the question asks about. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
APRA CPS 234 para 22 Evaluate the design of third-party controls
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
APRA CPS 234 para 28 Assess reliance on third-party control testing
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
PCI DSS 4.0 Requirement 12 Support Information Security with Organizational Policies and Programs
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
Application question If it is outsourced, who do you outsource it to?
CFC Underwriting application question

Facets (activity, control, population, threshold, frequency, exception): control: If it is outsourced, who do you outsource it to?

ISO 27001:2022 A.5.19 Information security in supplier relationships
Direct mapping: this control is what the question asks about. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
ISO 27001:2022 A.5.20 Addressing information security within supplier agreements
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
ISO 27001:2022 A.5.21 Managing information security in the information and communication technology (ICT) supply chain
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
SOC 2 CC9.2 Assessing and managing vendor and business partner risk
Direct mapping: this control is what the question asks about. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
SOC 2 P6.4 Privacy commitments from vendors and third parties
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
NIST CSF 2.0 GV.SC-01 A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders
Direct mapping: this control is what the question asks about. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
NIST CSF 2.0 GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
APRA CPS 234 para 16 Assess the security capability of related and third parties
Direct mapping: this control is what the question asks about. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
APRA CPS 234 para 22 Evaluate the design of third-party controls
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
APRA CPS 234 para 28 Assess reliance on third-party control testing
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact.
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
PCI DSS 4.0 Requirement 12 Support Information Security with Organizational Policies and Programs
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the third-party control asked about; it does not establish the security state of each supplier in fact. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)
  • the supplier or vendor register, with the security terms each is held to
  • a sample of a completed supplier due-diligence review
  • the rule on which suppliers need a security assessment and how often
Application question How many full-time employees do you have in your IT department?
CFC Underwriting application question

This is a scoping question, not a control requirement. It reaches no control.

Facets (activity, control, population, threshold, frequency, exception): population: employees

No mapping identified for this line in the documents. That is not a statement that a document does not ask it.

Application question How many of these employees are dedicated to a role in IT security?
CFC Underwriting application question

This is a scoping question, not a control requirement. It reaches no control.

Facets (activity, control, population, threshold, frequency, exception): population: employees

No mapping identified for this line in the documents. That is not a statement that a document does not ask it.

Application question Information security governance Who is responsible for IT security within your organisation (by job title?
CFC Underwriting application question

Facets (activity, control, population, threshold, frequency, exception): control: Information security governance Who is responsible for IT security within your organisation (by job title?

ISO 27001:2022 A.5.1 Policies for information security
Direct mapping: this control is what the question asks about. Limit: Establishes the governance or policy practice asked about; it does not establish how the policy is followed in practice.
Evidence to have on file (guidance, our wording)
  • the information-security policy and its owner, with the review date
  • the record of management review or approval of the policy
  • the role list showing who is accountable for security
ISO 27001:2022 A.5.2 Information security roles and responsibilities
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the governance or policy practice asked about; it does not establish how the policy is followed in practice.
Evidence to have on file (guidance, our wording)
  • the information-security policy and its owner, with the review date
  • the record of management review or approval of the policy
  • the role list showing who is accountable for security
ISO 27001:2022 A.5.4 Management responsibilities
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the governance or policy practice asked about; it does not establish how the policy is followed in practice.
Evidence to have on file (guidance, our wording)
  • the information-security policy and its owner, with the review date
  • the record of management review or approval of the policy
  • the role list showing who is accountable for security
SOC 2 CC1.3 Structures, reporting lines, authorities and responsibilities (COSO principle 3)
Direct mapping: this control is what the question asks about. Limit: Establishes the governance or policy practice asked about; it does not establish how the policy is followed in practice.
Evidence to have on file (guidance, our wording)
  • the information-security policy and its owner, with the review date
  • the record of management review or approval of the policy
  • the role list showing who is accountable for security
SOC 2 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the governance or policy practice asked about; it does not establish how the policy is followed in practice.
Evidence to have on file (guidance, our wording)
  • the information-security policy and its owner, with the review date
  • the record of management review or approval of the policy
  • the role list showing who is accountable for security
NIST CSF 2.0 GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
Direct mapping: this control is what the question asks about. Limit: Establishes the governance or policy practice asked about; it does not establish how the policy is followed in practice.
Evidence to have on file (guidance, our wording)
  • the information-security policy and its owner, with the review date
  • the record of management review or approval of the policy
  • the role list showing who is accountable for security
NIST CSF 2.0 GV.RR-01 Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the governance or policy practice asked about; it does not establish how the policy is followed in practice.
Evidence to have on file (guidance, our wording)
  • the information-security policy and its owner, with the review date
  • the record of management review or approval of the policy
  • the role list showing who is accountable for security
APRA CPS 234 para 14 Information security roles and responsibilities defined
Direct mapping: this control is what the question asks about. Limit: Establishes the governance or policy practice asked about; it does not establish how the policy is followed in practice.
Evidence to have on file (guidance, our wording)
  • the information-security policy and its owner, with the review date
  • the record of management review or approval of the policy
  • the role list showing who is accountable for security
APRA CPS 234 para 13 Board accountability for information security
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the governance or policy practice asked about; it does not establish how the policy is followed in practice.
Evidence to have on file (guidance, our wording)
  • the information-security policy and its owner, with the review date
  • the record of management review or approval of the policy
  • the role list showing who is accountable for security
PCI DSS 4.0 Requirement 12 Support Information Security with Organizational Policies and Programs
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the governance or policy practice asked about; it does not establish how the policy is followed in practice. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)
  • the information-security policy and its owner, with the review date
  • the record of management review or approval of the policy
  • the role list showing who is accountable for security
Application question How many years have they been in this position within your company?
CFC Underwriting application question

This is a scoping question, not a control requirement. It reaches no control.

No mapping identified for this line in the documents. That is not a statement that a document does not ask it.

Application question How often do you patch your operating sytems?
CFC Underwriting application question

Facets (activity, control, population, threshold, frequency, exception): control: How often do you patch your operating sytems?

ISO 27001:2022 A.8.8 Management of technical vulnerabilities
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
ISO 27001:2022 A.8.19 Installation of software on operational systems
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
ISO 27001:2022 A.8.29 Security testing in development and acceptance
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
SOC 2 CC7.1 Detecting configuration changes and new vulnerabilities
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
NIST CSF 2.0 ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
NIST CSF 2.0 PR.PS-02 Software is maintained, replaced, and removed commensurate with risk
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
ACSC Essential Eight PATCHAPP Patch applications
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
ACSC Essential Eight PATCHOS Patch operating systems
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
CIS Controls v8 7.3 Perform Automated Operating System Patch Management
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
CIS Controls v8 7.4 Perform Automated Application Patch Management
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
CIS Controls v8 7.7 Remediate Detected Vulnerabilities
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
PCI DSS 4.0 Requirement 6 Develop and Maintain Secure Systems and Software
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the patching or vulnerability practice asked about; it does not establish that every critical asset was patched within the stated window. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
PCI DSS 4.0 Requirement 11 Test Security of Systems and Networks Regularly
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the patching or vulnerability practice asked about; it does not establish that every critical asset was patched within the stated window. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
Application question How often do you conduct vulnerability scanning of your network perimeter?
CFC Underwriting application question

Facets (activity, control, population, threshold, frequency, exception): control: How often do you conduct vulnerability scanning of your network perimeter?

ISO 27001:2022 A.8.8 Management of technical vulnerabilities
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)
  • 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
  • the remediation or exception record for each finding, with the date it was closed
ISO 27001:2022 A.8.19 Installation of software on operational systems
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • 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
  • the remediation or exception record for each finding, with the date it was closed
ISO 27001:2022 A.8.29 Security testing in development and acceptance
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • 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
  • the remediation or exception record for each finding, with the date it was closed
SOC 2 CC7.1 Detecting configuration changes and new vulnerabilities
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)
  • 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
  • the remediation or exception record for each finding, with the date it was closed
NIST CSF 2.0 ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)
  • 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
  • the remediation or exception record for each finding, with the date it was closed
NIST CSF 2.0 PR.PS-02 Software is maintained, replaced, and removed commensurate with risk
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • 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
  • the remediation or exception record for each finding, with the date it was closed
ACSC Essential Eight PATCHAPP Patch applications
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • 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
  • the remediation or exception record for each finding, with the date it was closed
ACSC Essential Eight PATCHOS Patch operating systems
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • 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
  • the remediation or exception record for each finding, with the date it was closed
CIS Controls v8 7.6 Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)
  • 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
  • the remediation or exception record for each finding, with the date it was closed
CIS Controls v8 7.5 Perform Automated Vulnerability Scans of Internal Enterprise Assets
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • 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
  • the remediation or exception record for each finding, with the date it was closed
CIS Controls v8 7.1 Establish and Maintain a Vulnerability Management Process
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • 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
  • the remediation or exception record for each finding, with the date it was closed
PCI DSS 4.0 Requirement 11 Test Security of Systems and Networks Regularly
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)
  • 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
  • the remediation or exception record for each finding, with the date it was closed
PCI DSS 4.0 Requirement 6 Develop and Maintain Secure Systems and Software
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)
  • 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
  • the remediation or exception record for each finding, with the date it was closed
Application question How often do you conduct pentration testing of you network architecture?
CFC Underwriting application question

Facets (activity, control, population, threshold, frequency, exception): control: How often do you conduct pentration testing of you network architecture?

ISO 27001:2022 A.8.8 Management of technical vulnerabilities
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
ISO 27001:2022 A.8.19 Installation of software on operational systems
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
ISO 27001:2022 A.8.29 Security testing in development and acceptance
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
SOC 2 CC7.1 Detecting configuration changes and new vulnerabilities
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
SOC 2 CC6.6 Protection against threats from outside the system boundary
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the network control asked about; it does not establish the full architecture or that no path bypasses it.
Evidence to have on file (guidance, our wording)
  • 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
  • the network diagram, or the written rule stating what may cross the boundary
NIST CSF 2.0 ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
NIST CSF 2.0 PR.PS-02 Software is maintained, replaced, and removed commensurate with risk
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
ACSC Essential Eight PATCHAPP Patch applications
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
ACSC Essential Eight PATCHOS Patch operating systems
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
CIS Controls v8 7.3 Perform Automated Operating System Patch Management
Direct mapping: this control is what the question asks about. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
CIS Controls v8 7.4 Perform Automated Application Patch Management
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
CIS Controls v8 7.7 Remediate Detected Vulnerabilities
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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 (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
PCI DSS 4.0 Requirement 6 Develop and Maintain Secure Systems and Software
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the patching or vulnerability practice asked about; it does not establish that every critical asset was patched within the stated window. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation
PCI DSS 4.0 Requirement 11 Test Security of Systems and Networks Regularly
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the patching or vulnerability practice asked about; it does not establish that every critical asset was patched within the stated window. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)
  • the patch or vulnerability-management policy with the remediation windows it sets
  • a report of outstanding critical patches against the stated window
  • a sample of a recent vulnerability scan and its remediation

The other applications, each with its own page: Coalition, Chubb, CFC Underwriting, Beazley, Hiscox, AmTrust, Great American Insurance Group, Tokio Marine HCC, AXIS Insurance, Travelers, RLI, Corvus Insurance, Cowbell Cyber, At-Bay, QBE, The Hanover Insurance Group, The Hartford, CNA, Encore Fiduciary, Everest Insurance, RSA, Munich Re, Hiscox UK, AIG, Aon, Arch Insurance, DUAL Corporate Risks, Argonaut Insurance Company, Northbridge General Insurance Corporation, Trisura Guarantee Insurance Company, Aspen American Insurance Company, Capitol Indemnity Corporation (CapSpecialty), ATC Insurance Solutions Pty Ltd, SURA Technology Risks Pty Ltd (SURA Cyber), Apogee Insurance Group, SHORE Underwriting, London Australia Underwriting Pty Ltd, Discovery Insure Ltd, BOXX Insurance, The Hartford Steam Boiler Inspection and Insurance Company, The Cincinnati Insurance Company, USLI, Philadelphia Insurance Companies, Delta Insurance, Markel, Liberty Mutual Insurance Europe Limited, Emergence Insurance Pty Ltd, Ocean Underwriting. Compare this with any of them on the comparison page; the controls the documents share are ranked on the island. Worked answers: what counts as MFA and the funds-transfer question. For a renewal: the broker renewal checklist and the pre-renewal client review template. What is covered, and what is next: coverage.

Controls not asked in this document (450)

None of this document's questions reach 450 of the 487 controls (for example A.5.3, A.5.5, A.5.6, A.5.7, A.5.8, A.5.9, A.5.10, A.5.11). That is a fact about this document, not about what the carrier underwrites on: a carrier's fuller forms and supplements ask controls this summary does not, multi-factor authentication, offline backups and patching among them. A control here is not asserted as required, and not asserted as not required. A control the tool does not map is reported as no mapping identified, never as a control the document does not ask.