NIST SP 800-53 Rev. 5 SR-2(1) — Establish Scrm Team

What this control requires

Establish a dedicated supply chain risk management (SCRM) team with defined roles and responsibilities to lead and support SCRM activities. This team should consist of personnel from various departments, including IT, security, legal, and procurement, to ensure a comprehensive approach to managing supply chain risks. This control supports the Supply Chain Risk Management, Organizational Team capability within the Supply Chain Risk Management family.

In plain English

Establish a dedicated supply chain risk management (SCRM) team with defined roles and responsibilities to lead and support SCRM activities. In practice, this means you can prove you policy management-level controls on a defined cadence.

Why it matters

SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan.

Within Supply Chain Risk Management, the assessor will trace your implementation back to the catalogue reference (Control SR-2(1)) and look for objective evidence on the latest two assessment cycles.

How to implement

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

• Policy. Document the trigger, the owner and the cadence.
• Security. Document the trigger, the owner and the cadence.
• Chain. Document the trigger, the owner and the cadence.
• Control. Document the trigger, the owner and the cadence.
• Supply. Document the trigger, the owner and the cadence.
• Scope: management, personnel, capability, policy, roles, security, scrm team, it.

Evidence to collect

• Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Establish Scrm Team.

Common pitfalls

• Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• HIPAA (45 CFR Part 164) 164.308(a)(5)(i) — Security Awareness and Training
• BSI C5:2020 SP-01 — Documentation, communication and provision of policies and instructions
• ISO/IEC 27001:2022 A.5.21 — Managing information security in the ICT supply chain
• NIST SP 800-171 Rev. 3 3.17.2 — Acquisition Strategies, Tools, and Methods

Related controls in NIST SP 800-53 Rev. 5

• Control SR-3 — Supply Chain Controls And Processes
• Control SR-1 — Policy And Procedures
• Control SR-4(2) — Track And Trace
• Control SA-12(6) — Minimizing Procurement Time
• Control SR-4(1) — Identity
• Control PM-4 — Plan Of Action And Milestones Process

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control SR-2(1)

Topics: governance riskpolicy managementsupply chain security