RA-05 (05) Privileged Accessra-5.5
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 RA-05 (05). 6 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 RA-05 (05). 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 RA-05 (05). The nearest authored work is below.
Nobody has assessed RA-05 (05) 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-JIT, KSI-IAM-SNU — that is where the authoring would land. Browse /collect for the whole authored corpus.
Reaches the same indicator, not RA-05 (05)
These recipes prove a KSI that reaches it. None of them claims RA-05 (05) — treat them as neighbours worth reading, not as coverage.
- 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-JIT
- 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-JIT
- The enforced half of who may change what: the service control policy type actually enabled in the organization root, the customer-authored SCPs and the roots, OUs and accounts each one is attached to, and the permissions boundary carried by every principal your own tagging marks as a change authority via KSI-IAM-JIT
- Every identifier the account has issued, with the date it was assigned and the AWS-generated unique id behind it; the workforce identifiers issued through IAM Identity Center and the external issuer each one came from; and the CloudTrail record of identifiers being deleted, which is the only dated evidence of a name becoming free to reuse via KSI-IAM-JIT
- 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-SNU
What NIST requires of RA-05 (05)
The control statement from NIST 800-53 Rev5, verbatim. Square brackets are organization-defined parameters — yours to set, not FedRAMP's to dictate.
Implement privileged access authorization to [system components] for [vulnerability scanning activities].
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 (2)
Under 20x, these indicators are how this control is demonstrated — automated KSI evidence stands in for narrative control evidence.
- 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.
- IAMKSI-IAM-SNUSecuring Non-User Authentication
Appropriately secure authentication methods are used and persistently reviewed for 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.
- Follow the FedRAMP Vulnerability Detection and Response and Vulnerability Evaluation and Reporting rules.This guidance points at the Vulnerability Detection and Response rules (VDR, 18 requirements).This guidance points at the Vulnerability Evaluation and Reporting rules (VER, 23 requirements).
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.