CMMC Data Protection for DoD Contractors
Petronella Technology Group, Inc. is CMMC Registered Provider Organization #1449. Our four CMMC-RP practitioners architect, deploy, document, and monitor the data protection stack your DoD subcontract demands, encrypted CUI handling, ComplianceArmor® evidence automation, Petronella XDR for continuous monitoring, and Lead vCISO oversight from Blake Rea. Twenty-three years in cybersecurity. One honest pattern recommendation per engagement.
What does compliant CMMC data protection actually require?
Three things, applied to your specific CUI footprint. First, an architecture that contains Controlled Unclassified Information, either Microsoft GCC High, a Petronella encrypted enclave, or an on-premises boundary, selected based on prime-contract clauses and CUI volume, not on what is easiest to sell. Second, a documentation set that ties every architectural decision to a NIST 800-171 r3 control: System Security Plan, Plan of Action and Milestones, policies and procedures, network and CUI flow diagrams, Customer Responsibility Matrix. Third, continuous monitoring and governance, an XDR layer that produces audit evidence on demand, plus a vCISO who owns the program between assessments. Skip any of the three and the assessor finds it.
Petronella Technology Group, Inc. delivers all three under one engagement. The encrypted data and email system handles CUI in motion and at rest. ComplianceArmor® generates and maintains the documentation set. Petronella XDR runs the monitoring. Blake Rea leads the vCISO program. No external dependencies on six different vendor portals, one team, one accountability line, RPO #1449 on the door.
The DoD contractor's CUI problem
If your contract has DFARS 252.204-7012 in it, and as a DoD subcontractor you almost certainly do, you are obligated to provide adequate security for Controlled Unclassified Information that "is collected, developed, received, transmitted, used, or stored." That single sentence is where most contractors quietly fail their first assessment, because CUI moves through more systems than the program manager realizes.
Where CUI actually flows in a small-to-mid DoD shop:
- Inbound from the prime: drawings, statements of work, contract addenda, ITAR-flagged attachments, government furnished information arriving as email attachments to engineering@, contracts@, or a shared inbox.
- Internal collaboration: engineers passing CAD files, machinists annotating travelers, project managers updating program schedules, finance reconciling cost data tied to a covered defense article.
- Outbound to subcontractors: your own tier-3 suppliers, plating shops, heat treaters, specialty coating houses, who are now flowed down with the same DFARS clause.
- Shadow IT: engineers emailing CAD files to personal Gmail to work from home, mobile devices syncing to consumer cloud, the "old" laptop a recently-departed employee still has at their house.
Every one of those flow points is an assessor question. The fix is not a single product; it is an architecture decision (where does CUI live?), a control implementation (how is access enforced?), and a documentation trail (where is the evidence?). Petronella Technology Group, Inc. starts with the CUI flow diagram during Phase 1: before anyone signs an enclave license or migrates a mailbox, because the flow diagram drives the architecture, not the other way around.
And one more thing the brochures don't say plainly: GCC High alone is not always the right answer. Microsoft GCC High is the FedRAMP High lineage tenant required when CUI flows through Microsoft 365 services that handle covered data. It is excellent at what it does. But it is expensive, slow to provision, breaks many third-party connectors, and is overkill for the substantial number of DoD subs whose CUI footprint is small, bounded, and could be safely contained in a properly-scoped encrypted enclave with the rest of the business running on commercial Microsoft 365. The honest answer requires honest assessment of your specific data flows. That is what gap analysis is for.
The 3-pattern decision tree for CMMC data protection
Most CMMC consultants try to standardize the architecture so they can sell the same package repeatedly. Petronella Technology Group, Inc. publishes our decision tree openly because the right pattern is determined by your contract clauses, your CUI volume, and your existing M365 posture, not by which tier is most profitable for us.
Read the full 3-pattern decision tree, Power BI variant. The same architectural logic applies to the data protection stack as a whole.
Microsoft GCC High top-to-bottom
When: A prime contract clause mandates GCC High. CUI volume is large or distributed across many M365 services (SharePoint, Teams, OneDrive, Exchange, Power BI, Power Platform). Budget supports full migration. The organization will be operating in the DoD ecosystem long enough for the multi-year licensing to amortize.
- Microsoft 365 GCC High provisioning (E5 GCC High or equivalent)
- Entra ID (Azure AD) in the GCC High tenant
- SharePoint, Teams, OneDrive, Exchange all GCC High
- Power BI in GCC High when BI uses CUI
- Identity rebuild, mailbox migration, third-party connector replacement
- Petronella CMMC Compliance Enclave Hosting Package as the managed wrapper
Implementation tier: Enterprise scope. Request a Quote, pricing depends on tenant provisioning, seat count, and migration complexity.
Petronella encrypted enclave plus commercial Microsoft 365
When: No contract clause mandates GCC High. CUI volume is small and bounded, a defined group of engineers handling drawings and statements of work, with the rest of the business (HR, accounting, marketing) on commercial Microsoft 365. The organization wants CMMC Level 2 attestation without bearing GCC High licensing for users who never touch CUI.
- Petronella encrypted data and email system for CUI in transit and at rest
- Bounded enclave membership, only CUI-handling roles enrolled
- De-identified or aggregate data flowing to commercial M365 where useful
- Documented CUI boundary in the SSP, sharp line between enclave and commercial
- Petronella XDR monitoring both sides
- ComplianceArmor® documents the boundary, scope, and control coverage
Implementation tier: Foundation through Mid-Market scope. Request a Quote, pricing depends on enclave seat count and integration scope.
On-premises or hybrid air-gapped boundary
When: Prime contract clauses block external SaaS for CUI handling. The organization has existing on-premises infrastructure suitable for hosting an in-boundary stack. Air-gap or near-air-gap is desired for engineering or manufacturing workflows that touch ITAR-flagged drawings.
- On-premises identity, file services, and email gateway inside the assessor-scoped boundary
- Power BI Report Server on-prem (when BI is in scope), no Copilot, no external SaaS dependencies
- Petronella encrypted data and email system as the secure transport layer for any inbound or outbound CUI exchange
- Hardened endpoint posture, locked-down updates, network segmentation
- Petronella XDR monitoring inside the boundary with audit forwarding to a CMMC-aware SIEM
- Longer release cycles and a higher infrastructure operating cost, accepted as the price of in-boundary control
Implementation tier: Enterprise scope with operational ownership. Request a Quote, pricing depends on infrastructure topology and existing posture.
Important: an encrypted enclave does not turn commercial Microsoft 365 into a CUI-capable platform on its own. It moves the CUI handling layer outside the commercial M365 services. The Petronella encrypted data and email system is the CUI vault in Pattern B; it complements GCC High in Pattern A as the third-party-exchange layer; and it is the secure transport layer alongside Pattern C. The pattern dictates the boundary, the enclave operates inside the chosen boundary.
How the Petronella stack anchors the 100+ of 110 control story
NIST 800-171 r3 has 110 controls grouped into 14 families. A CMMC Level 2 assessment grades each one. Petronella Technology Group, Inc. does not claim that a single product checks all 110 boxes, no product does. The stack approach (encrypted data and email system + ComplianceArmor® + Petronella XDR + vCISO oversight) collectively addresses every control family because each layer was selected to complement the others.
The selected mapping below illustrates how the encrypted data and email system covers control families 3.1, 3.4, 3.5, 3.8, 3.13, and 3.14, the foundation of any CUI-handling architecture.
| Control ID | Family | How the stack addresses it |
|---|---|---|
| 3.1.1 | Access Control, Account Management | Encrypted system enforces per-user device-bound keys; ComplianceArmor® generates the access-control policy and onboarding/offboarding SOP. |
| 3.1.3 | Access Control, Access Enforcement | Encrypted system enforces CUI access at the document level; only enrolled enclave members can decrypt; no shared-account access possible. |
| 3.1.5 | Access Control, Least Privilege | Approval Groups enforce admin-level least privilege; ComplianceArmor® documents the matrix; vCISO Blake Rea reviews quarterly. |
| 3.1.13 | Access Control, Remote Access | End-to-end encrypted sessions for remote CUI access; no plaintext at any hop; XDR monitors anomalous access patterns. |
| 3.3.1 | Audit and Accountability, Audit Logging | Petronella XDR collects audit logs from the encrypted system, endpoints, and identity layer; logs retained per the documented retention policy. |
| 3.3.3 | Audit and Accountability, Audit Review | XDR analysts perform daily review; vCISO reviews monthly; ComplianceArmor® archives the review evidence. |
| 3.4.1 | Configuration Management, Baseline Configuration | Encrypted system has a defined baseline that ComplianceArmor® documents; deviations require change-control approval. |
| 3.5.3 | Identification and Authentication, Multifactor Authentication | Device-bound cryptographic keys plus mobile attestation provide multifactor for CUI access, phishing-resistant by design. |
| 3.6.1 | Incident Response, Incident Handling | Petronella XDR runs 24/7 detection; vCISO-owned incident response playbook; Petronella DFE 604180 available for forensic escalation. |
| 3.8.1 | Media Protection, Media Access | CUI never lands on local media outside the enclave; ComplianceArmor® documents the media handling SOP. |
| 3.8.9 | Media Protection, Backups | Encrypted backups in a FedRAMP-Moderate-equivalent storage tier; restoration tests on a documented cadence. |
| 3.11.1 | Risk Assessment, Risk Assessment | vCISO Blake Rea owns the annual risk assessment; ComplianceArmor® stores the risk register and treatment plan. |
| 3.13.8 | System and Communications Protection, Transmission Confidentiality | End-to-end encryption on every CUI transmission; no plaintext in transit, ever; cryptographic standards documented. |
| 3.13.11 | System and Communications Protection, Cryptographic Key Establishment | FIPS-validated cryptography; keys generated on device, never escrowed; rotation policy documented. |
| 3.13.16 | System and Communications Protection, Protection of Information at Rest | CUI encrypted at rest in the enclave; encryption keys protected per the cryptographic policy. |
| 3.14.6 | System and Information Integrity, Monitoring for Indicators | Petronella XDR continuously monitors for indicators of attack across endpoints, identity, and the encrypted system. |
The remaining control families, 3.2 (Awareness and Training), 3.7 (Maintenance), 3.9 (Personnel Security), 3.10 (Physical Protection), 3.12 (Security Assessment), and 3.15 (System and Information Integrity governance), are operationalized through ComplianceArmor®-generated policies, our security awareness training program, and the Blake Rea vCISO program. The full mapping is documented in your engagement-specific SSP.
ComplianceArmor® generates the SSP, POA&M, and policies
The most expensive line item in a CMMC engagement, dollar for dollar, is documentation. The Department of Defense has publicly estimated the documentation work alone at approximately $150,000 per contractor when done from scratch. Most contractors stall in the documentation phase, not because they cannot do the work, but because writing 14 control-family policies, a System Security Plan that addresses 110 controls and 320 objectives, a Plan of Action and Milestones, a Customer Responsibility Matrix, network and CUI flow diagrams, and assessment-ready evidence files is a multi-month effort by a senior compliance practitioner.
ComplianceArmor® is Petronella's proprietary compliance documentation platform. It is a multi-framework system, CMMC, NIST 800-171, NIST 800-53, NIST CSF 2.0, SOC 2, HIPAA, PCI DSS, FTC Safeguards, and ISO 27001, designed to compress the documentation phase without compromising assessor defensibility. For a CMMC Level 2 engagement specifically, ComplianceArmor® generates:
- System Security Plan (SSP) covering all 110 NIST 800-171 r3 controls with the 320 objectives mapped, drafted from a guided intake against your specific enclave architecture, reviewed and signed by a Petronella CMMC-RP practitioner
- Plan of Action and Milestones (POA&M) with prioritized remediation, dates, owners, and evidence-collection targets
- 14 control-family policies matched to your actual environment (not boilerplate), Access Control, Audit and Accountability, Awareness and Training, Configuration Management, Identification and Authentication, Incident Response, Maintenance, Media Protection, Personnel Security, Physical Protection, Risk Assessment, Security Assessment, System and Communications Protection, System and Information Integrity
- Standard Operating Procedures for the operational tasks each policy implies
- Customer Responsibility Matrix (CRM) defining what Petronella, what the client, and what jointly-owned tasks each party is accountable for
- Network and CUI flow diagrams: auto-rendered from your environment data, kept current as your architecture evolves
- Boundary diagram showing the assessor-scoped CUI boundary and what is outside of scope
- Evidence trail: every assertion linked back to the artifact that proves it
The differentiator versus generic compliance accelerators: ComplianceArmor® is multi-framework. When a DoD subcontractor that is also a healthcare-adjacent supplier needs CMMC plus HIPAA, or when a publicly-traded prime needs CMMC plus SOC 2 Type II, the same platform handles both. One intake, one set of evidence, one renewal cycle. Per our own engineering directive, the platform uses LLM-assisted intake for the SSP narrative, questions, doc extraction, framework text citations, but never auto-generates compliance content that an assessor would have to take on faith. A CMMC-RP practitioner reviews and signs every artifact.
Petronella XDR for continuous CMMC monitoring
CMMC Level 2 is not a one-time certificate; it is a continuous control state that the assessor will return to verify. Audit logs, alert response time, incident handling evidence, and risk-treatment progress have to be demonstrably alive between assessments. Petronella XDR is our managed extended detection and response service, purpose-built for the audit-and-accountability burden a DoD contractor carries.
What Petronella XDR adds to the CMMC stack:
- 3.3 Audit and Accountability family coverage: log collection from endpoints, identity, the encrypted enclave, network gear, and cloud services; retention aligned with your SSP-documented policy; on-demand evidence packaging for assessor review
- 3.6 Incident Response family coverage: 24/7 detection, triage, and response playbooks with assessor-defensible documentation of every incident lifecycle
- 3.11 Risk Assessment family coverage: continuous threat telemetry feeding into the vCISO-owned risk register and annual risk assessment
- 3.14 System and Information Integrity family support: indicator monitoring, malicious code detection, security alert correlation
- Direct escalation to a Petronella Digital Forensic Examiner (License 604180-DFE) when an incident requires forensic preservation, attribution, or Kovel-style privileged work
The XDR is operated by Petronella Technology Group, Inc., same accountability line as the encrypted system, the documentation, and the vCISO program. When an assessor asks "show me your audit review evidence from Q3," you are not coordinating across three vendor portals. Read more about Petronella XDR.
vCISO oversight: Blake Rea leads engagements
Architecture, documentation, and monitoring are the technical layers. The governance layer is what keeps a CMMC program alive between assessments: and that is the role of the virtual Chief Information Security Officer. Without it, the SSP goes stale, the POA&M items don't close, the risk register is never opened, and the CMMC Level 2 attestation that took eight months to earn quietly erodes into something the next assessor will struggle to defend.
Blake Rea, CMMC-RP, is the Petronella Lead vCISO and Senior Compliance Practitioner. His role on a CMMC engagement covers:
- Governance and policy stewardship: the SSP, POA&M, and policy set stay current as the environment changes
- Quarterly executive risk briefings: the client's leadership team gets a non-technical risk view with clear remediation priorities
- Annual risk assessment ownership, risk register, treatment plan, and tracking against the documented risk appetite
- L2 control owner mapping: every NIST 800-171 r3 control has a named owner inside the client org and a documented review cadence
- Vendor and subcontractor flow-down review: DFARS 252.204-7012 flow-down obligations to your own tier-3 suppliers are tracked and documented
- Incident response readiness: tabletop exercises, runbook reviews, escalation contact validation
- C3PAO assessment preparation: coordination with the assessment body, evidence-package handoff, post-assessment remediation guidance
Craig Petronella serves as Executive Sponsor on vCISO engagements, the senior escalation point for client leadership on strategic risk decisions, with direct availability when matters cross the technical/strategic boundary. Blake owns day-to-day delivery; Craig stays at the founder-level relationship. Read more about the Petronella vCISO program.
How a Petronella CMMC engagement actually runs
No two CMMC engagements are identical because no two CUI footprints are identical. That said, the engagement structure has settled into a four-phase model that consistently delivers assessment-ready clients in four to eight months. Petronella Technology Group, Inc. publishes the structure openly so prospective clients can audit our process before they sign.
Phase 0: Discovery call (free)
Thirty minutes with Blake Rea or Craig Petronella. We confirm your CMMC level target, prime-contract clauses, CUI scope, existing M365 posture, and engagement timeline. Output: a written scope summary and a fixed-fee proposal range for Phase 1.
Phase 1: Gap analysis and pattern selection (2-4 weeks)
CUI flow diagram, current-state control gap, architecture pattern selection (A, B, or C), and a written Phase 2 implementation plan. Output: gap analysis report, draft SSP scaffold inside ComplianceArmor®, and a fixed-fee Phase 2 proposal.
Phase 2: Build and implement (12-20 weeks)
Encrypted enclave or GCC High deployment, identity, mailbox migration where applicable, third-party integration, Petronella XDR onboarding, ComplianceArmor® policy generation, control implementation, evidence collection. Phased fixed-fee billing.
Phase 3: Pre-assessment readiness (4-8 weeks)
POA&M closure, evidence package finalization, mock assessment dry run with a Petronella CMMC-RP practitioner playing the assessor role, remediation of any findings. Output: assessment-ready state. We introduce you to vetted C3PAOs for the official Level 2 assessment.
Ongoing after assessment: Petronella XDR continues, ComplianceArmor® stays current, and the Blake Rea vCISO program runs on a monthly cadence with quarterly executive risk briefings. The engagement converts from project-mode to managed-service mode after the C3PAO certificate is issued.
Payment terms. All Petronella fixed-fee milestones are paid 100% upfront at contract execution. No net-15. No mid-phase invoicing. Ongoing managed services (XDR, ComplianceArmor® subscription, vCISO retainer) are billed monthly or annually per the SOW.
Frequently asked questions about CMMC data protection
Will this pass a CMMC Level 2 assessment?
Yes, when the architecture is selected and implemented correctly. CMMC Level 2 maps to NIST 800-171 r3 (110 controls, 320 objectives). The Petronella stack, encrypted data and email system for CUI in transit and at rest, ComplianceArmor® for the SSP and POA&M, Petronella XDR for continuous monitoring, and vCISO governance from Blake Rea, addresses all 110 controls when scoped against your specific enclave boundary. Petronella Technology Group, Inc. is CMMC Registered Provider Organization #1449 and our four CMMC-RP practitioners design the implementation against C3PAO expectations from day one. A C3PAO performs the actual assessment; we get you assessment-ready.
Is the Petronella encrypted enclave cheaper than Microsoft GCC High?
For most small to mid-size DoD subcontractors, yes, significantly. The encrypted enclave approach (Pattern B) is typically 60 to 80 percent less than a full GCC High top-to-bottom migration once you account for GCC High licensing, identity rebuild, mailbox migration, third-party connector replacement, and ongoing administration. But cheaper isn't the right reason to pick it. The right reason is fit: Pattern B works when your CUI footprint is small and bounded, and when you don't have prime-contract clauses mandating a FedRAMP High lineage tenant. If a prime mandates GCC High, you go GCC High. We help you decide during gap analysis instead of selling you the wrong thing.
How long does CMMC Level 2 preparation actually take?
From kickoff to assessment-ready is typically four to eight months for a small to mid-size DoD subcontractor with no prior CMMC work. Phase 1 (gap analysis, scoping, pattern selection) is two to four weeks. Phase 2 (enclave deployment, ComplianceArmor® documentation generation, control implementation) is twelve to twenty weeks. Phase 3 (POA&M closure, evidence collection, pre-assessment dry run) is four to eight weeks. Petronella Technology Group, Inc. runs many of these phases in parallel so calendar time stays compressed without skipping evidence work.
Do I still need a C3PAO?
Yes, for Level 2 assessment certification. A C3PAO (Certified Third-Party Assessor Organization) is the only entity authorized by the Cyber AB to perform an official CMMC Level 2 assessment. Petronella Technology Group, Inc. is an RPO, not a C3PAO, we cannot assess our own work, by design. We get you assessment-ready, then introduce you to vetted C3PAOs we have worked with. The separation is in the framework for a reason: it preserves objectivity in the assessment itself.
What if my prime contractor specifically requires GCC High?
Then you go GCC High (Pattern A). Petronella Technology Group, Inc. operates a CMMC Compliance Enclave Hosting Package that provisions Microsoft 365 GCC High and managed identity inside the FedRAMP High boundary. We don't push our preferred architecture onto an engagement when the prime contract clauses require otherwise, your contract obligations come first. The conversation we have during gap analysis is honest: if a clause mandates GCC High, the entire stack design changes.
How does ComplianceArmor® differ from a CMMC-specific documentation accelerator?
ComplianceArmor® is a multi-framework compliance platform, CMMC, NIST 800-171, NIST 800-53, NIST CSF 2.0, SOC 2, HIPAA, PCI DSS, FTC Safeguards, and ISO 27001. Single-framework accelerators only cover CMMC. The advantage matters when you have stakeholders beyond DoD: a CPA firm wanting CMMC plus SOC 2, a healthcare-adjacent supplier wanting CMMC plus HIPAA, or a publicly-traded prime wanting CMMC plus SOC 2 Type II. One platform, one set of evidence, one renewal cycle. ComplianceArmor® also uses LLM-assisted intake for the SSP narrative and policy questions, which compresses the documentation phase compared to template-only tools.
What NIST 800-171 r3 controls does the encrypted data system actually cover?
The Petronella encrypted data and email system directly addresses key controls across the 3.1 (Access Control), 3.4 (Configuration Management), 3.5 (Identification and Authentication), 3.8 (Media Protection), 3.13 (System and Communications Protection), and 3.14 (System and Information Integrity) families, that is roughly 60 of the 110 controls when paired with ComplianceArmor® documentation. Petronella XDR adds 3.3 (Audit and Accountability), 3.6 (Incident Response), and 3.11 (Risk Assessment) coverage. The remaining controls, physical, personnel, training, supply chain, are governance controls Blake Rea operationalizes through the vCISO engagement. The stack as a whole hits all 110.
What is the difference between this and a typical MSP's CMMC offering?
Three differences. First, RPO #1449 status, most MSPs are not Cyber AB Registered Provider Organizations. Second, our entire compliance bench is CMMC-RP certified, Craig Petronella, Blake Rea, Justin Summers, and Jonathan Wood. Third, ComplianceArmor® is our proprietary documentation platform, not a reseller relationship. Petronella Technology Group, Inc. has been in operation since April 5, 2002, 23 years in cybersecurity and compliance. We don't sell CMMC because the market is hot; we built the practice deliberately.
What about CMMC Level 3?
Level 3 layers NIST 800-172 (revision 3 final) enhanced security requirements on top of Level 2. Practically, that means stronger separation, narrower service principal posture, formalized supply chain risk management, advanced threat hunting, and tighter audit log retention. The encrypted enclave plus Petronella XDR plus vCISO governance scales into Level 3 with additional control implementation and process documentation. We have published a detailed walkthrough of NIST 800-172 r3 on the Petronella blog (link below) and incorporate those controls into Level 3 scoping when the prime contract requires it.
Can you support contractors who already have a partial CMMC implementation?
Yes, this is one of our common engagement types. Many DoD subs have started CMMC work with a previous consultant, an internal effort, or a generic MSP, and have stalled in the documentation phase or hit blockers on enclave architecture. We do a focused gap analysis, identify what is salvageable, rebuild what is not, and migrate the working evidence into ComplianceArmor® so the SSP, POA&M, and policies are coherent and assessor-defensible. We do not require a clean-slate engagement.
Do you handle the encrypted email migration end-to-end?
Yes. Petronella Technology Group, Inc. handles the encrypted data and email system deployment end-to-end: tenant provisioning, identity integration, user onboarding, Outlook and mobile client setup, third-party guest accounts for CUI exchange with primes, retention policies, and ongoing first-line support out of our Raleigh office. The vendor-side ticketing process is largely transparent to you, you call us, we resolve. That bundled local support is part of why our clients move faster than they would running a vendor relationship directly.
What is the next step?
Request a quote on this page or call (919) 348-4912. We schedule a thirty-minute discovery call with Blake Rea or Craig Petronella to confirm your CMMC level target, scope, prime-contract obligations, and existing posture. From there we provide a fixed-fee Phase 1 gap analysis proposal. After Phase 1 we agree on the right architecture pattern (A, B, or C), confirm the implementation roadmap, and start ComplianceArmor® evidence generation from day one. Petronella Technology Group, Inc. has been doing this for 23 years; we do not have a generic intake script.
The Petronella CMMC-RP bench
Petronella Technology Group, Inc. is one of a small number of Registered Provider Organizations whose entire compliance bench is CMMC-RP certified. Member #1449 with the Cyber AB. Four practitioners. Twenty-three years in business.
Craig Petronella
Founder & Executive Sponsor
CMMC-RP, Cisco CCNA, CWNE, Hubbell Certified, Digital Forensic Examiner License 604180-DFE. MIT Sloan AI alum. #1 Amazon Best-Selling Author of 14+ cybersecurity books. Founded Petronella Technology Group, Inc. on April 5, 2002.
Blake Rea
Lead vCISO & Senior Compliance Practitioner
CMMC-RP. Day-to-day lead on Petronella vCISO engagements. Governance, policy stewardship, monthly executive risk briefings, L2 control owner mapping, vendor and subcontractor flow-down review, incident response readiness.
Justin Summers
Senior Compliance Practitioner
CMMC-RP. Control implementation, evidence collection, ComplianceArmor® intake, and POA&M closure across DoD subcontractor engagements.
Jonathan Wood
Senior Compliance Practitioner
CMMC-RP. Architecture review, gap analysis, and Phase 1 pattern selection across the CMMC engagement portfolio.
Related Petronella resources
- The Petronella Data Protection pillar (encrypted data and email system)
- CMMC Compliance Guide, framework explainer
- ComplianceArmor®, multi-framework documentation platform
- Petronella XDR, managed detection and response
- Petronella vCISO program, Blake Rea leads
- CMMC Power BI Reporting, full 3-pattern decision tree
- The Petronella CMMC-RP bench (4 practitioners)
- NIST SP 800-172 r3 Final, CMMC Level 3 Deep Dive
Request a CMMC scoping call
Tell us your CMMC level target, prime-contract obligations, and current posture. Blake Rea or Craig Petronella replies within 4 business hours, often sooner.
Prefer to call? Call Penny at (919) 348-4912, she answers 24/7 and can schedule an expert.
Ready to scope your CMMC data protection the right way?
Petronella Technology Group, Inc., RPO #1449, four CMMC-RP practitioners, ComplianceArmor® documentation, Petronella XDR monitoring, Blake Rea-led vCISO governance. Twenty-three years building secure, compliant IT for Department of Defense subcontractors and US clients.
Request a Quote