Are all users' passwords encrypted?
This is application question 20 of 53 on the The Cincinnati Insurance Company ML 004 01 18. It is a control question and reaches 11 controls. The wording is the carrier's, quoted verbatim.
Held from the Application for Cincinnati Cyber Defense Coverage, supplement to Pillar policy application (form ML 004 01 18) (read 2026-10-15), jurisdiction United States. All The Cincinnati Insurance Company questions.
Facets: control: Are all users' passwords encrypted?; population: all users
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.24: Use of cryptography (supporting)
Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
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 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 - 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-01: The confidentiality, integrity, and availability of data-at-rest are protected (supporting)
Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
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 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 3.11: Encrypt Sensitive Data at Rest (supporting)
Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
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 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 - PCI DSS 4.0 Requirement 3: Protect Stored Account Data (supporting)
Establishes that cryptography is used where the question names it; it does not establish the algorithm strength, key custody or coverage of every data store.
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
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 The Cincinnati Insurance Company page, the controls index, the island and the answers.