AWS Well-Architected Security Pillar
Identity & Access Management

AWS Well-Architected Security Pillar SEC02-BP02: Use temporary credentials

Replace long-lived IAM access keys with short-lived credentials issued via IAM roles, IAM Identity Center, STS or workload identity federation.

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

What else in your programme already covers this

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

CMMC 2.0 · 5 controls

NIST SP 800-53 Rev 5 · 5 controls

NIST SP 800-171 Rev 3 · 4 controls

ISO 27001:2022 · 3 controls

  • 5.17 Authentication information
  • 8.2 Privileged access rights
  • 8.5 Secure authentication

PCI DSS 4.0 · 3 controls

  • 7.2.5 7.2.5 Application and system accounts least privilege
  • 8.6.1 8.6.1 Interactive use of system accounts controlled
  • 8.6.2 8.6.2 No hard-coded passwords for interactive system accounts

Azure Security Benchmark · 2 controls

  • IM-3 Manage application identities securely and automatically
  • PA-2 Avoid standing access for user accounts and permissions

C5 (Germany) · 2 controls

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

FedRAMP High · 2 controls

  • AC-2(2) Automated Temporary and Emergency Account Management
  • IA-11 Re-Authentication

FedRAMP Moderate · 2 controls

  • AC-2(2) Automated Temporary and Emergency Account Management
  • IA-11 Re-Authentication

HIPAA Security Rule · 2 controls

ISO 27002:2022 · 2 controls

  • 5.17 Authentication information
  • 8.5 Secure authentication

NIST Cybersecurity Framework 2.0 · 2 controls

  • NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization
  • NIST-CSF-PR.AA-03 Users, services, and hardware are authenticated

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

ACSC Essential Eight · 1 control

  • E8-ADMIN-ML3 Restrict Administrative Privileges (ML3)

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

  • ASD37-23 Protect authentication credentials (Excellent)

CIS Controls v8 · 1 control

  • CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts

SOC 2 · 1 control

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets

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-BP02 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.

If you hold NIST SP 800-53 Rev 582.5% covered · 11 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.6% covered · 16 gapsIf you hold ISO 27002:202273% covered · 17 gapsIf you hold FedRAMP Moderate69.8% covered · 19 gapsIf you hold Azure Security Benchmark65.1% covered · 22 gapsIf you hold PCI DSS 4.063.5% covered · 23 gaps

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.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll AWS Well-Architected Security Pillar controls