“Follow NIST” can mean three different things. Start with the one you answer to.

  • We read the clause, board request or agency contract and tell you whether it means NIST SP 800-171, CSF 2.0 or SP 800-53.
  • We build it into Microsoft 365 and Azure with your IT team or MSP, and document what sits outside the tenant.
  • If more than one applies, you get one control set mapped across all of them, so the work is done once.

Book a 30 minute call

Three NIST frameworks, one control setLine drawing. A contract points to NIST SP 800-171, a board request to CSF 2.0 and an agency system to SP 800-53. All three lead into one control set in your Microsoft 365 and Azure tenant, set up in Entra ID, Intune, Defender and Purview. A crosswalk maps each control to all three, which gives evidence each reviewer can follow.ContractBoardAgencySP 800-171CSF 2.0SP 800-53Your Microsoft 365 and Azure tenantEntra ID, IntuneDefender, PurviewCrosswalk3.5.3 PR.AA-03 IA-2(1)Evidence each reviewer can followOne control setMapped once

200+ Microsoft 365 and Azure tenants. 100+ engagements. 20+ years in regulated technology.

Three ways “NIST” lands on your desk

The words are similar. The obligations are not.

“The contractor shall implement NIST SP 800-171.”

Typical line in a defense contract or subcontract

Points to SP 800-171 Rev 2

That usually arrives through DFARS 252.204-7012. It applies to the systems that hold the contract’s CUI, and it is the basis of CMMC Level 2.

“Should we adopt the NIST framework?”

Typical question from a board or owner

Points to CSF 2.0

They usually mean the Cybersecurity Framework: a voluntary structure for the program, not a contract requirement.

“The system must meet SP 800-53 controls.”

Typical line in a federal agency contract

Points to SP 800-53 Rev 5

You run a system for a federal agency. The agency decides which controls apply and who reviews them.

Last checked

Same publisher, different jobs

What each framework is for, what it asks and who checks it, as of November 2026.

Contract requirement

NIST SP 800-171

Protecting CUI in contractor systems

Applies when
Your contract or subcontract includes DFARS 252.204-7012 and your systems hold CUI
Size
110 requirements in 14 families, in Rev 2
Version in use
Rev 2. NIST finalized Rev 3 on May 14, 2024, but CMMC Level 2 and DoD contracts still point to Rev 2.
Who checks it
The Department of War and your prime, through CMMC self assessments posted in SPRS, C3PAO assessments and DIBCAC reviews

Voluntary structure

NIST CSF 2.0

A structure for any security program

Applies when
Nothing outside requires a framework, or leadership wants one structure to report against
Size
Six functions: Govern, Identify, Protect, Detect, Respond and Recover. Govern is new in 2.0.
Version in use
2.0, released February 26, 2024, and written for organizations of any size or sector
Who checks it
No one, unless you ask for a review

Federal systems

NIST SP 800-53

Controls for federal information systems

Applies when
You operate a system on behalf of a federal agency and the contract names SP 800-53 controls
Size
A catalog in 20 control families. The agency decides which controls apply.
Version in use
Rev 5, Release 5.2.0 of August 27, 2025
Who checks it
The agency you run the system for

Working toward CMMC? Take the CMMC readiness check

When more than one applies, the work is done once

SP 800-171 was derived from SP 800-53, and CSF 2.0 covers the same ground at a higher level. So one setting in the tenant can often answer all three, and the crosswalk shows where.

Crosswalk, three NIST frameworks

Sample format, illustrative content

Sample crosswalk
Control in your environment SP 800-171 CSF 2.0 SP 800-53
MFA required by Conditional Access 3.5.3 PR.AA-03 IA-2(1)
Audit logs kept in Purview 3.3.1 PR.PS-04 AU-2, AU-11
Intune configuration baselines 3.4.1 PR.PS-01 CM-2
Badge access to the office, outside the tenant 3.10.1 PR.AA-06 PE-2

How the work runs, and how long it takes

A step shows a length only when the length is known. The rest depends on which framework applies and what the gap register finds.

  1. A 30 minute call

    Length 30 minutes

    Bring the clause, request or contract that says NIST. You leave knowing which framework it most likely means and what the first step would be.

  2. Confirm which NIST applies

    Length Set by how many contracts and requests there are to read

    We read the contracts, subcontracts and requests, and write down which framework each one points to, for which systems, and why.

  3. Gap register

    Length About four weeks for CMMC Level 2. For CSF 2.0 or SP 800-53, set when we agree the scope.

    Each requirement checked against your tenant as it is today, with what meets it, what is missing and who owns it. For SP 800-171 that means scoring all 110 requirements the way SPRS counts them.

  4. Close the gaps

    Length Depends on what the gap register finds

    Changes in Entra ID, Intune, Defender and Purview with your IT team or MSP, in stages so nobody is locked out. Policies, training and physical security are documented with the people who own them.

  5. Keep the evidence current

    Length Ongoing, if you want it

    Evidence refreshed on a schedule so the next review is a check, not a project. This can run under our fractional security and compliance officer service.

What we need from your side

The contracts and requests that mention NIST, admin access agreed with your IT team or MSP, a person who can approve changes, and someone who can decide on scope and licenses.

Work we have delivered

What we can say about past SP 800-171 work without naming clients.

  • Defense, CMMC Level 2

    One defense contractor started with a four week gap assessment that scored all 110 NIST SP 800-171 requirements. It passed its CMMC Level 2 C3PAO assessment with every requirement met.

  • Defense, plan of action

    A Level 2 POA&M that an Air Force Research Laboratory program office accepted as the basis for releasing CUI.

CMMC Level 1 and 2

Who this is for, and who it is not for

A good fit

  • Contractors and subcontractors with NIST SP 800-171 in a contract.
  • Organizations adopting CSF 2.0 as the structure for their program.
  • Teams running a system for a federal agency on Microsoft 365 or Azure.
  • Anyone told to “follow NIST” without being told which one.

Not a fit

  • You want a report and no changes made in the tenant.
  • You need the assessment itself. Your assessor is independent of us.
  • You need help desk support.
  • You need legal advice on a contract. We tell you what a requirement asks of your environment, and your counsel reads the contract.

Questions before you book

Rev 2 or Rev 3?

NIST finalized Rev 3 on May 14, 2024, but CMMC Level 2 is built on Rev 2, and DoD contracts still point to Rev 2. If CMMC or DFARS 252.204-7012 is your reason, work to Rev 2 unless your contract says otherwise. We track both and tell you when that changes.

We are a subcontractor. Does this apply to us?

If your subcontract involves covered defense information, the prime has to flow DFARS 252.204-7012 down to you without alteration, so SP 800-171 applies to the systems that hold that information. Check the subcontract for the clause, and ask the prime what data you will receive.

Do we need all of SP 800-53?

Usually not. It is a catalog of 20 control families, and the agency decides which controls apply to your system. We start from what your contract names.

Is CSF 2.0 something an auditor checks?

Not on its own. CSF 2.0 is a voluntary structure for a security program. Many teams use it to report to the board and to map their other frameworks.

Can one control set cover NIST and SOC 2?

Often, for the controls that live in the tenant. The crosswalk can carry SOC 2 or ISO 27001 columns too. Each framework is still judged on its own terms by its own auditor or assessor, so each keeps its own column and evidence.

Can a tenant meet every requirement?

No. In SP 800-171, physical protection (3.10), personnel security (3.9), and the policy and training requirements are met outside the tenant. We document them with the people who own them.

Does this get us ready for CMMC?

For the controls, yes. CMMC Level 2 is built on the 110 requirements of SP 800-171 Rev 2, so the work carries over. Levels, scoring and assessments are covered on our CMMC page, linked above.

How is the work priced?

As a fixed scope project, or as a fractional security and compliance officer on retainer. We agree the scope in writing before work starts.

What happens after you book

  1. Pick a 30 minute time that suits you.
  2. We talk through the clause or request, your systems and your dates.
  3. You leave knowing which NIST applies and what the first step would be.

Bring the clause that says “NIST” to a 30 minute call.

You leave knowing which framework applies, what it asks of your tenant and what comes next.

Book a 30 minute call

(786) 577-9743 sales@ethereumtech.ai