CMMC Compliance in Michigan: What It Is, Why It Matters, and How to be Audit-Ready
Navigating the Cybersecurity Maturity Model Certification (CMMC) is essential for businesses working with the Department of Defense.
intro
What is CMMC?
CMMC stands for Cybersecurity Maturity Model Certification. It is a framework developed by the U.S. Department of Defense (DoD) to ensure that defense contractors have adequate cybersecurity practices in place to protect sensitive government information.
Processes
CMMC requires organizations to implement repeatable and documented cybersecurity processes that demonstrate maturity and consistency in protecting sensitive data.
Policies
Policies under CMMC define the rules and expectations for cybersecurity practices, ensuring that all personnel understand and follow standardized security protocols.
Controls
Controls are the specific technical and procedural safeguards mandated by CMMC to prevent, detect, and respond to cyber threats across systems and networks.
If you work with Controlled Unclassified Information (CUI) on defense-related projects, understanding and maintaining Cybersecurity Maturity Model Certification (CMMC) is not optional—it’s critical.
This comprehensive guide outlines the key components of the CMMC framework, explains its maturity levels, and details the practices and processes required to achieve and sustain compliance. Whether you’re part of a small business or a larger organization, staying compliant ensures you can continue working with the Department of Defense while protecting national security interests.
CUI & FCI
What You Must Protect
Federal Contract Information (FCI)
Government contract information not intended for public release. Requires safeguarding and process controls.
Controlled Unclassified Information (CUI)
Unclassified but sensitive information requiring safeguarding under law/regulation/policy. Requires full NIST 800-171 alignment and strict handling rules.
FAQ
CUI and FCI Demystified:
6 Things Contractors Should Understand
Who is in charge of CUI?
CUI isn’t managed by a single agency. Instead, several entities play a role:
- The National Archives maintains the official CUI registry, which categorizes types of CUI and links them to specific regulations.
- The National Institute of Standards and Technology, or NIST, defines the security controls needed to protect CUI in NIST SP 800-171.
- Each Federal Agency is responsible for enforcing CUI handling requirements within its domain.
- And for Department of Defense contractors, CMMC—the Cybersecurity Maturity Model Certification—is the specific framework for handling CUI.
The National Archives maintains the official CUI registry, which categorizes types of CUI and links them to specific regulations.
The National Institute of Standards and Technology, or NIST, defines the security controls needed to protect CUI in NIST SP 800-171.
Each Federal Agency is responsible for enforcing CUI handling requirements within its domain.
And for Department of Defense contractors, CMMC—the Cybersecurity Maturity Model Certification—is the specific framework for handling CUI.
How do I know if it’s CUI?
CUI requires clear markings in a standardized format.
Learn More About CUI MarkingsWhat types of CUI are there?
There are 2 main types of CUI:
- Basic CUI: This type requires protection but doesn’t include specific handling instructions. You apply NIST SP 800-171 controls and treat it as FISMA Moderate.
- Specified CUI: This includes detailed handling requirements and may require additional safeguards beyond NIST. For example, Controlled Technical Information that’s not commercial off-the-shelf (Non-COTS) falls into this category.
Basic CUI: This type requires protection but doesn’t include specific handling instructions. You apply NIST SP 800-171 controls and treat it as FISMA Moderate.
Specified CUI: This includes detailed handling requirements and may require additional safeguards beyond NIST. For example, Controlled Technical Information that’s not commercial off-the-shelf (Non-COTS) falls into this category.
What are some examples of CUI?
- Research and engineering data: Specifications, standards, and analysis reports.
- Engineering drawings: Detailed designs of systems or components.
- Technical reports: Summaries of research findings or test results.
- Technical orders: Instructions for maintaining or modifying equipment.
- Vulnerability assessments: Evaluations of weaknesses in infrastructure.
- Export control information: Data related to restricted technologies.
- Privacy data: Like PII, or Personally Identifiable Information.
- Sensitive business information: Non-public data that could be harmful if disclosed
Research and engineering data
Specifications, standards, and analysis reports.
Engineering drawings
Detailed designs of systems or components.
Technical reports
Summaries of research findings or test results.
Technical orders
Instructions for maintaining or modifying equipment.
Vulnerability assessments
Evaluations of weaknesses in infrastructure.
Export control information
Data related to restricted technologies.
Privacy data
Like PII, or Personally Identifiable Information.
Sensitive business information
Non-public data that could be harmful if disclosed
What are some examples of FCI?
- Contract award documents: Basic contract terms, dates, and deliverables.
- Project schedules or timelines: Internal planning documents related to contract fulfillment.
- Billing and invoicing information: Payment details submitted to the government.
- Employee assignments or labor categories: Who is working on the contract and their roles.
- Internal communications about contract performance: Emails or memos discussing progress or issues.
- Basic product or service descriptions: General descriptions of what is being provided under the contract.
- Non-sensitive procurement data: Purchase orders or vendor lists used to fulfill the contract.
Contract award documents
Basic contract terms, dates, and deliverables.
Project schedules or timelines
Internal planning documents related to contract fulfillment.
Billing and invoicing information
Payment details submitted to the government.
Employee assignments or labor categories
Who is working on the contract and their roles.
Internal communications about contract performance
Emails or memos discussing progress or issues.
Basic product or service descriptions
General descriptions of what is being provided under the contract.
Non-sensitive procurement data
Purchase orders or vendor lists used to fulfill the contract.
Why not treat everything as CUI?
It might seem safer to treat all information as CUI, but that’s inefficient and costly. Over-classifying information can lead to unnecessary security burdens, increased compliance costs, and operational slowdowns. It’s better to understand the distinctions, apply the correct controls, and ensure your team is trained to recognize and handle each type appropriately.
| Sensitivity Level |
| FCI: FISMA Low | CMMC 2.0 Level 1 |
| CUI: FISMA Moderate | CMMC 2.0 Level 2 |
| Marking Requirements |
| FCI: No specific marking required |
| CUI: Must be marked CUI |
| Examples |
| FCI: Contract dates, billing information, project schedules |
| CUI: Technical data, export-controlled info, engineering drawings |
| Handling Requirements |
| FCI: Basic protection; avoid public release |
| CUI: Requires safeguarding; use secure systems |
| Regulations |
| FCI: 48 CFR § 52.204-21 | 15 Safeguarding Controls (17 for CMMC) |
| CUI: NIST SP 800-171 | 110 Safeguarding Controls |
| Type | FCI | CUI |
| Sensitivity Level | FISMA Low CMMC 2.0 Level 1 | FISMA Moderate CMMC 2.0 Level 2 |
| Marking Requirements | No specific marking required | Must be marked CUI |
| Examples | Contract dates, billing information, project schedules | Technical data, export-controlled info, engineering drawings |
| Handling Requirements | Basic protection; avoid public release | Requires safeguarding; use secure systems |
| Regulations | 48 CFR § 52.204-21 15 Safeguarding Controls (17 for CMMC) | NIST SP 800-171 110 Safeguarding Controls |
THE ESSENTIALS
Working with CUI
Controlled Environments
CUI must be limited to controlled environments. Individuals should never read, discuss, or leave controlled documents unattended in areas where unauthorized personnel are present. Organizations handling CUI require policies and IT controls to ensure sensitive information is only available to authorized individuals.
Storage Requirements
The location of all CUI within an organization must be documented and controlled.
- Physical CUI must be stored in designated locked containers, desks, or cabinets.
- Digital CUI must be protected in a similar fashion—“locked” to only allow access to those with proper authorization. This is typically done using encryption that meets the FIPS 140-2 standard.
Physical CUI
Store in designated locked containers, desks or cabinets.
Digital Transmission
Whether on-premise in the cloud, restrict access to authorized users, typically using FIPS 140-2 encryption.
Emailing CUI
Encrypted in transit and at rest.
Secure Transmission
All CUI must move only through approved methods:
- For physical transmission, use first class mail, parcel post, or approved mass shipment methods.
- For digital transmission, use PKI or Transport Layer Security, such as HTTPS. Emailing CUI, if permitted by the organization, must be encrypted both in transit and at rest, and properly marked.
Physical Transmission
First class mail, parcel post, or approved mass shipment methods.
Digital Transmission
PKI or Transport Layer Security (HTTPS).
Emailing CUI
Encrypted in transit and at rest.
Data Destruction
When no longer needed, CUI must be destroyed so it is unreadable, indecipherable, and unrecoverable and recorded in a sanitization log.
- For Paper Documents, use cross-cut shredding or pulverizing methods. When using third-party destruction service, make sure to obtain a certificate of destruction.
- For Digital Information: Clear, Purge, or Destroy CUI data from all drives, including local and cloud backups, using procedures organization’s Media Sanitization and Disposal Policy.
Paper Documents
Use cross-cut shredding or pulverizing methods. When using third-party destruction service, make sure to obtain a certificate of destruction.
Digital Information
Clear, Purge, or Destroy data from all drives, including local and cloud backups. Follow procedures in the organization’s Media Sanitization and Disposal Policy.
VENDOR RISK
Vendor / Subcontractor Flow-Down
CMMC obligations flow down to subcontractors that handle your FCI/CUI. As part of your CMMC certification, you must:
- Classify vendors by risk and collect/verify safeguards and attestations.
- Embed flow-down language and responsibilities in agreements.
- Track notifications for vendor incidents affecting your CUI.
- Avoid improper de-marking — only originators/agencies can decontrol CUI.
CMMC obligations flow down to subcontractors that handle your FCI/CUI. ICS Data helps you:
Classify vendors by risk and collect/verify safeguards and attestations
Embed flow-down language and responsibilities in agreements
Track notifications for vendor incidents affecting your CUI
Avoid improper de-marking — only originators/agencies can decontrol CUI
Why Does CMMC Matter?
Risks to National Security, Organizations & Individuals
When working with the federal government, organizations often handle sensitive data that requires strict security controls.
The Cybersecurity Maturity Model Certification (CMMC) was developed to reduce national security risks by ensuring defense contractors protect this information effectively.
It also helps to safeguard organizations and individuals within the Defense Industrial Base (DIB), which faces growing threats from both state-sponsored and independent cyberattacks.
protecting defense systems
6 National Security Risks of Unauthorized Disclosure of CUI
When sensitive information is disclosed to our adversaries, it can expose our defense systems and critical infrastructure to risks such as:

Compromise Military Intelligence and Operations
Leaks may compromise military intelligence and operations. Adversaries could gain critical insights into US military strategies, capabilities, and troop movements, enabling them to develop countermeasures and neutralize advantages. For instance, compromised CUI about troop movements could allow adversaries to set up ambushes or re-route their forces, jeopardizing missions and potentially leading to casualties.

Military Strategy Disadvantage
Our military could also be put at a strategic disadvantage. Leaked CUI regarding military capabilities and plans could allow adversaries to tailor their tactics and technologies, potentially undermining US operations, leading to compromised missions and diminished deterrent effect of US military power.

Damage to Alliances
Unauthorized disclosure may damage critical alliances and partnerships. Leaks of sensitive information, even unclassified CUI, can erode trust with allied nations and hinder vital intelligence and strategic information sharing, weakening collective security efforts and joint missions.

Cyberattack Vulnerability
The Department of Defense could also experience increased vulnerability to cyberattacks. Information contained in leaked CUI, such as details about internal processes, security protocols, or personnel, could equip adversaries with knowledge to launch more targeted and effective cyberattacks.

Intellectual Property Theft
Federal contractors handling sensitive defense information are also tasked with preventing theft of intellectual property. Exposure of CUI related to critical technologies or military advancements could allow adversaries to replicate or exploit US innovations, impacting the economy and national security.

Operational Disruptions
Leaked CUI about military plans could enable adversaries to anticipate actions and disrupt operations, potentially resulting in tactical disadvantages and logistical challenges.
Securing Business Interests
6 Organizational Risks of Unauthorized Disclosure of CUI
In addition to these types of national security risks, unauthorized access or disclosure of CUI can result in severe consequences for organizations.

Legal Liability
At the organizational level, federal contractors risk legal liability when failing to follow protocols to protect sensitive information. Organizations may face civil lawsuits from individuals or other entities affected by a CUI breach.

Financial Penalties
Additionally, they may be subject to financial penalties. Fines and legal expenses can be substantial, depending on the severity of mishandling or breach.

Contract Losses
Failure to protect sensitive information could have contractual implications. Organizations may face loss of current and future government contracts, impacting revenue and business opportunities.

Increased Scrutiny
Even if organizations can preserve contracts, they may face Increased Oversight. Regulatory bodies might impose increased scrutiny and audits, adding to resource and financial burdens.

Damaged Reputation
Organizations could also suffer reputational damage. A breach of CUI can hurt an company’s reputation, leading to loss of trust with government agencies, industry partners, and customers.

Increased Costs
Organizations that wait until a leak to bring their information handling systems into compliance face increased cybersecurity costs. Implementing enhanced security measures and investing in remediation efforts after a breach can be substantial.
Ultimately, these costs and risks collectively lead to a Loss of Competitive Advantage. This is especially true if CUI containing proprietary business information is exposed. In this case, competitors may gain access to sensitive details, impacting the organization’s unique strategies or innovations.
Safeguarding PERSONAL Security
4 Individual Risks of Unauthorized Disclosure of CUI
Beyond national security concerns, unauthorized access or disclosure of Controlled Unclassified Information (CUI) can lead to serious personal and professional consequences. Individuals responsible for handling CUI may face legal, financial, or reputational risks if proper safeguards aren’t in place.

Legal Consequences
Depending on the severity of the mishandling, legal consequences may include fines, civil lawsuits, or even criminal charges. Mishandling CUI, especially if it includes personally identifiable information (PII), can violate privacy laws like HIPAA or GDPR, potentially leading to individual identity theft or fraud.

Security Clearance
If you hold security clearances, you may have those clearances reviewed and potentially revoked. Loss of security clearance may impact your career prospects or ability to meet your job responsibilities or advance internally.

Job Security
Depending on the nature of the disclosure and your organization’s policies, hanging onto your job. Organizations may terminate employees found responsible for mishandling CUI.

Career Advancement
Even if you aren’t fired, you may suffer damage to your professional reputation and potentially face challenges in future career opportunities.

PLAN AHEAD
Incident Readiness
If something goes wrong, you’ll need clear steps and proof of execution.
Incident Response Plan aligned to CMMC expectations
Detection/alerting integrations and evidence preservation
Reporting workflows (including agency notifications when applicable)
Post-incident review and POA&M updates
We Walk the Walk
Why ICS Data
ICS Data is a CMMC RPO (Registered Practitioner Organization) with proven hands-on experience delivering audit-ready compliance programs. Unlike most MSPs and consultants providing CMMC services to DIB clients, we actually have CMMC compliant policies and controls that govern our own organization’s information systems.
Policy-First Approach
We design programs that reduce scope, cost, and operational friction by focusing on practical, policy-driven solutions.
Deep Technical Expertise
Our team brings extensive knowledge of NIST 800-171, DFARS, and Microsoft enterprise security to every engagement.
CMMC Compliant
ICS Data is compliant with CMMC 2.0, ensuring our organization has a first-hand experience achieving and maintaining compliance.
WHAT YOU GET
A complete, audit-ready program — not just tools. Typical deliverables include:
Gap Assessment
A control-by-control review against NIST 800-171 to identify strengths, weaknesses, and required remediation.
Scope Definition & Reduction
We map systems, users, and data flows to minimize cost and complexity without sacrificing compliance.
System Security Plan (SSP) & POA&M
Ongoing ownership and updates of your core compliance documents to keep them audit-ready.
Policies & Procedures
Clear, practical policies covering access, media, incident response, vendors, CUI handling, and retention.
Technical Configurations
Implementation of MFA, least privilege, encryption, logging, and device compliance to secure your environment.
Microsoft 365 Enclave/GCC High
Design and lock down Microsoft 365 environments to meet CMMC and federal security requirements.
Audit Readiness Package
Client-controlled platform with policies, evidence, and control narratives to prove compliance during audits.
Ongoing Governance
Scheduled reviews, incident guidance, and vendor oversight to keep your program current and effective.
Staff Enablement
Role-based training and awareness so your team understands compliance responsibilities.
OUR PROCESS
A clear, end-to-end path from current state to audit readiness:
Assess
Identify CUI/FCI, run a gap analysis, prioritize risks.
Scope
Map flows & roles, define boundaries, reduce complexity.
Remediate
Implement technical/admin controls (MFA, logging, encryption, secure sharing).
Document
Build accurate SSP, policies, and evidence worksheets.
Validate
Run control tests, walk-throughs, incident drills, POA&M closure.
Maintain
Regularly scheduled reviews, vendor risk monitoring, structured change control.
MICROSOFT 365
Platforms & Enclaves
Whether you adopt GCC High or a contained enclave in Commercial or other compliant operating system, ICS Data designs and secures your environment to support CMMC:
Conditional Access & device compliance
Role-based access / privileged identity workflows
Data Loss Prevention (DLP) with sensitive info types
Advanced logging, auditing, retention & records controls
External sharing controls & approved collaboration channels
Whether you adopt GCC High or a contained enclave in Commercial or other compliant operating system, ICS Data designs and secures your environment to support CMMC:
- Conditional Access & device compliance
- Role-based access / privileged identity workflows
- Data Loss Prevention (DLP) with sensitive info types
- Advanced logging, auditing, retention & records controls
- External sharing controls & approved collaboration channels
FAQs
Do we need GCC High?
Not always. We evaluate data flows, sharing needs, and risk tolerance to decide between GCC High and a contained enclave strategy.
Learn More about Microsoft GCC & GCC HighHow long to get audit-ready?
Depends on current posture and scope. After an assessment, we provide a phased plan with milestones and critical-path items.
What does “audit-ready” actually mean?
Controls implemented, evidence captured and current, SSP/POA&M complete, and a repeatable governance cadence in place.
Will ICS Data train our team?
Yes — enablement is included as part of rollout, but it’s one component of a broader compliance program.
What if we only handle FCI?
We’ll right-size the program — safeguards and governance still apply, but typically with less complexity than CUI environments.


