Skip to main content

📝 Google User has both Service Account Admin and Service Account User roles assigned 🟢

  • Contextual name: 📝 User has both Service Account Admin and Service Account User roles assigned 🟢
  • ID: /ce/ca/google/iam/service-account-related-roles-to-users
  • Located in: 📁 Google IAM

Flags​

Our Metadata​

  • Policy Type: COMPLIANCE_POLICY
  • Policy Category:
    • SECURITY

Similar Policies​

Logic​

Description​

Open File

Description​

It is recommended that the principle of 'Separation of Duties' is enforced while assigning service-account related roles to users.

Rationale​

The built-in/predefined IAM role Service Account admin allows the user/identity to create, delete, and manage service account(s). The built-in/predefined IAM role Service Account User allows the user/identity (with adequate privileges on Compute and App Engine) to assign service account(s) to Apps/Compute Instances.

Separation of duties is the concept of ensuring that one individual does not have all necessary permissions to be able to complete a malicious action. In Cloud IAM - service accounts, this could be an action such as using a service account to access resources that user should not normally have access to.

Separation of duties is a business control typically used in larger organizations, meant to help avoid security or privacy incidents and errors. It is considered best practice.

No user should have Service Account Admin and Service Account User roles assigned at the same time.

... see more

Remediation​

Open File

Remediation​

From Google Cloud Console​

  1. Go to IAM & Admin/IAM using https://console.cloud.google.com/iam-admin/iam.
  2. For any member having both Service Account Admin and Service account User roles granted/assigned, click the Delete Bin icon to remove either role from the member. Removal of a role should be done based on the business requirements.

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlags
💼 CIS GCP v1.2.0 → 💼 1.8 Ensure that Separation of duties is enforced while assigning service account related roles to users - Level 2 (Manual)1
💼 CIS GCP v1.3.0 → 💼 1.8 Ensure That Separation of Duties Is Enforced While Assigning Service Account Related Roles to Users - Level 2 (Automated)1
💼 CIS GCP v2.0.0 → 💼 1.8 Ensure That Separation of Duties Is Enforced While Assigning Service Account Related Roles to Users - Level 2 (Automated)1
💼 CIS GCP v3.0.0 → 💼 1.8 Ensure That Separation of Duties Is Enforced While Assigning Service Account Related Roles to Users - Level 2 (Automated)1
💼 Cloudaware Framework → 💼 Role-Based Access Control (RBAC) Management13
💼 FedRAMP High Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)3764
💼 FedRAMP High Security Controls → 💼 AC-5 Separation of Duties (M)(H)13
💼 FedRAMP High Security Controls → 💼 AC-6 Least Privilege (M)(H)81153
💼 FedRAMP High Security Controls → 💼 MP-2 Media Access (L)(M)(H)12
💼 FedRAMP Low Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)64
💼 FedRAMP Low Security Controls → 💼 MP-2 Media Access (L)(M)(H)12
💼 FedRAMP Moderate Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)64
💼 FedRAMP Moderate Security Controls → 💼 AC-5 Separation of Duties (M)(H)13
💼 FedRAMP Moderate Security Controls → 💼 AC-6 Least Privilege (M)(H)653
💼 FedRAMP Moderate Security Controls → 💼 MP-2 Media Access (L)(M)(H)12
💼 ISO/IEC 27001:2013 → 💼 A.9.2.3 Management of privileged access rights38
💼 ISO/IEC 27001:2022 → 💼 5.10 Acceptable use of information and other associated assets1126
💼 ISO/IEC 27001:2022 → 💼 5.15 Access control1430
💼 ISO/IEC 27001:2022 → 💼 8.3 Information access restriction1023
💼 ISO/IEC 27001:2022 → 💼 8.4 Access to source code821
💼 NIST CSF v1.1 → 💼 PR.AC-1: Identities and credentials are issued, managed, verified, revoked, and audited for authorized devices, users and processes1930
💼 NIST CSF v1.1 → 💼 PR.AC-4: Access permissions and authorizations are managed, incorporating the principles of least privilege and separation of duties1752
💼 NIST CSF v1.1 → 💼 PR.DS-5: Protections against data leaks are implemented4766
💼 NIST CSF v2.0 → 💼 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization38
💼 NIST CSF v2.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 duties88
💼 NIST CSF v2.0 → 💼 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected114
💼 NIST CSF v2.0 → 💼 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected94
💼 NIST CSF v2.0 → 💼 PR.DS-10: The confidentiality, integrity, and availability of data-in-use are protected108
💼 NIST CSF v2.0 → 💼 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage66
💼 NIST SP 800-53 Revision 4 → 💼 AC-5 SEPARATION OF DUTIES34
💼 NIST SP 800-53 Revision 5 → 💼 AC-3 Access Enforcement15534
💼 NIST SP 800-53 Revision 5 → 💼 AC-5 Separation of Duties13
💼 NIST SP 800-53 Revision 5 → 💼 AC-6 Least Privilege102346
💼 NIST SP 800-53 Revision 5 → 💼 MP-2 Media Access212
💼 PCI DSS v3.2.1 → 💼 1.2.1 Restrict inbound and outbound traffic to that which is necessary for the cardholder data environment, and specifically deny all other traffic.1035
💼 PCI DSS v4.0.1 → 💼 1.3.1 Inbound traffic to the CDE is restricted.35
💼 PCI DSS v4.0.1 → 💼 1.3.2 Outbound traffic from the CDE is restricted.35
💼 PCI DSS v4.0 → 💼 1.3.1 Inbound traffic to the CDE is restricted.735
💼 PCI DSS v4.0 → 💼 1.3.2 Outbound traffic from the CDE is restricted.35
💼 SOC 2 → 💼 CC5.2-3 Establishes Relevant Security Management Process Controls Activities1535
💼 SOC 2 → 💼 CC6.1-3 Restricts Logical Access121
💼 SOC 2 → 💼 CC6.1-7 Restricts Access to Information Assets1326