AWSOverview
Access keys are long-term credentials for an IAM user or the AWS account root user. You can use access keys to sign programmatic requests to the AWS CLI or AWS API (directly or using the AWS SDK).
One of the best ways to protect your account is to not allow users to have multiple access keys as this is being used for programmatic requests.
Remediation guidance
From Console
Perform the following action to deactivate access keys:
- Sign into the AWS console as an Administrator and navigate to the IAM Dashboard.
- In the left navigation pane, choose Users.
- Click on the User name for which more than one active access key exists.
- Click on Security credentials tab.
- Click on the Make inactive to
deactivatethe non-operational key.
Note: Test your application to make sure that the active access key is working.
From Command Line
Run the update-access-key command below using the IAM user name and the non-operational access key IDs to deactivate the unnecessary key.
aws iam update-access-key --access-key-id <accessKeyID> --status Inactive --user-name <username>
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.
There is only one active access key available for any single IAM user
Connectors
Covered asset types
Expected check: eq []
AWS130IAM13 {...AssetFragment}
