November 16, 2026
Key takeaways
  • CMMC adds verified cybersecurity to DFARS 252.204-7012 to protect controlled unclassified information and federal contract information.
  • Three cumulative levels: Foundational Level 1, Advanced Level 2, Expert Level 3, aligning controls to contractor risk and data sensitivity.
  • Most contractors handling CUI must achieve Level 2, which requires a third-party audit every three years and annual executive affirmation.
  • DoD contracts will require CMMC compliance prior to award, with exceptions for COTS products and purchases below the $10,000 micro-purchase threshold.

Last Updated on November 16, 2026

Many SMB suppliers to the US Department of War (DoW) face a significant effort to get ready for their upcoming Cybersecurity Maturity Model Certification (CMMC) compliance audit. But with 110 interrelated controls to evaluate at CMMC Level 2, knowing where to start and what to focus on is crucial.

To help SMBs across the US Defense Industrial Base (DIB) prepare for CMMC Level 2, John Verry, Managing Director at CBIZ Cybersecurity, recorded a special episode of The Virtual CISO Podcast on the biggest challenges most SMBs will face on the road to CMMC Level 2 compliance, and how to solve them.

How to Beat CMMC Level 2’s Mobile Device Management Requirements

There are several controls within the CMMC’s Access Control practice at Level 2 that relate to managing mobile devices. These include AC.L2-3.1.18, “Control connection of mobile devices” and AC.L2-3.1.19, “Encrypt CUI on mobile devices and mobile computing platforms.”

According to John, the key idea to keep in mind with CMMC Level 2 controls is your obligation to maintain the confidentiality of Controlled Unclassified Information (CUI) throughout its lifecycle. So with mobile devices like phones, tablets and laptops, the goal is to make sure any CUI stored on or accessed by these devices is maintained in a FIPS-compliant, encrypted state.

“The easiest way to think about that, if you’re going to have a lot of mobile devices, is to move towards a mobile device management (MDM) solution,” John advises. Companies using Microsoft 365, for example, can potentially leverage Microsoft’s cloud-based Intune solution to control and encrypt CUI on mobile devices, as well as automatically delete CUI from lost/stolen devices.

A further benefit of Intune and similar MDM tools is the ability to enforce minimal configuration baselines before allowing a mobile device to connect to a network or application. This capability can help you meet CMMC’s configuration management requirements.

Training users on MDM can also present problems. “Nobody likes to put in multi-factors for authentication,” John acknowledges. But experience shows that users quickly get accustomed to it, especially when they understand that the company’s financial wellbeing… and hence their jobs… could depend on it.

“The answer to managing user expectations has a lot to do with what we refer to as ‘tone at the top,’” notes John. “As you’re making changes to move to CMMC… it’s definitely going to impact users. When you’re making these changes, it’s important to communicate why you’re making them. … This is the way the world is going.”

How to Beat CMMC Level 2’s Multifactor Authentication Requirements

Within the Identification and Authentication (IA) practice, CMMC Level 2 states: “Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.” Sounds pretty all-encompassing! But what does that mean for cloud-based systems, for instance? And what accounts are considered privileged?

“MFA is actually one of the more confusing areas of CMMC,” shares John. “The simplest way to look at this is that MFA for all users is really what your target should be.”

“MFA is one of the single most important mechanisms to reduce the likelihood that your organization has a breach or is hacked. And at the end of the day, we want to be certified, but we also want to be secure, right? This is national defense. This is our national economy. And with the minimal amount of additional overhead associated with MFA for all user accounts, it’s a no-brainer to do that,” John adds.

Affordable, easy-to-use tools are available to help SMBs implement MFA, like the free authenticators offered with Microsoft 365 or Google Workspace.

“We see credential thefts, credential stuffing attacks, things of that nature… Once somebody has your password, they are you, right? They have access to the CUI [Controlled Unclassified Information],” adds John. “By adding a second factor, even if you have my password, you still can’t get to the CUI.”

“Everybody should be using MFA on any information that’s important to them, is my opinion at this point in time,” John stresses.

How to Beat CMMC Level 2’s Encryption Requirements

Within the CMMC’s Access Control practice and elsewhere, CMMC Level 2 mandates that all shared files and emails containing CUI need to be encrypted both at rest and in transit. How can SMBs manage this cost-effectively?

“There are an awful lot of places within CMMC where the concept of encryption comes into play,” notes John. “That makes sense because what [NIST] 800-171 and CMMC are trying to do is ensure the confidentiality of Controlled Unclassified Information (CUI), and encryption is the single most significant way to provide that confidentiality.”

CUI must be encrypted both in transit and at rest to meet CMMC Level 2. This means you’ll need a solution that can encrypt emails and shared files. Further, the solution’s cryptographic mechanisms must be FIPS-validated, to ensure it meets the US federal government’s encryption standard.

Email Spam Protection and Sandboxing

Most people are familiar with email spam protection techniques, which use various degrees of automation/artificial intelligence and user intervention to keep spam, phishing attacks and other potentially malware-loaded emails out of users’ inboxes. But what is email attachment sandboxing? “Sandboxing” is a generic IT term that basically means running software in an isolated, safe environment where it can’t harm production systems if it’s full of bugs or infested with malware. For example, say you open a malicious file attachment in an email sent by hackers. Most likely it will run a macro, which will try to pull more malicious code down from the internet onto your computer. But an email attachment sandboxing solution can test that malicious attachment out in a safe place and neutralize, quarantine or delete it before a user ever sees it in his or her inbox.

According to John, “CMMC has done a good job of recognizing that the single largest threat vector for most organizations is email.” Anti-spam, attachment sandboxing and related solutions are “basic cyber hygiene” steps for any organization. Without them, your data is a sitting duck. Thus, CMMC Level 2 includes malicious code protection requirements, such as SI.L2-3.14.2, that these tools help address.

“The good news is that the vast majority of organizations already have the basics in place,” John states. For example, many Microsoft 365 customers take advantage of built-in email protection mechanisms at various licensing levels. Others leverage third-party email protection solutions like Mimecast or Proofpoint.

Does this mean that most DIB suppliers already have these capabilities on tap and just need to tune them to achieve CMMC Level 2 compliance? John continues: “For organizations that have at least a moderately robust set of information security practices, the answer is yes. … You’re probably doing 80%-90% of the stuff right already. But unfortunately, in the DIB there are a number of smaller organizations. And some of them are from fields that don’t traditionally make significant investments in information security.”

“If you’re a law firm, you’re already going to have a pretty good information security posture,” John explains. “If you’re a 25-person manufacturing company, very often those will be a little bit less mature, and these hurdles could be a little bit higher for them.”

Here’s What Your CMMC Level 2 Readiness Assessment Will Look Like

What will your CMMC Level 2 readiness assessment look like? How in-depth will it go? And what will you need to have in place as a starting point?

An assessor’s first sniff test is likely to be your system security plan (SSP).

“In a well-formed SSP you’re going to have the definition of the data; you’re going to have the definition of the assets that are in scope; hopefully you have a data flow diagram; you know who the key stakeholders are; you have an idea of how each of the 110 practices are actually being implemented…”

“And I like in a good SSP to even have some indication of how you’re going to evidence each of those practices. That way, from an auditor’s perspective, they can walk in and they’ve got one consolidated package to look at,” comments John.

A major concern for many companies is the identification of CUI. “That’s one of the most common complaints I hear,” John observes. “When we ask if they have CUI, they say, ‘Nothing is labeled that way…’ And we’re like, ‘Yeah, that doesn’t mean you don’t have CUI.’”

This is why getting started early with your preparation is so critical.

Get a CMMC Level 2 readiness assessment from CBIZ Pivot Point Security. Contact us to get started.

Back to Blog