Do you have controls in place ensuring timely removal of system access when an employee leaves the organisation, or when access is no longer required for business purposes?
This is application question 14 of 19 on the SURA Technology Risks Pty Ltd (SURA Cyber) SCCIPF. It is a control question and reaches 12 controls. The wording is the carrier's, quoted verbatim.
Held from the Cyber Insurance Proposal Form (form SCCIPF 1.0 11-2024; earlier edition STRCIPF 1.0 03-2024) (read 2026-10-12), jurisdiction Australia. All SURA Technology Risks Pty Ltd (SURA Cyber) questions.
Facets: control: Do you have controls in place ensuring timely removal of system access when an employee leaves the organisation, or when access is no longer required for business purposes?; population: employee
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 SURA Technology Risks Pty Ltd (SURA Cyber) page, the controls index, the island and the answers.