Who this checklist is for
It is designed for organisations establishing a baseline before an assurance review, a security programme refresh or a scoped conversation with a supplier.
Need urgent help? Call +48 732 059 711 (answered around the clock) or email pilne@cydefen.com.
NIST CSF 2.0 · reviewed 23 August 2026
A useful readiness review shows where the organisation can make and evidence a decision under pressure. This checklist follows the six functions of NIST CSF 2.0 while keeping the questions practical for security and IT leaders.
It is designed for organisations establishing a baseline before an assurance review, a security programme refresh or a scoped conversation with a supplier.
For every item, mark not started, partly evidenced or evidenced. Name the accountable owner and link to the record that proves the practice works. A policy without operating evidence does not count as complete.
Name the executive owner, operational lead and deputies. Record who may accept risk, approve exceptions and release emergency funding.
Define which services, legal entities, suppliers and locations the programme covers. Make exclusions visible and time-bound.
Identify critical dependencies and confirm that contracts address access, notification, recovery, evidence and exit arrangements.
Start with the outcomes the organisation must continue delivering, then map systems, data, people, facilities and external dependencies beneath them.
Give important assets and data named owners. Apply classification rules that change access, handling, retention and recovery decisions.
Describe plausible events and their operational impact. Prioritise using business consequence and exposure, not a vulnerability score alone.
Protective measures and detection should be reviewed together: prevention without visibility leaves the team unsure whether a control held.
Review joiners, movers, leavers, strong authentication, service accounts, administrator paths and emergency access. Test the process with real records.
Define approved baselines, patch decisions and exception handling. Make unauthorised or high-risk change visible to an accountable team.
For each critical service, identify the logs and alerts that would reveal misuse or failure, who reviews them and what triggers escalation.
Train for role-specific decisions and provide a simple reporting path. Measure whether people can recognise and escalate the scenarios they may face.
Document severity criteria, decision rights, safe communication channels and alternates. Avoid a plan that depends on one unavailable person.
Prepare contact routes and decision prompts for customers, regulators, insurers, law enforcement, suppliers and internal leadership where relevant.
Run a scenario that crosses security, IT, legal, communications and a critical supplier. Track every lesson to an owner and completion date.
Set service restoration priorities and acceptable data loss with business owners. Check that technical recovery plans reflect those decisions.
Test restoration under realistic constraints, including identity, dependencies, clean infrastructure and people. Keep evidence of the result and follow-up work.
Feed incidents, exercises, audit findings and near misses back into risk decisions, control design and investment priorities.
We will send the working copy for internal use. This form does not add you to a newsletter or an automated sales sequence.
After submission, the file is also available on the confirmation page.