Backups are isolated and separate from the production domain (i.e. cloud backups with MFA protection) or they are immutable.
This is application question 45 of 79 on the AIG AIG CyberEdge Proposal Form (FullForm 0413), CyberEdge Proposal Form (Hong Kong 2012) and Cyber Insurance Application Form (group revenue up to 500M). It is a control question and reaches 13 controls. The wording is the carrier's, quoted verbatim.
Held from the AIG CyberEdge Insurance Proposal Form (Asia Pacific, form 0413) and CyberEdge Proposal Form (Hong Kong, 2012) and Cyber Insurance Application Form (group revenue up to 500M) (read 2026-10-12), jurisdiction Singapore, Hong Kong and the United Kingdom and Europe. All AIG 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.
Flagged warranty: an answer the carrier relies on, which can affect underwriting or cover if wrong. What a warranty flag means here.
Facets: control: Backups are isolated and separate from the production domain (i.e. cloud backups with MFA protection) or they are immutable.
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 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 (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 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 (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.DS-11: Backups of data are created, protected, maintained, and tested (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 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 (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 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 (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 AIG page, the controls index, the island and the answers.