Benchmark: 7.2.6: All user access to query repositories of stored cardholder data
Description
The misuse of query access to repositories of cardholder data has been a regular cause of data breaches. Limiting such access to administrators reduces the risk of such access being abused by unauthorized users.
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-aws-complianceStart the Powerpipe server:
steampipe service startpowerpipe serverOpen http://localhost:9033 in your browser and select 7.2.6: All user access to query repositories of stored cardholder data.
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.pci_dss_v40_requirement_7_2_6Snapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.pci_dss_v40_requirement_7_2_6 --shareControls
- ECS containers should be limited to read-only access to root filesystems
- IAM users should be in at least one group
- OpenSearch domains should have fine-grained access control enabled
- AWS S3 permissions granted to other AWS accounts in bucket policies should be restricted
- RDS DB instances should prohibit public access
- Redshift clusters should prohibit public access
- S3 buckets should prohibit public read access
- S3 buckets should prohibit public write access
- SageMaker notebook instances should not have direct internet access