CMMC 2.0: What it really means & How to prepare

⚠️ 7/13/2026 Update: CMMC Phase II Suspended

The Department of War has immediately suspended CMMC Phase II requirements, which were scheduled to begin November 10, 2026.

What this means: Third-party certification is paused, but your obligation to protect CUI and maintain strong cybersecurity remains. CMMC Level 1 and Level 2 self-assessments are still required where already in your contracts, along with NIST SP 800-171 compliance and DFARS safeguarding requirements.

Translation: You were given more time to study for the test. Don’t waste it.

Key Takeaways

✅ What CMMC 2.0 is and Why it matters Now

✅ The definition and scope of CUI

✅ Common challenges

✅ Shared Responsibility

✅ Step-by-step guidance


+ Full Transcript

CMMC Level 2 Compliance: What Defense Manufacturers Need to Know

Important Update: Shortly after this webinar was recorded, CMMC implementation requirements and timelines continued to evolve. The fundamental security requirements and preparation strategies discussed throughout this webinar remain important, but organizations should always review current CMMC requirements and the specific requirements included in their contracts before determining their compliance obligations.

Moderator: Welcome. Today, we’re discussing CMMC Level 2, what it means for defense contractors and manufacturers, and how organizations can prepare.

Today’s presenters are Mark Jamieson, President and CEO; Tom Garren, CTO; and Alex Jamieson, Senior Solutions Engineer.

If you’re not familiar with 2W Tech, we’re a technology solutions and managed services provider specializing in manufacturing and distribution, with expertise across ERP, Microsoft, cybersecurity, cloud infrastructure, and managed IT services.

What Is CMMC Level 2?

Mark: If CMMC has felt like a moving target filled with acronyms and anxiety, you’re not alone.

We talk to clients about this all the time. Our goal today isn’t to overwhelm you. It’s to demystify CMMC and make the path forward easier to understand.

One of the most important things to remember is that compliance isn’t a product you simply buy, and it doesn’t happen automatically because you move to the cloud.

CMMC requires organizations to combine the right technology and security controls with the right processes, policies, responsibilities, and documentation.

For CMMC Level 2, organizations need to address 110 security requirements based on NIST SP 800-171 and demonstrate how those requirements are implemented within the applicable CMMC assessment scope.

What Is Controlled Unclassified Information (CUI)?

Mark: We’re going to talk a lot about Controlled Unclassified Information, or CUI. Alex, what does CUI actually mean?

Alex: At a high level, CUI can include government information that requires safeguarding or dissemination controls but isn’t classified information.

For manufacturers in the Defense Industrial Base, examples may include engineering drawings, CAD files, technical specifications, bills of materials, production data, project communications, and certain procurement information.

And it’s not always limited to the obvious technical documentation.

Depending on the information and contract requirements, CUI can also appear in emails, supplier communications, shipping information, sourcing documentation, collaborative systems, and other business processes.

That’s why identifying where CUI exists is so important.

Once CUI enters a system or workflow, you need to understand the systems where it resides, the users who have access, the applications that interact with it, and the integrations through which that information moves.

Why Is CMMC Important for the Defense Supply Chain?

Tom: Defense contractors have already been expected to protect CUI using requirements associated with NIST SP 800-171.

CMMC formalizes how those cybersecurity requirements are assessed and how the resulting CMMC status can be incorporated into Department of Defense contracting requirements.

Ultimately, this is about protecting the defense supply chain.

The government needs confidence that organizations handling Federal Contract Information and Controlled Unclassified Information are actually protecting that data, including when it flows to subcontractors and other organizations in the supply chain.

For manufacturers, that can affect design data, procurement information, quality documentation, supplier communications, ERP data, CAD files, shared systems, and other operational information.

What Are the Major CMMC Level 2 Compliance Areas?

Alex: The good news is you don’t have to think about CMMC as 110 completely disconnected requirements.

In practice, several major operational themes come up repeatedly.

Access Control: Do the right people have access to the right information? Are you using multifactor authentication? Are administrative privileges controlled? Are you using individually identifiable accounts rather than inappropriate shared credentials?

Logging and Monitoring: Can you see what’s happening inside your environment? Can you identify suspicious activity and produce evidence showing who accessed relevant systems and information?

Secure Configuration and Maintenance: Are systems supported, patched, configured consistently, and maintained securely?

Documentation and Evidence: Can you demonstrate that your security controls, policies, and processes actually exist and operate as described?

That’s a major theme with CMMC: show, don’t just tell.

Where Do Organizations Commonly Struggle with CMMC?

Alex: One of the biggest challenges is understanding where CUI actually lives.

The obvious locations might be your ERP system, file servers, email, or engineering environment.

The harder part is identifying where that information travels next.

Does another application receive it? Does an integration copy or transform it? Is it being stored in another platform? Is an employee sending it through email or sharing it externally?

That CUI sprawl can dramatically affect your CMMC scope.

Other common challenges include inconsistent MFA coverage, incomplete logging and monitoring, unsupported systems, shared accounts, and processes that exist primarily as tribal knowledge instead of documented procedures.

Tom: Incomplete evidence is another major issue.

An organization may actually be doing many of the right things but still struggle if its documented scope doesn’t match reality, responsibilities aren’t clearly assigned, or documentation and evidence don’t reflect what’s happening in the live environment.

Does Moving to Microsoft Government Cloud Make You CMMC Compliant?

Tom: No single Microsoft license, cloud environment, or infrastructure product automatically makes an organization CMMC compliant.

Microsoft Government cloud services, including environments such as Microsoft 365 GCC High and Azure Government, may support specific government, defense, data residency, and compliance requirements depending on the organization’s needs.

But the environment still has to be implemented, configured, managed, monitored, and documented correctly.

The right environment depends on your contracts, the type of information you’re handling, applicable regulatory requirements, data residency requirements, integrations, users, and other factors.

The infrastructure is the foundation. It isn’t the entire compliance program.

What Evidence Is Required for CMMC?

Tom: Security controls have to produce objective evidence.

It’s not enough to say, “We have MFA turned on.”

You may need evidence demonstrating how it is configured and operating, along with documentation explaining your organization’s associated procedures and responsibilities.

The same concept applies to identity, data protection, logging, monitoring, system configuration, and other security requirements.

An assessor is looking for a coherent story where the technology, the live environment, the policies, and the supporting evidence agree with one another.

Who Is Responsible for CMMC Compliance?

Tom: An organization may work with multiple technology providers, software vendors, managed service providers, consultants, and security partners.

Those providers can support different pieces of the compliance environment, but the contractor remains responsible for its CMMC requirements and assessment scope.

That’s why a shared responsibility matrix can be so important.

Document, control by control, who is responsible for implementation, configuration, monitoring, evidence, maintenance, and documentation.

For example, an ERP provider may have one responsibility, a cloud provider another, a managed service provider another, and your internal team another.

The important part isn’t just knowing who does what. You need to be able to demonstrate those responsibilities and make sure they reflect what’s actually happening.

How Do You Prepare for CMMC Level 2?

Alex: The first step is identifying where CUI exists.

Start with what you know. Maybe CUI exists in email, your file server, your ERP system, engineering applications, or other business systems.

Then begin defining your scope and identifying additional places where CUI may be stored, processed, or transmitted.

Step 1: Identify and Scope CUI.
Determine where CUI is stored, processed, transmitted, and accessed.

Step 2: Perform a CMMC Gap Assessment.
Compare your current processes and security environment against the applicable CMMC Level 2 security requirements.

Step 3: Define Ownership.
Identify exactly who owns each requirement, process, control, piece of documentation, and remediation activity.

Step 4: Build Your Documentation.
Develop and maintain required documentation, including your System Security Plan, or SSP, and applicable Plans of Action and Milestones, or POA&Ms.

Step 5: Implement and Validate Controls.
Address identified gaps and implement the necessary technical and administrative security controls.

Step 6: Prepare for Assessment.
Organize your evidence, validate that your documentation reflects the real environment, and prepare your team for the applicable CMMC assessment.

Step 7: Maintain Compliance.
CMMC isn’t something you complete once and forget. Your systems, employees, applications, vendors, and business processes continue changing, so your documentation, scope, controls, and evidence need to evolve with them.

Why Is Ongoing CMMC Maintenance Important?

Mark: There’s a natural tendency to sprint toward an assessment, get through it, and then stop because everybody is exhausted.

But your business doesn’t stop changing, and neither does your technology.

Applications change. Systems get upgraded. Employees come and go. Vendors change. Integrations get added.

Every one of those changes can affect your compliance environment.

Tom: That’s why maintaining documentation and evidence is so important.

CMMC isn’t simply an assessment-day exercise. Organizations need processes for continually maintaining the controls and documentation supporting their CMMC status.

How Can 2W Tech Help with CMMC Readiness?

Mark: Whether you work with 2W Tech or another qualified partner, we’d strongly encourage organizations to get help where they need it.

For our clients, the process can include helping identify CUI scope, conducting technology and security assessments, identifying gaps and risk areas, designing appropriate infrastructure, implementing security controls, and helping prepare technology evidence for an assessment.

That could include modernizing unsupported infrastructure, configuring Microsoft cloud environments, improving identity and access controls, strengthening logging and monitoring, or helping appropriately isolate systems handling CUI.

We can also support organizations as they prepare for assessments and help maintain the technology components of their compliance environment over time.

Tom: We can help with scope, design, implementation, evidence, and sustainment.

But ultimately, the contractor owns its CMMC obligations and certification.

Where Should You Start with CMMC?

Mark: Start with a readiness assessment.

Then determine where your CUI actually exists. It may be in places you’re not immediately thinking about, including emails, ERP records, technical documentation, integrations, or operational documents.

From there, build your scope, assess the gaps, define responsibilities, and create a realistic roadmap from where you are today to where your contracts require you to be.

CMMC Level 2 Webinar Q&A

Can You Support CMMC in Google Workspace or Google Cloud?

Tom: CMMC requirements are ultimately about whether the applicable security requirements can be implemented, managed, demonstrated, and assessed within the environment you’re using.

Our team has deeper experience implementing these controls within Microsoft environments, so that’s where we have the clearest path for helping customers design and document their infrastructure.

If you’re operating in another cloud environment, the same fundamental questions still apply: Where does CUI live? What requirements apply? Which controls can be inherited? Who owns the remaining controls? And can you produce the required evidence?

How Much Does It Cost to Become CMMC Compliant?

Mark: It depends heavily on where you’re starting.

An organization already using supported infrastructure, strong identity controls, centralized monitoring, good documentation, and well-defined processes will have a very different path than a company running unsupported servers, inconsistent MFA, shared accounts, and undocumented processes.

It’s useful to think about CMMC costs in several buckets: assessment and advisory costs, technology and infrastructure remediation, security tools or licensing, professional services, and the internal time required to build and maintain documentation.

Tom: It’s also worth separating ordinary technical debt from costs that exist purely because of CMMC.

Replacing unsupported infrastructure, maintaining security patches, and documenting critical IT processes are things businesses should often be doing regardless of CMMC.

What’s the Difference Between Being CMMC Audit-Ready and CMMC Certified?

Alex: Being assessment-ready means you’ve prepared your environment, controls, documentation, and evidence for the applicable assessment.

Certification is the status achieved after successfully completing the required CMMC certification assessment process.

The exact assessment requirement depends on the CMMC level and the requirements applicable to the contract.

Do You Have to Complete CMMC Level 1 Before Level 2?

Alex: CMMC Level 1 isn’t a prerequisite that every organization must complete before pursuing Level 2.

The CMMC level and assessment type your organization needs depends on the information you handle and the requirements associated with the applicable contract.

Level 1 is focused on protecting Federal Contract Information, while Level 2 addresses protection of Controlled Unclassified Information.

Organizations required to achieve Level 2 can pursue the applicable Level 2 status without treating Level 1 as a separate stepping stone.

Does Using a Compliant Cloud Provider Make Your Company CMMC Compliant?

Tom: No. A cloud provider can help satisfy or support certain requirements, but simply hosting a system in a particular cloud environment doesn’t make the organization CMMC compliant.

Depending on the service, an organization may be able to inherit certain controls or rely on infrastructure-level capabilities provided by the cloud provider.

But you still have responsibilities around configuration, identity, access control, CUI scoping, monitoring, documentation, evidence, employee behavior, integrations, and other requirements.

Mark: That’s an important distinction.

There isn’t a magic cloud platform or software product that makes a company CMMC compliant by itself.

The organization has to build, operate, document, and demonstrate the complete compliance environment.

What’s the Difference Between CMMC Level 2 and Level 3?

Alex: CMMC Level 2 focuses on protecting CUI through the applicable Level 2 security requirements.

Level 3 builds on Level 2 with additional requirements intended for organizations supporting certain higher-priority Department of Defense programs.

The requirement for Level 3 would come from the applicable contract or program requirements.

Do Subcontractors Handling CUI Need CMMC Level 2?

Tom: CMMC requirements can flow down through the defense supply chain to subcontractors.

The specific CMMC requirement depends on the contract and the information being handled, but subcontractors that process, store, or transmit CUI should expect CMMC requirements to be relevant to them.

Alex: That’s why organizations shouldn’t assume they’re outside the scope simply because they aren’t a prime contractor.

If you’re part of the Defense Industrial Base and handling CUI, understand exactly what your contracts and upstream customers require.

Final Takeaway: CMMC Is a Continuous Security Program

CMMC Level 2 isn’t simply a technology purchase, a cloud migration, or a one-time audit project.

It’s an ongoing cybersecurity and compliance program built around understanding where CUI lives, defining the correct scope, implementing the applicable security requirements, assigning clear ownership, maintaining documentation, producing evidence, and keeping the environment aligned as the business changes.

If you’re preparing for CMMC Level 2, start by understanding your CUI scope and current security posture. From there, you can build a practical roadmap toward the assessment requirements that apply to your organization.