CSF 2.0 Profiles and Tiers: Where You Are and Where You Want to Be
Current Profiles, Target Profiles and the four CSF Tiers
TL;DR (for busy owners)
- What it is: An Organizational Profile describes your cybersecurity posture in terms of CSF outcomes. A Current Profile says what you achieve today; a Target Profile says what you need to achieve. Tiers describe how rigorous your risk governance and management practices are.
- Why it matters: The gap between Current and Target is your roadmap — and a defensible answer when a board, customer or auditor asks "why these priorities?"
- Quick action: For each of the six Functions, write one sentence on where you are today and one on where you need to be in 12 months.
How Profiles work
- Scope the Profile: the whole company, one product, or one cloud environment.
- Gather information: policies, risk priorities, regulatory and contractual requirements, threats you care about.
- Create the Current Profile: which CSF outcomes (categories and subcategories) are achieved today, and how well.
- Create the Target Profile: which outcomes you need, informed by risk appetite and obligations.
- Analyze the gap and create an action plan.
- Implement and update the Profile as things change.
NIST's Organizational Profiles Quick-Start Guide (SP 1301) describes these steps in more detail.
The four Tiers
| Tier | Name | What it typically looks like |
|---|---|---|
| 1 | Partial | Ad hoc, reactive; limited awareness of cyber risk at the organizational level |
| 2 | Risk Informed | Leadership approves risk practices, but they are not consistently applied organization-wide |
| 3 | Repeatable | Practices are formally approved, expressed as policy and applied consistently |
| 4 | Adaptive | Practices adapt based on lessons learned and changing threats, as part of organizational culture |
Tiers are not a maturity score to maximize. NIST notes that organizations should choose a target Tier that fits their risk and resources; progression is not always required.
Common mistakes
- Treating the Target Profile as "every outcome at the highest level".
- Building the Current Profile from policy documents instead of what actually happens.
- Producing a gap analysis without owners, dates or a budget decision.
Fast checks
Profile readiness
- The scope of the Profile is written down
- The Current Profile is based on evidence, not just policy
- The Target Profile reflects legal, contractual and customer requirements
- Each gap has an owner, a priority and a target date
- A current and target Tier were chosen deliberately
Map to frameworks
Related NIST CSF 2.0 outcomes
Where Securitain fits
Securitain does not generate CSF Profiles. For AWS environments it can supply evidence for the identity and data outcomes in your Current Profile — for example who holds sensitive permissions, which roles trust external accounts and which resources are exposed — and its finding-to-control mappings support compliance evidence for supported frameworks.
Next steps
One page is enough to start
A one-page Current and Target Profile across the six Functions, with three prioritized gaps, is more useful than a 200-row spreadsheet nobody maintains. See how to prioritize the gaps.
Sources & References
- 1.The NIST Cybersecurity Framework (CSF) 2.0 — NIST CSWP 29
Profiles and Tiers are defined in the framework text
- 2.NIST CSF 2.0: Quick-Start Guide for Creating and Using Organizational Profiles (SP 1301)
Step-by-step Profile guidance
- 3.NIST CSF 2.0: Quick-Start Guide for Using the CSF Tiers (SP 1302)
How to choose and use Tiers
Finding-to-control mapping and evidence for supported frameworks, from a read-only AWS connection.
Gather AWS evidence for your Current Profile