Creating a NIST CSF 2.0 Profile: From the Current State to the Target Profile

How do you build current and target profiles with NIST CSF 2.0? The six functions, evidence-based category scoring, implementation tiers and a work plan from the gaps.
Technical summary
Technology
NIST CSF 2.0, NIST CSWP 29, NIST SP 800-53, CIS Controls, ISO/IEC 27001:2022
Topic
Measuring security posture with CSF 2.0 current and target profiles
Level
Intermediate
Prerequisites
  • Defining the scope and stakeholders
  • Access to reports from security tools
  • Risk assessment outputs
In this article7 sections

The question “what’s our security posture?” is answered with a product list: we have a firewall, we have EDR, we have backups. Management can’t make anything of this, and an auditor won’t accept it. The NIST Cybersecurity Framework (CSF) 2.0 describes an organization’s cybersecurity posture with the question “what outcome is achieved” instead of “which product is installed”. The practical tool for this is the profile: the difference between the current profile, which shows today, and the target profile turns into a prioritized work plan. This guide walks security and IT teams step by step through category-based assessment, the correct interpretation of tiers and turning gaps into concrete work.

The structure and functions of NIST CSF 2.0

CSF 2.0 was published by NIST in February 2024 as NIST CSWP 29. Its most visible difference from 1.1 is the Govern function; it ties cybersecurity risk management to organizational governance. The core has three levels: 6 functions, 22 categories, 106 subcategories.

Function Categories The question it asks
Govern (GV) GV.OC, GV.RM, GV.RR, GV.PO, GV.OV, GV.SC Are strategy, roles, policy and supply chain risk defined?
Identify (ID) ID.AM, ID.RA, ID.IM Are assets and risks known, and is improvement happening?
Protect (PR) PR.AA, PR.AT, PR.DS, PR.PS, PR.IR Are access, data, platforms and infrastructure protected?
Detect (DE) DE.CM, DE.AE Are adverse events monitored and analyzed?
Respond (RS) RS.MA, RS.AN, RS.CO, RS.MI Can an incident be managed and contained?
Recover (RC) RC.RP, RC.CO Can the recovery plan be executed and communication managed?

Subcategories are outcome statements. PR.AA-01 describes the outcome “identities and credentials for authorized users, services and hardware are managed by the organization”, and PR.DS-11 “backups of data are created, protected, maintained and tested”. They don’t say which technology will deliver it. For that, NIST also publishes implementation examples and informative references to other standards.

The concept of current and target profiles

In CSF 2.0, an organizational profile means selecting the outcomes in the core that are meaningful for the organization and describing their status. There are two types:

  • Current profile: To what extent each selected outcome is achieved today, and the evidence for it.
  • Target profile: The desired state and priority for each outcome, taking into account risk appetite, regulatory obligations and business goals.

NIST also refers to community profiles, which define a common target for a sector or threat scenario. They’re useful as a starting point when building your own target profile.

The first big decision in profile work is scope. A single profile for the whole organization gives management the big picture but stays too abstract for the technical team. A practical method: one profile for the organization as a whole, and a separate profile for a high-risk area (such as the production network or e-commerce infrastructure processing customer data). If the scope isn’t written at the top of the profile, the sentence “PR.PS-02 is met” becomes a claim for which it’s unclear which systems it applies to. A score without scope is an empty score.

The category-based assessment method

A team that tries to assess all 106 subcategories in detail in the first round usually gets stuck by the third week. This flow is more realistic:

  1. Define the scope and stakeholders. Assign an owner for each function; a management representative is essential for Govern.
  2. Select the subcategories. Leave out those irrelevant to the scope, with the reason.
  3. Score the status of each subcategory on the scale, and always tie the score to evidence.
  4. Set the target score and priority. The target doesn’t have to be the highest score everywhere; targeting 4 in every subcategory produces a plan with no budget.
  5. Calculate the gap and move it into the work plan.

CSF 2.0 doesn’t impose a scoring scale. A simple scale with clear definitions increases consistency between assessors; two people scoring the same control differently is the problem we see most often:

Score Definition Expected evidence
0 Not implemented None
1 Partial, person-dependent One-off output, undocumented practice
2 Defined, incomplete coverage A procedure exists and works on some systems
3 Defined and full coverage A tool report shows the full scope
4 Measured and improved Metric trend, record of regular review

Keeping the assessment in a table or tool with the fields below makes later mapping and reporting easier. Example rows (in CSV format):

subcategory,scope,current,target,priority,evidence,owner
ID.AM-01,Organization-wide,2,3,High,"CMDB and EDR inventory comparison",IT Infrastructure
PR.AA-03,Organization-wide,2,3,High,"Conditional Access report; no MFA on VPN",Identity Team
PR.DS-11,Organization-wide,3,4,Medium,"Backup job report; restore test once a year",Systems Team
DE.CM-01,Production network,1,3,High,"No traffic monitoring on the OT network",Security
ID.IM-04,Organization-wide,1,3,High,"Incident response plan in draft, no exercise",ISMS

Interpreting implementation tiers

Alongside profiles, the CSF defines four implementation tiers: Tier 1 Partial, Tier 2 Risk Informed, Tier 3 Repeatable and Tier 4 Adaptive. A common mistake is to use the tier like a subcategory-level maturity score. The two measure different things.

Tiers describe the overall character of the organization’s cybersecurity risk management and risk governance practices: are risk decisions made through a formal process, are they spread across the organization, are supply chain risks taken into account, are they adapted based on threat information? In other words, the tier shows the management environment in which the profile scores are produced. An organization that implements most technical controls well but leaves risk decisions to individuals may stay at Tier 2 despite high profile scores. A good system administrator isn’t a process.

In practice, the target tier is set once with management and affects the priorities of the target profile. Organizations that aim for written processes spread across the organization often choose Tier 3. In an organization targeting Tier 3, gaps in the GV.RM and GV.PO categories get high priority regardless of technical gaps.

Prioritizing gaps and the work plan

Every difference between current and target is a work item; they don’t all carry the same weight. Three inputs are used together for prioritization:

  • Gap size: The distance between the target and current scores.
  • Priority: The importance given in the target profile; it comes from the risk assessment and obligations.
  • Dependency: Some outcomes are preconditions for others. DE.CM monitoring coverage can’t be measured before the ID.AM inventory is complete. You can’t monitor a device you don’t know about.

With the example rows above, the work plan takes this shape. The missing MFA on the VPN (PR.AA-03) is both high priority and quick to close; it goes into the first quarter. Completing and exercising the incident response plan (ID.IM-04) starts in the same period, because it has few external dependencies. OT network monitoring (DE.CM-01) first needs an asset inventory of that network; that’s why the improvement of ID.AM-01 for the OT scope is brought forward. For backups (PR.DS-11), the gap is small and closes by increasing the frequency of restore testing. A test once a year doesn’t count as testing.

Each work item is written with an owner, an end date and a definition of “what evidence will show it’s closed”. As the work plan progresses, the profile is rescored; the cycle is repeated at least once a year, and additionally after major architectural changes. If the gaps need to be presented to management in the language of risk, the profile outputs can be combined with a cybersecurity risk assessment.

Mapping to other frameworks

The CSF doesn’t describe detailed controls itself; that’s why it’s usually used together with another control set. Through the Cybersecurity and Privacy Reference Tool (CPRT), NIST publishes informative references linking CSF 2.0 subcategories to sources such as SP 800-53; there are also mapping documents for ISO/IEC 27001 and CIS Controls.

Purpose Framework to map to Benefit
Choosing technical safeguards CIS Controls Breaks a subcategory into implementable safeguards
Certification ISO/IEC 27001:2022 Profile evidence is also used in ISMS records
Detailed control design NIST SP 800-53 Rev. 5 Control-level requirements and enhancements
Regulatory compliance NIS2 risk management measures Carries obligations into the target profile

The goal of mapping isn’t to link everything to everything, but to collect evidence once and use it in multiple frameworks. An MFA coverage report is the same evidence for PR.AA-03, for the ISO 27001 8.5 secure authentication control and for CIS safeguards 6.3–6.5. One report, three audits. Prioritization with CIS Controls is explained in the CIS Controls implementation groups article, and mapping NIS2 obligations to technical controls in the NIS2 technical measures guide.

The full text of the framework is on NIST’s Cybersecurity Framework page and in the NIST CSWP 29 publication; quick start guides and profile templates are available from the same page. Support for turning the profile work into a roadmap and management reporting is available within enterprise cybersecurity consulting.

Frequently asked questions

What’s the main difference between NIST CSF 2.0 and 1.1?

The most notable difference is the Govern function; strategy, roles, policy, oversight and supply chain risk management are gathered in this function. In addition, the scope was extended beyond critical infrastructure to all organizations, categories were reorganized, and supporting resources such as implementation examples and profile templates were added.

Is an implementation tier the same as a profile score?

No. The profile score shows to what extent the outcome is achieved in each subcategory. The tier describes the overall character of the organization’s cybersecurity risk management and governance, that is, how formal, consistent and adaptive its risk decisions are.

Is NIST CSF mandatory for a company in Türkiye?

No, the CSF is a voluntary framework and isn’t a direct legal requirement in Türkiye. Thanks to its outcome-focused structure, it’s widely used to measure the current state, report to management, and gather different obligations such as ISO 27001, NIS2 or customer requirements into a single target profile.

How often should the profile assessment be updated?

At least once a year; and also after a major architectural change, a merger or a serious security incident. As items in the work plan close, the related subcategories can also be rescored in between.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Cybersecurity

Firewall, VPN, endpoint security and threat prevention. We reduce the attack surface and measure and report the risks.

Knowledge Center

Other articles