Customize this training

Get a certificate — $15$5

NIST Cybersecurity Framework 2.0 Foundations

NIST Cybersecurity Framework 2.0 Foundations

Understand the six CSF 2.0 Functions, build a Current and Target Profile, pick a realistic Tier and turn the gaps into an action plan your leadership can follow.

What you will learn

  • Explain what CSF 2.0 is, who it is for and how its Core, Profiles and Tiers fit together.
  • Read the Core structure and apply the Govern Function, including supply chain risk management.
  • Use the Identify and Protect Functions to understand assets and risks and to put safeguards in place.
  • Apply the Detect, Respond and Recover Functions to find, contain and recover from incidents.
  • Build a Current and Target Organizational Profile and turn the gaps into a prioritised action plan.
  • Choose suitable Tiers and use CSF 2.0 to communicate risk, map other standards and report progress.

Modules

  1. What CSF 2.0 is and how it is built
  2. Reading the Core and the Govern Function
  3. Identify and Protect
  4. Detect, Respond and Recover
  5. Organizational Profiles and gap analysis
  6. Tiers, mapping and reporting

Course facts

Level
Awareness
Estimated study time
about 45 minutes
Final assessment
24 questions · Pass mark 80%
Available in
English, العربية
Price
Free. Optional verifiable certificate: $5
Last updated
Published by
AMAADOR ACADEMY

Who this course is for

IT and security staff, risk and compliance officers, auditors, managers and small-business owners who need to use or report against the NIST Cybersecurity Framework 2.0.

Prerequisites

None. Basic familiarity with how an organisation uses computers, networks and cloud services helps.

Course content

1. What CSF 2.0 is and how it is built

The NIST Cybersecurity Framework (CSF) is voluntary guidance from the US National Institute of Standards and Technology. It helps an organisation understand, assess, prioritise and communicate its cybersecurity risks. It does not tell you which product to buy or exactly how to configure a firewall. It describes outcomes to reach, and leaves you to choose how.

VersionYearWhat changed
1.02014First framework, written for US critical infrastructure
1.12018Refinements, more on supply chain and identity
2.026 February 2024Published as NIST CSWP 29; new Govern Function; scope widened to all organisations

NIST's own release says CSF 2.0 is meant for all organisations in any sector, from small schools and non-profits to large agencies and corporations. That is why it is used far beyond the United States: a bank in Casablanca, a hospital group in Riyadh or a manufacturer in Lyon can apply it alongside their national laws. NIST also publishes translations, including an Arabic version listed on its CSF page.

What the CSF is not: it is not a law in most countries, not a certification scheme and not a checklist to tick once. You cannot be "CSF certified". You can show how your practices meet its outcomes, and regulators or customers may ask you to.

2. Reading the Core and the Govern Function

The Core is a three-level tree. Each Function splits into Categories, and each Category into Subcategories, which are the specific outcomes you assess.

FunctionCodeQuestion it answers
GovernGVWho decides, with what strategy, policy and oversight?
IdentifyIDWhat do we have and what are our risks?
ProtectPRWhich safeguards reduce those risks?
DetectDEHow do we find attacks and compromises?
RespondRSWhat do we do once an incident is detected?
RecoverRCHow do we restore assets and operations?

Reading an identifier:GV.OC-01 means Function Govern (GV), Category Organizational Context (OC), Subcategory 01. Its outcome is that the organisation's mission is understood and informs cybersecurity risk management. Always quote identifiers this way in reports; it removes ambiguity between teams and auditors.

NIST presents the Functions as a wheel, with Govern at the centre. They are not a one-way sequence: all six should run at the same time. Govern informs how the other five are carried out; Identify feeds Protect and Detect; lessons from Respond and Recover feed back into Identify (the Improvement Category, ID.IM).

3. Identify and Protect

You cannot protect what you do not know you have. Identify has three Categories.

CategoryTypical evidence
ID.AM Asset ManagementInventories of hardware, software, services, data and suppliers; data flows; assets ranked by criticality
ID.RA Risk AssessmentVulnerability information, threat intelligence, likelihood and impact estimates, a risk register with chosen responses
ID.IM ImprovementLessons from assessments, exercises and real incidents turned into tracked actions
  1. List — every system, application, cloud service and data set, with an owner.
  2. Rank — which ones would stop the business or expose personal data if lost?
  3. Assess — known vulnerabilities and likely threats for the critical ones first.
  4. Decide — accept, reduce, transfer or avoid each risk, in line with the risk appetite set under Govern.
  5. Improve — feed findings back and track them to closure.
Case: the US Government Accountability Office (report GAO-18-559) found that attackers entered Equifax in 2017 through a known, unpatched vulnerability in the Apache Struts software on an online dispute portal, and stayed for 76 days. An expired certificate on a monitoring device meant encrypted traffic was not being inspected · the vulnerable system had not been found and patched · an accurate asset inventory linked to vulnerability scanning (ID.AM, ID.RA) and certificate management would have closed the gap.

4. Detect, Respond and Recover

No set of safeguards is perfect. Detect and Respond limit how long an attacker stays and how far they get.

FunctionCategoryWhat it means in practice
DetectDE.CM Continuous MonitoringNetworks, users, endpoints, cloud services and suppliers are monitored for anomalies
DE.AE Adverse Event AnalysisAlerts are correlated and analysed to decide whether an incident is occurring, then declared
RespondRS.MA Incident ManagementThe response plan is run with partners; incidents are triaged, categorised, prioritised and escalated
RS.AN Incident AnalysisInvestigation establishes what happened and the root cause; evidence is preserved
RS.CO Incident Response Reporting and CommunicationInternal and external stakeholders are notified as required by law, contracts and policy
RS.MI Incident MitigationIncidents are contained and eradicated
  1. Detect — an alert or a staff report reaches a defined contact point.
  2. Triage — is it an incident? How severe? Who must be called?
  3. Contain — isolate affected accounts and systems; preserve logs and images.
  4. Analyse — scope, entry point, data affected.
  5. Notify — management, legal, regulators, customers, within the deadlines that apply to you.
  6. Eradicate — remove the attacker's access and fix the cause.

5. Organizational Profiles and gap analysis

An Organizational Profile describes your cybersecurity posture in terms of Core outcomes. It has two parts:

  • The Current Profile: the outcomes you achieve today, and how well.
  • The Target Profile: the outcomes you want to achieve, chosen from your mission, risk appetite, legal duties and threats.

A Community Profile is a baseline of CSF outcomes written for a shared interest, such as a sector, a technology or a threat. NIST lists Community Profiles on its CSF pages. An organisation can use one as the starting point for its own Target Profile instead of starting from a blank page.

CSF 2.0 describes five steps for creating and using a Profile:

  1. Scope the Profile — the whole organisation, one business unit, one system or one service? Say so clearly.
  2. Gather information — policies, risk register, audit reports, inventories, laws and contracts, any Community Profile that fits.
  3. Create the Profile — decide which Subcategories are in scope and record current and target state for each.
  4. Analyse gaps and create an action plan — compare current and target; prioritise by risk and cost.
  5. Implement the plan and update the Profile — then repeat the cycle.

6. Tiers, mapping and reporting

CSF Tiers describe the rigour of an organisation's cybersecurity risk governance and management. Each Tier is described twice: for governance (how Govern works) and for management (how the other five Functions are run).

TierNameWhat it looks like
1PartialAd hoc, reactive; little awareness of cyber risk at leadership level; supplier risk not managed
2Risk InformedLeaders approve risk practices, but they are not organisation-wide policy; awareness exists but is uneven
3RepeatableRisk practices are approved as policy, applied consistently and updated as risks change
4AdaptivePractices adapt from lessons and indicators; cyber risk is part of the organisational culture and decisions

How to use Tiers well:

  1. Assess — which Tier best describes how you work today? Use evidence.
  2. Choose a target Tier — based on your risks, legal duties, customer expectations and resources.
  3. Link to the Profile — the target Tier guides how rigorous the Target Profile actions must be.
  4. Review — revisit after major changes, incidents or new regulations.

Remember: Tier 4 is not mandatory and not always sensible. NIST encourages moving to a higher Tier when risks or mandates are greater, or when a cost-benefit analysis shows a feasible and cost-effective reduction of cyber risk. Tiers are a guide for discussion, not a certification score.

The full lesson continues in the interactive course on this page.

Sources and references

Educational course based on NIST CSWP 29 (CSF 2.0). Not affiliated with or endorsed by NIST. The CSF is voluntary guidance, not a certification; it does not replace legal or regulatory obligations in your country (for example national cybersecurity laws or sector rules) or professional advice for your organisation.

All courses · Cybersecurity and IT — Free courses, certificate $5 | AMAADOR ACADEMY