AWS Config Not Enabled
AWS Config is not recording resource configuration in every Region, so changes to resources are not tracked and configuration rules and most Security Hub checks cannot run.
| Severity | Low |
| CVSS 3.1 | 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N Open in the calculator |
| CVSS 4.0 | 2.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-778: Insufficient Logging |
| OWASP Top 10 | A09:2025 Security Logging and Alerting Failures |
| Category | Insufficient Logging |
Description
AWS Config records the configuration of supported resources, such as security groups, IAM roles, S3 buckets and EC2 instances, as configuration items each time they change, and keeps a history of those changes and of the relationships between resources. Without it, the organisation has no reliable record of how its resources were configured at a given time: after an incident it may be unable to establish when a security group was opened, a bucket policy changed or a role's permissions widened, and, together with CloudTrail, by whom.
Config rules and conformance packs evaluate the recorded configuration against policy, and AWS Security Hub relies on Config for most of its security checks, so without a recorder, misconfigurations introduced by mistake or by an attacker are not detected by Config rules, and Security Hub cannot assess most of its controls. The weakness gives no access on its own; it weakens detection, investigation and assurance.
Config is enabled per Region by a configuration recorder and a delivery channel. The finding is raised when no recorder exists, when it is stopped, when it records only a narrow set of resource types, or when Regions are left out. IAM users, groups, roles and customer managed policies are global resources and are normally recorded in a single Region to avoid duplicates. The configuration is reviewed with aws configservice describe-configuration-recorders and aws configservice describe-configuration-recorder-status in each Region, and is reported by Prowler, ScoutSuite and Security Hub.
Remediation
Enable AWS Config in every Region in use, recording all supported resource types:
- Create a configuration recorder that records all supported resource types (
allSupportedset to true), include the global IAM resource types in one Region only, and start it withaws configservice start-configuration-recorder. - Deliver configuration history and snapshots to an S3 bucket in a dedicated log archive account.
- In an AWS organisation, deploy Config to all accounts and Regions centrally, for example with AWS Control Tower or CloudFormation StackSets, and use an aggregator in the security account to view every account together.
- Deploy Config rules or conformance packs for the organisation's key controls, such as public S3 buckets, unrestricted security groups and unencrypted volumes, and enable Security Hub on top of Config.
- Where cost is a concern, use daily recording for resource types that change frequently rather than leaving them unrecorded.
Confirm the fix with aws configservice describe-configuration-recorder-status showing the recorder recording, with a successful last status, in each Region.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.