Service accounts (accounts used by machines - not people - for running applications and other processes) have password lengths of at least 25 characters.
This is application question 53 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.
Facets: control: Service accounts (accounts used by machines - not people - for running applications and other processes) have password lengths of at least 25 characters.; population: accounts; threshold: at least 25
What this question reaches
- ISO 27001:2022 A.8.2: Privileged access rights (direct)
Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access - ISO 27001:2022 A.8.3: Information access restriction (supporting)
Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access - ISO 27001:2022 A.5.15: Access control (supporting)
Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access - SOC 2 CC6.3: Role-based access, least privilege and segregation of duties (direct)
Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access - SOC 2 CC6.1: Logical access security over protected information assets (supporting)
Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access - 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 (direct)
Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access - 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 ADMIN: Restrict administrative privileges (direct)
Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access - CIS Controls v8 5.4: Restrict Administrator Privileges to Dedicated Administrator Accounts (direct)
Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access - CIS Controls v8 6.5: Require MFA for Administrative Access (supporting)
Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access - CIS Controls v8 5.2: Use Unique Passwords (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 8: Identify Users and Authenticate Access to System Components (direct)
Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access - PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know (supporting)
Establishes the control over privileged accounts the question names; it does not establish the full lifecycle of every administrative account.
Evidence to have on file: the privileged-access or PAM configuration showing who holds administrative rights and how they are granted; a dated privileged-account access review, with the approval for standing or just-in-time access
Subject: privileged_access. Owner a broker routes it to: IT identity and access owner.
The same control on other applications
Great American Insurance Group Q20, Great American Insurance Group Q21, Tokio Marine HCC Q17, AXIS Insurance Q28, Corvus Insurance Q8, QBE Q2, QBE Q19, QBE Q21, CNA Q8, CNA Q26, Encore Fiduciary Q32, Encore Fiduciary Q33.
Map your own answers in the tool. See the AIG page, the controls index, the island and the answers.