CMMC and CUI: How Contractors Can Control Compliance Costs Without Lowering Security

Written by

in

Military commanders do not protect every road, building, and field in the same manner. They identify the mission, establish the perimeter, control access, and concentrate resources where the risk and mission value are highest. Contractors should take the same disciplined approach to CMMC and Controlled Unclassified Information.

The objective is not to build the largest possible compliance environment. The objective is to build the correct one.

Recent reporting has made clear why this distinction matters. In an August 19, 2026 article, Federal News Network reported that inconsistent Department of Defense CUI marking continues to drive confusion, broad flow-downs, over-scoping, and higher costs. The issue is especially serious for small businesses that may be required to fund a costly cybersecurity environment without receiving clear answers about what information they will actually handle.

Your company can protect sensitive information without placing every employee, device, application, and commercial operation inside the same CMMC boundary. The work begins with contract clarity, data mapping, defensible scoping, and practical execution.

CMMC Requirements Depend on the Contract and the Scope

CMMC is not a universal requirement applied identically to every government contractor. The applicable requirements depend on the contract, the clauses incorporated into that contract, the type of information involved, and the systems, people, and locations that process, store, or transmit that information.

That means you must first determine:

  • Which contract or subcontract creates the cybersecurity obligation;
  • Whether the work involves Federal Contract Information, CUI, or both;
  • Which CUI categories and handling requirements apply;
  • Whether your company receives, creates, stores, processes, or transmits CUI;
  • What systems and personnel will have access to the information; and
  • What requirements are being flowed down from the prime contractor.

A prime contractor may request or impose a requirement in a solicitation or subcontract. That request should be reviewed against the actual work and applicable contract language. If the requirement is unclear, ask for clarification from the prime and, where appropriate, the contracting officer.

Do not assume that a general statement such as “CMMC Level 2 required” answers the more important question: Level 2 for which systems, which data, and which contract activities?

Why Inconsistent CUI Marking Creates Unnecessary Cost

CUI is sensitive government information that is not classified but still requires protection under applicable laws, regulations, or government-wide policies. The challenge is that CUI is not always marked or described consistently.

Federal News Network’s coverage identified several concerns raised by industry organizations and the Small Business Administration’s Office of Advocacy, including:

  • Information being over-marked;
  • Sensitive information being under-marked or left unmarked;
  • Publicly available information being treated as CUI;
  • Prime contractors applying broad requirements to subcontractors;
  • Contractors being uncertain whether they create CUI during performance; and
  • Contracting officers applying requirements inconsistently.

When the boundary is unclear, companies often protect everything “just to be safe.” That approach may appear conservative, but it can create a larger and more expensive assessment environment than necessary. More systems require more controls. More users require more training and access reviews. More applications require more evidence, monitoring, remediation, and documentation.

Over-scoping does not automatically create better security. It can create operational confusion, increase the chance of control failures, and divert limited resources away from the data that requires the greatest protection.

Diagram showing how contract requirements and CUI data flows define the CMMC assessment boundary

Step One: Map the Data Before You Build the Environment

The first practical step is a data-flow map. You need to understand how information enters your company, where it is used, where it is stored, who can access it, and where it goes next.

Your map should address:

  1. Source: Does the information come from the government, a prime contractor, another supplier, or your own work product?
  2. Type: Is it FCI, CUI, technical information, contract information, design data, test data, or another category?
  3. Movement: Does it move through email, file-sharing platforms, collaboration tools, removable media, portals, or physical documents?
  4. Users: Which employees, subcontractors, administrators, and service providers can access it?
  5. Systems: Which endpoints, servers, cloud tenants, applications, and networks process or store it?
  6. Output: Does your company generate new drawings, reports, specifications, or other deliverables that may qualify as CUI?

The data-flow map should not be a decorative diagram. It should become a management document that supports your System Security Plan, internal procedures, contract discussions, and assessment preparation.

Federal News Network quoted a government contracts attorney describing the practical problem: a contractor may receive little or no marked CUI but still create information during contract performance that qualifies as CUI. Your analysis therefore must include both incoming information and work product created for the government.

Step Two: Establish a Narrow, Defensible CUI Environment

Once you understand the data flow, separate the CUI environment from general business operations wherever practical.

A properly designed enclave or segmented environment may include:

  • A dedicated cloud tenant or network segment;
  • Separate identity and access controls;
  • Dedicated project email and file storage;
  • Restricted endpoints for authorized personnel;
  • Controlled transfer points;
  • Multifactor authentication;
  • Logging and monitoring;
  • Defined administrative access; and
  • Written procedures for moving information into and out of the environment.

The purpose is not to hide information or avoid a requirement. The purpose is to ensure that the systems assessed are the systems that actually handle CUI.

A commercial division serving non-government customers may not need to be part of the CUI environment if it has no access path to CUI. Likewise, employees who do not work on the affected contract should not automatically receive access.

Segmentation must be real, documented, and technically enforced. A separate folder on a shared drive is not necessarily a separate environment. A separate label in an email system is not necessarily a boundary. Qualified cybersecurity professionals should evaluate whether the proposed architecture supports the intended scope.

Step Three: Confirm Flow-Downs Instead of Accepting Blanket Language

Small businesses frequently encounter broad flow-downs from primes. Some primes may require Level 2 controls across a supply chain because they are uncertain about CUI scope or want to reduce their own risk.

You should review the actual subcontract, attachments, statements of work, security exhibits, and incorporated clauses. Ask direct questions:

  • Will we receive or handle CUI?
  • Which CUI categories are involved?
  • Is the work limited to FCI?
  • Must we store or transmit CUI in our own systems?
  • Can CUI be accessed through a prime-controlled or hosted enclave?
  • Are we permitted to perform the work without bringing CUI into our corporate environment?
  • What evidence will be required before award and during performance?

The Defense Logistics Agency’s CMMC frequently asked questions and the Department of Defense CMMC Level 2 Assessment Guide provide useful reference points. They should not replace contract-specific analysis.

If the prime cannot answer the questions, document the request and continue the discussion. Do not casually agree to a broad requirement that could materially change your cost structure, delivery model, staffing, and competitiveness.

Step Four: Protect Unclear Information While Seeking Clarification

An unmarked document is not automatically free of handling obligations. If you have a reasonable basis to believe information qualifies as CUI, protect it while seeking clarification.

Your process should include:

  • Restricting access until the issue is resolved;
  • Recording the source and date received;
  • Identifying the suspected CUI category;
  • Asking the prime or contracting officer for written direction;
  • Preserving the communications and responses; and
  • Updating the data map and internal procedures after clarification.

This is a risk-management process, not an invitation to make final legal determinations without assistance. A government contracts attorney or qualified compliance advisor can help you evaluate the contract language, challenge an unclear designation, and document a defensible position.

Checklist graphic representing contract review, CUI identification, control documentation, and stakeholder communication

Step Five: Document Controls and Budget for the Full Lifecycle

CMMC costs extend beyond technology purchases. Your budget should account for:

  • Initial scoping and gap analysis;
  • Network or cloud architecture changes;
  • Identity, access, and endpoint controls;
  • Security policies and procedures;
  • Employee training;
  • Incident response preparation;
  • Continuous monitoring;
  • Documentation and evidence management;
  • Managed cybersecurity services;
  • Legal and contract review; and
  • Applicable assessment or affirmation activities.

Do not budget only for the assessment. Budget for the operation of the environment over the life of the contract.

Documentation is equally important. Maintain records showing why systems were included or excluded, how access is controlled, how incidents are handled, how vendors are evaluated, and how CUI clarification questions were resolved.

If your organization uses artificial intelligence tools in government-facing workflows, the NIST AI Risk Management Framework can provide a useful voluntary governance lens through its emphasis on governing, mapping, measuring, and managing risk. It is not a substitute for CMMC, NIST SP 800-171, contract clauses, or legal requirements. It can, however, help leadership evaluate whether AI tools introduce additional data leakage, access, privacy, accuracy, or vendor risks.

Security and Cost Control Are Not Opposing Goals

The strongest compliance strategy is both secure and commercially disciplined. You do not reduce risk by placing every system in scope without analysis. You reduce risk by identifying the information, controlling its movement, limiting access, documenting decisions, and testing the controls that matter.

The Infinity Group helps organizations understand the federal environment, evaluate opportunity requirements, strengthen government-market positioning, and coordinate the business, contractual, financial, and execution decisions that support federal growth. We are business-development and government-market advisors. We do not replace a C3PAO, qualified assessor, cybersecurity provider, or government contracts attorney. We help you organize the broader strategy and bring the right expertise to the table.

Your next steps should be straightforward:

  1. Gather every relevant contract, solicitation, subcontract, attachment, and security exhibit.
  2. Identify the information you receive and create.
  3. Map every CUI data flow.
  4. Define the smallest defensible environment.
  5. Confirm flow-down requirements in writing.
  6. Design segmentation and access controls.
  7. Document the system and its controls.
  8. Budget for implementation, operation, assessment, and legal support.
  9. Communicate early with your prime and contracting officer.
  10. Obtain qualified cybersecurity and legal guidance before making a certification or compliance representation.

The question is practical: Would a disciplined investment in scoping, segmentation, documentation, and expert guidance cost less than applying an unnecessarily broad compliance architecture across your entire company?

In many cases, the answer is clear.

Contact The Infinity Group at connect@infinity-us.com to discuss your government-market strategy, contract requirements, CUI concerns, and next steps.

CONTROL THE DATA. DEFINE THE SCOPE. PROTECT THE MISSION.

Sources

Publishing setting: Comments and replies disabled (no comments / no reply).

The Infinity Group official corporate logo with the tagline “Strategies + Execution = Funding and Growth”