What does a cyber application ask about encryption?
Encryption appears on 89 application questions across 37 of the 48 carrier forms. Each question below is verbatim, with the control it reaches and the evidence to have on file. This page never says what a carrier will accept: that is the carrier's underwriting decision.
The questions, verbatim and mapped
Application question Does Named Insured enable disk encryption on laptops, desktops, and other portable media devices?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.AA-06: Physical access to assets is managed, monitored, and enforced commensurate with risk. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
Application question Does the Applicant have third party software protecting its network (e.g. antivirus, encryption, firewalls, etc.?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.8.7: Protection against malware. Evidence to have on file: 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.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.8: Preventing and detecting unauthorised or malicious software. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.PS-05: Installation and execution of unauthorized software are prevented. Evidence to have on file: 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.
- APRA CPS 234 para 16: Assess the security capability of related and third parties. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 22: Evaluate the design of third-party controls. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 28: Assess reliance on third-party control testing. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- CIS Controls v8 12.2: Establish and Maintain a Secure Network Architecture. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- CIS Controls v8 12.4: Establish and Maintain Architecture Diagram(s). Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 5: Protect All Systems and Networks from Malicious Software. Evidence to have on file: 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.
Application question Is this information encrypted while at rest?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Is this information encrypted while in transit?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- ISO 27001:2022 A.5.14: Information transfer. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question If Yes, are such devices encrypted?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question in place that scan both encrypted and unencrypted data to restrict network traffic?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question If Yes, do you encrypt this data?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Does the Applicant have and enforce policies concerning the encryption of internal and external communication?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- ISO 27001:2022 A.5.14: Information transfer. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question Does the Applicant encrypt data stored on laptop computers and portable media?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.AA-06: Physical access to assets is managed, monitored, and enforced commensurate with risk. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
Application question Are tapes or other portable media containing backup materials encrypted?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: 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.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-11: Backups of data are created, protected, maintained, and tested. Evidence to have on file: 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.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: 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.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Password/passcode protected Encryption Traditional or next generation firewalls enabled/turned on Traditional or next generation antivirus products on all endpoints Endpoint Detection and Response (EDR) 24/7/365 on all devices If yes to EDR, Who is your provider?
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
- NIST CSF 2.0 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
- CIS Controls v8 5.2: Use Unique Passwords. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- CIS Controls v8 5.1: Establish and Maintain an Inventory of Accounts. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Do you encrypt all sensitive and confidential information stored on your organization's systems and networks?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Does the Applicant employ mandatory encryption to protect the following?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Does the applicant encrypt all physical devices, critical data, sensitive emails?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question Does the organization encrypt all external communications containing sensitive information?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- ISO 27001:2022 A.5.14: Information transfer. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question Does the organization encrypt sensitive information stored on the cloud?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the cloud storage encryption setting for the buckets or volumes the question names, and whether provider-managed or customer-managed keys are used; a sample of the storage configuration showing encryption at rest, with the key custody it states.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the cloud storage encryption setting for the buckets or volumes the question names, and whether provider-managed or customer-managed keys are used; a sample of the storage configuration showing encryption at rest, with the key custody it states.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the cloud storage encryption setting for the buckets or volumes the question names, and whether provider-managed or customer-managed keys are used; a sample of the storage configuration showing encryption at rest, with the key custody it states.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the cloud storage encryption setting for the buckets or volumes the question names, and whether provider-managed or customer-managed keys are used; a sample of the storage configuration showing encryption at rest, with the key custody it states.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the cloud storage encryption setting for the buckets or volumes the question names, and whether provider-managed or customer-managed keys are used; a sample of the storage configuration showing encryption at rest, with the key custody it states.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the cloud storage encryption setting for the buckets or volumes the question names, and whether provider-managed or customer-managed keys are used; a sample of the storage configuration showing encryption at rest, with the key custody it states.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the cloud storage encryption setting for the buckets or volumes the question names, and whether provider-managed or customer-managed keys are used; a sample of the storage configuration showing encryption at rest, with the key custody it states.
Application question Is all backup data encrypted once replicated?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: 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.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-11: Backups of data are created, protected, maintained, and tested. Evidence to have on file: 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.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: 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.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Does the applicant have a policy that all portable devices use full disk encryption?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.AA-06: Physical access to assets is managed, monitored, and enforced commensurate with risk. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
Application question Where does the applicant use encryption?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question How often does the applicant use encryption?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Indicate whether these nonpublic personal records are encrypted: While at rest, While electronically in transit, While on mobile devices
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question Information Security and Cyber Infrastructure Self-Assessment 14 On your wireless networks; do you use security at least as strong as WPA2 authentication and encryption, and do you require two factor authentication (access token and password/account logon) before allowing wireless connections to your network?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: 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.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: 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.
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: 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.
- NIST CSF 2.0 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: 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.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: 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.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: 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.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Do you encrypt all sensitive records and files that are held at rest and/or transmitted across public networks, and that are to be transmitted wirelessly?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question On your wireless networks; do you use security at least as strong as WPA2 authentication and encryption, and do you require two factor authentication (access token and password/account logon) before allowing wireless connections to your network?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: 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.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: 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.
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: 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.
- NIST CSF 2.0 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: 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.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: 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.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: 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.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Do you encrypt all sensitive and confidential information stored on your organization's systems and networks?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Do you disable media ports or restrict usage to only encrypted removable storage devices?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.AA-06: Physical access to assets is managed, monitored, and enforced commensurate with risk. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
Application question Do you enforce the use of encryption over all external communication lines (e.g. website, email, wireless?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- ISO 27001:2022 A.5.14: Information transfer. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question Do you enforce the use of encryption of sensitive information while at rest (e.g. on premise, mobile device,  Yes  No cloud?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the cloud storage encryption setting for the buckets or volumes the question names, and whether provider-managed or customer-managed keys are used; a sample of the storage configuration showing encryption at rest, with the key custody it states.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the cloud storage encryption setting for the buckets or volumes the question names, and whether provider-managed or customer-managed keys are used; a sample of the storage configuration showing encryption at rest, with the key custody it states.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the cloud storage encryption setting for the buckets or volumes the question names, and whether provider-managed or customer-managed keys are used; a sample of the storage configuration showing encryption at rest, with the key custody it states.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the cloud storage encryption setting for the buckets or volumes the question names, and whether provider-managed or customer-managed keys are used; a sample of the storage configuration showing encryption at rest, with the key custody it states.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the cloud storage encryption setting for the buckets or volumes the question names, and whether provider-managed or customer-managed keys are used; a sample of the storage configuration showing encryption at rest, with the key custody it states.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the cloud storage encryption setting for the buckets or volumes the question names, and whether provider-managed or customer-managed keys are used; a sample of the storage configuration showing encryption at rest, with the key custody it states.
- NIST CSF 2.0 PR.AA-06: Physical access to assets is managed, monitored, and enforced commensurate with risk. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the cloud storage encryption setting for the buckets or volumes the question names, and whether provider-managed or customer-managed keys are used; a sample of the storage configuration showing encryption at rest, with the key custody it states.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the cloud storage encryption setting for the buckets or volumes the question names, and whether provider-managed or customer-managed keys are used; a sample of the storage configuration showing encryption at rest, with the key custody it states.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the cloud storage encryption setting for the buckets or volumes the question names, and whether provider-managed or customer-managed keys are used; a sample of the storage configuration showing encryption at rest, with the key custody it states.
Application question If Yes, is payment card data either encrypted or tokenised at all times?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.8.11: Data masking. Evidence to have on file: the masking or tokenisation configuration showing where it is applied; a sample of the output with the sensitive fields masked.
- ISO 27001:2022 A.5.15: Access control. Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the masking or tokenisation configuration showing where it is applied; a sample of the output with the sensitive fields masked.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Do you have a policy to encrypt mobile computing devices (for example laptops, tablets, mobile telephones, PDAs) and portable data storage media (for example external drives or magnetic tapes) which hold, process, transact or store any of the personal data referred to in 1.7?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 GV.OC-03: Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed. Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
Application question Does the Company have encryption requirements for data-in-transit data-at-rest to protect the integrity of Sensitive Data including data on portable media (e.g., laptops, DVD backup tapes, disk drives, USB devices, etc.)?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: 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.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question If "Yes", please describe where or how such encryption is used:
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question If "Yes" is it encrypted?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Data is encrypted on end-user devices to safeguard data against lost devices. Example implementations include Windows Bitlocker, Apple FileVault, and Linux dm-crypt.
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
Application question Do you have access control procedures and hard drive encryption to prevent unauthorized access on your databases, servers, and data files?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.5.15: Access control. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- ISO 27001:2022 A.5.16: Identity management. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.2: Registering and authorising users before issuing credentials. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 6.8: Define and Maintain Role-Based Access Control. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- CIS Controls v8 6.1: Establish an Access Granting Process. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
Application question Do you ensure that all private information is encrypted at rest? In transit?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: 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.
- ISO 27001:2022 A.5.14: Information transfer. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question Do you ensure that all private information is encrypted whether at rest or in transit?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: 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.
- ISO 27001:2022 A.5.14: Information transfer. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question Is data (i.e. personal information) encrypted on laptops and other mobile devises used for storing and transferring data?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 GV.OC-03: Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed. Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
Application question Encrypt critical/sensitive information whilst at rest?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Encrypt critical/sensitive information in transit?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- ISO 27001:2022 A.5.14: Information transfer. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question If yes, is such sensitive data encrypted?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Is credit card data either encrypted or tokenised at all times?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.8.11: Data masking. Evidence to have on file: the masking or tokenisation configuration showing where it is applied; a sample of the output with the sensitive fields masked.
- ISO 27001:2022 A.5.15: Access control. Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the masking or tokenisation configuration showing where it is applied; a sample of the output with the sensitive fields masked.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question If the credit card data is not encrypted or tokenised, how is it secured?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.8.11: Data masking. Evidence to have on file: the masking or tokenisation configuration showing where it is applied; a sample of the output with the sensitive fields masked.
- ISO 27001:2022 A.5.15: Access control. Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the masking or tokenisation configuration showing where it is applied; a sample of the output with the sensitive fields masked.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Do you use encryption techniques for secure communications and the transfer of confidential information?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- ISO 27001:2022 A.5.14: Information transfer. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question Does the Applicant have access control procedures and drive encryption to prevent unauthorized exposure of data on all portable devices (USB drives, laptops, smartphones, etc.)?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 6.8: Define and Maintain Role-Based Access Control. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed.
Application question Does the Applicant encrypt all personally identifiable data while at rest in storage and during transmission? (i) Is there an online multifactor authentication method required to access company sensitive data?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: 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.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: 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.
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: 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.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: 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.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: 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.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Does the Applicant currently have encryption on mobile devices in place?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.AA-06: Physical access to assets is managed, monitored, and enforced commensurate with risk. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
Application question Does the Applicant currently have encryption on backups in place?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: 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.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-11: Backups of data are created, protected, maintained, and tested. Evidence to have on file: 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.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: 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.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Does the Applicant currently have encryption on databases and servers in place?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Does the Applicant currently have encryption on data transmitted within and from organization in place?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Is encryption used when transmitting personal information?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.5.34: Privacy and protection of personal identifiable information (PII). Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared.
- ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements. Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 P1.1: Privacy notice to data subjects. Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Do you authenticate and encrypt all remote access to your network and require all such access to be from systems at least as secure as your own?
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: 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.
- ISO 27001:2022 A.8.20: Networks security. Evidence to have on file: 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.
- ISO 27001:2022 A.8.22: Segregation of networks. Evidence to have on file: 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.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question On your wireless networks, do you use security at least as strong as WPA authentication and encryption, and do you require two factor authentication (e.g. some combination of VPN or Access token, and password/account logon) before allowing wireless connections to your network?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: 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.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: 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.
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: 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.
- NIST CSF 2.0 PR.AA-03: Users, services, and hardware are authenticated. Evidence to have on file: 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.
- NIST CSF 2.0 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: 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.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: 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.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: 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.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Do you encrypt personally identifiable information stored on portable devices and removable media and ensure that the encryption/decryption keys are not also stored on that device?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 GV.OC-03: Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed. Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
Application question Is all Personal data on individuals (PCI, PII, PFI and / or PHI) encrypted whilst on, and in transmission from, your network?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- ISO 27001:2022 A.5.14: Information transfer. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- ISO 27001:2022 A.5.34: Privacy and protection of personal identifiable information (PII). Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- NIST CSF 2.0 GV.OC-03: Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed. Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question 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. Evidence to have on file: 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.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question 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. Evidence to have on file: 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.
- ISO 27001:2022 A.7.1: Physical security perimeters. Evidence to have on file: the physical-access record for the site the question names; the rule on who may enter which area, and how visitors are handled.
- ISO 27001:2022 A.7.2: Physical entry. Evidence to have on file: the physical-access record for the site the question names; the rule on who may enter which area, and how visitors are handled.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.4: Restricting physical access to facilities and assets. Evidence to have on file: the physical-access record for the site the question names; the rule on who may enter which area, and how visitors are handled.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.AA-06: Physical access to assets is managed, monitored, and enforced commensurate with risk. Evidence to have on file: the physical-access record for the site the question names; the rule on who may enter which area, and how visitors are handled.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Do you encrypt critical/sensitive information whilst at rest?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Do you encrypt critical/sensitive information in transit?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- ISO 27001:2022 A.5.14: Information transfer. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question Do you store sensitive data on any mobile or portable device, including back-up tapes? If yes, is such sensitive data encrypted?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: 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.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-11: Backups of data are created, protected, maintained, and tested. Evidence to have on file: 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.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: 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.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Do you store credit card data on your network? If yes, is credit card data either encrypted or tokenised at all times?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.8.11: Data masking. Evidence to have on file: the masking or tokenisation configuration showing where it is applied; a sample of the output with the sensitive fields masked.
- ISO 27001:2022 A.5.15: Access control. Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the masking or tokenisation configuration showing where it is applied; a sample of the output with the sensitive fields masked.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question If Yes to 3. above, please confirm the Proposer ensures that portable media devices carrying Personal Information are encrypted.
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.5.34: Privacy and protection of personal identifiable information (PII). Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared.
- ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements. Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 P1.1: Privacy notice to data subjects. Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 GV.OC-03: Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed. Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Do you encrypt personal data: a) at rest, b) in transit, c) on corporate laptops, d) on removable media, e) on mobile devices, f) on backups?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: 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.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question Do you store your backups in an encrypted format?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: 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.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-11: Backups of data are created, protected, maintained, and tested. Evidence to have on file: 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.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: 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.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Do you encrypt all your mobile devices (laptops, flash drives, mobile phones, etc.) and confidential data?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.AA-06: Physical access to assets is managed, monitored, and enforced commensurate with risk. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
Application question Does the Applicant store sensitive information (whether personal or corporate) on any of the following media, and if yes, is it encrypted: a. Desktop/Laptop hard drives; b. PDA's/other mobile devices; c. Flash drives or other portable storage devices; d. Back-up tapes; e. Internet connected web servers?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: 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.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Are data in transit, including, but not limited to, short or long range wireless communications properly encrypted and authenticated?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- ISO 27001:2022 A.5.14: Information transfer. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question Are all users' passwords encrypted?
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- NIST CSF 2.0 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- CIS Controls v8 5.2: Use Unique Passwords. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- CIS Controls v8 5.1: Establish and Maintain an Inventory of Accounts. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the password or passphrase policy with its length, rotation and reuse rules; a report of the directory settings that enforce the policy, such as lockout and history.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Does the applicant encrypt personal information in the following scenarios: a. "At rest" within computer databases or on back-up storage devices; b. "In transit" via email or other electronic means of communication; c. Stored on mobile devices including laptops flash drives, and mobile phones?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- ISO 27001:2022 A.5.14: Information transfer. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the database encryption configuration, naming the algorithm, key length and where the keys are held; a report or sample showing the customer databases or data stores covered by encryption at rest.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the database encryption configuration, naming the algorithm, key length and where the keys are held; a report or sample showing the customer databases or data stores covered by encryption at rest.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the database encryption configuration, naming the algorithm, key length and where the keys are held; a report or sample showing the customer databases or data stores covered by encryption at rest.
Application question Is all sensitive data: a. encrypted at rest? b. encrypted in transit? c. accessible via mobile devices? If yes, are the devices encrypted?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question Is critical and sensitive data encrypted at rest?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Is critical and sensitive data encrypted in transit?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- ISO 27001:2022 A.5.14: Information transfer. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question Is critical and sensitive data encrypted on portable media (laptops)?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.AA-06: Physical access to assets is managed, monitored, and enforced commensurate with risk. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
Application question Does the Applicant store sensitive information on laptop hard drives, and if Yes, is it encrypted?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.AA-06: Physical access to assets is managed, monitored, and enforced commensurate with risk. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Does the Applicant store sensitive information on PDA's / other mobile devices, and if Yes, is it encrypted?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.AA-06: Physical access to assets is managed, monitored, and enforced commensurate with risk. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Does the Applicant store sensitive information on flash drives or other portable storage devices, and if Yes, is it encrypted?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Does the Applicant store sensitive information on back-up tapes, and if Yes, is it encrypted?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: 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.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-11: Backups of data are created, protected, maintained, and tested. Evidence to have on file: 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.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: 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.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Does the Applicant store sensitive information on Internet connected web servers, and if Yes, is it encrypted?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Does the Applicant store sensitive information on databases, audit logs, files on servers, and if Yes, is it encrypted?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.8.15: Logging. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
- ISO 27001:2022 A.8.16: Monitoring activities. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- CIS Controls v8 8.2: Collect Audit Logs. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Does the Applicant store sensitive information on email, and if Yes, is it encrypted?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Are all wireless access points to the Applicant's network encrypted with WPA/WPA2 or more recent standard (e.g., not unencrypted or using WEP standard)?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.8.20: Networks security. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- ISO 27001:2022 A.8.21: Security of network services. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- CIS Controls v8 12.2: Establish and Maintain a Secure Network Architecture. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- CIS Controls v8 12.4: Establish and Maintain Architecture Diagram(s). Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 1: Install and Maintain Network Security Controls. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
Application question Are all sessions where sensitive data is entered encrypted with a Secure Socket Layer (SSL)?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Does the Proposer encrypt all sensitive and confidential data stored on laptop computers and portable media?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.AA-06: Physical access to assets is managed, monitored, and enforced commensurate with risk. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
Application question Does the Proposer encrypt all sensitive and confidential data stored on back-up tapes?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: 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.
- ISO 27001:2022 A.5.12: Classification of information. Evidence to have on file: the classification or handling rule for the confidential data the question names; a sample of how that data is stored and who can reach it.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-11: Backups of data are created, protected, maintained, and tested. Evidence to have on file: 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.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: 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.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Application question Does the Proposer encrypt all sensitive and confidential data when at rest on the network?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: 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.
- ISO 27001:2022 A.5.12: Classification of information. Evidence to have on file: the classification or handling rule for the confidential data the question names; a sample of how that data is stored and who can reach it.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Does the Proposer encrypt all sensitive and confidential data when in transit from the network?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- ISO 27001:2022 A.5.14: Information transfer. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- ISO 27001:2022 A.5.12: Classification of information. Evidence to have on file: the classification or handling rule for the confidential data the question names; a sample of how that data is stored and who can reach it.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question Do you protect all personally identifiable information and other sensitive data through encryption while:
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.5.34: Privacy and protection of personal identifiable information (PII). Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared.
- ISO 27001:2022 A.5.31: Legal, statutory, regulatory and contractual requirements. Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 P1.1: Privacy notice to data subjects. Evidence to have on file: the privacy notice or policy the question names, with its review date; the record of how personal information is collected, used and shared.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: 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.
Application question Do you encrypt all data at rest, in-transit and all portable devices which are used to store personal data?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- CIS Controls v8 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.10: Encrypt Sensitive Data in Transit. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Evidence to have on file: the transport configuration record, naming the protocol and cipher suites in use for the traffic the question names; a sample of a recent scan or configuration check of the external-facing service.
Application question For all payment card transactions, are all point-of-sale devices point-to-point (E2EE) encrypted?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: 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.
- ISO 27001:2022 A.5.15: Access control. Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: 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.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the card-data flow showing where card numbers are stored, processed or transmitted; a sample of the controls at the card-data boundary, or the current merchant assessment.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: 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.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: 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.
- PCI DSS 4.0 Requirement 3: Protect Stored Account Data. Evidence to have on file: 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.
Frequently asked questions
How many carriers ask about encryption?
37 of the 48 carrier forms ask about encryption, on 89 questions.
Does the form mean at rest or in transit?
Both, separately. The questions name the store (databases, backups, laptops, portable media) and the path (email, wireless, transmission); the mapping splits them, and the evidence differs for each.
All answer pages: the answers index. The controls each question reaches: the controls index. Map your own answers in the tool.