Can backups only be accessed via an authentication mechanism (i.e., MFA/password vault/separate credentials or credential checkout?
This is application question 44 of 55 on the QBE The Solution for Cyber Risk Ransomware supplement. It is a control question and reaches 13 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: Can backups only be accessed via an authentication mechanism (i.e., MFA/password vault/separate credentials or credential checkout?
What this question reaches
- ISO 27001:2022 A.8.5: Secure authentication (direct)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: 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 (supporting)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: 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 (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 - SOC 2 CC6.1: Logical access security over protected information assets (direct)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: 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 (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.AA-03: Users, services, and hardware are authenticated (direct)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: 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 (supporting)
Establishes the password or credential rule asked about; it does not establish the strength or reuse state of every credential held.
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 (direct)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: 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 (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 6.4: Require MFA for Remote Network Access (direct)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: 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 (supporting)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: 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 (supporting)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: 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 (direct)
Establishes that a second factor is required for the scope named; it does not establish which systems, users or sign-in paths are covered beyond that scope.
Evidence to have on file: 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
Subject: mfa. Owner a broker routes it to: IT identity and access owner.
The same control on other applications
Coalition Q6, Chubb Q21, Chubb Q23, Beazley Q3, Beazley Q4, Hiscox Q25, Hiscox Q28, Hiscox Q29, Hiscox Q40, Hiscox Q67, Great American Insurance Group Q9, Great American Insurance Group Q18.
Map your own answers in the tool. See the QBE page, the controls index, the island and the answers.