Safeguard Docs
Frameworks and Connectors

CIS AWS Foundations Benchmark and connectors

Which connectors provide evidence for CIS AWS Foundations Benchmark, for which controls, and how to connect them.

Safeguard's automated tests map to 41 recommendations of CIS Amazon Web Services Foundations Benchmark v3.0.0. 41 tests apply: 41 read a connected system, and 0 read Safeguard's own records (policies, people, training and devices), so they need no connector. A passing result is evidence toward a control, not proof that the control is met on its own.

A CIS benchmark is a catalogue mapping: results show on the tests, filters and evidence with their recommendation numbers, and the benchmark is not a framework in your library.

How to connect for this framework

  1. Connect the systems you run from the table below. Each connector links to its setup steps.
  2. Open Compliance › Tests and filter by the benchmark to see its results.
  3. Tests run on their schedule, or straight away with Run now on Compliance › Tests. A passing test counts toward its controls once its preview period has ended.

Automated tests are switched on per workspace by the Safeguard team.

Connectors with automated evidence (1)

ConnectorControls it provides evidence forTests
Amazon Web Services (also AWS GovCloud, AWS CodeCommit, AWS Inspector, Amazon CloudWatch, Amazon S3, AWS Security Hub)1.1, 1.11, 1.13, 1.15, 1.16, 1.17, 1.18, 1.19, 1.2, 1.20, 1.21, 1.22, 1.6, 1.7, 2.1.1, 2.1.2, 2.1.3, 2.3.2, 2.4.1, 3.4, 3.8, 3.9, 4.1, 4.10, 4.11, 4.12, 4.13, 4.14, 4.15, 4.16, 4.2, 4.3, 4.4, 4.5, 4.6, 4.7, 4.8, 4.9, 5.1, 5.4, 5.641

Recommendations (41)

RecommendationTitleAutomated testsConnectors
1.1Account contact details are current17
1.2A security contact is registered for the account17
1.6Root MFA is hardware-backed17
1.7Root is not used for everyday tasks17
1.11No unused access key from user setup17
1.13An IAM user holds at most one active access key17
1.15IAM users get permissions through groups only17
1.16No custom policy grants full admin17
1.17A role can work with AWS Support17
1.18EC2 instances reach AWS through an instance role17
1.19Expired IAM server certificates are removed17
1.20Access Analyzer is on in every region17
1.21People sign in through federation17
1.22CloudShell full access is restricted17
2.1.1S3 bucket policies deny non-TLS requests17
2.1.2MFA Delete on S3 buckets17
2.1.3Macie discovers sensitive S3 data17
2.3.2RDS instances apply minor engine upgrades automatically17
2.4.1EFS is encrypted at rest17
3.4The CloudTrail bucket has access logging17
3.8S3 object writes are logged17
3.9S3 object reads are logged17
4.1Unauthorized API calls are alerted on17
4.2Console sign-in without MFA is alerted on17
4.3Root user activity is alerted on17
4.4IAM policy changes are alerted on17
4.5CloudTrail configuration changes are alerted on17
4.6Failed console sign-ins are alerted on17
4.7Disabling or deleting a customer-managed key is alerted on17
4.8S3 bucket policy changes are alerted on17
4.9AWS Config changes are alerted on17
4.10Security group changes are alerted on17
4.11Network ACL changes are alerted on17
4.12Network gateway changes are alerted on17
4.13Route table changes are alerted on17
4.14VPC changes are alerted on17
4.15AWS Organizations changes are alerted on17
4.16Security Hub is enabled17
5.1Network ACLs block internet admin ports17
5.4Default security groups allow no traffic17
5.6Instance metadata requires session tokens (IMDSv2)17

On this page