SEC02-BP04 Rely on a centralized identity provider
Federate workforce access to AWS through a single corporate identity provider via IAM Identity Center or SAML so that user lifecycle, MFA and access reviews are centrally governed.
Source: AWS Well-Architected Security Pillar, SEC02-BP04. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open AWS Well-Architected Security Pillar in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- IAM Identity Center configuration · Cloud console / configuration management
- SCIM provisioning logs · Identity provider / directory
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- SAML or OIDC IdP trust · Document repository
- Joiner mover leaver process · Policy repository / GRC workspace
First move
Common gaps auditors find
- local IAM users for workforce
- no SCIM deprovisioning
- duplicate identities across accounts
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetSEC02-BP03 Store and use secrets securely · SEC02-BP05 Audit and rotate credentials periodically