finding_uid is not unique in backup_recovery_point_encrypted and route53_dangling_ip_subdomain_takeover, cloudtrail_multi_region_enabled_logging_management_events #6138
Labels
bug
provider/aws
Issues/PRs related with the AWS provider
severity/low
Bug won't result in any noticeable breakdown of the execution.
Steps to Reproduce
prowler -s backup route53 cloudtrail
The program output CSV file with the same finding_uid like that
prowler-aws-backup_recovery_point_encrypted-<AWS_ACCOUNT_ID>-ap-southeast-1-aps1-ec2-ami-backup-vault
prowler-aws-backup_recovery_point_encrypted-<AWS_ACCOUNT_ID>-ap-southeast-1-aps1-rds-backup-vault
prowler-aws-route53_dangling_ip_subdomain_takeover-<AWS_ACCOUNT_ID>-us-east-1-<RESOURCE_ID>
prowler-aws-cloudtrail_multi_region_enabled_logging_management_events-<AWS_ACCOUNT_ID>-ap-northeast-1-Members
Expected behavior
The finding_uid must be unique id
Actual Result with Screenshots or Logs
No Log
How did you install Prowler?
Cloning the repository from github.com (git clone)
Environment Resource
OS used
Prowler version
Prowler 5.1.0 (You are running the latest version, yay!)
Pip version
pip 23.3
Context
It's the same problem with #6105 and I think it may be happen with many check that using for/loop then append report to finding array like that
The text was updated successfully, but these errors were encountered: