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.
| Control | Control area | Basis | Evidence owner | Evidence held | Review status | Review date | Limit |
|---|---|---|---|---|---|---|---|
| ISO 27001:2022 A.8.5 | Secure authentication | Direct | Head of Security | attached: identity-provider configuration showing the second factor and the sign-in paths in scope, reviewed 11 Oct | Reviewed with exception | 11 Oct | 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. |
| ISO 27001:2022 A.5.17 | Authentication information | Supporting | Head of Security | attached: identity-provider configuration showing the second factor and the sign-in paths in scope, reviewed 11 Oct | Reviewed with exception | 11 Oct | 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. |
| SOC 2 CC6.1 | Logical access security over protected information assets | Direct | Head of Security | attached: identity-provider configuration showing the second factor and the sign-in paths in scope, reviewed 11 Oct | Reviewed with exception | 11 Oct | 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. |
| NIST CSF 2.0 PR.AA-03 | Users, services, and hardware are authenticated | Direct | Head of Security | attached: identity-provider configuration showing the second factor and the sign-in paths in scope, reviewed 11 Oct | Reviewed with exception | 11 Oct | 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. |
| ACSC Essential Eight MFA | Multi-factor authentication | Direct | Head of Security | attached: identity-provider configuration showing the second factor and the sign-in paths in scope, reviewed 11 Oct | Reviewed with exception | 11 Oct | 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. |
| CIS Controls v8 6.4 | Require MFA for Remote Network Access | Direct | Head of Security | attached: identity-provider configuration showing the second factor and the sign-in paths in scope, reviewed 11 Oct | Reviewed with exception | 11 Oct | 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. |
| CIS Controls v8 6.5 | Require MFA for Administrative Access | Supporting | Head of Security | attached: identity-provider configuration showing the second factor and the sign-in paths in scope, reviewed 11 Oct | Reviewed with exception | 11 Oct | 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. |
| CIS Controls v8 6.3 | Require MFA for Externally-Exposed Applications | Supporting | Head of Security | attached: identity-provider configuration showing the second factor and the sign-in paths in scope, reviewed 11 Oct | Reviewed with exception | 11 Oct | 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. |
| PCI DSS 4.0 Requirement 8 | Identify Users and Authenticate Access to System Components | Direct | Head of Security | attached: identity-provider configuration showing the second factor and the sign-in paths in scope, reviewed 11 Oct | Reviewed with exception | 11 Oct | 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. |
| Control | Control area | Basis | Evidence owner | Evidence held | Review status | Review date | Limit |
|---|---|---|---|---|---|---|---|
| ISO 27001:2022 A.8.24 | Use of cryptography | Direct | Head of Infrastructure | attached: full-disk-encryption configuration record and the enrolled-device report, reviewed 11 Oct | Reviewed | 11 Oct | Establishes 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.10 | Storage media | Direct | Head of Infrastructure | attached: full-disk-encryption configuration record and the enrolled-device report, reviewed 11 Oct | Reviewed | 11 Oct | Establishes 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.1 | User end point devices | Direct | Head of Infrastructure | attached: full-disk-encryption configuration record and the enrolled-device report, reviewed 11 Oct | Reviewed | 11 Oct | Establishes 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.1 | Logical access security over protected information assets | Direct | Head of Infrastructure | attached: full-disk-encryption configuration record and the enrolled-device report, reviewed 11 Oct | Reviewed | 11 Oct | Establishes 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.7 | Restricting and protecting information in transmission, movement and removal | Supporting | Head of Infrastructure | attached: full-disk-encryption configuration record and the enrolled-device report, reviewed 11 Oct | Reviewed | 11 Oct | Establishes 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-01 | The confidentiality, integrity, and availability of data-at-rest are protected | Direct | Head of Infrastructure | attached: full-disk-encryption configuration record and the enrolled-device report, reviewed 11 Oct | Reviewed | 11 Oct | Establishes 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-06 | Physical access to assets is managed, monitored, and enforced commensurate with risk | Supporting | Risk and Compliance Lead | attached: device-management enrolment report for the mobile estate, reviewed 11 Oct | Reviewed | 11 Oct | Establishes the mobile or BYOD control the question names; it does not establish the state of every personal device. |
| CIS Controls v8 3.6 | Encrypt Data on End-User Devices | Direct | Head of Infrastructure | attached: full-disk-encryption configuration record and the enrolled-device report, reviewed 11 Oct | Reviewed | 11 Oct | Establishes 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.11 | Encrypt Sensitive Data at Rest | Supporting | Head of Infrastructure | attached: full-disk-encryption configuration record and the enrolled-device report, reviewed 11 Oct | Reviewed | 11 Oct | Establishes 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 3 | Protect Stored Account Data | Supporting | Head of Infrastructure | attached: full-disk-encryption configuration record and the enrolled-device report, reviewed 11 Oct | Reviewed | 11 Oct | Establishes 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.
| Control | Control area | Basis | Evidence owner | Evidence held | Review status | Review date | Limit |
|---|---|---|---|---|---|---|---|
| ISO 27001:2022 A.8.24 | Use of cryptography | Direct | Head of Infrastructure | attached: full-disk-encryption configuration record and the enrolled-device report, reviewed 12 Oct | Reviewed | 12 Oct | Establishes 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.10 | Storage media | Direct | Head of Infrastructure | attached: full-disk-encryption configuration record and the enrolled-device report, reviewed 12 Oct | Reviewed | 12 Oct | Establishes 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.1 | Logical access security over protected information assets | Direct | Head of Infrastructure | attached: full-disk-encryption configuration record and the enrolled-device report, reviewed 12 Oct | Reviewed | 12 Oct | Establishes 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.7 | Restricting and protecting information in transmission, movement and removal | Direct | Head of Infrastructure | attached: TLS configuration and the certificate inventory, reviewed 12 Oct | Reviewed | 12 Oct | Establishes protection of data while it moves; it does not establish protection of the same data at rest. |
| NIST CSF 2.0 PR.DS-01 | The confidentiality, integrity, and availability of data-at-rest are protected | Direct | Head of Infrastructure | attached: full-disk-encryption configuration record and the enrolled-device report, reviewed 12 Oct | Reviewed | 12 Oct | Establishes 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-02 | The confidentiality, integrity, and availability of data-in-transit are protected | Direct | Head of Infrastructure | attached: TLS configuration and the certificate inventory, reviewed 12 Oct | Reviewed | 12 Oct | Establishes protection of data while it moves; it does not establish protection of the same data at rest. |
| CIS Controls v8 3.11 | Encrypt Sensitive Data at Rest | Direct | Head of Infrastructure | attached: full-disk-encryption configuration record and the enrolled-device report, reviewed 12 Oct | Reviewed | 12 Oct | Establishes 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.10 | Encrypt Sensitive Data in Transit | Direct | Head of Infrastructure | attached: TLS configuration and the certificate inventory, reviewed 12 Oct | Reviewed | 12 Oct | Establishes protection of data while it moves; it does not establish protection of the same data at rest. |
| PCI DSS 4.0 Requirement 3 | Protect Stored Account Data | Supporting | Head of Infrastructure | attached: full-disk-encryption configuration record and the enrolled-device report, reviewed 12 Oct | Reviewed | 12 Oct | Establishes 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 4 | Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks | Supporting | Head of Infrastructure | attached: TLS configuration and the certificate inventory, reviewed 12 Oct | Reviewed | 12 Oct | Establishes protection of data while it moves; it does not establish protection of the same data at rest. |
| Control | Control area | Basis | Evidence owner | Evidence held | Review status | Review date | Limit |
|---|---|---|---|---|---|---|---|
| ISO 27001:2022 A.5.3 | Segregation of duties | Direct | Risk and Compliance Lead | attached: supplier bank-account verification record and the dated call log, reviewed 12 Oct | Reviewed | 12 Oct | Establishes 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.19 | Information security in supplier relationships | Supporting | Risk and Compliance Lead | attached: supplier bank-account verification record and the dated call log, reviewed 12 Oct | Reviewed | 12 Oct | Establishes 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.3 | Information security awareness, education and training | Supporting | Finance Controller | attached: payment approval record and the two-person authorisation log, reviewed 12 Oct | Reviewed | 12 Oct | Establishes 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.3 | Role-based access, least privilege and segregation of duties | Direct | Risk and Compliance Lead | attached: supplier bank-account verification record and the dated call log, reviewed 12 Oct | Reviewed | 12 Oct | Establishes 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.3 | Considering fraud risk (COSO principle 8) | Supporting | Risk and Compliance Lead | attached: supplier bank-account verification record and the dated call log, reviewed 12 Oct | Reviewed | 12 Oct | Establishes 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-05 | Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties | Direct | Risk and Compliance Lead | attached: supplier bank-account verification record and the dated call log, reviewed 12 Oct | Reviewed | 12 Oct | Establishes 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-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 | Risk and Compliance Lead | attached: supplier bank-account verification record and the dated call log, reviewed 12 Oct | Reviewed | 12 Oct | Establishes the verification step the wording names; it does not establish the wider payment approval workflow or the threshold above which a second approval applies. |
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
| Question | Exception logged | Compensating control | Owner | Review status | Review 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 Security | Exception 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 Manager | Resolved by the control owner on 13 Oct | 13 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.