DoD Specifies Implementation Requirements for NIST 800-171 Cyber Standard
Client Alert | 1 min read | 05.15.25
The Department of Defense (DoD) has released a memorandum establishing the DoD Organization-Defined Parameters (ODPs) for use in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171 Revision (Rev) 3. Currently, DoD’s cybersecurity regimes require government contractors to comply with NIST SP 800-171 Rev. 2. However, the release of this memorandum may indicate DoD’s intention to soon incorporate Rev. 3 into DFARS 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting (DFARS 7012) as well as the forthcoming Cybersecurity Maturity Model Certification (CMMC).
NIST SP 800-171 Rev. 3 was released in May 2024. Rev. 3 introduced new controls and control families, increased specificity for certain security requirements, and introduced Organization-Defined Parameters into 800-171. ODPs are “fill-in-the-blanks” to be filled by federal agencies to create tailored requirements for each agency’s specific needs.
DoD’s selected ODPs range from time-based requirements, such as requiring inactive user accounts to be terminated within 24 hours, to specific technical requirements, such as the use of Federal Information Processing Standard (FIPS) validated cryptography. The ODPs will also require flowing down certain protections to subcontracts, through requiring external service providers to meet NIST SP 800-171 Rev 2 and requiring integration of supply chain risk management into procurement policies.
The ODPs will not take immediate effect. Shortly after the release of NIST SP 800-171 Rev. 3, DoD issued a class deviation to clarify that NIST SP 800-171 Rev. 2 would continue to be used for the DFARS 7012 Safeguarding Clause. However, this new memorandum indicates that companies should begin preparing for Rev. 3, as it suggests that DoD is gearing up for Rev. 3 implementation in both the DFARS 7012 and CMMC requirements.
Recommendation
Companies should review the new security requirements and DoD-specific ODPs to determine what technical and administrative revisions would be required to meet these emerging requirements.
Contacts
Insights
Client Alert | 4 min read | 10.30.26
Recent sustain decisions by the U.S. Government Accountability Office (GAO) in Fluor Federal Solutions, LLC and Reliance Test & Technology send a clear message: when an agency tries to fix a Procurement Integrity Act (PIA) violation by committing a second one, the cure can be just as fatal as the disease. The cases involved the U.S. Air Force’s $1.8 billion procurement for O&M services at Elgin Air Force Base. During discussions, the Air Force inadvertently released a pricing overview slide with all offerors’ bottom-line evaluated costs to Reliance Test & Technology, which immediately notified the agency of the error. In response, the Air Force decided to level the playing field by providing the same information to all the other offerors in the procurement, stating, “[o]fferors may consider this disclosure in their [final proposal revision].”
Client Alert | 3 min read | 10.29.26
What University Licensors Should Learn From TexasLDPC v. Broadcom
Client Alert | 2 min read | 10.28.26
Debriefing to Dead Briefing: How to Avoid Dismissal by Identifying “Required” Debriefings

