Are backups tested for vulnerabilities/malware prior to restoration?
This is application question 48 of 55 on the QBE The Solution for Cyber Risk Ransomware supplement. It is a control question and reaches 17 controls. The wording is the carrier's, quoted verbatim.
Held from the The Solution for Cyber Risk - Ransomware supplement (US) (read 2026-10-11), jurisdiction United States. All QBE questions.
Priority underwriting question: a "no" here is a subject a cyber underwriter weighs most. A carrier may still accept a compensating-controls explanation, so it is not a binary decline.
Facets: control: Are backups tested for vulnerabilities/malware prior to restoration?
What this question reaches
- ISO 27001:2022 A.8.13: Information backup (direct)
Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file: the backup configuration 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 (supporting)
Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file: the backup configuration 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 (supporting)
Establishes the continuity or recovery planning asked about; it does not establish that the plan was exercised or that recovery objectives were met.
Evidence to have on file: 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 (direct)
Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file: the backup configuration 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 (supporting)
Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file: the backup configuration 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 (direct)
Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file: the backup configuration 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 (supporting)
Establishes the continuity or recovery planning asked about; it does not establish that the plan was exercised or that recovery objectives were met.
Evidence to have on file: 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 (direct)
Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file: the backup configuration 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 (supporting)
Establishes the patching or vulnerability practice asked about; it does not establish that every critical asset was patched within the stated window.
Evidence to have on file: 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 (supporting)
Establishes the patching or vulnerability practice asked about; it does not establish that every critical asset was patched within the stated window.
Evidence to have on file: 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 (supporting)
Establishes the continuity or recovery planning asked about; it does not establish that the plan was exercised or that recovery objectives were met.
Evidence to have on file: 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 (supporting)
Establishes the continuity or recovery planning asked about; it does not establish that the plan was exercised or that recovery objectives were met.
Evidence to have on file: 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 (direct)
Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file: the backup configuration and schedule, and the 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 (supporting)
Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file: the backup configuration and schedule, and the 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 (supporting)
Establishes the backup or restore practice asked about; unless the question says so it does not establish that a restore was tested or that a copy is offline.
Evidence to have on file: the backup configuration 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 (supporting)
Establishes the patching or vulnerability practice asked about; it does not establish that every critical asset was patched within the stated window.
Evidence to have on file: 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 (supporting)
Establishes the patching or vulnerability practice asked about; it does not establish that every critical asset was patched within the stated window.
Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window
Subject: backup. Owner a broker routes it to: IT operations and resilience owner.
The same control on other applications
Coalition Q5, Chubb Q19, Beazley Q8, Beazley Q14, Hiscox Q34, Hiscox Q35, Hiscox Q36, Hiscox Q37, Hiscox Q38, Hiscox Q39, Hiscox Q40, AmTrust Q13.
Map your own answers in the tool. See the QBE page, the controls index, the island and the answers.