SR-02 (01) Establish SCRM Teamsr-2.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.
No pipeline API proves itA Key Security Indicator reaches SR-02 (01) and no pipeline API decides it. This project has assessed it and closed it: the evidence is a document a person writes and an assessor reads, not telemetry. The reason is below.
Collect evidence (0)
Authored AWS and pipeline recipes whose output is evidence for SR-02 (01). This mapping is this project’s opinion (AWS overlay v3.0.0, pipeline overlay v0.8.0), versioned separately from the dataset — the upstream FedRAMP rules name none of these tools.
The control establishes a supply chain risk management team — organization-defined personnel, roles and responsibilities, leading defined SCRM activities. Nothing a pipeline emits evidences a team's existence or its charter. Recorded against the plan rather than silently: `docs/automation-beyond-aws.md` §P5 lists SR-02 (01) among the controls build attestation bears on, and `docs/code-scanning-overlay-plan.md` step 8 carries that into the attestation authoring batch. The control text does not support it. The attestation argument belongs to si-7.7 on its detection limb; KSI-SVC-VRI, which asks for cryptographic validation of integrity, reaches si-7 and si-7.1 instead — both already covered by an AWS partial recipe, which is where a pipeline attestation recipe would sit beside rather than replace one. A 3PAO reads the SCRM plan and the team's charter.
This project’s assessment (automation register v0.9.0, reviewed 2026-08-13), versioned separately from the dataset and from the evidence overlays. It is an opinion about the pipeline surface on that date, and the surface moves.
No recipe reaches it through its indicators either. The KSI that reaches it is KSI-PIY-RIS — which is what asks for it. The evidence it asks for is written, not fetched. Browse /collect for the whole authored corpus.
What NIST requires of SR-02 (01)
The control statement from NIST 800-53 Rev5, verbatim. Square brackets are organization-defined parameters — yours to set, not FedRAMP's to dictate.
Establish a supply chain risk management team consisting of [personnel, roles and responsibilities] to lead and support the following SCRM activities: [supply chain risk management 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 (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.