NIST CSF

Released / current context

NIST Cybersecurity Framework is a voluntary framework; CSF 2.0 expanded governance focus and is widely used globally.

Mandatory or voluntary

Voluntary unless required by customer, contract, grant, regulator, or sector-specific governance.

Who should care

Security programs that want a practical cyber-risk structure across Govern, Identify, Protect, Detect, Respond, and Recover outcomes.

Control model

Functions, categories, subcategories, profiles, target state, current state, gaps, risk decisions, and measurable improvement actions.

What NIST CSF asks teams to prove

Cybersecurity Framework becomes operational when obligations are turned into scoped controls, named owners, evidence requests, review decisions, residual risk, and management reporting. The guide page keeps that chain explicit so buyers can understand how the standard is handled inside PlanGRC.

Practical roadmap

1. Define scope

   Confirm business units, systems, data classes, regions, and services where NIST CSF applies.

2. Map controls

   Translate obligations into controls, owner assignments, due dates, testing approach, and evidence expectations.

3. Collect proof

   Request evidence from owners, preserve attachments or vault references, and keep reviewer decisions traceable.

4. Assess gaps

   Score readiness, identify missing evidence, evaluate residual risk, and create remediation tickets where needed.

5. Report and maintain

   Publish executive and audit-ready views, keep exceptions visible, and re-run periodic reviews after change.

Related workflows