What Does NIST Compliance Mean?

There is no single "NIST compliance" and no official NIST certificate. The US National Institute of Standards and Technology (NIST) publishes several cybersecurity documents, and what you need to do depends on which one applies to you and why.

For most organisations, the conversation starts with the NIST Cybersecurity Framework (CSF) 2.0, published on 26 February 2024. It describes cybersecurity outcomes without prescribing how to achieve them, which makes it usable by organisations of any size or sector.

0
CSF Functions
0
CSF Categories
0
CSF Subcategories

Which NIST Publication Applies to You?

Start by identifying the reason you are looking at NIST: a customer contract, a regulator, or a wish to improve your own programme. The answer points to the right document.

Publication Purpose Status
CSF 2.0 Organisation-wide cybersecurity risk management outcomes Voluntary
SP 800-53 Rev. 5 Catalogue of security and privacy controls in 20 families, used for US federal systems US federal
SP 800-171 Rev. 3 Protecting US Controlled Unclassified Information in nonfederal systems, across 17 families Often contractual
SP 800-82 Rev. 3 Security guidance for operational technology Guidance

In Saudi Arabia, adopting NIST does not replace your obligations under NCA or sector regulations. It works best as a way to organise your programme, while your regulator's controls remain the requirement you must evidence. Even so, the two fit well together: the NCA's own OTCC methodology, for example, draws on the NIST CSF.

The 6 CSF Functions

The CSF Core organises outcomes into Functions, Categories and Subcategories. Version 2.0 added Govern, which informs how an organisation carries out the other five Functions.

01
Govern (GV)
Sets risk strategy, expectations and policy: context, roles, oversight and supply chain risk.
6 Categories
02
Identify (ID)
Understands current risk through asset management, risk assessment and improvement.
3 Categories
03
Protect (PR)
Applies safeguards: access control, awareness, data security, platform security and resilient infrastructure.
5 Categories
04
Detect (DE)
Finds and analyses possible attacks through continuous monitoring and adverse event analysis.
2 Categories
05
Respond (RS)
Acts on detected incidents through management, analysis, communication and mitigation.
4 Categories
06
Recover (RC)
Restores affected assets and operations, and communicates during recovery.
2 Categories

Organisations can also use four Tiers to describe how rigorous their cybersecurity risk governance and management are. Tiers help set direction; they are not a compliance score, and NIST does not require every organisation to reach Tier 4.

Tier Name
Tier 1 Partial
Tier 2 Risk Informed
Tier 3 Repeatable
Tier 4 Adaptive

How to Implement the CSF

NIST's suggested approach centres on Organizational Profiles: a Current Profile of the outcomes you achieve today and a Target Profile of those you want to achieve. The steps below follow that approach, with validation added at the end.

6-Step CSF Roadmap
01
Scope the Profile
Decide what the Profile covers: the whole organisation, a business unit, or a specific system. Record who owns it and why you are building it.
Output: defined scope
02
Gather Information
Collect the inputs you need, such as policies, risk priorities, asset records, contractual duties, and regulatory requirements including those from the NCA.
Output: source pack
03
Create Current & Target Profiles
Record which outcomes you achieve today and choose the ones you need. You do not have to treat every Subcategory equally; prioritise according to your risk.
Output: two profiles
04
Analyse Gaps & Plan Actions
Compare the two Profiles, consider the risk behind each gap, and build a prioritised action plan with owners, resources and dates.
Output: action plan
05
Implement & Update
Carry out the plan using control catalogues such as SP 800-53 where helpful, then update the Profile as risks, technology and business needs change.
Ongoing
06
Validate Independently
Have an independent assessor test your claims against evidence. Report the result honestly, such as "aligned with CSF 2.0, Target Profile achieved", rather than as a certificate.
Output: assessment report

Common NIST Mistakes

Most problems come from misunderstanding what NIST publications are, rather than from the technical controls themselves.

⚠️

Beware of "NIST Certified" Claims: NIST does not certify organisations against the CSF. A "NIST certified" badge from a vendor is not a NIST credential. If a contract requires SP 800-171, overstating your position can bring contractual and legal consequences, so make sure every claim is backed by evidence.

Other common mistakes are treating the CSF as a checklist, which NIST explicitly says it is not; adopting NIST and assuming that NCA requirements are covered; and building a Profile once and never updating it. Before relying on any publication, also check for newer versions: NIST released a draft of SP 800-82 Rev. 4 in September 2026.

How CyberOps Can Help

CyberOps can help you decide which NIST publications matter for your organisation and how they fit alongside NCA, SAMA and customer requirements, so you avoid doing the same work twice.

Our gap and risk assessments can form the basis of your Current and Target Profiles. Our GRC, vulnerability assessment, penetration testing and security awareness services can then support your action plan.

Ready to Align with NIST?

Book a free consultation with our GRC specialists and get a high-level readiness assessment within 48 hours.

Get in Touch