CMMC Compliance
Cybersecurity Requirements for Aerospace Manufacturers in 2026
Cybersecurity requirements for aerospace manufacturers in 2026 are stricter, enforced faster, and tied directly to contract eligibility. If you supply parts, components, or services to the DoD or prime contractors, you need to understand CMMC Level 2, NIST 800-171, DFARS 252.204-7012, and ITAR controls, and how DARS Class Deviation 2026-O0025 Revision 3 changes the way CMMC compliance is currently demonstrated. Falling behind on any of these puts contract eligibility at risk.
Here's what's actually required right now, what's paused, and what it costs.
The 2026 Aerospace Cybersecurity Landscape (Simple Breakdown)
Think of aerospace cybersecurity like FAA airworthiness. You can't just claim your aircraft is safe. You must prove it through documented inspections, certified processes, and audits.
Cybersecurity works the same way, with one important nuance in 2026. Under DARS Class Deviation 2026-O0025 Revision 3, issued September 3, 2026, CMMC Level 1 and Level 2 can currently be satisfied by self-assessment, and third-party C3PAO assessment is not being designated in new DoD solicitations. No date has been set for its return. That does not mean the underlying requirements went away. Primes and the DoD still expect:
- Documented evidence of the 110 NIST 800-171 controls
- Continuous monitoring
- Incident reporting within 72 hours under DFARS 252.204-7012
- Accurate self-assessments and annual affirmations, now under more scrutiny with no third-party assessor sharing the risk
If you can't prove compliance internally, you're exposed the moment third-party assessment returns, and you're exposed to False Claims Act liability right now if your self-assessment or affirmation is inaccurate.
Core Cybersecurity Requirements for 2026
1. CMMC Level 2 Alignment
CMMC Level 2 is the baseline standard for any aerospace manufacturer handling Controlled Unclassified Information (CUI). It requires all 110 NIST 800-171 controls fully implemented, a documented System Security Plan (SSP) and POA&M, and an annual affirmation of continued compliance, which carries False Claims Act exposure. Under Revision 3, Level 2 can currently be satisfied by a self-assessment posted to SPRS, but the underlying control requirements have not changed.
2. NIST 800-171 Implementation
NIST 800-171 is the underlying control framework for CMMC. It covers 14 control families, including access control, audit and accountability, configuration management, incident response, and system and communications protection. Each control must be implemented, documented, and continuously monitored, regardless of how CMMC compliance is currently assessed.
3. DFARS 252.204-7012 Compliance
DFARS requires aerospace manufacturers to report cyber incidents to DoD within 72 hours, preserve and protect compromised data, provide forensic access to DoD investigators, and flow down requirements to subcontractors. This is a contractual requirement, not optional, and it was not affected by Revision 3.
4. ITAR Compliance for Technical Data
If you handle technical data on defense articles, ITAR applies. You must restrict access to U.S. persons only, use ITAR-compliant cloud environments (typically GCC High), document data handling procedures, and prevent foreign national access, including remote workers. ITAR violations carry significant penalties per occurrence.
5. Continuous Monitoring With SIEM and MDR
Point-in-time security is not acceptable under NIST 800-171. Aerospace manufacturers need SIEM for log aggregation and correlation, MDR for 24/7 threat hunting, a SOC with live analysts responding to alerts, and documented incident response with tested playbooks. This continuous monitoring requirement is explicit in NIST 800-171 and is unaffected by the pause in third-party assessment.
Why Aerospace Manufacturers Get This Wrong
Mistake 1: Treating CMMC as a one-time project, or assuming the move to self-assessment means the work can stop. Continuous monitoring and annual evidence collection are mandatory regardless of how compliance is assessed.
Mistake 2: Relying on Microsoft 365 Commercial for CUI. CUI typically requires GCC High or a properly configured enclave. Commercial tenants fail audits.
Mistake 3: Ignoring subcontractor flow-down. If your subcontractor handles CUI, they need the same controls. Their gap becomes your gap.
Mistake 4: Underbudgeting. GCC High migration, CUI enclave design, and 24/7 monitoring are often left out of the first budget, and they are usually the largest pieces of the work.
Illustrative Scenario. Consider a 120-employee aerospace component supplier in the Pacific Northwest holding several million dollars in annual DoD subcontracts through a Tier 1 prime. A gap assessment identified Microsoft 365 Commercial in use instead of GCC High, no SIEM or 24/7 monitoring, CUI mixed with general business data, no documented incident response plan, and system access held by personnel who required additional screening under ITAR.
The remediation roadmap ran across four phases: GCC High migration and CUI enclave deployment, SIEM and MDR rollout with SOC integration, ITAR access controls and documentation, and pre-assessment preparation. Delivered through compliance managed IT, the readiness work and ongoing maintenance were covered by one rate of $275 to $350 per user per month with no separate project fee, roughly $396,000 to $504,000 in the first year for 120 users, against several million dollars in protected annual contract revenue. Assessment fees are separate. This is a representative example, not a specific client engagement.
The math is straightforward. Compliance protects revenue.
What This Means for Your Aerospace Business
- Contract eligibility: falling behind on core controls puts new DoD work at risk regardless of how CMMC compliance is currently assessed.
- Prime relationships: primes are increasingly building their own supplier cybersecurity expectations into contracts, independent of the federal assessment timeline.
- Insurance costs: cyber insurance increasingly requires proof of security controls.
- Competitive advantage: suppliers with documented, audit-ready controls win bids faster.
- Operational risk: aerospace intellectual property remains a top nation-state target, whoever does the assessing.
Cybersecurity is not an IT expense. It's a revenue protection strategy.
How to Meet 2026 Requirements: A 5-Step Framework
- Assess. Conduct a CMMC and NIST 800-171 gap analysis against all 110 controls.
- Scope. Identify where CUI lives and isolate it in a compliant enclave.
- Implement. Deploy SIEM, MDR, MFA, encryption, and access controls.
- Document. Build your SSP, POA&M, incident response plan, and evidence packages.
- Prepare for assessment. Get assessment-ready now so you're positioned the moment third-party assessment returns.
Most aerospace manufacturers need 6 to 18 months to complete this cycle, depending on where they start.
Bottom Line
Aerospace cybersecurity in 2026 remains a contract requirement, not a recommendation, even with third-party CMMC assessment currently paused. NIST 800-171, DFARS 252.204-7012, and ITAR are all still fully in force. The deadline moved; the obligation did not. Manufacturers that keep building toward full compliance now will be ready whenever third-party assessment returns. Those that stand down risk falling behind competitors who kept going.
Ready to meet 2026 requirements? Start with a CMMC and NIST 800-171 gap assessment built specifically for aerospace manufacturers.
Related Resources
Frequently Asked Questions
Is CMMC Level 2 third-party assessment still required for aerospace manufacturers?
No, not currently. Under DARS Class Deviation 2026-O0025 Revision 3, issued September 3, 2026, CMMC Level 2 can be satisfied by self-assessment, and no date has been set for third-party C3PAO assessment to return to DoD solicitations. Self-assessment against the 110 NIST 800-171 controls, SPRS reporting, and annual affirmations remain mandatory.
Does ITAR still apply while third-party CMMC assessment is paused?
Yes. ITAR is a separate regulatory framework governing technical data on defense articles and was not affected by Revision 3 or the pause in third-party CMMC assessment.
Can aerospace manufacturers use Microsoft 365 Commercial for CUI?
No. CUI typically requires Microsoft 365 GCC High or an equivalent properly configured compliant enclave. Commercial tenants routinely fail audits on this point.
How long does it take to meet 2026 aerospace cybersecurity requirements from a standing start?
Most aerospace manufacturers need 6 to 18 months to complete gap assessment, remediation, documentation, and pre-assessment preparation, depending on where they start.