Cyber Insurance Application Scannermap an application to controls

An example of a saved submission

This is a worked example, read-only. It is not a real client and not a real application, and nothing here is collected or sent. It shows what the workspace keeps for a submission you come back to (one seat, or Team shared by up to five people): the questions, the controls each one reaches with its direct or supporting basis, who owns the evidence for each row and the artifact held against it, the exceptions you logged, the review status and date on each row, a note where the carrier changed its form, and the approval history.

Example submission: a managed service provider, annual cyber renewal, first submission to the carrier this cycle. The control rows below are mapped by the same engine that runs the free scanner; the owner, status, date and history fields are the example workspace data.

Example application question Do you require multi-factor authorization when your network is accessed remotely and/or when cloud resources are utilized?
CNA application question
ControlControl areaBasisEvidence ownerEvidence heldReview statusReview dateLimit
ISO 27001:2022 A.8.5Secure authenticationDirectHead of Securityattached: identity-provider configuration showing the second factor and the sign-in paths in scope, reviewed 11 OctReviewed with exception11 OctEstablishes 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.
ISO 27001:2022 A.5.17Authentication informationSupportingHead of Securityattached: identity-provider configuration showing the second factor and the sign-in paths in scope, reviewed 11 OctReviewed with exception11 OctEstablishes 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.
SOC 2 CC6.1Logical access security over protected information assetsDirectHead of Securityattached: identity-provider configuration showing the second factor and the sign-in paths in scope, reviewed 11 OctReviewed with exception11 OctEstablishes 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.
NIST CSF 2.0 PR.AA-03Users, services, and hardware are authenticatedDirectHead of Securityattached: identity-provider configuration showing the second factor and the sign-in paths in scope, reviewed 11 OctReviewed with exception11 OctEstablishes 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.
ACSC Essential Eight MFAMulti-factor authenticationDirectHead of Securityattached: identity-provider configuration showing the second factor and the sign-in paths in scope, reviewed 11 OctReviewed with exception11 OctEstablishes 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.
CIS Controls v8 6.4Require MFA for Remote Network AccessDirectHead of Securityattached: identity-provider configuration showing the second factor and the sign-in paths in scope, reviewed 11 OctReviewed with exception11 OctEstablishes 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.
CIS Controls v8 6.5Require MFA for Administrative AccessSupportingHead of Securityattached: identity-provider configuration showing the second factor and the sign-in paths in scope, reviewed 11 OctReviewed with exception11 OctEstablishes 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.
CIS Controls v8 6.3Require MFA for Externally-Exposed ApplicationsSupportingHead of Securityattached: identity-provider configuration showing the second factor and the sign-in paths in scope, reviewed 11 OctReviewed with exception11 OctEstablishes 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.
PCI DSS 4.0 Requirement 8Identify Users and Authenticate Access to System ComponentsDirectHead of Securityattached: identity-provider configuration showing the second factor and the sign-in paths in scope, reviewed 11 OctReviewed with exception11 OctEstablishes 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.
Example application question Does Named Insured enable disk encryption on laptops, desktops, and other portable media devices?
Coalition application question
ControlControl areaBasisEvidence ownerEvidence heldReview statusReview dateLimit
ISO 27001:2022 A.8.24Use of cryptographyDirectHead of Infrastructureattached: full-disk-encryption configuration record and the enrolled-device report, reviewed 11 OctReviewed11 OctEstablishes encryption of data at rest on the devices or stores the question names; it does not establish encryption in transit, key management, or coverage of every data store.
ISO 27001:2022 A.7.10Storage mediaDirectHead of Infrastructureattached: full-disk-encryption configuration record and the enrolled-device report, reviewed 11 OctReviewed11 OctEstablishes encryption of data at rest on the devices or stores the question names; it does not establish encryption in transit, key management, or coverage of every data store.
ISO 27001:2022 A.8.1User end point devicesDirectHead of Infrastructureattached: full-disk-encryption configuration record and the enrolled-device report, reviewed 11 OctReviewed11 OctEstablishes encryption of data at rest on the devices or stores the question names; it does not establish encryption in transit, key management, or coverage of every data store.
SOC 2 CC6.1Logical access security over protected information assetsDirectHead of Infrastructureattached: full-disk-encryption configuration record and the enrolled-device report, reviewed 11 OctReviewed11 OctEstablishes encryption of data at rest on the devices or stores the question names; it does not establish encryption in transit, key management, or coverage of every data store.
SOC 2 CC6.7Restricting and protecting information in transmission, movement and removalSupportingHead of Infrastructureattached: full-disk-encryption configuration record and the enrolled-device report, reviewed 11 OctReviewed11 OctEstablishes encryption of data at rest on the devices or stores the question names; it does not establish encryption in transit, key management, or coverage of every data store.
NIST CSF 2.0 PR.DS-01The confidentiality, integrity, and availability of data-at-rest are protectedDirectHead of Infrastructureattached: full-disk-encryption configuration record and the enrolled-device report, reviewed 11 OctReviewed11 OctEstablishes encryption of data at rest on the devices or stores the question names; it does not establish encryption in transit, key management, or coverage of every data store.
NIST CSF 2.0 PR.AA-06Physical access to assets is managed, monitored, and enforced commensurate with riskSupportingRisk and Compliance Leadattached: device-management enrolment report for the mobile estate, reviewed 11 OctReviewed11 OctEstablishes the mobile or BYOD control the question names; it does not establish the state of every personal device.
CIS Controls v8 3.6Encrypt Data on End-User DevicesDirectHead of Infrastructureattached: full-disk-encryption configuration record and the enrolled-device report, reviewed 11 OctReviewed11 OctEstablishes encryption of data at rest on the devices or stores the question names; it does not establish encryption in transit, key management, or coverage of every data store.
CIS Controls v8 3.11Encrypt Sensitive Data at RestSupportingHead of Infrastructureattached: full-disk-encryption configuration record and the enrolled-device report, reviewed 11 OctReviewed11 OctEstablishes encryption of data at rest on the devices or stores the question names; it does not establish encryption in transit, key management, or coverage of every data store.
PCI DSS 4.0 Requirement 3Protect Stored Account DataSupportingHead of Infrastructureattached: full-disk-encryption configuration record and the enrolled-device report, reviewed 11 OctReviewed11 OctEstablishes encryption of data at rest on the devices or stores the question names; it does not establish encryption in transit, key management, or coverage of every data store.

Changed since the carrier last updated the form: The carrier refreshed this form after the copy we read. The wording was re-checked against the current form and the mapped controls are unchanged.

Example application question Do you encrypt all sensitive records and files that are held at rest and/or transmitted across public networks, and that are to be transmitted wirelessly?
CNA application question
ControlControl areaBasisEvidence ownerEvidence heldReview statusReview dateLimit
ISO 27001:2022 A.8.24Use of cryptographyDirectHead of Infrastructureattached: full-disk-encryption configuration record and the enrolled-device report, reviewed 12 OctReviewed12 OctEstablishes encryption of data at rest on the devices or stores the question names; it does not establish encryption in transit, key management, or coverage of every data store.
ISO 27001:2022 A.7.10Storage mediaDirectHead of Infrastructureattached: full-disk-encryption configuration record and the enrolled-device report, reviewed 12 OctReviewed12 OctEstablishes encryption of data at rest on the devices or stores the question names; it does not establish encryption in transit, key management, or coverage of every data store.
SOC 2 CC6.1Logical access security over protected information assetsDirectHead of Infrastructureattached: full-disk-encryption configuration record and the enrolled-device report, reviewed 12 OctReviewed12 OctEstablishes encryption of data at rest on the devices or stores the question names; it does not establish encryption in transit, key management, or coverage of every data store.
SOC 2 CC6.7Restricting and protecting information in transmission, movement and removalDirectHead of Infrastructureattached: TLS configuration and the certificate inventory, reviewed 12 OctReviewed12 OctEstablishes protection of data while it moves; it does not establish protection of the same data at rest.
NIST CSF 2.0 PR.DS-01The confidentiality, integrity, and availability of data-at-rest are protectedDirectHead of Infrastructureattached: full-disk-encryption configuration record and the enrolled-device report, reviewed 12 OctReviewed12 OctEstablishes encryption of data at rest on the devices or stores the question names; it does not establish encryption in transit, key management, or coverage of every data store.
NIST CSF 2.0 PR.DS-02The confidentiality, integrity, and availability of data-in-transit are protectedDirectHead of Infrastructureattached: TLS configuration and the certificate inventory, reviewed 12 OctReviewed12 OctEstablishes protection of data while it moves; it does not establish protection of the same data at rest.
CIS Controls v8 3.11Encrypt Sensitive Data at RestDirectHead of Infrastructureattached: full-disk-encryption configuration record and the enrolled-device report, reviewed 12 OctReviewed12 OctEstablishes encryption of data at rest on the devices or stores the question names; it does not establish encryption in transit, key management, or coverage of every data store.
CIS Controls v8 3.10Encrypt Sensitive Data in TransitDirectHead of Infrastructureattached: TLS configuration and the certificate inventory, reviewed 12 OctReviewed12 OctEstablishes protection of data while it moves; it does not establish protection of the same data at rest.
PCI DSS 4.0 Requirement 3Protect Stored Account DataSupportingHead of Infrastructureattached: full-disk-encryption configuration record and the enrolled-device report, reviewed 12 OctReviewed12 OctEstablishes encryption of data at rest on the devices or stores the question names; it does not establish encryption in transit, key management, or coverage of every data store.
PCI DSS 4.0 Requirement 4Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public NetworksSupportingHead of Infrastructureattached: TLS configuration and the certificate inventory, reviewed 12 OctReviewed12 OctEstablishes protection of data while it moves; it does not establish protection of the same data at rest.
Example application question Does the Applicant verify all vendor and supplier bank accounts by a direct call to the receiving bank, prior to accounts being established in the accounts payable system?
Chubb application question
ControlControl areaBasisEvidence ownerEvidence heldReview statusReview dateLimit
ISO 27001:2022 A.5.3Segregation of dutiesDirectRisk and Compliance Leadattached: supplier bank-account verification record and the dated call log, reviewed 12 OctReviewed12 OctEstablishes the verification step the wording names; it does not establish the wider payment approval workflow or the threshold above which a second approval applies.
ISO 27001:2022 A.5.19Information security in supplier relationshipsSupportingRisk and Compliance Leadattached: supplier bank-account verification record and the dated call log, reviewed 12 OctReviewed12 OctEstablishes the verification step the wording names; it does not establish the wider payment approval workflow or the threshold above which a second approval applies.
ISO 27001:2022 A.6.3Information security awareness, education and trainingSupportingFinance Controllerattached: payment approval record and the two-person authorisation log, reviewed 12 OctReviewed12 OctEstablishes the funds-transfer or dual-control practice the question names; it does not establish the bank's own configuration or that no fraudulent payment was made.
SOC 2 CC6.3Role-based access, least privilege and segregation of dutiesDirectRisk and Compliance Leadattached: supplier bank-account verification record and the dated call log, reviewed 12 OctReviewed12 OctEstablishes the verification step the wording names; it does not establish the wider payment approval workflow or the threshold above which a second approval applies.
SOC 2 CC3.3Considering fraud risk (COSO principle 8)SupportingRisk and Compliance Leadattached: supplier bank-account verification record and the dated call log, reviewed 12 OctReviewed12 OctEstablishes the verification step the wording names; it does not establish the wider payment approval workflow or the threshold above which a second approval applies.
NIST CSF 2.0 PR.AA-05Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of dutiesDirectRisk and Compliance Leadattached: supplier bank-account verification record and the dated call log, reviewed 12 OctReviewed12 OctEstablishes the verification step the wording names; it does not establish the wider payment approval workflow or the threshold above which a second approval applies.
NIST CSF 2.0 GV.SC-05Requirements 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 partiesSupportingRisk and Compliance Leadattached: supplier bank-account verification record and the dated call log, reviewed 12 OctReviewed12 OctEstablishes the verification step the wording names; it does not establish the wider payment approval workflow or the threshold above which a second approval applies.
Example application question If available, please advise exact number of unique PII records stored:
Aon application question

This line is a scoping question, not a control requirement, so it maps no control: the answer is a record count the carrier asks for. It is kept in the saved submission so the number is on file.

Exceptions ledger

QuestionException loggedCompensating controlOwnerReview statusReview date
Is MFA required for all remote access?Two legacy on-premises consoles do not support single sign-on.Both consoles sit on an isolated management segment with no internet route, and are removed at the next hardware refresh.Head of SecurityException accepted internally by the vCISO on 13 Oct (not an insurer acceptance)13 Oct
Are offline backups tested?The quarterly restore test slipped by three weeks in the last cycle.The test was completed and the dated record is attached; the schedule was moved to a fixed calendar slot.IT Operations ManagerResolved by the control owner on 13 Oct13 Oct

An internal acceptance is a decision by our own named risk owner to proceed with a compensating control, and it is a different decision from an insurer acceptance of the exception. Where the carrier accepts an exception it is labelled "insurer accepted" and carries the carrier and the date; nothing on this page is an insurer acceptance.

Approval history

Drafted by the risk and compliance lead; each control owner above confirmed the evidence held and attached it; the one exception was accepted internally by the vCISO on 13 Oct; reviewed by the vCISO; approved for submission to the carrier on 14 Oct. A change to any answer above reopens the row for review and appends a new line here.

This is a specimen of the saved workspace on a one seat or Team plan. Map a carrier application for free on the scanner; sign in to save one at the workspace. Nothing on this page is a real client, a real application or advice.