What does a cyber application ask about backups?
Backup appears on 129 application questions across 44 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 have procedures to back up, archive, and restore sensitive data and critical business systems?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Business Interruption (Only if applying for this coverage) Are system backup and recovery procedures implemented, documented and tested at least annually for all mission-critical systems?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Do you regularly back up your business critical data?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question If you rely on a cloud-based backup service, is it a "syncing 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.
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Please specify how often you back-up all of your critical data and systems?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question please indicate frequency) Never Is the back-up disconnected from your systems?
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.3: Testing recovery plan procedures. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
Application question If Yes, is the back-up regularly tested?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question If you have a back-up of all of your critical data and systems, does that include an offline copy?
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.3: Testing recovery plan procedures. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
Application question If Yes, how old is the back-up?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Do you utilize cloud back-ups?
- 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.
- 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.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- 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.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question If Yes, are the cloud back-ups secured via two-factor authentication or other similar means?
- 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.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.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 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.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-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 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.
- 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 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.
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 Do you backup all mission critical systems and data?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question How frequently do you back up?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question o Daily/nightly o Weekly o Less frequently than weekly Which of the following back-up solutions do you employ?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question How quickly can you restore from back-ups?
- 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.
- 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.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- 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.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Are back-up restoration plans tested?
- 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.
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question How frequently do you test your ability to restore from back-ups?
- 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.
- 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.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- 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.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Do you use a data backup solution for all critical data?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Daily Weekly Monthly (2) Which of the following best describes your data backup solution?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Local backup Network drive Tape backup Off-site storage Cloud backup Other: (3) Please list your data backup provider: (4) Is your data backup solution: (a) physically disconnected from your network?
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.3: Testing recovery plan procedures. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
Application question (5) How long do you expect it to take to recover from backups in the event of a widespread malware or ransomware attack within your network?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Does the Applicant conduct regular backup of data?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Which of the following does the Applicant utilize Tapes Disks Cloud for backups?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Where are backups stored?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Are backups subject to the following measures?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Is full recovery from a backup tested at least annually?
- 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.
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Backup and recovery procedures in place for all important business and customer data If Yes, are such procedures automated?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Based upon testing results, how long does it take to restore the Applicant's critical business operations following a network or systems interruption?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Do you have a backup solution?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question If "Yes", how frequently do you back up systems and data?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Which of the following are in place for your backup solution(s?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question How often does the organization perform backups of business-critical data?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Does the Applicant keep offline backups that are disconnected from its network or store backups with a cloud service provider?
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.5.19: Information security in supplier relationships. 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.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.3: Testing recovery plan procedures. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- NIST CSF 2.0 GV.SC-01: A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders. 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.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 11.2: Perform Automated Backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. 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.
Application question Does the applicant perform full backups for databases, applications, endpoints, and servers (operating systems?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question How often are full backups performed?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Are backups stored offline?
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.3: Testing recovery plan procedures. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
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 Where are backups stored?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Can backups only be accessed via an authentication mechanism (i.e., MFA/password vault/separate credentials or credential checkout?
- 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.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.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 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.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.
- 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 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.
Application question If yes, how are the backups accessed and who can access them?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question If no, how is the applicant protecting the backups?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Is virus/malware scanning used on the backups?
- 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.
- 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.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- 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.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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 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 Are backups tested for vulnerabilities/malware prior to restoration?
- 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.
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- CIS Controls v8 11.5: Test Data Recovery. 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 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question back-ups of critical Data and Computer Systems If either 2.a. or 2.b. has been selected is one copy stored on-line?
- 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.
- 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.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- 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.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question If yes, are backups stored offline and/or isolated from production systems?
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.3: Testing recovery plan procedures. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
Application question And, how often do the applicants test recovering data from the backup?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Do you back-up your network data and configuration files daily and store back-up files in a secure location, and rehearse your procedure for restoring from back-ups at least yearly?
- 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.
- ISO 27001:2022 A.8.9: Configuration management. Evidence to have on file: the hardening baseline or configuration standard for the system the question names; a configuration report showing the baseline applied.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- NIST CSF 2.0 PR.PS-01: Configuration management practices are established and applied. Evidence to have on file: the hardening baseline or configuration standard for the system the question names; a configuration report showing the baseline applied.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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 2: Apply Secure Configurations to All System Components. Evidence to have on file: the hardening baseline or configuration standard for the system the question names; a configuration report showing the baseline applied.
Application question Do you use a data backup solution?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Which best describes your data backup solution?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question How frequently are backups run?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Does the Applicant maintain redundant backups of sensitive and critical system information?
- 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.
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question If "Yes", is there at least one backup destination that is maintained offline?
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.3: Testing recovery plan procedures. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
Application question on enterprise assets (e.g., databases, file shares, backups?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question You back up Your Critical Data at least weekly to a different location?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question The backup of Your Critical Data is stored in a secure locked location with access restricted to authorised personnel only?
- 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.
- 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.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- 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 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.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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 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 How quickly can you obtain backups of Critical Data?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question How long would it take You to fully restore from your backup?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question How are your backups stored?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Are unique backup credentials stored separately from other user credentials?
- 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.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.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 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.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-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 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 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 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.
Application question Are backup processes tested to ensure data can be restored with minimal impact to the business?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Are full system backups taken at least weekly and stored either off site or disconnected from your network?
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.3: Testing recovery plan procedures. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
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 Does the Company have and maintain backup and recovery procedures for all: i) mission critical systems?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Does the Company have and maintain backup and recovery procedures for all: ii) data and information assets?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question A process for creating regular backups exists (even if it is undocumented and/or ad hoc).
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Backup strategy includes regular offline backups (either onsite or offsite).
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.3: Testing recovery plan procedures. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
Application question Backups are isolated and separate from the production domain (i.e. cloud backups with MFA protection) or they are immutable.
- 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.13: Information backup. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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-11: Backups of data are created, protected, maintained, and tested. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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.
Application question Do you have procedures to back up, archive, and restore sensitive data and critical business systems?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Are your backups kept separate from your network ("offline"), in a cloud service designed for this purpose, or stored on a separate device or service which cannot be accessed from your network?
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.3: Testing recovery plan procedures. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
Application question How often are your backups performed?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Have you tested the successful restoration and recovery of key server configurations and data from backups in the last six months?
- 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.
- ISO 27001:2022 A.8.9: Configuration management. Evidence to have on file: the hardening baseline or configuration standard for the system the question names; a configuration report showing the baseline applied.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- NIST CSF 2.0 PR.PS-01: Configuration management practices are established and applied. Evidence to have on file: the hardening baseline or configuration standard for the system the question names; a configuration report showing the baseline applied.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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 2: Apply Secure Configurations to All System Components. Evidence to have on file: the hardening baseline or configuration standard for the system the question names; a configuration report showing the baseline applied.
Application question Are your backups kept separate from your network ("offline") or in a cloud service designed for this purpose?
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.3: Testing recovery plan procedures. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
Application question Are all your backups taken monthly and stored on a separate device or service which cannot be accessed from your network?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Have you tested the successful restoration and recovery of key server configurations and data from backups?
- 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.
- ISO 27001:2022 A.8.9: Configuration management. Evidence to have on file: the hardening baseline or configuration standard for the system the question names; a configuration report showing the baseline applied.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- NIST CSF 2.0 PR.PS-01: Configuration management practices are established and applied. Evidence to have on file: the hardening baseline or configuration standard for the system the question names; a configuration report showing the baseline applied.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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 2: Apply Secure Configurations to All System Components. Evidence to have on file: the hardening baseline or configuration standard for the system the question names; a configuration report showing the baseline applied.
Application question If yes, how often are backups tested for restoration and recovery of key server configurations and data?
- 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.
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- CIS Controls v8 11.5: Test Data Recovery. 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 2: Apply Secure Configurations to All System Components. Evidence to have on file: the hardening baseline or configuration standard for the system the question names; a configuration report showing the baseline applied.
Application question What is your estimated recovery time for critical systems to restore operations after a cyber attack or other loss/corruption?
- 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.
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Are system backup and recovery procedures documented and regularly tested for all mission critical systems/websites? If no, how often?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Are network and system backups performed at least once per week?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Store sensitive data on any mobile or portable device, including back-up tapes?
- 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.
- 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.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- 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.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Back-up all sensitive/critical data at least daily?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question If yes, are these back-ups stored off-site?
- 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.
- 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.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- 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.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question How long does it take to restore the applicant's critical systems following a network outage?
- 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.
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Do you backup computer data and store it off site?
- 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.
- 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.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- 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.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question (d) Is there an established and documented system backup and recovery procedure in place? i) If Yes, is it implemented on all systems under the Applicant's control?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question In the event of an attack (e.g. ransomware) what is the applicant's RTO (Restore time objective?)
- 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.
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
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 How frequently are computer systems and data backups performed?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question How frequently are such backups tested?
- 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.
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Are backups stored off-site in a secure location?
- 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.
- 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.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- 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.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Do you back-up your network data and configuration files daily and store back-up files in a secure location, and rehearse your procedure for restoring from back-ups at least yearly?
- 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.
- ISO 27001:2022 A.8.9: Configuration management. Evidence to have on file: the hardening baseline or configuration standard for the system the question names; a configuration report showing the baseline applied.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- NIST CSF 2.0 PR.PS-01: Configuration management practices are established and applied. Evidence to have on file: the hardening baseline or configuration standard for the system the question names; a configuration report showing the baseline applied.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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 2: Apply Secure Configurations to All System Components. Evidence to have on file: the hardening baseline or configuration standard for the system the question names; a configuration report showing the baseline applied.
Application question Do you (or your IT service provider) backup your data to an isolated environment at least every 7 days and test it at least every 365 days?
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.5.19: Information security in supplier relationships. 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.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.3: Testing recovery plan procedures. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- NIST CSF 2.0 GV.SC-01: A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders. 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.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 11.2: Perform Automated Backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. 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.
Application question Do you require MFA (multi-factor authentication) for back-ups (internal and external)?
- 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.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.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 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.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-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 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.
- 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 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.
Application question Please confirm how frequently you back up systems?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
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 back-up all sensitive/critical data at least daily? If yes, are these back-ups stored off-site?
- 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.
- 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.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- 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.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question How long does it take to restore your critical systems following a network outage?
- 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.
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Does the Proposer use a third party vendor as a Cloud/back-up provider, and if Yes, what is the name of the third party?
- 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.
- ISO 27001:2022 A.5.19: Information security in supplier relationships. 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.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- NIST CSF 2.0 GV.SC-01: A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders. 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.
- 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.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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 12: Support Information Security with Organizational Policies and Programs. 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.
Application question Does the Proposer take at least weekly backups of all critical data and store the same off-site or in a fireproof safe or does the Proposer have an outsourced provider that meets these minimum requirements?
- 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.
- ISO 27001:2022 A.5.19: Information security in supplier relationships. 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.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- NIST CSF 2.0 GV.SC-01: A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders. 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.
- 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.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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 12: Support Information Security with Organizational Policies and Programs. 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.
Application question Do you perform at least weekly backups of business critical data? (If yes, please indicate frequency)
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
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 Are your backups stored in a segregated environment, cloud environment or offline (e.g. backup tape)?
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.3: Testing recovery plan procedures. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 Do you take backups of critical systems and data at least weekly?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Do your backups include backups of applications, databases, servers, workstations / laptops and endpoints?
- 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.
- 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.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- 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.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
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 regularly test your ability to restore from backups?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Do you maintain redundant back-ups of sensitive and critical system information?
- 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.
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Are restore procedures documented and tested?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Do you use credentials unique to backups that are stored separately from other user credentials?
- 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.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.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 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.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-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 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 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 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.
Application question Do you perform backups of business critical data on at least a weekly basis?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question If you perform backups of business critical data on at least a weekly basis, is the backup stored offsite in a secure location?
- 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.
- 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.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- 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.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question If you perform backups of business critical data on at least a weekly basis, do you test your restore process on at least a monthly basis?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
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 Does the applicant back up all valuable/sensitive data, including personal information of others, on a daily basis?
- 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.
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- 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.
- 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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
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 Are system back-up and recovery procedures tested for all mission critical systems and performed at least annually?
- 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.
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question How long would it take to restore your operations after a computer attack or other loss/corruption of data?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Does the Applicant regularly back-up critical / important data to an offline location (disconnected from the live environment) and ensure that these backups can be restored?
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.3: Testing recovery plan procedures. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
Application question With regards to maintaining regular backup and recovery procedures for all critical, data and information assets; how often is data backed up to a Local server?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question How quickly can the Applicant restore critical systems following a network interruption:
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
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 have written procedures for routine backups and maintain proof of backups?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Is all valuable / sensitive data back-up by the Proposer on a daily basis?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
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 How frequently do you take regular backups of critical data and systems?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Do you keep a copy of critical backups offline, segregated from and inaccessible to your network?
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.3: Testing recovery plan procedures. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
Application question Is your backup environment:
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question How frequently do you test system restoration capabilities by performing a full restoration from a backup?
- 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 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.
- SOC 2 A1.3: Testing recovery plan procedures. 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-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 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.
- CIS Controls v8 11.5: Test Data Recovery. 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.
Application question Do you take regular back-ups (at least weekly) of all critical data and store the backups offline, or offsite, or in a fire-proof safe, or does your outsourced service provider meet this requirement on your behalf?
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- ISO 27001:2022 A.5.19: Information security in supplier relationships. 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.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- SOC 2 A1.3: Testing recovery plan procedures. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- NIST CSF 2.0 GV.SC-01: A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders. 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.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- 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 11.2: Perform Automated Backups. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the backup configuration and schedule for the offline copy, and the restore-test record with its date; the report of the last successful restore from the offline copy, with the date the copy was taken offline.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. 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.
Frequently asked questions
How many carriers ask about backup?
44 of the 48 carrier forms ask about backup, on 129 questions.
What evidence answers the backup questions?
Backup configuration, a dated restore test and, where the form asks, evidence the copy is offline or segregated. The questions state the frequency and scope they ask about.
All answer pages: the answers index. The controls each question reaches: the controls index. Map your own answers in the tool.