Two lab technicians in safety glasses testing medical-device equipment, one at a computer and one adjusting an instrument rack

Medical & regulated devices

NIST SP 800-171A Rev. 3 (assessing CUI security requirements), explained

Last updated:

NIST SP 800-171A Revision 3, "Assessing Security Requirements for Controlled Unclassified Information," is the companion assessment-procedures document to SP 800-171 that tells an assessor how to determine whether the security requirements a nonfederal organization implemented to protect Controlled Unclassified Information (CUI) are actually satisfied. Per its own abstract, the publication "provides organizations with assessment procedures and a methodology that can be used to conduct assessments of the security requirements in NIST Special Publication 800-171," with procedures that "are flexible and can be customized to the needs of organizations and assessors," supporting independent third-party assessments as well as government-sponsored ones. Authored by Ron Ross and Victoria Pillitteri, Revision 3 was published in May 2024, superseding the original edition of June 2018.

Key takeaways

  • Section 2.1 of the SP 800-171A Rev.
  • Every procedure in Section 3 has the same four blocks.
  • Preparing for assessments — establishing the objective and scope, notifying organizational officials, selecting assessors (considering assessor independence), and providing artifacts to the assessment team.
  • Other than satisfied — either a potential anomaly that the organization needs to address, or a case where the assessor could not obtain sufficient information to make the determination called for.

How is this built on SP 800-53A's methodology?

Section 2.1 of the SP 800-171A Rev. 3 full text is explicit that the assessment procedures in Section 3 "have been derived from the assessment procedures in SP 800-53A," and Section 2.2 adds that they are "based on and sourced to" those procedures. Each of the 17 SP 800-171 requirement families is assessed using methods and object categories lifted directly from SP 800-53A's model, and each procedure ends with a References line naming the SP 800-53A source procedure(s) it traces back to (for example, the account-management procedure cites AC-02, AC-02(03), AC-02(05), AC-02(13)). Appendix C confirms the same lineage for the overall assessment process: the four-phase approach "is based on the methodology in SP 800-53A." Where SP 800-53A assesses the federal SP 800-53 control catalog, SP 800-171A narrows that same machinery to the 17-family, CUI-specific requirement set in SP 800-171.

What are examine, interview and test, and what gets assessed?

Section 2.1 defines the three assessment methods:

  • Examine — "the process of reviewing, studying, inspecting, or analyzing assessment objects."
  • Interview — "the process of holding discussions with individuals or groups about assessment objects."
  • Test — "the process of exercising assessment objects (i.e., activities, mechanisms) under specified conditions to compare actual with expected behavior."

Assessment objects fall into four categories: specifications (documented artifacts — plans, policies, procedures, requirements, design documentation), mechanisms (the hardware, software and firmware safeguards implemented in a system), activities (protection-related actions involving people, such as conducting a system backup or exercising an incident response plan), and individuals (the people applying those specifications, mechanisms or activities). A footnote adds that artifacts "may be in formats other than documents," naming databases, GRC tools and OSCAL. Each assessment method carries depth and coverage attributes that set "the rigor, scope, and level of effort for the assessment as well as the degree of assurance that the security requirements have been satisfied" — for the full basic/focused/comprehensive definitions of those attributes, the publication points readers to SP 800-53A, Appendix C, rather than redefining them.

How do you read one assessment procedure?

Every procedure in Section 3 has the same four blocks. Taking 03.14.01 Flaw Remediation from the PDF:

  1. ODP statements come firstWhere the requirement contains an organization-defined parameter, the objective opens by checking that the value exists: A.03.14.01.ODP[01] asks whether "the time period within which to install security-relevant software updates after the release of the updates is defined," and ODP[02] asks the same for firmware updates.
  2. Determination statements followA.03.14.01.a[01] to a[03] check that system flaws are identified, reported and corrected; A.03.14.01.b[02] checks that "security-relevant firmware updates are installed within" the ODP[02] period.
  3. Methods and objects are a menuEach method is introduced with "SELECT FROM:" and a list, for example "test results from the installation of software and firmware updates to correct system flaws" under Examine.
  4. The References line names the sourceFor 03.14.01 it is SI-02.

Two notation rules matter. Identifiers always begin with "A" to mark them as part of an assessment procedure, followed by the SP 800-171 requirement identifier; dotted suffixes such as 03.01.01.f.02 point at a sub-item of the requirement itself. Square-bracketed numbers mark where the procedure decomposes a requirement into finer statements; the publication's own example is A.03.01.12.a[01], a[02], a[03]. Rev. 3's change log (Appendix E) lists ODPs as a new addition versus the 2018 original, which had no such mechanism.

How does the four-phase assessment process run?

Appendix C lays out the process in four phases, each summarized in its own table (Tables 2–5):

  1. Preparing for assessments— establishing the objective and scope, notifying organizational officials, selecting assessors (considering assessor independence), and providing artifacts to the assessment team. A footnote lists previous results that may be reused, including "vulnerability scans," "developmental testing and evaluation, vendor flaw remediation activities," and ISO 15408 evaluations.
  2. Developing assessment plans— determining which requirements are in scope from the system security plan, then selecting, tailoring (methods, objects, depth and coverage values) and optimizing the Section 3 procedures, and obtaining approval.
  3. Conducting assessments— executing the approved plan; each determination statement executed produces one finding, and the phase outcome is "an assessment report that documents whether the security requirements have been satisfied."
  4. Analyzing, documenting and reporting assessment results— reviewing findings, starting risk responses (acceptance, mitigation, rejection, transfer or sharing), and updating the system security plan and plan of action and milestones.

The publication frames the resulting evidence as part of an assurance case — "a body of evidence organized into an argument demonstrating" compliance with SP 800-171's security requirements — and notes this evidence can come from multiple sources, including independent third-party product assessments such as Common Criteria and FIPS 140 testing, not solely from a single system-level assessment event.

What do "satisfied" and "other than satisfied" mean?

Applying an assessment procedure produces a finding of either:

  • Satisfied — the assessment objective was fully met, a fully acceptable result; or
  • Other than satisfied — either a potential anomaly that the organization needs to address, or a case where the assessor could not obtain sufficient information to make the determination called for.

The publication is explicit that the broad list of potential assessment methods and objects for a given procedure "does not necessarily reflect and should not be directly associated with actual compliance or noncompliance" on its own — organizations select whichever specific methods and objects are sufficient to obtain the evidence they need, rather than treating the full list as mandatory artifacts.

Which families and how many requirements are assessed?

Table 1 organizes the assessment procedures into the same 17 requirement families as SP 800-171 Rev. 3 itself: Access Control, Awareness and Training, Audit and Accountability, Configuration Management, Identification and Authentication, Incident Response, Maintenance, Media Protection, Personnel Security, Physical Protection, Planning, Risk Assessment, Security Assessment and Monitoring, System and Communications Protection, System and Information Integrity, System and Services Acquisition, and Supply Chain Risk Management. Counting the headings in Section 3 gives 130 requirement identifiers, of which 33 are marked "Withdrawn" (with a note such as "Incorporated into 03.13.08."), leaving 97 requirements with a procedure. See our SP 800-171 / CMMC 2.0 guide for the underlying requirement catalog, and the NIST CSRC page for the same procedures as a CPRT dataset.

Which procedures reach firmware, devices and suppliers?

A contractor's assessor applies these procedures to the contractor's system, not to a supplier's product. But several procedures can only be satisfied with evidence that comes from the maker of the devices and firmware inside that system:

Procedure Source (References line) ODPs the contractor sets Evidence a device or firmware maker can supply
03.04.10 System Component Inventory CM-08, CM-08(01) review and update frequency Component list per firmware release, such as a firmware SBOM
03.11.02 Vulnerability Monitoring and Scanning RA-05, RA-05(02) monitoring and scanning frequency; remediation response times; update frequency for scanned vulnerabilities Known-CVE match results per release, advisories, and how prioritization works (see KEV and EPSS)
03.14.01 Flaw Remediation SI-02 software and firmware update installation periods Release notes naming fixed CVEs, update test results, signed update packages
03.17.03 Supply Chain Requirements and Processes SR-03 security requirements against supply chain risk Answers to the contractor's supplier questionnaire, secure development and disclosure process (see SP 800-161 C-SCRM)

03.11.02 is worth reading in full: it has four ODPs and checks scanning both on a schedule and "when new vulnerabilities that affect the system are identified." A supplier that publishes affected-component data quickly makes that second statement easier to satisfy.

Which edition does CMMC Level 2 use?

The 2018 edition, for now. The CMMC program rule incorporates by reference "SP 800-171A, Assessing Security Requirements for Controlled Unclassified Information, June 2018" and SP 800-171 Revision 2, per 32 CFR 170.2 on eCFR. A CMMC Level 2 assessment therefore uses the Rev. 2 numbering (for example 3.14.1) and the June 2018 objectives, not the A.03.14.01 statements described here. Rev. 3 procedures apply where a contract or agency cites SP 800-171 Rev. 3. Ask which edition the contract names before building an evidence index, because identifiers do not carry across directly.

Worked example (synthetic): what does a supplier evidence pack look like?

Synthetic example. "TM-7" is an invented networked test instrument with embedded Linux firmware, sold to a contractor that holds CUI; it is not a real product or customer. The contractor's assessor plans 03.04.10, 03.11.02 and 03.14.01 against systems that include the TM-7. The instrument's maker prepares:

  1. Scope noteWhich procedures touch the TM-7, and the contractor's ODP values in writing, for example "firmware updates installed within 30 days of release" (an illustrative value; the contractor sets it).
  2. Inventory (`A.03.04.10.a`)The CycloneDX SBOM for firmware 3.2.0 with the image's SHA-256 hash, which the contractor's team can open in the SBOM viewer.
  3. Vulnerabilities (`A.03.11.02.a[03]`, `b`)The known-CVE match report for 3.2.0 with each finding's engineer decision, and the date the maker last checked for new advisories.
  4. Flaw remediation (`A.03.14.01.a[03]`, `b[02]`)Release notes for 3.2.1 naming the corrected CVEs, the release date, and the signed package hash, so the contractor can show installation within its ODP period.
  5. IndexOne table: artifact, firmware version, hash, and the determination statement it supports.

The pack supports examine and interview; testing the contractor's own update process stays with the contractor and its assessor.

What are the common pitfalls?

  • Citing the wrong edition. Rev. 2 / June 2018 numbering under CMMC, Rev. 3 numbering elsewhere; mixing them stalls the assessment.
  • Undefined ODPs. The first statement for 03.14.01 is that the period "is defined." Without it the procedure fails before any record is examined.
  • Unversioned evidence. An SBOM or scan result that names no firmware version cannot support a determination about the deployed one.
  • Treating "SELECT FROM" as a checklist. The list is a menu; pick what is sufficient.
  • Over-reading product certificates. A FIPS 140 or Common Criteria result covers the evaluated product configuration, not the contractor's flaw remediation process.

What is a workable starting point?

  1. Read the References line on every procedure before tailoring itIt names the exact SP 800-53A source procedure(s), which is the fastest way to find deeper assessment-method guidance SP 800-171A itself doesn't repeat.
  2. Resolve every ODP before building the assessment planA determination statement with an unresolved ODP (an undefined time period, an unspecified role list) can't be meaningfully examined, interviewed against, or tested.
  3. Don't treat the full assessment-object list as a checklistThe publication explicitly disclaims that the complete set of potential objects for a procedure represents a required evidence list — select what's sufficient for the assurance level needed.
  4. Separate "satisfied" from "no evidence."An "other than satisfied" finding can mean either a genuine gap or simply that the assessor couldn't get the evidence — the four-phase process keeps that distinction visible through to the final report.
  5. Remember this assesses SP 800-171 Rev. 3, not the CMMC-referenced Rev. 2 baselineIf the assessment is for a CMMC Level 2 determination, confirm which NIST SP 800-171 revision the contract actually requires before applying these Rev. 3-aligned procedures — see our SP 800-171 / CMMC 2.0 guide for that distinction, and our SP 800-172A guide for the enhanced-requirement procedures that sit on top. Medical-device makers selling into the same buyers will find the overlap with FDA expectations in our FDA premarket cybersecurity guide.

SoftWSP extracts a CycloneDX 1.6 SBOM from a firmware image, matches its components against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, and drafts a cited report for an engineer to review. That output can be one examine artifact for the inventory and vulnerability rows above; it is not an SP 800-171A assessment, and it does not test a contractor's remediation process. See Device & Firmware Security.

This guide summarises NIST SP 800-171A Revision 3 (May 2024), the related SP 800-171/SP 800-53A publications and 32 CFR 170.2 as published on eCFR; it is not a substitute for the full text and does not constitute compliance or legal advice.

Put this guide to work

Frequently asked questions

What is NIST SP 800-171A?

"Assessing Security Requirements for Controlled Unclassified Information" — the companion assessment-procedures document to [NIST SP 800-171](/guides/nist-sp-800-171-cmmc-2-0/) that tells an assessor how to determine whether the security requirements in SP 800-171 have actually been satisfied. Per its own abstract, it "provides organizations with assessment procedures and a methodology that can be used to conduct assessments of the security requirements in NIST Special Publication 800-171," and states the procedures "are flexible and can be customized to the needs of organizations and assessors," supporting independent third-party assessments or government-sponsored assessments alike. Revision 3, authored by Ron Ross and Victoria Pillitteri (NIST), was published in May 2024, superseding the original edition of June 2018.

What are the examine, interview and test assessment methods, and what gets assessed?

Section 2.1 defines the three assessment methods, each applied to an "assessment object": **examine** is "the process of reviewing, studying, inspecting, or analyzing assessment objects"; **interview** is "the process of holding discussions with individuals or groups about assessment objects"; and **test** is "the process of exercising assessment objects (i.e., activities, mechanisms) under specified conditions to compare actual with expected behavior." Assessment objects themselves fall into four categories: specifications (documented artifacts such as plans, policies and procedures), mechanisms (hardware, software and firmware safeguards), activities (protection-related actions involving people, such as running a backup or exercising an incident response plan), and individuals (the people applying the specifications, mechanisms or activities). The methods also carry depth and coverage attributes — "the rigor, scope, and level of effort for the assessment" — which the publication points readers to in SP 800-53A, Appendix C.

How are determination statements numbered, and what is an ODP?

Each assessment objective is built from one or more alphanumeric determination statements that always start with "A" to flag them as part of an assessment procedure, followed by the SP 800-171 requirement identifier they target — e.g., `A.03.01.06.a` assesses requirement 03.01.06 (Least Privilege – Privileged Accounts). An **organization-defined parameter (ODP)** is a value — commonly a time period, frequency, or set of roles — that the implementing organization must fill in to complete a requirement; these are tagged `ODP[nn]` in square brackets, e.g. `A.03.01.06.ODP[01]`. Square brackets are also used where a procedure decomposes one requirement into several more granular determination statements, e.g. `A.03.01.12.a[01]` through `a[03]`. Rev. 3's own change log notes that ODPs were newly added in this revision — the 2018 original had no ODP mechanism.

How does the four-step process relate to SP 800-53A, and what counts as a passing result?

Appendix C states the four-phase process — (1) preparing for assessments, (2) developing assessment plans, (3) conducting assessments, and (4) analyzing, documenting and reporting assessment results — "is based on the methodology in SP 800-53A," and Section 2.1 confirms that the 17-family assessment procedures in Section 3 "have been derived from the assessment procedures in SP 800-53A" (each procedure's References line names its source SP 800-53A control, e.g. `AC-02, AC-02(03), AC-02(05), AC-02(13)` for account management). An assessment produces a finding of either **satisfied** — the assessment objective was fully met — or **other than satisfied**, meaning either a potential anomaly needing remediation or that the assessor could not obtain enough evidence to make the determination. See our [SP 800-53A guide](/guides/nist-sp-800-53a-control-assessment/) for the parent methodology this publication reuses.

Sources

  1. NIST: SP 800-171A Rev. 3, Assessing Security Requirements for Controlled Unclassified Information (May 2024) — publication page
  2. NIST SP 800-171Ar3 (Ross, Pillitteri), full text PDF
  3. NIST: SP 800-171 Rev. 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations — publication page
  4. eCFR: 32 CFR 170.2, Incorporation by reference (CMMC: SP 800-171 R2 and SP 800-171A June 2018)
  5. NIST: SP 800-53A Rev. 5, Assessing Security and Privacy Controls — publication page
Was this guide helpful?

In this cluster