Unauthorized access and disclosure of government information has become all too common in these times of frequent cyber-attacks. As a result, the government has extended mandatory safeguards – found in NIST SP 800-171 – to non-federal organizations that process, store or transmit Controlled Unclassified Information (CUI) or Covered Defense Information (CDI) in non-federal information systems.
These non-federal organizations may include prime contractors, subcontractors, suppliers, distributors, and other service providers. Additionally, CUI is often provided to, or shared with, state and local governments, colleges and universities, and independent research organizations.
Do you need to make sure your organization complies with regulations? Keep reading to learn how you can do just that.
Table of Contents
NIST SP 800-171 Compliance Requirements
To comply with CUI safeguarding requirements, government contractors and other organizations processing CUI must fully understand what information they store, process, or transmit in the course of doing business with the federal government.
Defense industrial base contractors and suppliers must be prepared to provide adequate documentation describing their technical solutions, policies, and evidence of being able to detect and respond to incidents. safeguards, as defined by National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations, which currently includes fourteen families of security requirements and a total of 110 individual controls.
The CUI requirements within NIST SP 800-171 are directly related to the baseline controls described in NIST SP 800-53, Security and Privacy Controls for Federal Information Systems and Organizations, and are intended for use by federal agencies in contracts or other agreements established between those agencies and non-federal organizations.
TestPros provides a full range of NIST Compliance Consulting Services to help you establish the necessary controls, and build the documentation the Government requires.
What are the NIST 800-171 controls?
NIST SP 800-171 currently includes fourteen families of security requirements and a total of 110 individual controls.
The CUI requirements are directly related to the baseline controls described in NIST SP 800-53, Security and Privacy Controls for Federal Information Systems and Organizations, and are intended for use by federal agencies in contracts or other agreements established between those agencies and non-federal organizations..
The 14 security families that make up the 110 controls
- Access Control
- Awareness and Training
- Audit and Accountability
- Configuration Management
- Identification and Authentication
- Incident Response
- Media Protection
- Personnel Security
- Physical Protection
- Risk Assessment
- Security Assessment
- System and Communications Protection
- System and Information Integrity
Do I need to be NIST 800-171 compliant?
If your business is contracted to provide services, goods or research funds to the U.S. federal government, then NIST SP 800-171 compliance becomes a critical responsibility for protecting CUI. This includes contractors and service providers, organizations receiving funding from the state or federal government – as well as businesses supplying goods or services to any of these entities.
When will NIST 800-171 Compliance Be Required?
If you are a contractor providing services to the U.S. federal government, your organization is responsible for protecting CUI. For Department of Defense contractors, DFARS 252.204-7012 & 252.204-7008 require that you implement the safeguards defined by NIST SP 800-171 over these materials by December 31, 2017. Prior to the deadline, DoD contractors must report any NIST SP 800-171 requirements not implemented, within 30 days of contract award.
While no equivalent FAR regulations are currently in place that map to the DFAR requirements, there are Executive Orders that mandate compliance for all government agencies.
CUI requirements are based on Executive Order (EO) 13556 of November 4, 2010 as well as 32 CFR Part 2002, Controlled Unclassified Information (CUI) in effect November 14, 2017, and supported by “CUI Notice 2016-01: Implementation Guidance for the CUI Program,” which was issued by NARA September 14, 2016 (“Day-0”).
Per that guidance, agencies must be at an Initial Operating Capability (IOC) one year after Day-0 to be compliant, and be at Full Operating Capability (FOC) three years after Day-0 (September 14, 2019) to be compliant. It is only a matter of time before non-DoD agencies pass along the same CUI handling requirements to their contractors.
Regardless of the legal or statutory requirement, it makes good business sense to implement the security steps defined by NIST SP 800-171!
How to become compliant
There are four steps to becoming NIST 800-171 compliant:
- Review business requirements.
- Assess your current security posture.
- Remediate and implement necessary security controls.
- Continuous monitoring and reporting of security controls to ensure ongoing compliance.
As illustrated in the figure above, our Assessment Services include audits and compliance assessments against the NIST 800-171 standard, after which we advise on security program enhancements and control implementation where gaps are identified.
Our approach is pragmatic – where possible, we identify ways to reduce the scope of our client’s effort. For example, in lieu of hardening client-hosted servers and networks, it is often more expeditious and cost effective to isolate CUI data on FedRAMP-certified, cloud-based servers.
Need help complying with NIST 800-171?
Assessments, remediation, consulting
What is Cybersecurity Maturity Model Certification (CMMC)?
The Cybersecurity Maturity Model Certification (CMMC) is a new framework that will replace the NIST 800-171 requirements in DFARS 7012 compliance.With a 3-tiered approach, CMMC accounts for an organization’s current cybersecurity posture. It also outlines the specific steps needed to improve it. The focus is to reduce risk in DoD supply chains.
Read our post that outlines specific steps for CMMC Compliance.
NIST 800-171 Assessment Services
For each of the NIST 800-171 control objectives, TestPros delivers the following audit / assessment services and documentation:
- Identify applicable compliance guidance
- Determine if Group Policies (Active Directory or other LDAP), other Policies and Standards, Documented Processes and SOPs are in place
- Identify related technology considerations
- Document compliance status
- Justify any deviation from standard (pre-implementation only)
- Note any clarifying information, for example, reference to duplicate controls
System Security Plans (SSP) & NIST Remediation Services
Once we have helped our client identify their requirements, TestPros is available to help you create NIST 800-171 required documentation sets, including a System Security Plan (SSP) that documents how you protect and ensure control of CUI and any additional guidance based on client or agency requirements.
We develop supporting compliance programs, including cost-effective alternative approaches, to implement and maintain (continuous monitoring) the required controls for transmitting or storing this data in non-federal information systems. We work from either existing client or TestPros-provided templates to accelerate the process.
TestPros NIST 800-171 Consulting For Compliance
Our experts know that NIST 800-171 compliance starts with making sure that Software, Hardware and Document accessibility is part of each IT requirement. This should be done before anything else as part of the system development life cycle.
TestPros offers NIST 800-171 gap analysis, compliance support, program support, and training services to assist your organization safeguard it’s networks and become compliant!
Most frequent questions and answers
To ensure the security of a company’s computer systems and data in compliance with National Institute of Standards and Technology (NIST) regulations, NIST 800-171 dictates that specific safeguards such as intrusion detection systems and firewalls must be applied. This is to protect against potential unauthorized access, use, disclosure, alteration or misappropriation of private information. If you’re unsure where your organization stands, give us a ring today.
NIST compliance costs can range from $5,000 to $100,000 depending on the size and complexity of the business. To save costs, many companies opt to outsource their compliance needs to a third-party or consultant. The cost of NIST 800-171 certification also follows the same trend; for smaller organizations with simpler systems it would be between $2,500 and $20,000 while larger enterprises with more complex systems might reach up to $50,000 or above.
To prevent NIST 800-171 Split Tunneling, organizations should identify a single tunnel for all data transmission; VPNs and other secure tunneling protocols are preferred. Besides that, robust authentication methods must be employed to ensure only permitted individuals access the network. Moreover, monitoring traffic and data flows in the tunnel is essential while policies limiting actions such as downloading large files or sharing confidential information over public networks are recommended.
To comply with NIST 800-171 requirements, the National Institute of Standards and Technology (NIST) suggests that organizations should maintain system event logs for no less than 180 days—extending this period depending on any legal or business considerations. Furthermore, it is imperative to guarantee sufficient storage resources as well as encrypt all stored log data to shield against unauthorized access.
To stay compliant with NIST 800-171, organizations must regularly perform vulnerability scans via automated tools. These scannings discover any existing weaknesses or possible vulnerabilities in your system or application and should be closely reviewed to detect areas of concern. Necessary corrective measures are then taken – if needed – to remain adherent to the standards set by this security measure.