Compliancemanzill.com
CIS Amazon Web Services Foundations Benchmark v1.2.0

CIS Amazon Web Services Foundations Benchmark v1.2.0/Logging/27 of 49

2.5Ensure AWS Config is enabled in all regions

Control family: Logging

Control description

AWS Config is a web service that performs configuration management of supported AWS resources within your account and delivers log files to you. The recorded information includes the configuration item (AWS resource), relationships between configuration items (AWS resources), any configuration changes between resources. It is recommended to enable AWS Config be enabled in all regions.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

AWS Config keeps a history of how each resource was configured and how that changed, which is what you need to answer "when did this security group open up, and who did it?". It records only in the Regions where it is turned on, so it is turned on in every Region, with global resources such as IAM recorded once.

Before you start

The same on every cloud, before the steps in the tabs.

  • Decide which account collects AWS Config data across the organization and who owns it.
  • Set how long configuration history is kept, to match your logging standard.

Evidence

  • The configuration recording standard and its owner

On AWS the tasks set up recording in each Region, then use an aggregator to show at a glance which Regions are recording.

Task 1Set up AWS Config recording in a Region

  1. Sign in to the AWS Management Console at console.aws.amazon.com, pick the Region with the Region selector and open AWS Config.
  2. Choose Get started (or 1-click setup for the AWS defaults).
  3. Under Settings > Recording method, choose All resource types with customizable overrides and Continuous recording.
  4. In one Region only, include the global IAM resource types by choosing Remove on their override; leave them excluded elsewhere so they aren't recorded twice.
  5. Under Data governance, choose the service-linked role for IAM role for AWS Config.
  6. Under Delivery method, choose a central bucket with Choose a bucket from your account or Choose a bucket from another account.
  7. Choose Next through Rules and Review, then Confirm.
  8. Repeat in every Region, or deploy the same settings to all accounts and Regions with a CloudFormation StackSet.

Task 2See which Regions are recording

  1. In the AWS Config delegated administrator or management account, choose Aggregators > Create aggregator.
  2. Choose to add individual accounts or your whole organization, and select all Regions, including future ones.
  3. Choose Create aggregator and open it once it has collected data.
  4. Check it: every account and Region appears as a source with a successful status; set up recording wherever one is missing.

Evidence

  • AWS Config > Settings in each Region, showing recording on for all resource types
  • The aggregator's source list, showing every account and Region reporting
  • Security Hub CSPM control Config.1, showing passed

Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.