AWS Well-Architected Security Pillar
Identity & Access Management

AWS Well-Architected Security Pillar SEC02-BP05: Audit and rotate credentials periodically

Use IAM credential reports, Access Advisor and Access Analyzer to find unused credentials, rotate keys on schedule and remove stale users and roles.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 59 controls across 21 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

PCI DSS 4.0 · 5 controls

  • 7.2.5.1 7.2.5.1 Application and system account access reviewed periodically
  • 8.2.6 8.2.6 Inactive accounts removed within 90 days
  • 8.3.9 8.3.9 Single-factor passwords changed every 90 days or dynamic analysis
  • 7.2.4 7.2.4 User accounts and privileges reviewed every six months
  • 8.6.3 8.6.3 System account passwords protected against misuse

FedRAMP High · 4 controls

FedRAMP Moderate · 4 controls

HIPAA Security Rule · 4 controls

NIST SP 800-66 Rev 2 · 4 controls

  • ASBv3-LT-2 Enable threat detection for identity and access management
  • ASBv3-PA-4 Review and reconcile user access regularly
  • PA-3 Manage lifecycle of identities and entitlements

CIS Controls v8 · 3 controls

  • CIS-5.1 Establish and Maintain an Inventory of Accounts
  • CIS-5.3 Disable Dormant Accounts
  • CIS-5.5 Establish and Maintain an Inventory of Service Accounts

ISO 27001:2022 · 3 controls

  • 5.16 Identity management
  • 5.17 Authentication information
  • 5.18 Access rights

NIST SP 800-171 Rev 3 · 3 controls

NIST SP 800-53 Rev 5 · 3 controls

UK Cyber Essentials · 3 controls

  • CE-AC.3 Remove or Disable Accounts When No Longer Required
  • CE-AC.4 Privileged Account Approval and Tracking
  • CE-AC.6 Periodic Review of Privileged Access
  • ANSSI-HYG-05 Maintain an Exhaustive Inventory of Privileged Accounts
  • ANSSI-HYG-09 Assign the Correct Rights on Sensitive Resources

C5 (Germany) · 2 controls

  • C5-IDM-03 Locking and withdrawal of user accounts in the event of inactivity or multiple failed logins
  • C5-IDM-05 Regular review of access rights

CMMC 2.0 · 2 controls

ISO 27002:2022 · 2 controls

  • 5.17 Authentication information
  • 5.18 Access rights
  • NIST-CSF-DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events
  • NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization

NIST SP 800-161 Rev 1 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)
  • SOC2-CC6.2 CC6.2 Registering and authorising users before issuing credentials
  • E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)

ISO 27701:2019 · 1 control

  • 6.6.2 User access management

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Identity & Access Management

You are reading one control. How much of AWS Well-Architected Security Pillar have you already done?

AWS Well-Architected Security Pillar SEC02-BP05 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of AWS Well-Architected Security Pillar your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 52 of 63 AWS Well-Architected Security Pillar controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 59 it maps to, and the evidence behind each claim, over MCP and REST.