Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations [including updates as of 01-14-2016]

Published: January 21, 2016


Ronald S. Ross, Kelley L. Dempsey, Patrick Viscuso, Mark Riddle, Gary Guissanie


[Superseded by SP 800-171 Rev. 1 (December 2016): controlled-unclassified-information-nonfederal-systems-and-organizations] The protection of Controlled Unclassified Information (CUI) while residing in nonfederal information systems and organizations is of paramount importance to federal agencies and can directly impact the ability of the federal government to successfully carry out its designated missions and business operations. This publication provides federal agencies with recommended requirements for protecting the confidentiality of CUI: (i) when the CUI is resident in nonfederal information systems and organizations; (ii) when the information systems where the CUI resides are not used or operated by contractors of federal agencies or other organizations on behalf of those agencies; and (iii) where there are no specific safeguarding requirements for protecting the confidentiality of CUI prescribed by the authorizing law, regulation, or governmentwide policy for the CUI category or subcategory listed in the CUI Registry. The requirements apply to all components of nonfederal information systems and organizations that process, store, or transmit CUI, or provide security protection for such components. The CUI requirements are intended for use by federal agencies in contractual vehicles or other agreements established between those agencies and nonfederal organizations. [Supersedes SP 800-171 (June 2015, updated 9/3/2015):]
Citation: Special Publication (NIST SP) - 800-171
Report Number:
Pub Type: NIST Pubs


Superseded by

Download Paper


Contractor Information Systems, Controlled Unclassified Information, CUI Registry, Executive Order 13556, FIPS Publication 199, FIPS Publication 200, FISMA, NIST SP 800-53, Nonfederal Information Systems, Security Control, Security Requirement, Derived Security Requirement, Security Assessment
Created January 21, 2016, Updated November 08, 2017