5 Steps to Effective CUI Classification

Prior to the U.S. government’s National Archives and Records Administration’s (NARA) implementation of the Controlled Unclassified Information (CUI) protection framework, government agencies employed ad hoc agency-specific policies, procedures and markings to safeguard and control all information that did not meet the criteria required for classification. The rule was designed to primarily safeguard sensitive government data that had not been designated confidential or secret while it was shared between different government and commercial entities.

This confusing patchwork resulted in inconsistent marking and safeguarding of documents, which led to unclear or unnecessarily restrictive dissemination policies and the creation of barriers to authorized information sharing. CUI didn’t have much of an established profile before the framework was implemented, and yet, this kind of material falling into the wrong hands could be a national security risk.

Cybersecurity Live - Boston

Success in winning a government contract could depend on how your organization addresses CUI. While it isn’t classified data, the data is still sensitive enough to require controls and, as such, its release could still pose a threat to national security. It is critical for organizations wishing to work with the government to ensure they are compliant with CUI standards. To achieve this, there are five key steps to master the principles of data classification involving the categorization and labeling of data.

What, Exactly, is CUI?

CUI covers data that is created or possessed by, or on behalf of, the government, when it resides in non-federal information systems and is handled by non-federal organizations. And its most critical element—the standardized labeling of CUI to ensure that appropriate protections can be implemented and consistently enforced—makes the rule actionable by those handling CUI.

The CUI framework is more about people than technology. The CUI registry, which specifies by category and subcategory, which marking must be applied to a particular data subject, also details critical procedures relating to the handling, safeguarding and control of the data as it moves through non-federal systems.

Across ‘CUI Basic’, ‘CUI Specified’ and ‘Limited Dissemination’, the marking/labeling is central to ensuring that CUI data is handled and secured in appropriate ways, and is only accessible to users who need to work with it, with appropriate downstream security controls across all IT systems, devices and databases.

Today, as a matter of strict compliance, both federal and non-federal organizations must provide evidence that they comply with NARA’s guidelines to meet both legal and contractual obligations. This includes demonstrating a comprehensive information security and classification program that ensures that all points where data travels or resides are treated as locations where CUI must be controlled.

This must address 14 key areas of technical security and compliance including: audits, training, access control, configuration management, identification and authentication, incident response, maintenance, media protection, physical protection, personnel security, risk assessment, security assessment, system and communications protection and system and information integrity.

The 5 Steps to Effective CUI Classification

With the right tools and training, organizations can demonstrate they have the capabilities in place to recognize and handle any type of CUI classification and labeling and also produce evidence where necessary. This breaks down into five key steps:

1. Identify

Know the CUI you create, process, store and disseminate. Understand your contracting security obligations or partner organization’s security policies and what you need to do to comply with both these and the new framework. This includes understanding the types of information that needs to be marked, what language must be used and what the markings mean.

2. Discover

Get visibility into what CUI you are required to process, where it comes from, where it resides, where it is sent and who might have access to it. From here, establish what controls you need to put on it.

3. Classify

Select a technology solution that will enable users to consistently apply the classification scheme, add critical metadata to the file and, via clear labeling, control who should have access to each type of CUI. Start with classifying ‘live’ data including emails, files and documents that are being received, created and handled right now. Then move on to labeling existing and legacy CUI that is stored and held around the organization.

4. Secure

Employ the tools that will control and protect CUI through its journey. The metadata label will enable higher grade controls such as DLP solutions, security incident and event monitoring (SIEM) tools, access control tools and data governance tools to safeguard data when it’s accessed or used later.

5. Monitor

CUI frameworks evolve over time, so use monitoring and reporting tools to track how CUI is being accessed, used and classified in your organization, and keep available the background intelligence needed to evolve the approach in line with regulatory changes.

Failing to adequately protect CUI has considerable implications. A data leak that exposes a client or breaches a regulation could lead to a damaged reputation and brand, penalties and the possible loss of business. By adopting the CUI framework, organizations can demonstrate the ability to protect federal government information and enhance their ability to respond to opportunities to work with the U.S. government.

Featured eBook
The Dangers of Open Source Software and Best Practices for Securing Code

The Dangers of Open Source Software and Best Practices for Securing Code

More and more organizations are incorporating open source software into their development pipelines. After all, embracing open source products such as operating systems, code libraries, software and applications can reduce costs, introduce additional flexibility and help to accelerate delivery. Yet, open source software can introduce additional concerns into the development process—namely, security. Unlike commercial, or ... Read More
Security Boulevard

Adam Strange

Adam Strange is Global Marketing Director at Titus, by HelpSystems, working to define and implement strategic go-to-market campaigns. He brings a proven and successful record of managing integrated business-to-business marketing activity to both increase brand profile and capture leads and opportunities. Adam has a widespread understanding of enterprise IT infrastructure across areas such as Cybersecurity, Threat Intelligence, Cloud-based Services, Business Applications, Databases and Hardware. Prior to working at Titus, a HelpSystems company, Adam ran the marketing and alliances function at Becrypt and has held former marketing and partnering positions at BAE Systems, Oracle and Computacenter. 

adam-strange has 2 posts and counting.See all posts by adam-strange