Using NIST CSF 2.0 to organize security work
Use the six NIST CSF 2.0 functions, current and target profiles, and evidence of completed work to organize a business security plan.

NIST’s Cybersecurity Framework 2.0 provides a way to describe security outcomes and discuss priorities. It can help management and IT organize the work without starting with a shopping list of products.
Use it alongside your business requirements and applicable Canadian obligations. Picking a framework won’t protect your systems or meet a legal or contractual requirement on its own.
Understand the six functions
The framework has six functions. Govern was added in version 2.0; Identify, Protect, Detect, Respond and Recover remain part of the structure. They run together and continuously.
In practical terms:
- Govern: Agree on priorities, responsibilities and how the business makes security decisions.
- Identify: Understand the assets, dependencies and risks in scope.
- Protect: Put safeguards around accounts, information and systems.
- Detect: Identify and assess activity that may indicate a problem.
- Respond: Manage an identified incident and its communications.
- Recover: Restore affected operations and check the result.
NIST’s framework FAQs explain the structure and its focus on outcomes. The Core doesn’t prescribe one universal set of implementation steps.
Begin with a business scope
Choose the services, systems and information the review covers. Include suppliers and the work that depends on them.
Ask management which interruptions or disclosures would have the greatest effect. Record the requirements that come from clients, contracts, insurers and applicable law; ask your lawyer or adviser about any you’re unsure of.
NIST’s small-business quick-start guide offers a starting point for organizations with modest or no existing security plan. It supplements the framework.
Compare current and target outcomes
A Current Profile records the relevant outcomes being achieved and how. A Target Profile states the outcomes the organization wants to achieve. Profiles and Tiers existed before CSF 2.0; they aren’t entirely new additions.
Use evidence to describe the current state. If device coverage or a restore procedure hasn’t been verified, record the uncertainty instead of assuming the outcome is complete.
NIST’s profile guide explains how to tailor and use profiles. The gap between the two gives you work to prioritize.
Use Tiers with context
Tiers describe the rigour of risk governance and management, from Partial to Adaptive. They don’t certify that a device or product is secure.
Use the Tier guide to support a discussion about the processes the organization needs. Claiming a higher tier won’t close a gap unless the practice changes too.
Turn gaps into owned actions
For each priority, name the business owner, technical work, dependencies and acceptance evidence. Record the cost and a realistic review date.
Use the security action-plan guide to organize delivery. Check completed work against the selected outcomes and keep unresolved exceptions visible.
NIST doesn’t offer certification for CSF implementations. Describe what you’ve assessed and completed accurately, and revisit the profiles when the business or its systems change.


