The phrase, and why it has no certificate
The National Institute of Standards and Technology writes the documents. It does not audit anyone, certify anyone, or keep a list of organizations that meet its standards. So when a customer, a contract, an insurer, or a board member says "we need to be NIST compliant," the first job is to find out which document they mean, because the three most common answers ask for very different things.
SP 800-171: the contract one
NIST Special Publication 800-171 is for Controlled Unclassified Information (CUI) held in systems the government does not own. It has 110 security requirements in Revision 2, organized into fourteen families, and it is the document behind every CMMC Level 2 requirement in a Department of Defense contract.
If the person asking holds or flows down a defense contract, this is the one. The expected answer is a self-assessment score computed under 32 CFR 170.24 and submitted to the Supplier Performance Risk System, and, from November 10, 2026, a third-party certification for applicable new awards. Revision 3 of 800-171 was published in 2024 with 97 requirements, but the CMMC program still assesses against Revision 2, so a contract that says 800-171 means Revision 2 until the clause says otherwise.
SP 800-53: the catalog one
NIST Special Publication 800-53 is the catalog: more than a thousand controls in twenty families, written for federal information systems and the programs built on them, including FedRAMP. Nobody implements all of it. It is used by selecting a baseline and tailoring it, which is why "800-53" on its own tells you very little until someone names the baseline.
It is also the document most other guidance derives from. CISA's Secure Cloud Business Applications (SCuBA) baseline for Microsoft 365, for example, is a specific set of tenant settings, each traced back to an 800-53 control. So when an insurer's questionnaire or a customer's security review cites NIST, it is usually asking about a handful of 800-53 controls in practice: multifactor authentication, privileged access, logging, encryption, backup and recovery.
If the person asking is a customer running a security review, an insurer, or an auditor, this is probably the one, and what they will accept is evidence that specific controls are in place, not a statement that the organization follows NIST.
The Cybersecurity Framework: the board one
NIST's Cybersecurity Framework is not a control list. It is a way of organizing a security program into functions, from governance through identification, protection, detection, response, and recovery, so that leadership can talk about it without reading a catalog. It has no score, no assessor, and no pass mark.
If the person asking sits on a board or reads about security in the business press, this is usually the vocabulary they have. The framework is a useful way to present a program. It is not something an organization is assessed against, and a vendor offering to make you "framework compliant" is selling a word.
Who is asking, and what they will accept
- A defense contract clause or a prime means SP 800-171 Rev. 2, and will accept a self-assessment score in SPRS, or a C3PAO certification where the contract requires one.
- A customer security review, an insurer, or an auditor means SP 800-53 controls, usually through a baseline such as SCuBA, and will accept evidence that named controls are in place.
- A board or an executive means the Cybersecurity Framework, and will accept a program described in its functions, with the evidence behind it.
The useful answer is evidence against a named set
Whatever the document, the response that ends the conversation is the same: a named control set, each control evidenced as in place or recorded as a gap, and a plan for the gaps. A statement of belief does not satisfy a contracting officer, an underwriter, or an assessor, and it should not satisfy a board.
For an organization on Microsoft 365, most of the evidence lives in the tenant and can be collected setting by setting. That is what Mount Xion's identity security assessment does for the 800-53-derived controls, and what its CMMC readiness engagement does for all 110 requirements of 800-171.
Common questions
Is there a NIST certification?
No. NIST publishes standards and guidance and certifies nothing. CMMC certification, which is based on NIST SP 800-171, is issued through the Department of Defense's program by authorized third-party assessors. FedRAMP authorization, based on 800-53, is granted by the government. Outside those programs, "NIST compliant" is a self-description.
Which document does a cyber insurer mean?
Usually none by name. Insurance questionnaires ask about specific controls, multifactor authentication, privileged access, backups, email protection, logging, that trace back to 800-53. The useful answer is evidence for each question, which is also what makes the next renewal easier.
Our customer sent a questionnaire that says NIST. What do we send back?
Ask which document and which controls, then answer each with evidence: the setting, where it is configured, and when it was last verified. A current assessment report with evidence for every finding answers most questionnaires directly.
Does 800-171 apply to us if we are not a defense contractor?
Only if a contract says so. 800-171 is tied to Controlled Unclassified Information, which flows down through federal, mostly defense, contracts. A commercial customer asking for NIST almost always means 800-53-derived controls, not 800-171.
Should we adopt the Cybersecurity Framework?
As a way to organize and present the program to leadership, it is useful and free. It does not replace a control set with evidence behind it, and it is not something to be assessed against.
Where Mount Xion fits. Mount Xion's Microsoft 365 identity security assessment reviews controls that map to the CISA SCuBA baseline and the derived NIST SP 800-53 Rev. 5 controls, with evidence for every finding. Its CMMC readiness engagement evidences all 110 NIST SP 800-171 Rev. 2 controls and computes the self-assessment score. Both are fixed-fee and scoped on a discovery call.