What does a cyber application ask about access control?
Access control appears on 42 application questions across 22 of the 48 carrier forms. Each question below is verbatim, with the control it reaches and the evidence to have on file. This page never says what a carrier will accept: that is the carrier's underwriting decision.
The questions, verbatim and mapped
Application question If No, is such information stored on a segregated server with role-based access controls?
- ISO 27001:2022 A.5.15: Access control. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.
Application question Does the Applicant terminate all computer access and user accounts as part of the regular exit process when an employee leaves the company or when a third party contractor no longer provides the contracted services?
- ISO 27001:2022 A.5.15: Access control. 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. 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. 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. 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. 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. 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. 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. 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.
- APRA CPS 234 para 16: Assess the security capability of related and third parties. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 22: Evaluate the design of third-party controls. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 28: Assess reliance on third-party control testing. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- CIS Controls v8 6.8: Define and Maintain Role-Based Access Control. 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. 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. 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. 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 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
Application question Is multifactor authentication (MFA) required to remotely connect to the network, all critical internet facing systems and privilege accounts?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.2: Privileged access rights. 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. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.3: Role-based access, least privilege and segregation of duties. 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-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- 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. 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.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. 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.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. 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.
Application question Are firewalls configured according to the principles of least privileges?
- ISO 27001:2022 A.8.2: Privileged access rights. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.8: Define and Maintain Role-Based Access Control. 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. 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. 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.
Application question (2) Access control with role-based assignments?
- ISO 27001:2022 A.5.15: Access control. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.
Application question (b) segregated with 2-factor authentication access control?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.15: Access control. 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. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.2: Registering and authorising users before issuing credentials. 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-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- NIST CSF 2.0 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization. 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 MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. 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.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.5: Require MFA for Administrative Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. 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.
Application question How are privileged accounts secured and managed?
- ISO 27001:2022 A.8.2: Privileged access rights. 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. 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. 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. 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. 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. 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.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. 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. 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. 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 8: Identify Users and Authenticate Access to System Components. 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. 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.
Application question a. Do the applicant's privileged users require more extensive training relating to phishing attacks?
- ISO 27001:2022 A.8.2: Privileged access rights. 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. 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. 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. 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. 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. 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.PS-05: Installation and execution of unauthorized software are prevented. Evidence to have on file: the email-filtering configuration and the checks it applies to inbound mail; a sample of blocked or quarantined messages and their handling.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. 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. 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. 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 9.5: Implement DMARC. Evidence to have on file: the email-filtering configuration and the checks it applies to inbound mail; a sample of blocked or quarantined messages and their handling.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. 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. 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.
Application question Does the applicant utilize a Privileged Access Management (PAM) solution?
- ISO 27001:2022 A.8.2: Privileged access rights. 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. 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. 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. 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. 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. 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.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. 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. 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. 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 8: Identify Users and Authenticate Access to System Components. 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. 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.
Application question Do you physically and electronically limit access to sensitive information on a need –to-know basis and revoke access privileges upon a reduction in an individual's need to know?
- ISO 27001:2022 A.8.2: Privileged access rights. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.8: Define and Maintain Role-Based Access Control. 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. 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. 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.
Application question Do you physically and electronically limit access to sensitive information on a need-to-know basis and revoke access privileges upon a reduction in an individual's need to know?
- ISO 27001:2022 A.8.2: Privileged access rights. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.8: Define and Maintain Role-Based Access Control. 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. 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. 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.
Application question (2) Access control with role-based assignments?
- ISO 27001:2022 A.5.15: Access control. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.
Application question Do you use MFA to protect all local and remote access to privileged user accounts?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.2: Privileged access rights. 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. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.3: Role-based access, least privilege and segregation of duties. 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-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- 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. 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.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. 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. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. 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.
Application question Do you manage privileged accounts using privileged account management software (PAM) (e.g., CyberArk, BeyondTrust, etc.?
- ISO 27001:2022 A.8.2: Privileged access rights. 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. 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. 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. 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. 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. 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.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. 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. 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. 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 8: Identify Users and Authenticate Access to System Components. 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. 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.
Application question You secure remote access (access control procedures to prevent unauthorised access) to Your network and Your data?
- ISO 27001:2022 A.6.7: Remote working. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- ISO 27001:2022 A.8.20: Networks security. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- ISO 27001:2022 A.8.22: Segregation of networks. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- SOC 2 CC6.1: Logical access security over protected information assets. 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.IR-01: Networks and environments are protected from unauthorized logical access and usage. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- NIST CSF 2.0 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization. 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. 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. 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. 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. 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. Evidence to have on file: the VPN or remote-access gateway configuration and the authentication it requires; a report of active remote sessions, or of the users and devices allowed to connect remotely.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. 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.
Application question You enforce a policy of auditing of managing computer and user accounts?
- ISO 27001:2022 A.5.15: Access control. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.
Application question Do you restrict user access (employees, contractors etc.) on a business need-to-know & least-privilege basis?
- ISO 27001:2022 A.8.2: Privileged access rights. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.8: Define and Maintain Role-Based Access Control. 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. 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. 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.
Application question Do you have a formal process in place for assigning and revoking user accounts and access rights?
- ISO 27001:2022 A.5.15: Access control. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.
Application question Is logging and alerting configured for all privileged account activity?
- ISO 27001:2022 A.8.2: Privileged access rights. 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. 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. 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. 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. 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. 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 DE.CM-01: Networks and network services are monitored to find potentially adverse events. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. 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.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
- CIS Controls v8 5.4: Restrict Administrator Privileges to Dedicated Administrator Accounts. 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. 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 8.2: Collect Audit Logs. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. 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. 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.
Application question Do you configure service accounts using the principle of least privilege?
- ISO 27001:2022 A.8.2: Privileged access rights. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.8: Define and Maintain Role-Based Access Control. 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. 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. 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.
Application question Do you log the activity of service accounts that are able to override system or application controls (e.g. elevation Yes No of privileges, lateral movement etc.?
- ISO 27001:2022 A.8.2: Privileged access rights. 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. 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. 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. 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. 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. 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 DE.CM-01: Networks and network services are monitored to find potentially adverse events. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. 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.
- ACSC Essential Eight APP: Application control. Evidence to have on file: the application-control ruleset and the hosts it is applied to; a sample of an allowed or blocked execution event and its handling.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
- CIS Controls v8 5.4: Restrict Administrator Privileges to Dedicated Administrator Accounts. 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. 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 8.2: Collect Audit Logs. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. 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. 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.
Application question Is multi-factor authentication (MFA) required for access to privileged user accounts?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.2: Privileged access rights. 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. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.3: Role-based access, least privilege and segregation of duties. 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-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- 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. 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.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. 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. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. 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.
Application question Do you have access control procedures and hard drive encryption to prevent unauthorized access on your databases, servers, and data files?
- ISO 27001:2022 A.8.24: Use of cryptography. 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.
- ISO 27001:2022 A.5.15: Access control. 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. 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. 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.2: Registering and authorising users before issuing credentials. 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.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. 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.
- NIST CSF 2.0 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization. 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. 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 3.11: Encrypt Sensitive Data at Rest. 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 6.8: Define and Maintain Role-Based Access Control. 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. 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 3: Protect Stored Account Data. 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 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. 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.
Application question If yes, are user accounts audited regularly to determine their security levels are appropriately set?
- ISO 27001:2022 A.5.15: Access control. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.
Application question 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?
- ISO 27001:2022 A.5.17: Authentication information. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.
Application question Are special privileges restricted to systems administration personnel with an approved need to have these privileges?
- ISO 27001:2022 A.8.2: Privileged access rights. 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. 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. 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. 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. 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. 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.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. 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. 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. 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 8: Identify Users and Authenticate Access to System Components. 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. 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.
Application question Does the Applicant have access control procedures and drive encryption to prevent unauthorized exposure of data on all portable devices (USB drives, laptops, smartphones, etc.)?
- ISO 27001:2022 A.8.24: Use of cryptography. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.7.10: Storage media. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- SOC 2 CC6.7: Restricting and protecting information in transmission, movement and removal. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- NIST CSF 2.0 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization. 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. 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 3.6: Encrypt Data on End-User Devices. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 3.11: Encrypt Sensitive Data at Rest. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- CIS Controls v8 6.8: Define and Maintain Role-Based Access Control. 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 3: Protect Stored Account Data. Evidence to have on file: the full-disk-encryption configuration record and the enrolled-device report showing which laptops, desktops and endpoints are covered; a sample endpoint showing encryption at rest, with its recovery key escrowed.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. 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.
Application question Does the Applicant have a documented information security policy? (i) Are all employment positions clearly defined and employees assigned specific rights, privileges, and unique user ID passwords, which are reviewed and validated periodically?
- ISO 27001:2022 A.8.2: Privileged access rights. 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. 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. 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. 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. 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. 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. 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. 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.
- APRA CPS 234 para 14: Information security roles and responsibilities defined. Evidence to have on file: the information-security policy and its owner, with the review date; the record of management review or approval of the policy.
- APRA CPS 234 para 13: Board accountability for information security. Evidence to have on file: the information-security policy and its owner, with the review date; the record of management review or approval of the policy.
- CIS Controls v8 5.4: Restrict Administrator Privileges to Dedicated Administrator Accounts. 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. 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. 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. 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. 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.
Application question (ii) Does the Applicant immediately terminate all associated computer access and user accounts as part of the exit process when an employee leaves the company?
- ISO 27001:2022 A.5.15: Access control. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.
Application question Is employee access to personally identifiable or sensitive information on a business need to know basis?
- ISO 27001:2022 A.5.15: Access control. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.
Application question Does the Applicant restrict access to private consumer information or customer files to employees on a business need to know basis?
- ISO 27001:2022 A.5.15: Access control. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.
Application question Do you physically and electronically limit access to sensitive information on a need to know basis and revoke access privileges upon a reduction in an individual's need to know?
- ISO 27001:2022 A.8.2: Privileged access rights. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.8: Define and Maintain Role-Based Access Control. 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. 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. 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.
Application question Do you require MFA (multi-factor authentication) for privileged accounts?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.2: Privileged access rights. 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. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.3: Role-based access, least privilege and segregation of duties. 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-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- 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. 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.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. 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. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. 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.
Application question Do you have a process for user account creation, approval and removal?
- ISO 27001:2022 A.5.15: Access control. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.
Application question Do privileged users have a separate administrative account in order to carry out specific administrative duties?
- ISO 27001:2022 A.8.2: Privileged access rights. 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. 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. 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. 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. 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. 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.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. 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. 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. 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 8: Identify Users and Authenticate Access to System Components. 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. 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.
Application question Do you restrict employees' and external users' IT systems privileges and access to personal information on a business-need-to-know basis?
- ISO 27001:2022 A.8.2: Privileged access rights. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.8: Define and Maintain Role-Based Access Control. 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. 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. 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.
Application question Does the Applicant restrict employee access to personally identifiable information on a business need to know basis?
- ISO 27001:2022 A.5.15: Access control. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.
Application question Does the applicant restrict employee access to Personally Identifiable Information on a business "need-to-know" basis?
- ISO 27001:2022 A.5.15: Access control. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.
Application question Does applicant terminate all associated computer access and user accounts as part of the regular exit process when an employee leaves the company?
- ISO 27001:2022 A.5.15: Access control. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.
Application question Do you have access control procedures that address access to critical and sensitive computer systems?
- ISO 27001:2022 A.5.15: Access control. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.
Application question Are access controls employed using the principle of least privilege?
- ISO 27001:2022 A.8.2: Privileged access rights. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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.8: Define and Maintain Role-Based Access Control. 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. 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. 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.
Application question Do you require multi-factor authentication for all access to privileged accounts, for both on premise and remote access?
- ISO 27001:2022 A.8.5: Secure authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.5.17: Authentication information. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ISO 27001:2022 A.8.2: Privileged access rights. 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. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- SOC 2 CC6.3: Role-based access, least privilege and segregation of duties. 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-03: Users, services, and hardware are authenticated. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- 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. 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.
- ACSC Essential Eight MFA: Multi-factor authentication. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- ACSC Essential Eight ADMIN: Restrict administrative privileges. 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. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.4: Require MFA for Remote Network Access. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- CIS Controls v8 6.3: Require MFA for Externally-Exposed Applications. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 8: Identify Users and Authenticate Access to System Components. Evidence to have on file: the identity-provider or directory configuration showing the second factor required, and the users or sign-in paths in scope; the report of enrolled authentication methods, or the registration status by user group.
- PCI DSS 4.0 Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know. 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.
Frequently asked questions
How many carriers ask about access control?
22 of the 48 carrier forms ask about access control, on 42 questions.
What evidence answers the access questions?
The access policy, a current access review and the joiner, mover, leaver process with a dated example. Where the form asks about privileged access, hold the privileged account inventory and the approval record.
All answer pages: the answers index. The controls each question reaches: the controls index. Map your own answers in the tool.