Cyber Insurance Application Scannermap an application to controls

Apogee Insurance Group cyber policy application, held

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

The questions of the Cyber Liability Insurance Questionnaire, 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, Cyber Liability Insurance Questionnaire (read 2026-10-12). 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. Apogee Insurance Group is a source document, never a customer.

This document

Form identifierCyber Liability Insurance Questionnaire
Edition or versionundated
JurisdictionUnited States
ProductCyber Liability
Application typenew business questionnaire
Scope conditionsa short questionnaire; desired limits are bounded between two hundred and fifty thousand and five million, retention between two thousand five hundred and twenty thousand
Page referencesa single page

This document's questions reach 9 of 487 controls. Whether an applicant is offered cover is the carrier’s underwriting decision. 1 question here is 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 Does the applicant have multi-factor authentication (MFA/2FA) enabled on email access and remote network access?
Apogee Insurance Group application question

Priority underwriting question: a "no" here is a subject a cyber underwriter weighs most. A carrier may still accept a compensating-controls explanation, or accept a "remote access not permitted" answer, so it is not a binary decline.

Facets (activity, control, population, threshold, frequency, exception): control: Does the applicant have multi-factor authentication (MFA/2FA) enabled on email access and remote network access?

ISO 27001:2022 A.8.5 Secure authentication
Direct mapping: this control is what the question asks about. Limit: Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file (guidance, our wording)
  • the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope
  • the report of enrolled authentication methods, or the registration status by user group
  • the written rule stating where the second factor is required and where it is not
ISO 27001:2022 A.5.17 Authentication information
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file (guidance, our wording)
  • the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope
  • the report of enrolled authentication methods, or the registration status by user group
  • the written rule stating where the second factor is required and where it is not
SOC 2 CC6.1 Logical access security over protected information assets
Direct mapping: this control is what the question asks about. Limit: Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file (guidance, our wording)
  • the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope
  • the report of enrolled authentication methods, or the registration status by user group
  • the written rule stating where the second factor is required and where it is not
NIST CSF 2.0 PR.AA-03 Users, services, and hardware are authenticated
Direct mapping: this control is what the question asks about. Limit: Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file (guidance, our wording)
  • the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope
  • the report of enrolled authentication methods, or the registration status by user group
  • the written rule stating where the second factor is required and where it is not
ACSC Essential Eight MFA Multi-factor authentication
Direct mapping: this control is what the question asks about. Limit: Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file (guidance, our wording)
  • the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope
  • the report of enrolled authentication methods, or the registration status by user group
  • the written rule stating where the second factor is required and where it is not
CIS Controls v8 6.4 Require MFA for Remote Network Access
Direct mapping: this control is what the question asks about. Limit: Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file (guidance, our wording)
  • the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope
  • the report of enrolled authentication methods, or the registration status by user group
  • the written rule stating where the second factor is required and where it is not
CIS Controls v8 6.5 Require MFA for Administrative Access
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file (guidance, our wording)
  • the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope
  • the report of enrolled authentication methods, or the registration status by user group
  • the written rule stating where the second factor is required and where it is not
CIS Controls v8 6.3 Require MFA for Externally-Exposed 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 second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file (guidance, our wording)
  • the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope
  • the report of enrolled authentication methods, or the registration status by user group
  • the written rule stating where the second factor is required and where it is not
PCI DSS 4.0 Requirement 8 Identify Users and Authenticate Access to System Components
Direct mapping: this control is what the question asks about. Limit: Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file (guidance, our wording)
  • the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope
  • the report of enrolled authentication methods, or the registration status by user group
  • the written rule stating where the second factor is required and where it is not
Application question Projected Gross Revenue (Next 12 Months)
Apogee Insurance Group 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 Description of Business Operations
Apogee Insurance Group 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 Desired Limits ($250K min. - $5M max.) & Retention ($2.5K min. - $20K max.)
Apogee Insurance Group application question

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

Facets (activity, control, population, threshold, frequency, exception): threshold: $250

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

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 (478)

None of this document's questions reach 478 of the 487 controls (for example A.5.1, A.5.2, A.5.3, A.5.4, A.5.5, A.5.6, A.5.7, A.5.8). 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.