A U.S. Federal Contractor sought to secure a lucrative DoD contract to upgrade the Surveillance and Targeting systems on a fleet of older-generation UAVs. However, the contract conditions required the Federal Contractor to have implemented proper safeguards to protect the technical data, such as project specifications provided by the DoD and any other sensitive information it generated during the execution of the contract. If this information were to fall into the wrong hands, it could have severe implications, including compromising the Air Force's competitive edge and reducing the warfighter's lethality.
Understanding the importance of fortifying its cybersecurity posture to effectively handle the CUI and demonstrate compliance with NIST SP 800-171, the Contractor sought assistance from Cleared Systems. This strategic partnership with us was an avenue for the Federal Contractor to achieve NIST SP 800-171 compliance and exemplify their unwavering commitment to the highest security standards.
Objectives
- To comprehensively assess the Federal Contractor's current environment against all 110 NIST SP 800-171 security requirements. This would allow us to identify gaps where implemented security controls do not fully meet the standards and requirements outlined in this publication.
- To develop a prioritized roadmap for gap remediation that maps out plans to address all identified control deficiencies in the Federal Contractors environment, equipment, systems, and processes, thereby strengthening the Contractor's security framework.
- To deploy new technical security solutions on the Federal Contractor's assets that process, transmit, or store CUI to satisfy requirements related to access control, multi-factor authentication, encryption, activity monitoring, vulnerability management, and other domains critical for securing CUI data.
- To support the federal Contractor in establishing new formally documented policies, procedures, and processes to fulfill NIST SP 800-171 requirements focused on security planning, auditing, incident response, personnel screening, and other areas key to the contracting work.
- To assist the federal Contractor in creating a System Security Plan containing an inventory of all applicable security controls and current implementation status against NIST 800-171 benchmarks.
- To help the federal Contractor create a thorough Plan of Action and Milestones (POA&M) that details plans to remediate all control deficiencies with projected budgets, timelines, and owners.
- To validate full compliance with NIST SP 800-171 security requirements to support the Federal Contractor in securing the lucrative DoD contract to upgrade the surveillance and targeting systems.
Challenges
- It was Challenging to Implement some controls: Certain NIST 800-171 control requirements like encrypting data-at-rest and during transmission, enforcing multi-factor authentication, or enabling comprehensive audit logging proved difficult for the federal Contractor to implement fully due to technology limitations.
- Interoperability issues: The federal Contractor struggled to ensure that the security tools and systems used across its various heterogeneous IT environments could seamlessly interoperate and work together to protect the sensitive CUI data.
- Failure to properly Understand the covered information systems: The federal Contractor initially struggled to identify and map out all information systems that process, store, or transmit CUI data covered under NIST 800-171. Not having complete visibility made it hard to apply controls.
- Incident response preparedness: Developing, regularly testing, and maintaining an effective NIST 800-171 tailored incident response plan was essential but proved challenging for the Federal Contractor.
- Hardships segregating covered DOD information systems from commercial systems: The federal Contractor found it challenging to maintain separate security policies, controls, and processes for the systems handling CUI versus ordinary commercial data. Strict segregation is required by NIST 800-171 but challenging to execute.
- Incorrectly marking CUI: The federal Contractor found it challenging to accurately identify, categorize, and manage CUI data to apply appropriate safeguards due to the complexity of the task. This led to incorrect marking of CUI, making it hard to adequately meet all the controls of NIST SP 800-171.
- Ambiguities in some NIST SP 800-171 security controls: The federal Contractor faced difficulties interpreting some of the control requirements in NIST 800-171, which contain ambiguities. The lack of clarity created confusion around exactly how to implement specific controls.
