Does the Applicant restrict employee access to personally identifiable information on a business need to know basis?
This is application question 35 of 53 on the The Cincinnati Insurance Company ML 004 01 18. It is a control question and reaches 12 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: Does the Applicant restrict employee access to personally identifiable information on a business need to know basis?; population: personally identifiable information
What this question reaches
- ISO 27001:2022 A.5.15: Access control (direct)
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 - ISO 27001:2022 A.5.16: Identity management (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 - ISO 27001:2022 A.5.18: Access rights (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 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.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 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-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 (direct)
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 6.8: Define and Maintain Role-Based Access Control (direct)
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 6.1: Establish an Access Granting Process (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 6.2: Establish an Access Revoking Process (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 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: access_control. Owner a broker routes it to: IT identity and access owner.
The same control on other applications
Chubb Q9, Beazley Q4, Hiscox Q4, Hiscox Q8, Hiscox Q19, Hiscox Q26, Hiscox Q27, AmTrust Q7, AmTrust Q8, Great American Insurance Group Q4, Great American Insurance Group Q21, Tokio Marine HCC Q9.
Map your own answers in the tool. See the The Cincinnati Insurance Company page, the controls index, the island and the answers.