IA-05 (01) Password-based Authenticationia-5.1
Whether an AWS call fetches evidence for this control, and what to run. Its Rev5 baselines, the indicators that reach it and the FedRAMP guidance attached to it open below.
Nothing names itNo recipe names IA-05 (01). 5 reach an indicator it shares, which is adjacency and not coverage — worth reading, not worth recording as evidence for this control.
Collect evidence (0)
Authored AWS recipes whose output is evidence for IA-05 (01). This mapping is this project’s opinion (overlay v3.0.0), versioned separately from the dataset — the upstream FedRAMP rules name none of these tools.
No authored recipe names IA-05 (01). The nearest authored work is below.
get-account-password-policy returns the length, complexity, reuse and age settings this enhancement asks for, and the ODPs are numbers a recipe can carry as parameters — that half is telemetry. The organization-defined values themselves, and whether IAM users are the password population at all on an estate signing in through an external IdP, are the judgement. Dropped from iam-credential-report on 2026-08-26: access-key age is not a password rule.
A recipe would call:
This project’s assessment (automation register v0.9.0, reviewed 2026-08-26), versioned separately from the dataset and from the evidence overlays. It is an opinion about the AWS surface on that date, and the surface moves.
The KSI that reaches it is KSI-IAM-APM — that is where the authoring would land. Browse /collect for the whole authored corpus.
Reaches the same indicator, not IA-05 (01)
These recipes prove a KSI that reaches it. None of them claims IA-05 (01) — treat them as neighbours worth reading, not as coverage.
- Account-wide credential report proving MFA is active per principal and that passwords/access keys are rotated within policy via KSI-IAM-APM
- AWS Config compliance result for the managed rule proving every IAM user with a console password has MFA enabled via KSI-IAM-APM
- AWS Config compliance result proving long-lived IAM access keys (including those used by service/non-user identities) are rotated within the maximum age via KSI-IAM-APM
- Every way a workforce user can authenticate into the account, counted and named in one pass — how many IAM users and federated trusts exist, which SAML and OIDC providers are registered, whether an IAM Identity Center instance is the workforce entry path — together with the state of the two credentials that belong to no person: the root user's access key and the account's X.509 signing certificate via KSI-IAM-APM
- For every Amazon Cognito directory that fronts non-organizational users: the user pool's multi-factor configuration, and every identity pool's guest-access flag together with the named external providers it will exchange a token for via KSI-IAM-APM
What NIST requires of IA-05 (01)
The control statement from NIST 800-53 Rev5, verbatim. Square brackets are organization-defined parameters — yours to set, not FedRAMP's to dictate.
For password-based authentication: (a) Maintain a list of commonly-used, expected, or compromised passwords and update the list [frequency] and when organizational passwords are suspected to have been compromised directly or indirectly; (b) Verify, when users create or update passwords, that the passwords are not found on the list of commonly-used, expected, or compromised passwords in IA-5(1)(a); (c) Transmit passwords only over cryptographically-protected channels; (d) Store passwords using an approved salted key derivation function, preferably using a keyed hash; (e) Require immediate selection of a new password upon account recovery; (f) Allow user selection of long passwords and passphrases, including spaces and all printable characters; (g) Employ automated tools to assist the user in selecting strong password authenticators; and (h) Enforce the following composition and complexity rules: [composition and complexity rules].
NIST SP 800-53 Rev5 catalog 5.2.0, from usnistgov/oscal-content at 78650f0. The FedRAMP dataset carries no control text; this is borrowed and pinned.
Rev5 baseline membership
Membership is the whole relationship — a baseline is a set of control ids. Class A carries no baseline at all. The Low/Moderate/High labels are an interpretation from control counts, not a dataset fact.
KSI indicators reaching this control (1)
Under 20x, these indicators are how this control is demonstrated — automated KSI evidence stands in for narrative control evidence.
Pages exist for the 209 controls reached by at least one KSI. Baseline-only controls are the orphans on /coverage. Control titles and full text live in the NIST catalog, not this dataset.