ID.SC-4 Suppliers and partners routinely assessed

NIST Cybersecurity Framework (1.1, legacy) · 1.1

What the standard requires

Suppliers and third-party partners are routinely assessed using audits, test results, or other forms of evaluations to confirm they are meeting their contractual obligations.

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

Maps to 2 controls in 2 other frameworks

Framework	Control
NIST Cybersecurity Framework 2.0	GV.SC-07 The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored
TISAX (VDA ISA v6)	6.2.2 Supplier security is monitored over time

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-4 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