AWSOverview
The "root" account is the most privileged user in an AWS account. AWS Access Keys provide programmatic access to a given AWS account. It is recommended that all access keys associated with the "root" account be removed.
Rationale
Removing access keys associated with the root account limits vectors by which the account can be compromised. Additionally, removing the root access keys encourages the creation and use of role based accounts that are least privileged.
Remediation guidance
Perform the following to delete or disable active root access keys being used
Via the AWS Console
- Sign in to the AWS Management Console as Root and open the IAM console at https://console.aws.amazon.com/iam/.
- Click on <Root_Account_Name> at the top right and select
Security Credentialsfrom the drop down list - On the pop out screen Click on
Continue to Security Credentials - Click on
Access Keys(Access Key ID and Secret Access Key) - Under the Status column if there are any Keys which are Active
- Click on
Make Inactive- (Temporarily disable Key - may be needed again) - Click
Delete- (Deleted keys cannot be recovered)
References
- https://docs.aws.amazon.com/general/latest/gr/aws-access-keys-best-practices.html
- https://docs.aws.amazon.com/general/latest/gr/managing-aws-access-keys.html
- https://docs.aws.amazon.com/IAM/latest/APIReference/API_GetAccountSummary.html
- CCE-78910-7
- CIS CSC v6.0 #5.1
Service-wide remediation
Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.
AWS
Use AWS Organizations guardrails, AWS Config rules or conformance packs where they fit, approved account baselines, and IaC modules so new resources inherit the secure setting.
Operational rollout
- Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
- Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
- Re-scan and track approved exceptions with an owner and expiry date.
Query logic
These are the stored checks tied to this control.
AWS Root users with access key
Connectors
Covered asset types
Expected check: eq []
{
rootUsers(
where: {
hasIAMUserCredentials: {
OR: [{ accessKey1Active: true }, { accessKey2Active: true }]
}
}
) {
connector {...AssetFragment}
}
}
