Join our Newsletter — 33% off our NHI Course
Home› Guides› NIST CSF 2.0 Profiles and Tiers Guide: Build…
Guide Regulations & Frameworks

NIST CSF 2.0 Profiles and Tiers Guide: Build Current and Target Profiles That Drive Decisions

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 13 min read
On this page

Most NIST CSF 2.0 programmes produce a spreadsheet of scores that nobody uses, because the Organizational Profile was never scoped to a decision and the Tiers were treated as a maturity grade to maximise. This guide goes beyond our CSF 2.0 overview to show how to design, populate and govern Current and Target Profiles, how to select Tiers the way NIST intends, how the two interact, and how to turn the gap into a funded action plan. It draws on the CSF 2.0 core document (CSWP 29), the Quick-Start Guides SP 1301 (Organizational Profiles) and SP 1302 (Tiers), and NIST's published templates. It is written for GRC leads, CISOs, internal auditors and consultants who build or review CSF profiles.

Key takeaways

  • Scope the Profile to a decision. A Profile for a business unit, system or product that leadership must fund or accept is far more useful than one generic organisation-wide score sheet.
  • Tiers describe rigour, not maturity. CSF 2.0 says Tiers complement your risk methodology rather than replace it, and SP 1302 encourages higher Tiers only when risks or mandates require them.
  • Leadership selects Tiers at Function or Category level. SP 1302 says selection at the overall, Function or Category level gives a better picture than per Subcategory.
  • Ratings need evidence definitions. CSF prescribes no scale, so define what each rating level requires in evidence before anyone scores, or results drift between assessors and years.
  • The gap becomes a plan of action. CSWP 29 names a risk register, risk detail report or Plan of Action and Milestones as the output; a Profile without one has not finished step 4.

Profiles and Tiers in CSF 2.0: what each is for

CSF 2.0 (NIST CSWP 29, February 2024) has three components: the Core (Functions, Categories and Subcategories of outcomes), Organizational Profiles and Tiers. Profiles say which outcomes matter and how well they are achieved; Tiers say how rigorously cybersecurity risk is governed and managed.

ConstructQuestion it answersGranularityWho owns itTypical output
Current ProfileWhich Core outcomes are we achieving or attempting now, and how well?Subcategory (or Category)Control owners, assessed by GRC or auditStatus, rating and evidence per outcome
Target ProfileWhich outcomes have we selected and prioritised, allowing for expected change?Subcategory (or Category)CISO with business risk ownersPriority and goals per outcome
Community ProfileWhat shared baseline does a sector, technology or threat community recommend?SubcategoryPublishing community (NIST, sector bodies)Starting point for a Target Profile
Tiers (1 Partial, 2 Risk Informed, 3 Repeatable, 4 Adaptive)How rigorous are our governance and risk management practices?Overall, Function or CategoryOrganisation leadershipCurrent and target Tier per Function, with characteristics

For the Core, the Govern Function and mapping to other control sets, see the NIST CSF 2.0 Guide and the NIST CSF 2.0 Govern Function Guide.

Designing an Organizational Profile

Choosing the scope

  • Whole organisation: useful for a board baseline or annual report; usually too coarse to drive specific investment.
  • Business unit or subsidiary: fits groups where units have different regulators or risk appetites, or after an acquisition.
  • System, product or service: fits a critical platform, a SaaS product sold to regulated customers, or an OT site.
  • Threat or use case: a ransomware readiness Profile or a supplier assurance Profile, often started from a Community Profile.
  • Multiple Profiles: SP 1301 explicitly supports several Profiles with different scopes and combining them where scopes overlap. Keep a common outcome list so they can roll up.

Information to gather first

CSWP 29 lists the inputs: policies, risk priorities and resources, enterprise risk profiles, business impact analysis registers, requirements and standards, practices and tools, and work roles. NIST IR 8286D (February 2025) describes using business impact analysis to set impact values and protection requirements that feed enterprise risk management, which gives the Target Profile its priorities. See the NIST IR 8286 Cybersecurity and ERM Integration Guide.

The columns

SP 1301's notional template has the CSF outcome (identifier and description), then Current Profile columns for practices (policies, processes, procedures, roles, optional evidence), status and rating, then Target Profile columns for priority and goals. Gaps are found by reading Current and Target side by side. NIST publishes the CSF 2.0 Organizational Profile Template as an XLSX file, and SP 1301 encourages adding or removing columns; Current and Target may even use different columns.

ColumnRecommended contentCommon addition
OutcomeCSF 2.0 Subcategory ID and text, or a custom outcomeIn scope flag with exclusion rationale
Current practicesPolicy, process and tool that deliver the outcome, with roleLink to evidence (ticket, report, configuration export)
Current status and ratingStatus narrative plus a rating on a defined scaleAssessment date and assessor
Target priorityHigh, medium, low or 1 to 5Driver: regulation, contract, risk scenario
Target goalsPlanned outcome state, drawn from Informative References, new requirements or threat intelligenceTarget date
Informative ReferencesMapped controls, for example SP 800-53 CM-1 and CM-2ISO/IEC 27001 Annex A reference; see the NIST CSF to ISO 27001 Mapping Guide
ActionGap closure activity, owner, cost, dateRisk register or POA&M identifier

Rating outcomes consistently

CSF does not prescribe a rating scale. SP 1301's examples include high, medium and low, 1 to 5, or a percentage. Whatever you choose, define each level by evidence before scoring.

RatingEvidence definition (example for a 0 to 4 scale)
0 Not achievedNo practice in place, or practice exists only informally with no evidence
1 InitiatedPractice designed or partially deployed; covers less than half of in-scope assets
2 Partially achievedPractice documented and operating for most in-scope assets; known exceptions not yet tracked
3 Largely achievedPractice operating across scope; exceptions recorded and approved; evidence available on request
4 Fully achievedPractice operating across scope, measured by a metric, independently tested within the last 12 months

Worked example: SP 1301 uses PR.PS-01 (configuration management practices are established and applied). The notional Current Profile rates it 3 out of 5 with high priority, noting inconsistent change control and unenforced baselines; the Target goals are enforced baselines, continuous monitoring and documented change approvals, with SP 800-53 CM-1 and CM-2 as references. Writing the gap that specifically is what makes the action plan obvious.

Selecting and using Tiers

Tiers characterise the rigour of cybersecurity risk governance (the Govern Function) and cybersecurity risk management (Identify, Protect, Detect, Respond and Recover). CSWP 29 Appendix B gives notional characteristics that organisations can reuse, customise or replace.

TierGovernance characteristics (Appendix B, summarised)Management characteristics (Appendix B, summarised)
1 PartialRisk strategy applied ad hoc; prioritisation informal and not tied to objectives or threatsLimited awareness; risk managed irregularly case by case; information sharing may be lacking; supplier risks largely unknown
2 Risk InformedManagement approves practices, but they are not organisation-wide policy; priorities informed by risk objectives and the threat environmentRisk recognised at organisational level without an organisation-wide approach; assessments not consistently repeated; informal sharing
3 RepeatablePractices formally approved as policy, implemented as intended, reviewed and updated as conditions changeOrganisation-wide approach; routine information sharing; consistent methods to respond to risk changes; supplier risk addressed through written agreements and governance
4 AdaptiveOrganisation-wide, risk-informed policies; executives monitor cyber risk alongside financial risk; budgets reflect risk environment and tolerancePractices adapt from lessons learned and predictive indicators; continuous improvement; near real-time supplier information; sharing with authorised third parties

How to select

  1. Leadership decides: SP 1302 says selection is generally performed by organisation leadership, which ties Tiers to risk appetite (GV.RM-02).
  2. Pick the level: overall, per Function or per Category; never per Subcategory.
  3. Weigh the factors SP 1302 lists: current risk management practices, threat environment, legal and regulatory requirements, information sharing practices, business and mission objectives, supply chain requirements and organisational constraints including resources.
  4. Test the choice: the selected Tier should support goals, be feasible, and reduce risk to critical assets to an acceptable level.
  5. Use components separately if useful: SP 1302 allows a governance-only scope that omits the management descriptions.

Decision guidance

  • Small organisations: Tier 2 for most Functions with Tier 3 for Respond and Recover is often a defensible target; a single organisation-wide Profile at Category level is usually enough.
  • Regulated or critical infrastructure operators: regulators and customers expect documented, consistently applied practice, which is Tier 3 language; Tier 4 is justified where threat exposure and the cost of failure are highest.
  • Groups and multinationals: set a group-wide Tier floor in Govern, then let business units set Function Tiers for their own risk.
  • Do not average: reporting "Tier 2.6" hides the Function that matters; report per Function.

How Tiers and Profiles work together

SP 1302 gives the pattern: if leadership sets Tier 2 for Identify and Protect, the Current Profile shows how well Tier 2 characteristics are achieved in each relevant Category, and the Target Profile shows the improvements needed to fully meet Tier 2. In practice:

  • Tier sets the bar for "how": a Tier 3 target for Respond means incident procedures are approved policy, consistently applied and updated, so RS outcomes such as RS.MA-01 need documented plans and exercises, not just capability.
  • Profile sets the bar for "what": the Target Profile lists which outcomes must be achieved at all; a high Tier cannot compensate for an outcome left out of scope.
  • Use both in board reporting: current and target Tier per Function, plus the percentage of high-priority outcomes at target rating.
  • Do not confuse with maturity models: a domain maturity model can sit underneath a Profile row to explain a rating; see the GRC Maturity Model.

Using Community Profiles as a starting point

A Community Profile is a shared baseline of outcomes for organisations with a common interest, and CSWP 29 says an organisation can use one as the basis for its Target Profile. NIST's profiles page lists, among others, the Manufacturing, Ransomware Risk Management, Incident Response, Semiconductor, Genomic Data, Transit and Foundational PNT Profiles, the Cloud Security Alliance's Cloud Security Community Profile and the Cyber Risk Institute's Financial Sector Profile, plus a draft federal O-RAN deployment Profile. NIST also links a draft Community Profile template and guidance on creating Community Profiles.

  1. Select the Community Profiles that match your sector and top threats.
  2. Import their priorities as the first draft of your Target Profile.
  3. Adjust for your own risk appetite, regulation and contracts, and record why each change was made.
  4. Keep the Community Profile version in the Profile header so updates can be tracked.

See the NIST CSF 2.0 Community Profiles Catalogue Guide and, for a worked sector example, the NIST CSF Manufacturing Profile Guide.

From gap to action plan: a phased rollout

  1. Weeks 1 to 2, scope and sponsor: agree the Profile scope, the decision it supports, the rating scale with evidence definitions and the Tier selection level.
  2. Weeks 2 to 6, gather and draft: collect the CSWP 29 inputs, start from a Community Profile if one fits, and draft Target priorities with risk owners.
  3. Weeks 4 to 10, assess the Current Profile: interview control owners, collect evidence and rate. Pilot on one Function first (Protect is usually the most evidence-heavy) to calibrate assessors.
  4. Weeks 8 to 12, select Tiers: leadership workshop using Appendix B characteristics and SP 1302 factors; record current and target Tier per Function.
  5. Weeks 10 to 14, analyse gaps: list gaps for high-priority outcomes, estimate cost and effort, and feed them into the risk register or POA&M (SP 800-53 PM-4, CA-5). See the Risk Register Template.
  6. Ongoing, implement and update: track progress with KPIs, KRIs and POA&Ms as SP 1301 suggests; refresh after major change and at least annually.
  7. Rollback and correction: if ratings prove inconsistent, freeze the published version, re-calibrate on a sample with a second assessor and re-issue with a change note, rather than silently editing scores.

The CSF 2.0 Organizational Profile worksheet in the CSF 2.0 Organisational Profiles Template can be used as-is for steps 2 to 5.

Detection, measurement and governance of the Profile

  • Attainment: percentage of high-priority outcomes at or above target rating.
  • Gap closure: POA&M items closed on time against those due.
  • Evidence freshness: share of ratings backed by evidence less than 12 months old.
  • Tier alignment: Functions whose current Tier meets the leadership target.
  • Assessor consistency: rating differences between two assessors on a sample of outcomes.
  • Exceptions: outcomes excluded or accepted as risk, each with a named approver and review date.
Outcome or controlRole in running Profiles and Tiers
GV.RM-01, GV.RM-02Risk objectives and risk appetite that set Target priorities and Tiers
GV.OV-01, GV.OV-03Reviewing strategy outcomes and risk management performance, which is where Profile results are reported
ID.RA-05Using threats, vulnerabilities, likelihood and impact to prioritise risk response
ID.IM-01, ID.IM-02Improvements identified from evaluations, tests and exercises, which update the Current Profile
GV.SC-01Supply chain programme; CSWP 29 notes a Target Profile can set supplier expectations
SP 800-53 PM-9, PM-4, CA-5Risk management strategy and Plan of Action and Milestones that carry the gap

Common failure patterns

  • Self-attested ratings without evidence: scores reflect what owners believe, not what operates. The Change Healthcare breach began with a stolen credential on a Citrix remote access portal that did not require MFA; an evidence-based rating of PR.AA-03 across every internet-facing access path is the kind of check that surfaces such an exception before attackers do.
  • Tier 4 as the universal target: NIST frames progression as risk and mandate driven, and Tier 4 everywhere is rarely affordable or necessary.
  • Per-Subcategory Tiers: SP 1302 advises against it; it creates hundreds of judgements with no added insight.
  • One Profile for everything: an organisation-wide average hides the critical platform with the weakest controls.
  • No action plan: a gap list without owners, dates and funding stops at step 3 of the five.
  • Stale Profiles: a Profile not refreshed after an acquisition, new regulation or major incident gives leadership false comfort.

Practitioner checklist

  • Write the decision each Profile supports and its scope in the Profile header.
  • Define the rating scale with evidence requirements before assessing.
  • Start the Target Profile from a relevant Community Profile and record every deviation.
  • Record exclusions with a rationale and an approver.
  • Have leadership select Tiers per Function or Category using the SP 1302 factors.
  • Report current and target Tier per Function, never an averaged Tier.
  • Feed every high-priority gap into the risk register or POA&M with owner, cost and date.
  • Calibrate ratings with a second assessor on a sample each cycle.
  • Refresh Profiles at least annually and after major change.

Standards and references

Related NHI Mgmt Group resources: NIST CSF 2.0 Guide · CSF 2.0 Organisational Profiles Template · NIST CSF 2.0 Community Profiles Catalogue Guide · NIST IR 8286 Cybersecurity and ERM Integration Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.