Download our CMMC Guide for Manufacturers
Download our guide for manufacturers today.
On January 12, 2024, NIST (The National Institute for Standards and Technology) announced the beginning of a public comment period on NIST SP 800-171r3. These comments are in regard to the final draft proposal. Here are six facts you should know now about revision three of NIST SP 800-171.
The introduction mentions, “Approximately 40 comments addressed CMMC, DFARS, FedRAMP, the identification and marking of CUI, flow-down requirements, and the cost of implementation — all topics deemed out of scope for NIST to address.” There are definitely several organizations involved in ensuring the security of CUI nationwide, but NIST is truly only responsible for the NIST 800-171 standard.
Even though the assessment guide is essential to succeeding in the compliance journey, the summary notes that fewer than 150 comments were received and “Many commenters were not as familiar with the purpose, scope, and structure of the [SP 800-171A] assessment procedures or the source [SP 800-53A] assessment methodology and terminology.” If you do not understand the importance of NIST SP 800-171Ar3, please feel free to contact us for some clarification.
NIST 800-53 is mentioned several times throughout the comment summary. NIST 800-53 is a robust standard intended to protect federal information. In order to understand the references to this standard, downloading and reviewing it briefly will be helpful. You can download the standard here. Alternatively, again, feel free to reach out and we can help you “connect the dots” between NIST 800-53 and NIST 800-171.
After the summary of comments, NIST listed seven changes that the DIB (Defense Industrial Base) will see in the final publications of NIST 800-171r3, NIST 800-171Ar3, and supplemental materials. Those seven changes are:
a. Cleaning up errors, omissions, and typos.
b. Better alignment and consistency between SP 800-53 / 53A and SP 800-171r3 and 171Ar3.
c. Organization Defined Parameters (ODPs) and the concept of “periodically” will be analyzed again. In the initial public draft of 800-171, NIST used the term “ODP” to indicate that the cadence or requirements would have to be clarified by the organization. This was a source of confusion, so in the final proposed draft, NIST replaced several of the “ODP” mentions with the word “periodically.” Commenters still want more guidance, but, ultimately, NIST is trying to say that each organization has to define certain facets themselves.
d. NIST will review all of its discussion sections to focus more on tailoring guidance without using specific examples.
e. More introductory background on 800-53 and 800-53A. NIST notes in a footnote that free, on-demand introductory courses on SP 800-53, 53A, and 53B will be available in the third quarter of 2024. Smithers will keep you updated on that release.
f. Changes to SP 800-171A will be made in order to keep it aligned with security requirement changes to SP 800-171.
g. Updates to the FAQs will include more about defining ODPs, the history and evolution of CUI requirements, and more.