Are documented procedures in place for user and password management and are they monitored for compliance? Do you have a process for managing user accounts including promptly deleting or modifying access upon a change of responsibilities or termination?
This is application question 44 of 101 on the Arch Insurance 00 NPL0154 00 07 16 and 00 NPL0151 00 07 16. It is a control question and reaches 13 controls. The wording is the carrier's, quoted verbatim.
Held from the Short Form Application for Arch NetSafe 2.0 Network Security & Privacy & Media Insurance (form 00 NPL0154 00 07 16) and Application for Arch NetSafe 2.0 Network Security & Privacy, Technology, E&O & Media Insurance (form 00 NPL0151 00 07 16) (read 2026-10-12), jurisdiction United States. All Arch Insurance questions.
Facets: control: Are documented procedures in place for user and password management and are they monitored for compliance? Do you have a process for managing user accounts including promptly deleting or modifying access upon a change of responsibilities or termination?; 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.5.15: Access control (supporting)
Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed - 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 CC6.2: Registering and authorising users before issuing credentials (supporting)
Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed - 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.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties (supporting)
Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed - ACSC Essential Eight ADMIN: Restrict administrative privileges (supporting)
Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed - 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 6.8: Define and Maintain Role-Based Access Control (supporting)
Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed - PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components (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 - PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know (supporting)
Establishes the access rule the question names; it does not establish that access was reviewed or removed on time for every leaver.
Evidence to have on file: the access rule and the role or group model that enforces it; a dated access review showing rights were confirmed or removed
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 Arch Insurance page, the controls index, the island and the answers.