CloudWiki
Rules
Description

Rotating your IAM credentials on a monthly basis is crucial to minimizing the risk of accidental exposure and unauthorized access to your AWS resources. This practice greatly reduces the possibility of a compromised set of access keys being used without your knowledge to gain access to specific parts of your AWS account.

Remediation

To ensure that access keys are rotated every 90 days or less, you can follow these remediation steps:

  1. Set up an IAM policy that requires access keys to be rotated every 90 days or less. You can create a custom IAM policy that specifies the required rotation interval and apply it to your IAM users and roles.
  2. Configure AWS to send reminder notifications to users and administrators when their access keys are due for rotation. You can use AWS Config rules to monitor access key rotation compliance and send notifications via Amazon SNS or email.
  3. Enforce access key rotation during user onboarding and offboarding processes. When a new user is onboarded, ensure that they are aware of the access key rotation policy and their responsibility to comply with it. When a user leaves the organization, ensure that their access keys are disabled or deleted.
  4. Use automation tools to simplify the access key rotation process. You can use AWS Lambda functions or other automation tools to rotate access keys automatically on a scheduled basis.

By following these remediation steps, you can ensure that access keys are rotated regularly to decrease the likelihood of accidental exposures and protect your AWS resources against unauthorized access.

Enforced Resources
Note: Remediation steps provided by Lightlytics are meant to be suggestions and guidelines only. It is crucial to thoroughly verify and test any remediation steps before applying them to production environments. Each organization's infrastructure and security needs may differ, and blindly applying suggested remediation steps without proper testing could potentially cause unforeseen issues or vulnerabilities. Therefore, it is strongly recommended that you validate and customize any remediation steps to meet your organization's specific requirements and ensure that they align with your security policies and best practices.