Skip to content

Wrong KMS crypto key id in output #4600

Description

@benlahav

Steps to Reproduce

  1. Run prowler for gcp, e.g. prowler gcp --credentials-file ./credentials.json
  2. Watch the output CSV and see for kms checks kms_key_not_publicly_accessible, kms_key_rotation_enabled that RESOURCE_UID & RESOURCE_NAME are both the same kms key name.

Expected behavior

Have the RESOURCE_UID include the key-ring which this key is included in for distinction.

Actual Result with Screenshots or Logs

image

How did you install Prowler?

From brew (brew install prowler)

Environment Resource

Workstation

OS used

MacOS

Prowler version

4.3.0

Pip version

24.1.2

Context

Running prowler for gcp account and see that this can't have distinction.
Different key can have same name if they are under the different key ring, this means that in the current report we can't distinct between 2 similar keys.

Metadata

Metadata

Assignees

Labels

bugprovider/gcpIssues/PRs related with the Google Cloud Platform providerseverity/mediumResults in some unexpected or undesired behavior.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions