CMMC Compliance Managed Services for Defense Industrial Base Contractors
Mission-Critical IT. Battle-Tested Operations.
CMMC Resource Hub
The CMMC Compliance Guide for Defense Contractors
Scoping your environment, closing control gaps, preparing evidence, and choosing where CUI actually lives. This guide pulls together what defense contractors ask us most, with links to the deeper breakdowns behind each topic.
Since 2017, VSO has served defense contractors operating in some of the most sensitive, compliance-intensive environments in the industry. We understand the stakes. Your IT infrastructure isn’t just supporting business operations — it’s protecting Controlled Unclassified Information (CUI), enabling cleared personnel, and maintaining the operational security that keeps defense programs moving forward.
We’ve built our managed services specifically for organizations navigating CMMC 2.0, NIST SP 800-171, and the complex security architectures required by DoW contracts. Our team brings real-world experience operating in SCIF environments, managing enclaves with strict access controls, and maintaining the documentation and operational discipline that auditors expect to see.
What This Guide Covers:
Scoping & Boundaries
Almost every expensive CMMC mistake traces back to scope. Contractors either draw the boundary too wide, pulling the entire corporate network into assessment and multiplying the cost of every control, or they draw it too narrow and discover that CUI has been flowing through systems nobody accounted for.
Scope is a data question before it is a technology question. Where does CUI enter the business, who touches it, where does it rest, and where does it leave. Once that map exists, the boundary draws itself and the cloud decision becomes obvious rather than agonizing.
CMMC Scoping Explained: What Counts as In-Scope at Your Company
How the asset categories work in practice, and the common places contractors accidentally widen their own boundary.
What Is a Government Cloud Enclave
The case for isolating CUI in a defined enclave instead of hardening every system your company operates.
Azure Government for CMMC Level 2 Compliance
Where Azure Government and GCC High fit, what they cover, and what still falls to you to configure and document.
AWS GovCloud Explained for Defense Contractors
AWS GovCloud services explained: regions, compliance boundaries, and eligibility written specifically for defense contractors by a veteran-led MSP.
Closing Control Gaps
The 110 controls in NIST SP 800-171 are not evenly difficult. A handful account for most of the findings we see, and they tend to be the ones that look finished on paper but fall apart under evidence review. Identity is the usual culprit, followed closely by logging, media protection, and configuration baselines nobody has revisited since deployment.
Top 5 CMMC Gaps We See in Defense Contractors
The recurring findings that surface across engagements, and what it actually takes to close each one.
Multi-Factor Authentication for CMMC: What Actually Counts as Compliant
Why the MFA you already deployed may not satisfy the control, and which factor types hold up under review.
Assessment Readiness
Readiness is a documentation discipline more than a technical one. Contractors who struggle are rarely missing the control. They are missing the artifact that proves the control has been operating continuously, which is a different problem and a harder one to fix in the weeks before a review.
The three pieces worth understanding early are which assessment path applies to you, how the scoring math treats partial implementation, and what the review itself actually looks like when it happens.
CMMC Self-Assessment vs. C3PAO Assessment: Which Do You Need?
How the paths differ, which contract conditions point to each, and where your obligations stand today.
CMMC Scoring: How the 110-Point Assessment Math Actually Works
Why a single control can cost five points, how deductions compound, and what your SPRS score communicates.
CMMC Audit Day: What to Expect and How to Prepare
The sequence of a formal review, the evidence requested, and how to prepare your team for the interviews.
A note on timing: the last two resources describe formal third-party assessment. With Phase II suspended, those assessments are not currently required. We keep the material available because the evidence discipline it describes is exactly what Phase I self-assessment and SPRS submission depend on, and because the requirement is under review rather than withdrawn.
Not sure where your boundary actually sits?
Our CUI data flow gap analysis maps where regulated data moves through your business before anyone spends a dollar on tooling. Call (888) 805-0510 or email sales@vso-inc.com.
Your Supply Chain and Your IT Provider
CMMC obligations do not stop at your own perimeter. They travel down through subcontracts, and they reach sideways into every vendor that touches your environment. Your IT provider is the vendor with the deepest access of all, which makes their posture part of your posture whether the contract says so or not.
Smaller contractors feel this hardest. The obligations arrive at full scale regardless of headcount, and the teams absorbing them are often one or two people who also handle everything else.
Does Your IT Provider Need to Be CMMC Compliant?
What to require of an MSP that administers systems inside your boundary, and how to verify the claims they make.
Flow-Down Clauses: How to Track Subcontractor CMMC Compliance
Which DFARS clauses pass through, and how primes verify subcontractor posture without guessing.
CMMC for Small Defense Contractors: A Survival Guide
A sequencing approach for lean teams, built around narrowing scope before expanding spend.
AI and Emerging Technology Under CMMC
AI tools entered defense contractor workflows faster than governance could follow. The compliance exposure is rarely the model itself. It is the prompt that carries a drawing, a specification, or an export-controlled detail into a system outside your boundary, logged somewhere you have no visibility into and no ability to produce evidence about. See more by clicking the image below ↓
How VSO Supports CMMC Compliance
VSO is a managed services provider and implementation partner. We design, build, and operate the environments that carry CUI, and we maintain the evidence trail that proves those controls are working. We are not a C3PAO and we do not perform assessments, which means our work has no conflict with whoever eventually reviews you.
If you are evaluating managed services specifically rather than researching requirements, our CMMC services page covers engagement structure and how we scope the work.
CUI Data Flow Gap Analysis
Mapping where regulated data enters, rests, and leaves your business, then setting a defensible boundary around it. This is where every engagement starts.
CMMC Enclave Design and Management
Architecting an isolated environment for CUI so the rest of your business stays out of scope, then running it day to day.
Managed Government Cloud
Azure Government and Microsoft 365 GCC High, AWS GovCloud, and hybrid configurations, deployed and operated by a Microsoft Solutions Partner and AWS Advanced Consulting Partner.
24/7/365 NOC and SOC Operations
A combined network and security operations model, staffed entirely in the United States, generating the continuous monitoring evidence your controls depend on.
Zero Trust Enforcement
Identity, device, and access controls implemented against the requirements rather than around them, including conditional access and privileged access management.
Service Desk and Endpoint Management
U.S.-based support for cleared and uncleared users, with endpoint hardening, patching, and configuration baselines held to your compliance boundary.
Evidence and Documentation Support
System security plans, POA&M maintenance, and the continuous artifact trail that turns implemented controls into provable ones.
Cleared IT Staffing
Technical personnel with active clearances, placed into programs that require them, drawn from a hiring pipeline built around military veterans.
Why Defense Contractors Choose VSO
VSO has grown entirely through client referrals since 2017. No outbound engine, no channel program. Contractors send us to other contractors because the work holds up, and because the people doing it understand the mission environment from the inside.
“Hiring veterans is our business model. They arrive understanding accountability, classification, and what it means when the mission depends on your work being right.”
Steve O’Keefe, Chief Executive Officer, Virtual Service Operations
VSO is a DoD SkillBridge participant, and veteran hiring runs through every part of the business rather than sitting beside it. That matters operationally. The engineers in our NOC and SOC have worked inside environments where compliance failures carried consequences, which changes how they treat a control that looks fine on paper.
Start with the boundary, not the tooling
Tell us where CUI moves through your business and we will tell you what actually falls in scope. Call (888) 805-0510, email sales@vso-inc.com, or visit vso-inc.com.
Frequently Asked Questions
Is CMMC still required now that Phase II is suspended?
Yes, in the form that currently applies. The Department of War suspended Phase II, which covered third-party assessment. Phase I self-assessment, NIST SP 800-171 Rev 2 implementation, SPRS score submission, and the DFARS clauses covering CUI all remain in effect and still govern contract eligibility.
Does VSO perform CMMC assessments?
No. VSO is a managed services provider and implementation partner. We build and operate compliant environments and maintain the supporting evidence. Formal assessment is performed by a certified third-party assessment organization, and keeping those roles separate avoids any conflict of interest.
What is the difference between CMMC Level 1 and Level 2?
Level 1 applies to contractors handling Federal Contract Information and covers a smaller set of basic safeguarding practices. Level 2 applies to contractors handling Controlled Unclassified Information and aligns to the 110 controls in NIST SP 800-171. Which applies depends on the data your contracts carry.
Do I need to move everything into a government cloud?
Usually not. Most contractors are better served by isolating CUI inside a defined enclave and leaving the rest of the business out of scope. Moving everything tends to raise cost and complexity without improving posture.
Does my IT provider need to be CMMC compliant?
If they administer systems inside your CUI boundary, their security posture becomes part of yours. External service providers handling or protecting CUI carry obligations, and you should expect documented evidence rather than verbal assurance.
How long does it take to get compliant?
It depends almost entirely on how much scope reduction is possible and how mature your documentation already is. A contractor with a tight boundary and reasonable records moves quickly. One discovering CUI across an unmanaged network needs to fix the architecture before the controls mean anything.
Can defense contractors use AI tools under CMMC?
Yes, with governance. The exposure comes from regulated data entering systems outside your boundary through prompts or integrations. Tools operating inside a compliant environment, with controls on what can be submitted to them, can be used safely.
What does a CUI data flow gap analysis involve?
We trace where regulated data enters your business, which people and systems touch it, where it rests, and where it leaves. That map defines your boundary, which in turn determines scope, platform choice, and the real cost of compliance.
NIST 110 Controls
110 controls · tap any one
Every one of these has to be implemented, documented, and provable.
Tap a control to read what it actually requires. Colors group them into the fourteen families an assessment is organized around.
Authorized Access Control [CUI Data]
Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems).
Transaction & Function Control [CUI Data]
Limit system access to the types of transactions and functions that authorized users are permitted to execute.
Control CUI Flow
Control the flow of CUI in accordance with approved authorizations.
Separation of Duties
Separate the duties of individuals to reduce the risk of malevolent activity without collusion.
Least Privilege
Employ the principle of least privilege, including for specific security functions and privileged accounts.
Non-Privileged Account Use
Use non-privileged accounts or roles when accessing nonsecurity functions.
Privileged Functions
Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.
Unsuccessful Logon Attempts
Limit unsuccessful logon attempts.
Privacy & Security Notices
Provide privacy and security notices consistent with applicable CUI rules.
Session Lock
Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity.
Session Termination
Terminate (automatically) a user session after a defined condition.
Control Remote Access
Monitor and control remote access sessions.
Remote Access Confidentiality
Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.
Remote Access Routing
Route remote access via managed access control points.
Privileged Remote Access
Authorize remote execution of privileged commands and remote access to security-relevant information.
Wireless Access Authorization
Authorize wireless access prior to allowing such connections.
Wireless Access Protection
Protect wireless access using authentication and encryption.
Mobile Device Connection
Control connection of mobile devices.
Encrypt CUI on Mobile
Encrypt CUI on mobile devices and mobile computing platforms.
External Connections [CUI Data]
Verify and control/limit connections to and use of external systems.
Portable Storage Use
Limit use of portable storage devices on external systems.
Control Public Information [CUI Data]
Control CUI posted or processed on publicly accessible systems.
Role-Based Risk Awareness
Inform managers, systems administrators, and users of organizational systems of the security risks associated with their activities and of the applicable policies, standards, and procedures related to the security of those systems.
Role-Based Training
Train personnel to carry out their assigned information security-related duties and responsibilities.
Insider Threat Awareness
Provide security awareness training on recognizing and reporting potential indicators of insider threat.
System Auditing
Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity.
User Accountability
Uniquely trace the actions of individual system users, so they can be held accountable for their actions.
Event Review
Review and update logged events.
Audit Failure Alerting
Alert in the event of an audit logging process failure.
Audit Correlation
Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity.
Reduction & Reporting
Provide audit record reduction and report generation to support on-demand analysis and reporting.
Authoritative Time Source
Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records.
Audit Protection
Protect audit information and audit logging tools from unauthorized access, modification, and deletion.
Audit Management
Limit management of audit logging functionality to a subset of privileged users.
System Baselining
Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.
Security Configuration Enforcement
Establish and enforce security configuration settings for information technology products employed in organizational systems.
System Change Management
Track, review, approve or disapprove, and log changes to organizational systems.
Security Impact Analysis
Analyze the security impact of changes prior to implementation.
Access Restrictions for Change
Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.
Least Functionality
Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities.
Nonessential Functionality
Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.
Application Execution Policy
Apply deny-by-exception (blacklisting) policy to prevent the use of unauthorized software or deny-all, permit-by-exception (whitelisting) policy to allow the execution of authorized software.
User-Installed Software
Control and monitor user-installed software.
Identification [CUI Data]
Identify system users, processes acting on behalf of users, and devices.
Authentication [CUI Data]
Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems.
Multifactor Authentication
Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.
Replay-Resistant Authentication
Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts.
Identifier Reuse
Prevent reuse of identifiers for a defined period.
Identifier Handling
Disable identifiers after a defined period of inactivity.
Password Complexity
Enforce a minimum password complexity and change of characters when new passwords are created.
Password Reuse
Prohibit password reuse for a specified number of generations.
Temporary Passwords
Allow temporary password use for system logons with an immediate change to a permanent password.
Cryptographically-Protected
Passwords Store and transmit only cryptographically protected passwords.
Obscure Feedback
Obscure feedback of authentication information.
Incident Handling
Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.
Incident Reporting
Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.
Incident Response Testing
Test the organizational incident response capability.
Perform Maintenance
Perform maintenance on organizational systems.
System Maintenance Control
Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance.
Equipment Sanitization
Sanitize equipment removed for off-site maintenance of any CUI.
Media Inspection
Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems.
Nonlocal Maintenance
Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete.
Maintenance Personnel
Supervise the maintenance activities of maintenance personnel without required access authorization.
Media Protection
Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital.
Media Access
Limit access to CUI on system media to authorized users.
Media Disposal [CUI Data]
Sanitize or destroy system media containing CUI before disposal or release for reuse.
Media Markings
Mark media with necessary CUI markings and distribution limitations.
Media Accountability
Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas.
Portable Storage Encryption
Implement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport unless otherwise protected by alternative physical safeguards.
Removable Media
Control the use of removable media on system components.
Shared Media
Prohibit the use of portable storage devices when such devices have no identifiable owner.
Protect Backups
Protect the confidentiality of backup CUI at storage locations.
Screen Individuals
Screen individuals prior to authorizing access to organizational systems containing CUI.
Personnel Actions
Protect organizational systems containing CUI during and after personnel actions such as terminations and transfers.
Limit Physical Access [CUI Data]
Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals.
Monitor Facility
Protect and monitor the physical facility and support infrastructure for organizational systems.
Escort Visitors [CUI Data]
Escort visitors and monitor visitor activity.
Physical Access Logs [CUI Data]
Maintain audit logs of physical access.
Manage Physical Access [CUI Data]
Control and manage physical access devices.
Alternative Work Sites
Enforce safeguarding measures for CUI at alternate work sites.
Risk Assessments
Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational systems and the associated processing, storage, or transmission of CUI.
Vulnerability Scan
Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.
Vulnerability Remediation
Remediate vulnerabilities in accordance with risk assessments.
Security Control Assessment
Periodically assess the security controls in organizational systems to determine if the controls are effective in their application.
Operational Plan of Action
Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems.
Security Control Monitoring
Monitor security controls on an ongoing basis to determine the continued effectiveness of the controls.
System Security Plan
Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships with or connections to other systems.
Boundary Protection [CUI Data]
Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems.
Security Engineering
Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.
Role Separation
Separate user functionality from system management functionality.
Shared Resource Control
Prevent unauthorized and unintended information transfer via shared system resources.
Public-Access System Separation
[CUI Data] Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.
Network Communication by
Exception Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).
Split Tunneling
Prevent remote devices from simultaneously establishing non-remote connections with organizational systems and communicating via some other connection to resources in external networks (i.e., split tunneling).
Data in Transit
Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.
Connections Termination
Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity.
Key Management
Establish and manage cryptographic keys for cryptography employed in organizational systems.
CUI Encryption
Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.
Collaborative Device Control
Prohibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device.
Mobile Code
Control and monitor the use of mobile code.
Voice over Internet Protocol
Control and monitor the use of Voice over Internet Protocol (VoIP) technologies.
Communications Authenticity
Protect the authenticity of communications sessions.
Data at Rest
Protect the confidentiality of CUI at rest.
Flaw Remediation [CUI Data]
Identify, report, and correct system flaws in a timely manner.
Malicious Code Protection [CUI Data]
Provide protection from malicious code at designated locations within organizational systems.
Security Alerts & Advisories
Monitor system security alerts and advisories and take action in response.
Update Malicious Code Protection
[CUI Data] Update malicious code protection mechanisms when new releases are available.
System & File Scanning [CUI Data]
Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed.
Monitor Communications for
Attacks Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks.
Identify Unauthorized Use
Identify unauthorized use of organizational systems.
