This episode unpacks how MSPs help Department of Defense contractors achieve CMMC compliance. Learn about critical security practices like access control and incident response, real-world success stories, and the role of the Shared Responsibility Model in compliance. Featuring insights into industry acronyms and the contributions of teams like Prevail and MT Security, this is your guide to fostering a culture of compliance.
Eric Marquette
Welcome to the first chapter of today’s deep dive into understanding the critical role of Managed Service Providers—or MSPs—in achieving Cybersecurity Maturity Model Certification, or as we’ll refer to it, CMMC. If you’ve never heard of CMMC before, here’s the quick version. It’s a comprehensive cybersecurity framework required for any contractor that works with the Department of Defense, the DoD. And really, it’s designed to ensure that sensitive data, like CUI, and FCI, remains secure across the supply chain.
Eric Marquette
Now, where do MSPs like us fit into this? Our role is central. You see, many of our clients, especially smaller contractors, rely on us for far more than just IT maintenance. We help them navigate a maze of standards and practices that can be overwhelming without technical support. But, and this is a critical distinction, we’re not here to achieve compliance for them, nor are we responsible for everything. MSPs operate in a space called the Shared Responsibility Model. It’s exactly what it sounds like: we handle certain responsibilities, the client handles theirs, and together we build a compliant environment.
Eric Marquette
We'll break it down a little further later this year but here is a quick example. On our end, our responsibilities might include things like setting up secure networks, managing system patches, and ensuring regular data backups are in place. We might even assist with training their users. But compliance itself—whether it’s documenting policies or ensuring that individual users adhere to best practices—that’s on the client. So, we play a pivotal role without being the whole story.
Eric Marquette
Now, let me share a quick case study that perfectly illustrates how an MSP can empower a small business to achieve compliance. Picture a small manufacturing client—20 employees, tight margins, no dedicated IT department. They needed to land a government contract, which meant adhering to CMMC standards. They were overwhelmed at first, thinking they’d need to hire a cybersecurity expert full-time. Instead, they partnered with an MSP that tailored its remote management solutions to address their exact needs.
Eric Marquette
The MSP set up secure access protocols across their systems, implemented automated monitoring for potential vulnerabilities, and trained staff on password best practices. In six months, with the MSP’s guidance, they passed their assessment with flying colors. And the best part? They didn’t need to upend their entire operation to do it.
Eric Marquette
Stories like this emphasize how crucial our role is. It’s not about doing it all—it’s about doing the most impactful things exceptionally well. And that’s how we, as MSPs, contribute to a client’s compliance goals while staying within reasonable limits. But remember, there’s still some heavy lifting on the customer’s side too.
Eric Marquette
And here’s where it gets even more interesting. While MSPs own pieces of the puzzle, key security controls like Access Control, Logging, and Incident Response are what allow both us and our clients to succeed in this journey. These controls—when executed properly—not only help meet compliance but also prevent potential cybersecurity nightmares.
Eric Marquette
We’re diving into a common misconception—thinking that security tools alone make a company CMMC-compliant. Spoiler alert: They don’t. Compliance isn’t just about having firewalls, antivirus, or backups. It’s about policies, training, and audits. Let’s break it down. Imagine a bank with high-tech security cameras and reinforced doors—but no policies on who can access the vault, no employee training, and no audits to catch suspicious behavior. That’s what happens when companies rely only on security tools for compliance.
Eric Marquette
on why are just as critical as their IT defenses. Compliance is
Eric Marquette
Alright, everyone—let’s talk about acronyms. I know, acronyms can be daunting. But when it comes to CMMC compliance, these terms aren’t just jargon—they’re guideposts to help us understand what’s at stake. Let’s start with DFARS, which stands for the Defense Federal Acquisition Regulation Supplement. It’s the rulebook for contractors and subcontractors working with the Department of Defense. Think of it as the game’s rulebook, outlining what’s non-negotiable and why you need to secure sensitive data.
Eric Marquette
Then, there’s NIST, the National Institute of Standards and Technology. Imagine NIST as the playbook for creating a robust security strategy. Specifically, the NIST 800-171 standard becomes the cheat sheet for those looking to implement the controls required by DFARS and CMMC. And guys, here’s a specific takeaway: without NIST, you’re essentially playing a high-stakes game of cybersecurity without knowing the rules.
Eric Marquette
Next up, POA, or Plan of Action and Milestones. If compliance is a marathon, a POA is your training schedule. It lists areas where you fall short and maps your path to improvement—complete with deadlines and measurable steps. Finally, let’s touch on C3PAO, or CMMC Third-Party Assessment Organization. They’re the referees, the ones who come in and confirm if you’re truly hitting the compliance standards. Sure, getting reviewed might sound intimidating, but it’s how you prove your work and build lasting trust with clients. A simplified way to look at it might be that NIST sets the rules, DFARS enforces them, POA&M tracks issues, and C3PAO audits everything.
Eric Marquette
Now, let’s shift gears and talk about teamwork. You might think compliance is just for your IT gurus or your policy pros, but it’s not. Every single member of an MSP team plays a part, from professional services engineers setting up secure architectures or to support teams reinforcing password protocols on those late-night calls or from a Strategic Advisor who educates clients on why this is more than just IT security to Administrative employees that assist with documentation, and policy management.
Eric Marquette
So, here’s the grand takeaway as we wrap up today’s episode: Compliance isn’t just about meeting regulations—it’s about forging stronger, more secure collaborations. Every role is a crucial piece of the puzzle. When we lean into shared responsibility and own our part of the process, we set ourselves and our clients up for success. And remember, compliance isn’t just a task or a destination; it’s a way of thinking—an ongoing commitment that benefits everyone.
Eric Marquette
And on that note, that’s all we have for today. Thank you for joining me on this journey through MSPs and CMMC compliance. Remember, the work you do every day makes a difference—not just for your clients, but for the security of critical information. Until next time, keep your networks safe and your practices solid. Take care!
Chapters (3)
About the podcast
Join The IT Company on our CMMC General Education Journey, where we break down the Cybersecurity Maturity Model Certification (CMMC) in a way that’s accessible, practical, and relevant for businesses and IT professionals. Whether you're just starting to understand CMMC compliance or looking for strategies to level up your security posture, this podcast provides insights from industry experts, MSPs, and cybersecurity professionals navigating the same challenges
This podcast is brought to you by Jellypod, Inc.
© 2025 All rights reserved.