Cyber Insurance Application Scannermap an application to controls

SURA Technology Risks Pty Ltd (SURA Cyber) cyber policy application, held

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

The questions of the Cyber Insurance Proposal Form (form SCCIPF 1.0 11-2024; earlier edition STRCIPF 1.0 03-2024), 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 Insurance Proposal Form (form SCCIPF 1.0 11-2024; earlier edition STRCIPF 1.0 03-2024) (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. SURA Technology Risks Pty Ltd (SURA Cyber) is a source document, never a customer.

This document

Form identifierSCCIPF
Edition or versionform SCCIPF 1.0 11-2024, with the earlier STRCIPF 1.0 03-2024 edition
JurisdictionAustralia
ProductCyber Insurance
Application typeproposal form
Scope conditionsan Australian proposal form; the proposal together with any other information supplied forms the basis of the contract of insurance
Page referencespages 1 to 5

This document's questions reach 92 of 487 controls. Whether an applicant is offered cover is the carrier’s underwriting decision. 5 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 How many unique Personally Identifiable Information (PII) / Payment Card Industry (PCI) data, or Protected Health Information (PHI) records do you store on your system?
SURA Technology Risks Pty Ltd (SURA Cyber) application question

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

Facets (activity, control, population, threshold, frequency, exception): population: Personally Identifiable Information

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

Application question Do you encrypt all sensitive and confidential information stored on your organisation's systems and networks?
SURA Technology Risks Pty Ltd (SURA Cyber) application question

Facets (activity, control, population, threshold, frequency, exception): control: Do you encrypt all sensitive and confidential information stored on your organisation's systems and networks?

ISO 27001:2022 A.8.24 Use of cryptography
Direct mapping: this control is what the question asks about. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the disk-encryption configuration record, naming the algorithm and key length in use
  • a sample of enrolled-device or full-disk-encryption reports showing which laptops, desktops and portable media are covered
  • the exception report for any device not yet encrypted, with the date it was raised
ISO 27001:2022 A.7.10 Storage media
Direct mapping: this control is what the question asks about. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the disk-encryption configuration record, naming the algorithm and key length in use
  • a sample of enrolled-device or full-disk-encryption reports showing which laptops, desktops and portable media are covered
  • the exception report for any device not yet encrypted, with the date it was raised
SOC 2 CC6.1 Logical access security over protected information assets
Direct mapping: this control is what the question asks about. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the disk-encryption configuration record, naming the algorithm and key length in use
  • a sample of enrolled-device or full-disk-encryption reports showing which laptops, desktops and portable media are covered
  • the exception report for any device not yet encrypted, with the date it was raised
SOC 2 CC6.7 Restricting and protecting information in transmission, movement and removal
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the disk-encryption configuration record, naming the algorithm and key length in use
  • a sample of enrolled-device or full-disk-encryption reports showing which laptops, desktops and portable media are covered
  • the exception report for any device not yet encrypted, with the date it was raised
NIST CSF 2.0 PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected
Direct mapping: this control is what the question asks about. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the disk-encryption configuration record, naming the algorithm and key length in use
  • a sample of enrolled-device or full-disk-encryption reports showing which laptops, desktops and portable media are covered
  • the exception report for any device not yet encrypted, with the date it was raised
CIS Controls v8 3.11 Encrypt Sensitive Data at Rest
Direct mapping: this control is what the question asks about. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the disk-encryption configuration record, naming the algorithm and key length in use
  • a sample of enrolled-device or full-disk-encryption reports showing which laptops, desktops and portable media are covered
  • the exception report for any device not yet encrypted, with the date it was raised
PCI DSS 4.0 Requirement 3 Protect Stored Account Data
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)
  • the disk-encryption configuration record, naming the algorithm and key length in use
  • a sample of enrolled-device or full-disk-encryption reports showing which laptops, desktops and portable media are covered
  • the exception report for any device not yet encrypted, with the date it was raised
Application question Do you encrypt sensitive data that is physically removed from your premises by mobile device (e.g. laptop / USB / mobile phones)?
SURA Technology Risks Pty Ltd (SURA Cyber) application question

Facets (activity, control, population, threshold, frequency, exception): control: Do you encrypt sensitive data that is physically removed from your premises by mobile device (e.g. laptop / USB / mobile phones)?

ISO 27001:2022 A.8.24 Use of cryptography
Direct mapping: this control is what the question asks about. Limit: Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
Evidence to have on file (guidance, our wording)
  • the cryptography policy naming the approved algorithms, key lengths and where each applies
  • a configuration record for the system or data store the question names
  • a sample showing the encryption setting in place
ISO 27001:2022 A.7.1 Physical security perimeters
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the physical or environmental control named; it does not establish the security of every site.
Evidence to have on file (guidance, our wording)
  • the physical-access record for the site the question names
  • the rule on who may enter which area, and how visitors are handled
  • a sample of a recent access or visitor record
ISO 27001:2022 A.7.2 Physical entry
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the physical or environmental control named; it does not establish the security of every site.
Evidence to have on file (guidance, our wording)
  • the physical-access record for the site the question names
  • the rule on who may enter which area, and how visitors are handled
  • a sample of a recent access or visitor record
SOC 2 CC6.1 Logical access security over protected information assets
Direct mapping: this control is what the question asks about. Limit: Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
Evidence to have on file (guidance, our wording)
  • the cryptography policy naming the approved algorithms, key lengths and where each applies
  • a configuration record for the system or data store the question names
  • a sample showing the encryption setting in place
SOC 2 CC6.4 Restricting physical access to facilities and assets
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the physical or environmental control named; it does not establish the security of every site.
Evidence to have on file (guidance, our wording)
  • the physical-access record for the site the question names
  • the rule on who may enter which area, and how visitors are handled
  • a sample of a recent access or visitor record
NIST CSF 2.0 PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected
Direct mapping: this control is what the question asks about. Limit: Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
Evidence to have on file (guidance, our wording)
  • the cryptography policy naming the approved algorithms, key lengths and where each applies
  • a configuration record for the system or data store the question names
  • a sample showing the encryption setting in place
NIST CSF 2.0 PR.AA-06 Physical access to assets is managed, monitored, and enforced 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 physical or environmental control named; it does not establish the security of every site.
Evidence to have on file (guidance, our wording)
  • the physical-access record for the site the question names
  • the rule on who may enter which area, and how visitors are handled
  • a sample of a recent access or visitor record
CIS Controls v8 3.11 Encrypt Sensitive Data at Rest
Direct mapping: this control is what the question asks about. Limit: Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
Evidence to have on file (guidance, our wording)
  • the cryptography policy naming the approved algorithms, key lengths and where each applies
  • a configuration record for the system or data store the question names
  • a sample showing the encryption setting in place
PCI DSS 4.0 Requirement 3 Protect Stored Account Data
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)
  • the cryptography policy naming the approved algorithms, key lengths and where each applies
  • a configuration record for the system or data store the question names
  • a sample showing the encryption setting in place
Application question Do you require MFA (multi-factor authentication) for remote access to network?
SURA Technology Risks Pty Ltd (SURA Cyber) 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: Do you require MFA (multi-factor authentication) for remote access to network?

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
ISO 27001:2022 A.6.7 Remote working
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes how remote access is provided or restricted; it does not establish the endpoint posture of the connecting device.
Evidence to have on file (guidance, our wording)
  • the VPN or remote-access gateway configuration and the authentication it requires
  • a report of active remote sessions, or of the users and devices allowed to connect remotely
  • the written rule stating how remote access is granted, logged and restricted
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
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 how remote access is provided or restricted; it does not establish the endpoint posture of the connecting device.
Evidence to have on file (guidance, our wording)
  • the VPN or remote-access gateway configuration and the authentication it requires
  • a report of active remote sessions, or of the users and devices allowed to connect remotely
  • the written rule stating how remote access is granted, logged and restricted
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
NIST CSF 2.0 PR.IR-01 Networks and environments are protected from unauthorized logical access and usage
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes how remote access is provided or restricted; it does not establish the endpoint posture of the connecting device.
Evidence to have on file (guidance, our wording)
  • the VPN or remote-access gateway configuration and the authentication it requires
  • a report of active remote sessions, or of the users and devices allowed to connect remotely
  • the written rule stating how remote access is granted, logged and restricted
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 Do you require MFA (multi-factor authentication) for privileged accounts?
SURA Technology Risks Pty Ltd (SURA Cyber) application question

Answer options on this form: No / Yes.

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: Do you require MFA (multi-factor authentication) for privileged accounts?; population: accounts

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
ISO 27001:2022 A.8.2 Privileged access rights
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file (guidance, our wording)
  • the privileged-access or PAM configuration showing who holds administrative rights and how they are granted
  • a dated privileged-account access review, with the approval for standing or just-in-time access
  • the report of administrative accounts and their last activity
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
SOC 2 CC6.3 Role-based access, least privilege and segregation of duties
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file (guidance, our wording)
  • the privileged-access or PAM configuration showing who holds administrative rights and how they are granted
  • a dated privileged-account access review, with the approval for standing or just-in-time access
  • the report of administrative accounts and their last activity
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
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
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file (guidance, our wording)
  • the privileged-access or PAM configuration showing who holds administrative rights and how they are granted
  • a dated privileged-account access review, with the approval for standing or just-in-time access
  • the report of administrative accounts and their last activity
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
ACSC Essential Eight ADMIN Restrict administrative privileges
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file (guidance, our wording)
  • the privileged-access or PAM configuration showing who holds administrative rights and how they are granted
  • a dated privileged-account access review, with the approval for standing or just-in-time access
  • the report of administrative accounts and their last activity
CIS Controls v8 6.5 Require MFA for Administrative 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.4 Require MFA for Remote Network 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
PCI DSS 4.0 Requirement 7 Restrict Access to System Components and Cardholder Data by Business Need to Know
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file (guidance, our wording)
  • the privileged-access or PAM configuration showing who holds administrative rights and how they are granted
  • a dated privileged-account access review, with the approval for standing or just-in-time access
  • the report of administrative accounts and their last activity
Application question Do you require MFA (multi-factor authentication) for back-ups (internal and external)?
SURA Technology Risks Pty Ltd (SURA Cyber) 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: Do you require MFA (multi-factor authentication) for back-ups (internal and external)?

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
ISO 27001:2022 A.8.13 Information backup
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file (guidance, our wording)
  • the backup configuration and schedule, and the restore-test record with its date
  • the report of the last successful restore, or the notes of a restore drill
  • the rule on backup retention and how copies are kept
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
SOC 2 A1.2 Environmental protection, backup and recovery infrastructure
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file (guidance, our wording)
  • the backup configuration and schedule, and the restore-test record with its date
  • the report of the last successful restore, or the notes of a restore drill
  • the rule on backup retention and how copies are kept
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
NIST CSF 2.0 PR.DS-11 Backups of data are created, protected, maintained, and tested
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file (guidance, our wording)
  • the backup configuration and schedule, and the restore-test record with its date
  • the report of the last successful restore, or the notes of a restore drill
  • the rule on backup retention and how copies are kept
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
ACSC Essential Eight BACKUP Regular backups
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file (guidance, our wording)
  • the backup configuration and schedule, and the restore-test record with its date
  • the report of the last successful restore, or the notes of a restore drill
  • the rule on backup retention and how copies are kept
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 Do you require MFA (multi-factor authentication) for web application email access?
SURA Technology Risks Pty Ltd (SURA Cyber) 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: Do you require MFA (multi-factor authentication) for web application email 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
ISO 27001:2022 A.5.15 Access control
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the web or personal-email access control asked about; it does not establish the posture of the device used.
Evidence to have on file (guidance, our wording)
  • the configuration for the web or personal-email access the question names
  • a sample of the access rule applied to a user or group
  • the rule on what may be reached from outside the corporate network
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 Do you use a next generation antivirus (NGAV) product or Endpoint Detection Response (EDR) tool to protect all endpoints across your enterprise?
SURA Technology Risks Pty Ltd (SURA Cyber) 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: Do you use a next generation antivirus (NGAV) product or Endpoint Detection Response (EDR) tool to protect all endpoints across your enterprise?

ISO 27001:2022 A.8.7 Protection against malware
Direct mapping: this control is what the question asks about. Limit: Establishes the endpoint or malware control the question names; it does not establish coverage of every endpoint or that the tool was effective in an incident.
Evidence to have on file (guidance, our wording)
  • the endpoint-protection or EDR console report showing coverage and the last agent update
  • a sample of a detection or quarantine event and its handling
  • the anti-malware or EDR policy, including any exclusions
ISO 27001:2022 A.8.1 User end point devices
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the endpoint or malware control the question names; it does not establish coverage of every endpoint or that the tool was effective in an incident.
Evidence to have on file (guidance, our wording)
  • the endpoint-protection or EDR console report showing coverage and the last agent update
  • a sample of a detection or quarantine event and its handling
  • the anti-malware or EDR policy, including any exclusions
SOC 2 CC6.8 Preventing and detecting unauthorised or malicious software
Direct mapping: this control is what the question asks about. Limit: Establishes the endpoint or malware control the question names; it does not establish coverage of every endpoint or that the tool was effective in an incident.
Evidence to have on file (guidance, our wording)
  • the endpoint-protection or EDR console report showing coverage and the last agent update
  • a sample of a detection or quarantine event and its handling
  • the anti-malware or EDR policy, including any exclusions
NIST CSF 2.0 PR.PS-05 Installation and execution of unauthorized software are prevented
Direct mapping: this control is what the question asks about. Limit: Establishes the endpoint or malware control the question names; it does not establish coverage of every endpoint or that the tool was effective in an incident.
Evidence to have on file (guidance, our wording)
  • the endpoint-protection or EDR console report showing coverage and the last agent update
  • a sample of a detection or quarantine event and its handling
  • the anti-malware or EDR policy, including any exclusions
NIST CSF 2.0 DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the endpoint or malware control the question names; it does not establish coverage of every endpoint or that the tool was effective in an incident.
Evidence to have on file (guidance, our wording)
  • the endpoint-protection or EDR console report showing coverage and the last agent update
  • a sample of a detection or quarantine event and its handling
  • the anti-malware or EDR policy, including any exclusions
PCI DSS 4.0 Requirement 5 Protect All Systems and Networks from Malicious Software
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the endpoint or malware control the question names; it does not establish coverage of every endpoint or that the tool was effective in an incident. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)
  • the endpoint-protection or EDR console report showing coverage and the last agent update
  • a sample of a detection or quarantine event and its handling
  • the anti-malware or EDR policy, including any exclusions
Application question Please confirm how quickly critical patches are carried out.
SURA Technology Risks Pty Ltd (SURA Cyber) application question

Facets (activity, control, population, threshold, frequency, exception): control: Please confirm how quickly critical patches are carried out.

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 Please confirm how frequently you back up systems?
SURA Technology Risks Pty Ltd (SURA Cyber) application question

Facets (activity, control, population, threshold, frequency, exception): control: Please confirm how frequently you back up systems?

ISO 27001:2022 A.8.13 Information backup
Direct mapping: this control is what the question asks about. Limit: Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file (guidance, our wording)
  • the backup configuration and schedule, and the restore-test record with its date
  • the report of the last successful restore, or the notes of a restore drill
  • the rule on backup retention and how copies are kept
ISO 27001:2022 A.8.14 Redundancy of information processing facilities
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file (guidance, our wording)
  • the backup configuration and schedule, and the restore-test record with its date
  • the report of the last successful restore, or the notes of a restore drill
  • the rule on backup retention and how copies are kept
SOC 2 A1.2 Environmental protection, backup and recovery infrastructure
Direct mapping: this control is what the question asks about. Limit: Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file (guidance, our wording)
  • the backup configuration and schedule, and the restore-test record with its date
  • the report of the last successful restore, or the notes of a restore drill
  • the rule on backup retention and how copies are kept
SOC 2 A1.3 Testing recovery plan procedures
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file (guidance, our wording)
  • the backup configuration and schedule, and the restore-test record with its date
  • the report of the last successful restore, or the notes of a restore drill
  • the rule on backup retention and how copies are kept
NIST CSF 2.0 PR.DS-11 Backups of data are created, protected, maintained, and tested
Direct mapping: this control is what the question asks about. Limit: Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file (guidance, our wording)
  • the backup configuration and schedule, and the restore-test record with its date
  • the report of the last successful restore, or the notes of a restore drill
  • the rule on backup retention and how copies are kept
ACSC Essential Eight BACKUP Regular backups
Direct mapping: this control is what the question asks about. Limit: Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file (guidance, our wording)
  • the backup configuration and schedule, and the restore-test record with its date
  • the report of the last successful restore, or the notes of a restore drill
  • the rule on backup retention and how copies are kept
CIS Controls v8 11.2 Perform Automated Backups
Direct mapping: this control is what the question asks about. Limit: Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file (guidance, our wording)
  • the backup configuration and schedule, and the restore-test record with its date
  • the report of the last successful restore, or the notes of a restore drill
  • the rule on backup retention and how copies are kept
CIS Controls v8 11.4 Establish and Maintain an Isolated Instance of Recovery Data
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file (guidance, our wording)
  • the backup configuration and schedule, and the restore-test record with its date
  • the report of the last successful restore, or the notes of a restore drill
  • the rule on backup retention and how copies are kept
CIS Controls v8 11.5 Test Data Recovery
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file (guidance, our wording)
  • the backup configuration and schedule, and the restore-test record with its date
  • the report of the last successful restore, or the notes of a restore drill
  • the rule on backup retention and how copies are kept
Application question Do you have an incident response plan or business continuity plan in place? If yes, is it tested at least annually?
SURA Technology Risks Pty Ltd (SURA Cyber) application question

Facets (activity, control, population, threshold, frequency, exception): control: Do you have an incident response plan or business continuity plan in place? If yes, is it tested at least annually?; frequency: at least annually

ISO 27001:2022 A.5.29 Information security during disruption
Direct mapping: this control is what the question asks about. Limit: Establishes the continuity or recovery planning asked about; it does not establish that the plan was exercised or that recovery objectives were met.
Evidence to have on file (guidance, our wording)
  • the business-continuity or disaster-recovery plan with its recovery objectives
  • the record of the last test or exercise, with the date and the outcome
  • the list of critical systems and the failover arrangement for each
ISO 27001:2022 A.5.30 ICT readiness for business continuity
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the continuity or recovery planning asked about; it does not establish that the plan was exercised or that recovery objectives were met.
Evidence to have on file (guidance, our wording)
  • the business-continuity or disaster-recovery plan with its recovery objectives
  • the record of the last test or exercise, with the date and the outcome
  • the list of critical systems and the failover arrangement for each
ISO 27001:2022 A.8.14 Redundancy of information processing facilities
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the continuity or recovery planning asked about; it does not establish that the plan was exercised or that recovery objectives were met.
Evidence to have on file (guidance, our wording)
  • the business-continuity or disaster-recovery plan with its recovery objectives
  • the record of the last test or exercise, with the date and the outcome
  • the list of critical systems and the failover arrangement for each
SOC 2 CC9.1 Mitigating risks of business disruption
Direct mapping: this control is what the question asks about. Limit: Establishes the continuity or recovery planning asked about; it does not establish that the plan was exercised or that recovery objectives were met.
Evidence to have on file (guidance, our wording)
  • the business-continuity or disaster-recovery plan with its recovery objectives
  • the record of the last test or exercise, with the date and the outcome
  • the list of critical systems and the failover arrangement for each
SOC 2 A1.2 Environmental protection, backup and recovery infrastructure
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the continuity or recovery planning asked about; it does not establish that the plan was exercised or that recovery objectives were met.
Evidence to have on file (guidance, our wording)
  • the business-continuity or disaster-recovery plan with its recovery objectives
  • the record of the last test or exercise, with the date and the outcome
  • the list of critical systems and the failover arrangement for each
NIST CSF 2.0 PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations
Direct mapping: this control is what the question asks about. Limit: Establishes the continuity or recovery planning asked about; it does not establish that the plan was exercised or that recovery objectives were met.
Evidence to have on file (guidance, our wording)
  • the business-continuity or disaster-recovery plan with its recovery objectives
  • the record of the last test or exercise, with the date and the outcome
  • the list of critical systems and the failover arrangement for each
NIST CSF 2.0 RC.RP-01 The recovery portion of the incident response plan is executed once initiated from the incident response process
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the continuity or recovery planning asked about; it does not establish that the plan was exercised or that recovery objectives were met.
Evidence to have on file (guidance, our wording)
  • the business-continuity or disaster-recovery plan with its recovery objectives
  • the record of the last test or exercise, with the date and the outcome
  • the list of critical systems and the failover arrangement for each
ACSC Essential Eight BACKUP Regular backups
Direct mapping: this control is what the question asks about. Limit: Establishes the continuity or recovery planning asked about; it does not establish that the plan was exercised or that recovery objectives were met.
Evidence to have on file (guidance, our wording)
  • the business-continuity or disaster-recovery plan with its recovery objectives
  • the record of the last test or exercise, with the date and the outcome
  • the list of critical systems and the failover arrangement for each
APRA CPS 234 para 24 Maintain information security response plans
Direct mapping: this control is what the question asks about. Limit: Establishes the continuity or recovery planning asked about; it does not establish that the plan was exercised or that recovery objectives were met.
Evidence to have on file (guidance, our wording)
  • the business-continuity or disaster-recovery plan with its recovery objectives
  • the record of the last test or exercise, with the date and the outcome
  • the list of critical systems and the failover arrangement for each
APRA CPS 234 para 26 Annual review and testing of response plans
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the continuity or recovery planning asked about; it does not establish that the plan was exercised or that recovery objectives were met.
Evidence to have on file (guidance, our wording)
  • the business-continuity or disaster-recovery plan with its recovery objectives
  • the record of the last test or exercise, with the date and the outcome
  • the list of critical systems and the failover arrangement for each
APRA CPS 234 para 23 Detect and respond to incidents promptly
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes planning for, or handling of, the incidents named; it does not establish that a real incident was contained within a stated time.
Evidence to have on file (guidance, our wording)
  • the incident-response plan and its contact or escalation list
  • the record of the last tabletop exercise or plan test, with the date
  • the forensic retainer, or the named handler for a confirmed incident
APRA CPS 234 para 25 Response plan content: stages and escalation
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes planning for, or handling of, the incidents named; it does not establish that a real incident was contained within a stated time.
Evidence to have on file (guidance, our wording)
  • the incident-response plan and its contact or escalation list
  • the record of the last tabletop exercise or plan test, with the date
  • the forensic retainer, or the named handler for a confirmed incident
CIS Controls v8 11.1 Establish and Maintain a Data Recovery Process
Direct mapping: this control is what the question asks about. Limit: Establishes the continuity or recovery planning asked about; it does not establish that the plan was exercised or that recovery objectives were met.
Evidence to have on file (guidance, our wording)
  • the business-continuity or disaster-recovery plan with its recovery objectives
  • the record of the last test or exercise, with the date and the outcome
  • the list of critical systems and the failover arrangement for each
CIS Controls v8 11.5 Test Data Recovery
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the continuity or recovery planning asked about; it does not establish that the plan was exercised or that recovery objectives were met.
Evidence to have on file (guidance, our wording)
  • the business-continuity or disaster-recovery plan with its recovery objectives
  • the record of the last test or exercise, with the date and the outcome
  • the list of critical systems and the failover arrangement for each
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 planning for, or handling of, the incidents named; it does not establish that a real incident was contained within a stated time. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)
  • the incident-response plan and its contact or escalation list
  • the record of the last tabletop exercise or plan test, with the date
  • the forensic retainer, or the named handler for a confirmed incident
Application question Do you have a privacy policy available which includes details of data retention and destruction?
SURA Technology Risks Pty Ltd (SURA Cyber) application question

Facets (activity, control, population, threshold, frequency, exception): control: Do you have a privacy policy available which includes details of data retention and destruction?

ISO 27001:2022 A.5.33 Protection of records
Direct mapping: this control is what the question asks about. Limit: Establishes the retention or disposal practice asked about; it does not establish that every record followed it.
Evidence to have on file (guidance, our wording)
  • the retention schedule for the records the question names
  • the disposal or destruction record for a dated batch, with the method
  • the rule on re-use or secure disposal of equipment
ISO 27001:2022 A.8.10 Information deletion
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the retention or disposal practice asked about; it does not establish that every record followed it.
Evidence to have on file (guidance, our wording)
  • the retention schedule for the records the question names
  • the disposal or destruction record for a dated batch, with the method
  • the rule on re-use or secure disposal of equipment
ISO 27001:2022 A.7.14 Secure disposal or re-use of equipment
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the retention or disposal practice asked about; it does not establish that every record followed it.
Evidence to have on file (guidance, our wording)
  • the retention schedule for the records the question names
  • the disposal or destruction record for a dated batch, with the method
  • the rule on re-use or secure disposal of equipment
SOC 2 P4.2 Retaining personal information
Direct mapping: this control is what the question asks about. Limit: Establishes the retention or disposal practice asked about; it does not establish that every record followed it.
Evidence to have on file (guidance, our wording)
  • the retention schedule for the records the question names
  • the disposal or destruction record for a dated batch, with the method
  • the rule on re-use or secure disposal of equipment
SOC 2 P4.3 Securely disposing of personal information
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the retention or disposal practice asked about; it does not establish that every record followed it.
Evidence to have on file (guidance, our wording)
  • the retention schedule for the records the question names
  • the disposal or destruction record for a dated batch, with the method
  • the rule on re-use or secure disposal of equipment
NIST CSF 2.0 PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected
Direct mapping: this control is what the question asks about. Limit: Establishes the retention or disposal practice asked about; it does not establish that every record followed it.
Evidence to have on file (guidance, our wording)
  • the retention schedule for the records the question names
  • the disposal or destruction record for a dated batch, with the method
  • the rule on re-use or secure disposal of equipment
NIST CSF 2.0 GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the privacy practice or notice asked about; it does not establish compliance with every applicable privacy law.
Evidence to have on file (guidance, our wording)
  • the privacy notice or policy the question names, with its review date
  • the record of how personal information is collected, used and shared
  • the rule on requests about personal information and how they are answered
PCI DSS 4.0 Requirement 3 Protect Stored Account Data
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the retention or disposal practice asked about; it does not establish that every record followed it. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)
  • the retention schedule for the records the question names
  • the disposal or destruction record for a dated batch, with the method
  • the rule on re-use or secure disposal of equipment
Application question Do all employees receive social engineering training? If yes, does this include phishing simulations?
SURA Technology Risks Pty Ltd (SURA Cyber) application question

Facets (activity, control, population, threshold, frequency, exception): control: Do all employees receive social engineering training? If yes, does this include phishing simulations?; population: all employees

ISO 27001:2022 A.8.23 Web filtering
Direct mapping: this control is what the question asks about. Limit: Establishes the email control the question names; it does not establish that every malicious message was caught or reported.
Evidence to have on file (guidance, our wording)
  • the email-filtering configuration and the checks it applies to inbound mail
  • a sample of blocked or quarantined messages and their handling
  • the rule on external-message tagging and user reporting
ISO 27001:2022 A.8.7 Protection against malware
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the email control the question names; it does not establish that every malicious message was caught or reported.
Evidence to have on file (guidance, our wording)
  • the email-filtering configuration and the checks it applies to inbound mail
  • a sample of blocked or quarantined messages and their handling
  • the rule on external-message tagging and user reporting
ISO 27001:2022 A.5.14 Information transfer
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the email control the question names; it does not establish that every malicious message was caught or reported.
Evidence to have on file (guidance, our wording)
  • the email-filtering configuration and the checks it applies to inbound mail
  • a sample of blocked or quarantined messages and their handling
  • the rule on external-message tagging and user reporting
SOC 2 CC6.8 Preventing and detecting unauthorised or malicious software
Direct mapping: this control is what the question asks about. Limit: Establishes the email control the question names; it does not establish that every malicious message was caught or reported.
Evidence to have on file (guidance, our wording)
  • the email-filtering configuration and the checks it applies to inbound mail
  • a sample of blocked or quarantined messages and their handling
  • the rule on external-message tagging and user reporting
SOC 2 CC1.4 Attracting, developing and retaining competent people (COSO principle 4)
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes that training is provided; it does not establish that every user completed it or changed behaviour.
Evidence to have on file (guidance, our wording)
  • the security-awareness programme content and its schedule
  • the completion record for the last round of training, with the date
  • a sample of a phishing-simulation result and the follow-up
NIST CSF 2.0 PR.PS-05 Installation and execution of unauthorized software are prevented
Direct mapping: this control is what the question asks about. Limit: Establishes the email control the question names; it does not establish that every malicious message was caught or reported.
Evidence to have on file (guidance, our wording)
  • the email-filtering configuration and the checks it applies to inbound mail
  • a sample of blocked or quarantined messages and their handling
  • the rule on external-message tagging and user reporting
NIST CSF 2.0 PR.AT-01 Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes that training is provided; it does not establish that every user completed it or changed behaviour.
Evidence to have on file (guidance, our wording)
  • the security-awareness programme content and its schedule
  • the completion record for the last round of training, with the date
  • a sample of a phishing-simulation result and the follow-up
CIS Controls v8 9.5 Implement DMARC
Direct mapping: this control is what the question asks about. Limit: Establishes the email control the question names; it does not establish that every malicious message was caught or reported.
Evidence to have on file (guidance, our wording)
  • the email-filtering configuration and the checks it applies to inbound mail
  • a sample of blocked or quarantined messages and their handling
  • the rule on external-message tagging and user reporting
CIS Controls v8 9.4 Restrict Unnecessary or Unauthorized Browser and Email Client Extensions
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the email control the question names; it does not establish that every malicious message was caught or reported.
Evidence to have on file (guidance, our wording)
  • the email-filtering configuration and the checks it applies to inbound mail
  • a sample of blocked or quarantined messages and their handling
  • the rule on external-message tagging and user reporting
CIS Controls v8 9.7 Deploy and Maintain Email Server Anti-Malware Protections
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the email control the question names; it does not establish that every malicious message was caught or reported.
Evidence to have on file (guidance, our wording)
  • the email-filtering configuration and the checks it applies to inbound mail
  • a sample of blocked or quarantined messages and their handling
  • the rule on external-message tagging and user reporting
PCI DSS 4.0 Requirement 5 Protect All Systems and Networks from Malicious Software
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the email control the question names; it does not establish that every malicious message was caught or reported. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)
  • the email-filtering configuration and the checks it applies to inbound mail
  • a sample of blocked or quarantined messages and their handling
  • the rule on external-message tagging and user reporting
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 that training is provided; it does not establish that every user completed it or changed behaviour. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)
  • the security-awareness programme content and its schedule
  • the completion record for the last round of training, with the date
  • a sample of a phishing-simulation result and the follow-up
Application question Do you have controls in place ensuring timely removal of system access when an employee leaves the organisation, or when access is no longer required for business purposes?
SURA Technology Risks Pty Ltd (SURA Cyber) application question

Facets (activity, control, population, threshold, frequency, exception): control: Do you have controls in place ensuring timely removal of system access when an employee leaves the organisation, or when access is no longer required for business purposes?; population: employee

ISO 27001:2022 A.5.15 Access control
Direct mapping: this control is what the question asks about. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)
  • the access rule and the role or group model that enforces it
  • a dated access review showing rights were confirmed or removed
  • a sample of how access is granted and revoked for a leaver
ISO 27001:2022 A.5.16 Identity management
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)
  • the access rule and the role or group model that enforces it
  • a dated access review showing rights were confirmed or removed
  • a sample of how access is granted and revoked for a leaver
ISO 27001:2022 A.5.18 Access rights
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)
  • the access rule and the role or group model that enforces it
  • a dated access review showing rights were confirmed or removed
  • a sample of how access is granted and revoked for a leaver
SOC 2 CC6.1 Logical access security over protected information assets
Direct mapping: this control is what the question asks about. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)
  • the access rule and the role or group model that enforces it
  • a dated access review showing rights were confirmed or removed
  • a sample of how access is granted and revoked for a leaver
SOC 2 CC6.2 Registering and authorising users before issuing credentials
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)
  • the access rule and the role or group model that enforces it
  • a dated access review showing rights were confirmed or removed
  • a sample of how access is granted and revoked for a leaver
NIST CSF 2.0 PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization
Direct mapping: this control is what the question asks about. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)
  • the access rule and the role or group model that enforces it
  • a dated access review showing rights were confirmed or removed
  • a sample of how access is granted and revoked for a leaver
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
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)
  • the access rule and the role or group model that enforces it
  • a dated access review showing rights were confirmed or removed
  • a sample of how access is granted and revoked for a leaver
ACSC Essential Eight ADMIN Restrict administrative privileges
Direct mapping: this control is what the question asks about. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)
  • the access rule and the role or group model that enforces it
  • a dated access review showing rights were confirmed or removed
  • a sample of how access is granted and revoked for a leaver
CIS Controls v8 6.8 Define and Maintain Role-Based Access Control
Direct mapping: this control is what the question asks about. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)
  • the access rule and the role or group model that enforces it
  • a dated access review showing rights were confirmed or removed
  • a sample of how access is granted and revoked for a leaver
CIS Controls v8 6.1 Establish an Access Granting Process
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)
  • the access rule and the role or group model that enforces it
  • a dated access review showing rights were confirmed or removed
  • a sample of how access is granted and revoked for a leaver
CIS Controls v8 6.2 Establish an Access Revoking Process
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file (guidance, our wording)
  • the access rule and the role or group model that enforces it
  • a dated access review showing rights were confirmed or removed
  • a sample of how access is granted and revoked for a leaver
PCI DSS 4.0 Requirement 7 Restrict Access to System Components and Cardholder Data by Business Need to Know
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver. Applicability: applies where cardholder data is in scope
Evidence to have on file (guidance, our wording)
  • the access rule and the role or group model that enforces it
  • a dated access review showing rights were confirmed or removed
  • a sample of how access is granted and revoked for a leaver
Application question Does your organisation send and / or receive wire / electronic transfers? If yes, is approval by more than one employee required to initiate the transfer of funds?
SURA Technology Risks Pty Ltd (SURA Cyber) application question

Facets (activity, control, population, threshold, frequency, exception): control: Does your organisation send and / or receive wire / electronic transfers? If yes, is approval by more than one employee required to initiate the transfer of funds?; population: employee

ISO 27001:2022 A.5.3 Segregation of duties
Direct mapping: this control is what the question asks about. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the bank or treasury platform dual-authorisation setup and the payment approval workflow, showing a second approver on a different device above the threshold
  • the payment approval log, with a dated example above the threshold
  • the callback or out-of-band verification for a change to payee bank details, with a dated example
ISO 27001:2022 A.6.3 Information security awareness, education and training
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the bank or treasury platform dual-authorisation setup and the payment approval workflow, showing a second approver on a different device above the threshold
  • the payment approval log, with a dated example above the threshold
  • the callback or out-of-band verification for a change to payee bank details, with a dated example
ISO 27001:2022 A.8.5 Secure authentication
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the bank or treasury platform dual-authorisation setup and the payment approval workflow, showing a second approver on a different device above the threshold
  • the payment approval log, with a dated example above the threshold
  • the callback or out-of-band verification for a change to payee bank details, with a dated example
SOC 2 CC6.3 Role-based access, least privilege and segregation of duties
Direct mapping: this control is what the question asks about. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the bank or treasury platform dual-authorisation setup and the payment approval workflow, showing a second approver on a different device above the threshold
  • the payment approval log, with a dated example above the threshold
  • the callback or out-of-band verification for a change to payee bank details, with a dated example
SOC 2 CC3.3 Considering fraud risk (COSO principle 8)
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the bank or treasury platform dual-authorisation setup and the payment approval workflow, showing a second approver on a different device above the threshold
  • the payment approval log, with a dated example above the threshold
  • the callback or out-of-band verification for a change to payee bank details, with a dated example
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 mapping: this control is what the question asks about. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the bank or treasury platform dual-authorisation setup and the payment approval workflow, showing a second approver on a different device above the threshold
  • the payment approval log, with a dated example above the threshold
  • the callback or out-of-band verification for a change to payee bank details, with a dated example
Application question Do you have a call back procedure to initiate payment to a new bank account or to change banking details for an existing bank account (in respect of internal staff and external vendor / supplier / client requests)?
SURA Technology Risks Pty Ltd (SURA Cyber) application question

Facets (activity, control, population, threshold, frequency, exception): control: Do you have a call back procedure to initiate payment to a new bank account or to change banking details for an existing bank account (in respect of internal staff and external vendor / supplier / client requests)?; population: account

ISO 27001:2022 A.5.3 Segregation of duties
Direct mapping: this control is what the question asks about. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how
  • a contact channel verified before the request was made, held independently of the message that asked for the change
  • a dated record of the verification for the specific change, with the person who checked and the source used
ISO 27001:2022 A.5.19 Information security in supplier relationships
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how
  • a contact channel verified before the request was made, held independently of the message that asked for the change
  • a dated record of the verification for the specific change, with the person who checked and the source used
ISO 27001:2022 A.6.3 Information security awareness, education and training
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the bank or treasury platform dual-authorisation setup and the payment approval workflow, showing a second approver on a different device above the threshold
  • the payment approval log, with a dated example above the threshold
  • the callback or out-of-band verification for a change to payee bank details, with a dated example
SOC 2 CC6.3 Role-based access, least privilege and segregation of duties
Direct mapping: this control is what the question asks about. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how
  • a contact channel verified before the request was made, held independently of the message that asked for the change
  • a dated record of the verification for the specific change, with the person who checked and the source used
SOC 2 CC3.3 Considering fraud risk (COSO principle 8)
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how
  • a contact channel verified before the request was made, held independently of the message that asked for the change
  • a dated record of the verification for the specific change, with the person who checked and the source used
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 mapping: this control is what the question asks about. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how
  • a contact channel verified before the request was made, held independently of the message that asked for the change
  • a dated record of the verification for the specific change, with the person who checked and the source used
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 verification step the wording names; it does not establish the wider payment approval workflow or the threshold above which a second approval applies.
Evidence to have on file (guidance, our wording)
  • the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how
  • a contact channel verified before the request was made, held independently of the message that asked for the change
  • a dated record of the verification for the specific change, with the person who checked and the source used
Application question Do you have an approval threshold with your bank requiring a phone call from your bank to release funds on transfers over $25,000?
SURA Technology Risks Pty Ltd (SURA Cyber) application question

Facets (activity, control, population, threshold, frequency, exception): control: Do you have an approval threshold with your bank requiring a phone call from your bank to release funds on transfers over $25,000?; threshold: $25,000

ISO 27001:2022 A.5.3 Segregation of duties
Direct mapping: this control is what the question asks about. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the bank or treasury platform dual-authorisation setup and the payment approval workflow, showing a second approver on a different device above the threshold
  • the payment approval log, with a dated example above the threshold
  • the callback or out-of-band verification for a change to payee bank details, with a dated example
ISO 27001:2022 A.6.3 Information security awareness, education and training
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the bank or treasury platform dual-authorisation setup and the payment approval workflow, showing a second approver on a different device above the threshold
  • the payment approval log, with a dated example above the threshold
  • the callback or out-of-band verification for a change to payee bank details, with a dated example
ISO 27001:2022 A.8.5 Secure authentication
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the bank or treasury platform dual-authorisation setup and the payment approval workflow, showing a second approver on a different device above the threshold
  • the payment approval log, with a dated example above the threshold
  • the callback or out-of-band verification for a change to payee bank details, with a dated example
SOC 2 CC6.3 Role-based access, least privilege and segregation of duties
Direct mapping: this control is what the question asks about. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the bank or treasury platform dual-authorisation setup and the payment approval workflow, showing a second approver on a different device above the threshold
  • the payment approval log, with a dated example above the threshold
  • the callback or out-of-band verification for a change to payee bank details, with a dated example
SOC 2 CC3.3 Considering fraud risk (COSO principle 8)
Supporting practice: this control is adjacent to what the question asks; the question on its own does not establish it. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the bank or treasury platform dual-authorisation setup and the payment approval workflow, showing a second approver on a different device above the threshold
  • the payment approval log, with a dated example above the threshold
  • the callback or out-of-band verification for a change to payee bank details, with a dated example
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 mapping: this control is what the question asks about. Limit: 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.
Evidence to have on file (guidance, our wording)
  • the bank or treasury platform dual-authorisation setup and the payment approval workflow, showing a second approver on a different device above the threshold
  • the payment approval log, with a dated example above the threshold
  • the callback or out-of-band verification for a change to payee bank details, with a dated example
Application question Are you aware of a matter that is reasonably likely to give rise to any loss or claim, or have you suffered any loss or any claim in the last 5 years?
SURA Technology Risks Pty Ltd (SURA Cyber) application question

This is a loss history 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 Have you been subject to any government action, investigation or subpoena regarding any alleged violation of any privacy / data security law or regulation?
SURA Technology Risks Pty Ltd (SURA Cyber) application question

This is a loss history 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.

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

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