IA-04 (04) Identify User Statusia-4.4
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-04 (04). 14 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-04 (04). 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-04 (04). The nearest authored work is below.
Nobody has assessed IA-04 (04) against AWS and pipeline yet. That is a gap in this project’s research — not a finding about the control, and not a claim that nothing collects it.
The KSIs that reach it are KSI-IAM-AAM, KSI-IAM-ELP, KSI-IAM-JIT — that is where the authoring would land. Browse /collect for the whole authored corpus.
Reaches the same indicator, not IA-04 (04)
These recipes prove a KSI that reaches it. None of them claims IA-04 (04) — treat them as neighbours worth reading, not as coverage.
- Full snapshot of every IAM user, group, role, and attached/inline policy with their relationships, used to review that granted permissions match least-privilege intent via KSI-IAM-AAM KSI-IAM-ELP
- Documented just-in-time / break-glass privilege-elevation process backed by IAM Identity Center permission sets and account assignments, showing privileged access is role/attribute-based, time-bound, and approval-gated rather than standing via KSI-IAM-AAM KSI-IAM-JIT
- The mechanism that ends a temporary or emergency account without anyone deciding to: the AWS Config rule that measures how long an IAM credential has gone unused, the period it is configured with, the remediation configuration proving the revocation fires automatically, and an empty non-compliant set showing nothing has outlived the period via KSI-IAM-AAM
- Account-wide credential report proving MFA is active per principal and that passwords/access keys are rotated within policy via KSI-IAM-ELP
- Active unused-access findings identifying IAM roles, access keys, console passwords, and service/action-level permissions that have not been used within the configured age, driving right-sizing and removal via KSI-IAM-ELP KSI-IAM-JIT
What NIST requires of IA-04 (04)
The control statement from NIST 800-53 Rev5, verbatim. Square brackets are organization-defined parameters — yours to set, not FedRAMP's to dictate.
Manage individual identifiers by uniquely identifying each individual as [characteristics].
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 (3)
Under 20x, these indicators are how this control is demonstrated — automated KSI evidence stands in for narrative control evidence.
- IAMKSI-IAM-AAMAutomating Account Management
The lifecycle and privileges of all accounts, roles, and groups are securely managed using automation.
- IAMKSI-IAM-ELPEnsuring Least Privilege
Identity and access management measures are used and persistently reviewed to ensure each user or device can only access the resources they need.
- IAMKSI-IAM-JITAuthorizing Just-in-Time
A least-privileged, role and attribute-based, and just-in-time security authorization model is used and persistently reviewed for all user and non-user accounts and services.
FedRAMP guidance & parameters
Where you read the rule. Guidance names an FRR document, never a clause, so the links below offer the whole document and leave the reading to you.
| Parameter | FedRAMP-defined value |
|---|---|
| ia-04.04_odp | contractors; foreign nationals |
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.