Skip to main content

🛡️ Google Project with KMS keys has a principal with Owner role🟢

Logic​

Description​

Open File

Description​

This policy identifies Google Projects that contain one or more Cloud KMS cryptographic keys and have at least one principal (user, group, or service account) assigned the primitive roles/owner role.

Rationale​

The roles/owner role is a highly privileged primitive role that grants full administrative access to all resources within a project, including Cloud KMS keys. This permission allows principals to create, delete, modify, and use keys for cryptographic operations such as encryption and decryption.

Assigning the Owner role in projects containing sensitive cryptographic keys violates the principle of least privilege and the security best practice of separation of duties. A single compromised Owner account could lead to the exposure, misuse, or destruction of sensitive encrypted data.

Audit​

This policy flags a Google Project as INCOMPLIANT if it contains at least one Google Cloud KMS Crypto Key and has a related IAM Policy Binding with the roles/owner role.

Remediation​

Open File

Remediation​

From Google Cloud Console​

  1. Navigate to IAM & Admin - IAM: https://console.cloud.google.com/iam-admin/iam
  2. Locate any principals (users, groups, or service accounts) assigned the Owner (roles/owner) role within the project.
  3. Click the Delete Bin icon to remove the Owner role from the principal.
  4. Assign a more granular role (e.g., roles/editor, roles/viewer, or a specific KMS-related predefined/custom role**) based on the user’s job responsibilities.

Note: Role removal should be performed carefully to ensure users retain the permissions necessary for their tasks.

From gcloud CLI​

  1. Remove the Owner role from the principal:

    gcloud projects remove-iam-policy-binding {{project-id}} \
        --member="{{principal-type}}:{{principal-email}}" \
        --role="roles/owner"

  2. Assign a least-privilege role appropriate for the principal’s responsibilities:

    gcloud projects add-iam-policy-binding {{project-id}} \

... see more

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 Cloudaware Framework → 💼 User Account Management19no data
💼 FedRAMP High Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)3768no data
💼 FedRAMP High Security Controls → 💼 AC-5 Separation of Duties (M)(H)15no data
💼 FedRAMP High Security Controls → 💼 AC-6 Least Privilege (M)(H)81157no data
💼 FedRAMP High Security Controls → 💼 MP-2 Media Access (L)(M)(H)13no data
💼 FedRAMP Low Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)68no data
💼 FedRAMP Low Security Controls → 💼 MP-2 Media Access (L)(M)(H)13no data
💼 FedRAMP Moderate Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)68no data
💼 FedRAMP Moderate Security Controls → 💼 AC-5 Separation of Duties (M)(H)15no data
💼 FedRAMP Moderate Security Controls → 💼 AC-6 Least Privilege (M)(H)657no data
💼 FedRAMP Moderate Security Controls → 💼 MP-2 Media Access (L)(M)(H)13no data
💼 ISO/IEC 27001:2013 → 💼 A.9.2.3 Management of privileged access rights312no data
💼 ISO/IEC 27001:2013 → 💼 A.10.1.2 Key management912no data
💼 ISO/IEC 27001:2022 → 💼 5.10 Acceptable use of information and other associated assets1127no data
💼 ISO/IEC 27001:2022 → 💼 5.15 Access control1431no data
💼 ISO/IEC 27001:2022 → 💼 8.3 Information access restriction1024no data
💼 ISO/IEC 27001:2022 → 💼 8.4 Access to source code822no data
💼 NIST CSF v1.1 → 💼 PR.AC-1: Identities and credentials are issued, managed, verified, revoked, and audited for authorized devices, users and processes1934no data
💼 NIST CSF v1.1 → 💼 PR.AC-4: Access permissions and authorizations are managed, incorporating the principles of least privilege and separation of duties1756no data
💼 NIST CSF v1.1 → 💼 PR.DS-1: Data-at-rest is protected1530no data
💼 NIST CSF v1.1 → 💼 PR.DS-2: Data-in-transit is protected1653no data
💼 NIST CSF v1.1 → 💼 PR.DS-5: Protections against data leaks are implemented4791no data
💼 NIST CSF v2.0 → 💼 PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization42no data
💼 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 duties116no data
💼 NIST CSF v2.0 → 💼 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected148no data
💼 NIST CSF v2.0 → 💼 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected125no data
💼 NIST CSF v2.0 → 💼 PR.DS-10: The confidentiality, integrity, and availability of data-in-use are protected142no data
💼 NIST CSF v2.0 → 💼 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage95no data
💼 NIST SP 800-53 Revision 4 → 💼 AC-6 LEAST PRIVILEGE1027no data
💼 NIST SP 800-53 Revision 4 → 💼 SC-12 CRYPTOGRAPHIC KEY ESTABLISHMENT AND MANAGEMENT545no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-3 Access Enforcement15540no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-5 Separation of Duties15no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-6 Least Privilege102350no data
💼 NIST SP 800-53 Revision 5 → 💼 MP-2 Media Access213no data
💼 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.1056no data
💼 PCI DSS v3.2.1 → 💼 3.5 Document and implement procedures to protect keys used to secure stored cardholder data against disclosure and misuse.41no data
💼 PCI DSS v4.0.1 → 💼 1.3.1 Inbound traffic to the CDE is restricted.56no data
💼 PCI DSS v4.0.1 → 💼 1.3.2 Outbound traffic from the CDE is restricted.56no data
💼 PCI DSS v4.0.1 → 💼 3.6.1 Procedures are defined and implemented to protect cryptographic keys used to protect stored account data against disclosure and misuse.31no data
💼 PCI DSS v4.0 → 💼 1.3.1 Inbound traffic to the CDE is restricted.756no data
💼 PCI DSS v4.0 → 💼 1.3.2 Outbound traffic from the CDE is restricted.56no data
💼 PCI DSS v4.0 → 💼 3.6.1 Procedures are defined and implemented to protect cryptographic keys used to protect stored account data against disclosure and misuse.31no data
💼 SOC 2 → 💼 CC5.2-3 Establishes Relevant Security Management Process Controls Activities1536no data
💼 SOC 2 → 💼 CC6.1-3 Restricts Logical Access122no data
💼 SOC 2 → 💼 CC6.1-7 Restricts Access to Information Assets1327no data