ID.SC-3 Supply chain contracts reflect cybersecurity requirements

NIST Cybersecurity Framework (1.1, legacy) · 1.1

What the standard requires

Contracts with suppliers and third-party partners are used to implement appropriate measures designed to meet the objectives of an organization’s cybersecurity program and Cyber Supply Chain Risk Management Plan.

Quoted verbatim from NIST Cybersecurity Framework (CSF) 1.1, which is in the public domain.

Maps to 3 controls in 3 other frameworks

Framework	Control
HITRUST CSF v11	05.b.03 Security requirements are included in third-party agreements
NIST Cybersecurity Framework 2.0	GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts
TISAX (VDA ISA v6)	6.1.1 Information security requirements for suppliers are defined

Mappings are CMDash’s own, seeded with the product and shown on both frameworks they connect. In the product they mean evidence you attach here also counts against the controls listed above.

Integrations that carry evidence for this family

CrowdStrike Falcon

Endpoint inventory

These connectors produce data relevant to NIST Cybersecurity Framework (1.1, legacy)’s Identify (ID) family, which is the granularity CMDash publishes — there is no pre-built per-control mapping, and claiming one would be inventing it. You decide which evidence answers which control.

Track ID.SC-3 with evidence behind it

In CMDash this control is a row with an owner, a status, uploaded evidence kept with its full history, and an export an assessor can read.

Start free trial All NIST Cybersecurity Framework (1.1, legacy) controls