CMMC Level 1, 2 and 3 by RPO #1449.
The fastest path to CMMC Level 2 for DoD subcontractors. NIST SP 800-171 alignment, 110-control gap assessment, SSP and POA&M structure, mock C3PAO audit, delivered by an RPO-listed CMMC-RP practitioner team based in Raleigh.
New from Petronella Technology Group: CMMC Level 1 self-assessment guide for DoD subcontractors and the C3PAO selection guide for Phase 2 readiness.
What CMMC compliance actually requires
CMMC 2.0 has three levels. Level 1 is annual self-attestation against 17 basic safeguarding controls. Level 2 is the one most defense subcontractors actually need: a C3PAO-led assessment of all 110 NIST SP 800-171 controls, with a numeric SPRS score posted to the DoD's Supplier Performance Risk System. Level 3 stacks a subset of NIST SP 800-172 controls on top for contracts touching the most sensitive CUI.
If your prime contractor has flowed down a DFARS 252.204-7012 clause and you handle Controlled Unclassified Information, you need Level 2. Start with our CMMC compliance guide if you want the full lay of the land before scoping work. If you want the short version of where your gaps are right now, run the CMMC compliance checklist and the SPRS calculator in the same sitting.
Our CMMC engagement, step by step
We are a CMMC-AB Registered Practitioner Organization, RPO #1449. Every engineer assigned to your engagement is a CMMC-RP. We do not certify and we do not assess. C3PAOs do that, by design. What we do is take you from "we have a CUI flow-down clause" to "we are ready for the assessor" without burning twelve months of internal time figuring out what each control actually requires.
A typical engagement opens with a CMMC gap assessment against all 110 controls, including CUI boundary scoping and an SPRS score baseline. From there we close the technical gaps that almost always block Level 2: multifactor authentication on every required path (3.5.3), session lock and termination (3.1.10), risk assessment cadence (3.11.1), FIPS-validated encryption, audit logging that actually correlates, and the configuration management baseline. We author the System Security Plan and Plan of Action & Milestones, organize the evidence library, then run a mock C3PAO assessment against the same Conformity Assessment Procedures the real assessor will use.
If Level 2 is not the right scope for you
Not every contractor needs the full Level 2 path. Some only handle FCI and qualify for Level 1 self-attestation. Some can shrink scope dramatically by moving CUI into a separate enclave instead of certifying their whole tenant. Some are evaluating whether a managed-tenant offering is cheaper than building their own. We walk through those tradeoffs honestly in CMMC alternatives, and we do not pretend a Level 2 engagement is mandatory when it is not.
CMMC Compliance services
Pick the path that matches what you need next. Or call Penny - she'll book your free 15-minute consult.
CMMC Compliance Guide
The full lay of CMMC 2.0: levels, scope, SPRS, C3PAOs, what changed, and what the deadline really means for subcontractors.
Read the guide →CMMC Assessment
110-control gap assessment against NIST 800-171 with an SPRS baseline and a prioritized remediation roadmap.
See the assessment →CMMC Compliance Checklist
A working checklist that walks every NIST 800-171 family with the artifact a C3PAO will expect to see for each control.
Open the checklist →SPRS Calculator
Score your current NIST 800-171 posture on the same +110 / -203 SPRS scale the DoD uses. No login. Free.
Run the calculator →CMMC Alternatives
Enclave-only, managed-tenant, GCC High, and consortium options compared honestly against full Level 2 in your existing environment.
Compare alternatives →CMMC Compliance Services
Done-for-you remediation: SSP authoring, POA&M tracking, MFA and FIPS rollout, mock C3PAO assessment, C3PAO handoff package.
View services →Defense Contractor Cybersecurity
Industry vertical for defense primes and subs - DFARS 252.204-7012, CUI handling, SPRS, and the supply-chain controls a flow-down clause expects.
See defense vertical →CMMC for Manufacturers
Manufacturing-specific CMMC playbook - shop-floor OT, ITAR-adjacent CUI, ERP boundary scoping, and what a discrete manufacturer needs to pass Level 2.
See manufacturing CMMC →Related pillars, defense resources, and supply-chain reading
- Related Petronella pillars
- Compliance hub (CMMC, HIPAA, NIST, CCPA)
- Cybersecurity pillar (24/7 SOC + ZeroHack stack)
- HIPAA compliance for defense health contractors
- Private AI services (CUI-safe model deployment)
- CUI-grade hardware and GPU servers
- Already breached? Digital forensics + IR
- 2026 annual security awareness training course (NIST 800-171 3.2.1 evidence)
- Defense AI and verticals
- AI for defense contractors (CMMC-aware private AI)
- Defense contractor cybersecurity vertical
- IT services for federal contractors
- Manufacturing cybersecurity
- CMMC for manufacturing companies
- AI for government
- Private AI cluster (CUI-safe AI infrastructure)
- Supply chain security
- Guides
- Digital forensics guide
- 2026 cybersecurity outlook
CMMC compliance by city - North Carolina service areas
- Angier, NC
- Apex, NC
- Burlington, NC
- Carrboro, NC
- Cary, NC
- Chapel Hill, NC
- Charlotte, NC
- Clayton, NC
- Concord, NC
- Apex Consultant, NC
- Durham, NC
- Fayetteville, NC
- Fuquay-Varina, NC
- Garner, NC
- Gastonia, NC
- Goldsboro, NC
- Greensboro, NC
- Henderson, NC
- High Point, NC
- Hillsborough, NC
- Holly Springs, NC
- Jacksonville, NC
- Knightdale, NC
- Louisburg, NC
- Mebane, NC
- Morrisville, NC
- Pittsboro, NC
- Raleigh, NC
- Research Triangle Park, NC
- Rocky Mount, NC
- Rolesville, NC
- Sanford, NC
- Smithfield, NC
- Wake Forest, NC
- Wendell, NC
- Wilmington, NC
- Winston-Salem, NC
- Zebulon, NC
NIST 800-171 control library - all 110 controls explained
- 3.1 - Access Control (family)
- 3.1.1 Limit system access
- 3.1.2 Limit to authorized functions
- 3.1.3 Control CUI flow
- 3.1.4 Separation of duties
- 3.1.5 Least privilege
- 3.1.6 Non-privileged accounts
- 3.1.7 Prevent privileged execution
- 3.1.8 Limit logon attempts
- 3.1.9 Privacy & security notices
- 3.1.10 Session lock
- 3.1.11 Terminate sessions
- 3.1.12 Monitor remote access
- 3.1.13 Crypto for remote access
- 3.1.14 Route remote access
- 3.1.15 Remote privileged commands
- 3.1.16 Authorize wireless access
- 3.1.17 Protect wireless access
- 3.1.18 Control mobile devices
- 3.1.19 Encrypt CUI on mobile
- 3.1.20 External system connections
- 3.1.21 Portable storage limits
- 3.1.22 Public-system CUI control
- 3.2 - Awareness & Training (family)
- 3.2.1 Security awareness training
- 3.2.2 Role-based training
- 3.2.3 Insider threat awareness
- 3.3 - Audit & Accountability (family)
- 3.3.1 Create & retain audit logs
- 3.3.2 Individual accountability
- 3.3.3 Review audited events
- 3.3.4 Alert on audit failure
- 3.3.5 Correlate audit records
- 3.3.6 Audit record reduction
- 3.3.7 Authoritative time source
- 3.3.8 Protect audit information
- 3.3.9 Limit audit log management
- 3.4 - Configuration Management (family)
- 3.4.1 Baseline configurations
- 3.4.2 Security config settings
- 3.4.3 Track config changes
- 3.4.4 Analyze change impact
- 3.4.5 Access restrictions for changes
- 3.4.6 Least functionality
- 3.4.7 Restrict nonessential programs
- 3.4.8 Deny-by-exception policy
- 3.4.9 User-installed software
- 3.5 - Identification & Auth (family)
- 3.5.1 Identify users & processes
- 3.5.2 Authenticate users
- 3.5.3 MFA local & network
- 3.5.4 Replay-resistant auth
- 3.5.5 Prevent ID reuse
- 3.5.6 Disable inactive IDs
- 3.5.7 Password complexity
- 3.5.8 Prohibit password reuse
- 3.5.9 Temporary passwords
- 3.5.10 Crypto-protected passwords
- 3.5.11 Obscure auth feedback
- 3.6 - Incident Response (family)
- 3.6.1 Incident handling capability
- 3.6.2 Track & report incidents
- 3.6.3 Test incident response
- 3.7 - Maintenance (family)
- 3.7.1 Perform maintenance
- 3.7.2 Control maintenance tools
- 3.7.3 Sanitize maintenance equipment
- 3.7.4 Check media for malicious code
- 3.7.5 MFA for nonlocal maintenance
- 3.7.6 Supervise external maintenance
- 3.8 - Media Protection (family)
- 3.8.1 Protect CUI on media
- 3.8.2 Limit media access
- 3.8.3 Sanitize CUI media
- 3.8.4 Mark CUI media
- 3.8.5 Control CUI media access
- 3.8.6 Crypto for portable storage
- 3.8.7 Control removable media
- 3.8.8 Prohibit unowned storage
- 3.8.9 Protect backup CUI
- 3.9 - Personnel Security (family)
- 3.9.1 Screen individuals
- 3.9.2 CUI during personnel actions
- 3.10 - Physical Protection (family)
- 3.10.1 Limit physical access
- 3.10.2 Monitor physical facility
- 3.10.3 Escort visitors
- 3.10.4 Physical access audit logs
- 3.10.5 Physical access devices
- 3.10.6 Alternate work sites
- 3.11 - Risk Assessment (family)
- 3.11.1 Periodically assess risk
- 3.11.2 Scan for vulnerabilities
- 3.11.3 Remediate vulnerabilities
- 3.12 - Security Assessment (family)
- 3.12.1 Assess security controls
- 3.12.2 Plans of action
- 3.12.3 Monitor controls ongoing
- 3.12.4 Develop & update SSP
- 3.13 - System & Comms Protection (family)
- 3.13.1 Boundary protection
- 3.13.2 Architectural security
- 3.13.3 Separate user & mgmt
- 3.13.4 Prevent unauth transfer
- 3.13.5 Public subnetworks
- 3.13.6 Deny by default
- 3.13.7 Prevent split tunneling
- 3.13.8 Crypto for CUI in transit
- 3.13.9 Terminate network sessions
- 3.13.10 Manage crypto keys
- 3.13.11 FIPS-validated crypto
- 3.13.12 Prohibit remote activation
- 3.13.13 Control mobile code
- 3.13.14 Control VoIP
- 3.13.15 Authentic comm sessions
- 3.13.16 Protect CUI at rest
- 3.14 - System & Info Integrity (family)
- 3.14.1 Remediate system flaws
- 3.14.2 Protect from malicious code
- 3.14.3 Monitor security alerts
- 3.14.4 Update malicious code defs
- 3.14.5 Periodic & real-time scans
- 3.14.6 Monitor comms for attacks
- 3.14.7 Unauthorized system use
Ready to talk?
Call Penny - she answers before the third ring, asks 3 qualifying questions, then books your free 15.