Are unique backup credentials stored separately from other user credentials?
This is application question 50 of 121 on the Munich Re MRS Insurance Application Cyber Risk. It is a control question and reaches 12 controls. The wording is the carrier's, quoted verbatim.
Held from the Insurance Application - Cyber Risk (UK) (read 2026-10-11), jurisdiction United Kingdom. All Munich Re 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 unique backup credentials stored separately from other user credentials?; population: user
What this question reaches
- ISO 27001:2022 A.5.17: Authentication information (direct)
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 - ISO 27001:2022 A.8.5: Secure authentication (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 - 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 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 - 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-01: Identities and credentials for authorized users, services, and hardware are managed by the organization (direct)
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 - 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, 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 (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 5.2: Use Unique Passwords (direct)
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 - CIS Controls v8 5.1: Establish and Maintain an Inventory of Accounts (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 - CIS Controls v8 11.2: Perform Automated 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 - PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components (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
Subject: password. Owner a broker routes it to: IT identity and access owner.
The same control on other applications
Beazley Q3, Beazley Q4, Hiscox Q25, Hiscox Q28, Hiscox Q29, Hiscox Q40, Great American Insurance Group Q9, Great American Insurance Group Q18, Great American Insurance Group Q19, Great American Insurance Group Q20, Tokio Marine HCC Q13, Tokio Marine HCC Q16.
Map your own answers in the tool. See the Munich Re page, the controls index, the island and the answers.