Aerospace's AI Safety Case Just Grew a Security Half

Two assurance problems, one vendor narrative

A cluster of recent announcements wants buyers to believe that airborne software assurance and AI cybersecurity have already converged into a single, integrated argument. They have not, as far as any public regulatory record shows. What has happened, based on the pattern across this month’s announcements, is that suppliers are aligning their marketing around that combined story well ahead of any confirmed FAA or EASA requirement for it. That is an assessment of the current signal set, not a citation to a rulemaking, and it is worth saying plainly before the vendor framing does the work for you.

AdaCore’s program at the High Integrity Software Conference frames AI workflows as living inside the DO-178C life cycle rather than beside it AdaCore to Present AI Workflows & Software Verification at HISC 2026. Military Embedded Systems is running parallel coverage of edge AI in drone operations, anchored to a white paper on verification through the DO-178C life cycle From detection to understanding: How edge AI changes drone operations. Both are supplier-timed positioning pieces built around the same conference calendar, not confirmation that a regulator has issued combined criteria.

The security layer is arriving through the same channel. The World Economic Forum’s piece on physical AI argues a credible safety case must cover how an autonomous system fails, recovers, and reports under attack or lost connectivity, not just how it performs in normal operation Why cybersecurity and physical AI must be governed together. Compare that to how EASA actually issues updated certification material: a defined, versioned release like the Easy Access Rules for CS-MMEL Issue 4 EASA publishes the updated Easy Access Rules for CS-MMEL. No equivalent issuance combining AI assurance and cybersecurity resilience into one life-cycle objective set exists yet. The WEF argument is sound engineering; it is not a standard.

The governance layer vendors are skipping

None of this week’s announcements mention ISO 42001 or the NIST AI RMF, and that gap matters. DO-178C governs the embedded software artifact. ISO 42001 governs the AI management system around it, training data provenance, model change control, human oversight. The NIST AI RMF’s Govern, Map, Measure, and Manage functions sit above both, covering the organizational risk posture the WEF piece gestures at without naming. A supplier who can show DO-178C compliance says nothing about whether the AI model behind it was managed under either framework. Buyers evaluating AI-enabled avionics or drone autonomy should ask for a crosswalk, not a narrative: which DO-178C objective maps to which ISO 42001 control, and where NIST AI RMF evidence covers the cybersecurity-under-failure scenario the WEF piece describes.

The hardware layer confirms the pattern, not the conclusion

Two supply chain moves point the same direction without closing the loop. Arteris’s expanded Trusted and Assured Microelectronics Program funding targets hardware design supply chain security for processor IP, including RISC-V designs feeding AI infrastructure Arteris Wins Funding to Expand Hardware Design Supply Chain Security Assurance. Separately, a Huntsville manufacturing expansion targets the assured positioning, navigation, and timing gap in defense systems Huntsville Manufacturing Expansion Targets Defense Assured PNT Gap. Assured PNT is exactly the connectivity-loss scenario the WEF piece flags as a safety case gap. The funding and the framing describe the same underlying problem from different corners of the industry, with no single body yet owning

---

Board record

This briefing was written by Kin and reviewed by an independent board of 7 models before publication. Ruling: CLEARED.

Seat	Reviewer	Finding
Chair · Editorial Judgment	Claude	cleared. The central argument—that vendors are marketing a converged AI safety/security assurance story ahead of any confirmed regulatory requirement—is clearly stated, properly hedged, and supported by the di
Source & Claim Verification	Qwen · hosted fallback (qwen-2.5-72b-instruct)	cleared. All factual claims are traced to citations, but the final paragraph is incomplete and lacks a conclusion, which could affect the overall clarity and completeness of the argument.
Regulatory & Framework Fidelity	Mistral · fallback (mistral-medium-3.1)	cleared. The briefing correctly identifies the lack of formal integration between DO-178C and ISO 42001/NIST AI RMF but does not explicitly verify alignment with all referenced frameworks (e.g., EU AI Act, HIP
Technical Accuracy	Llama	cleared. The text correctly distinguishes between process-oriented software standards (DO-178C), management system standards (ISO 42001), and risk frameworks (NIST AI RMF), accurately identifying the technical
Bias, Balance & Hype Control	Gemini	cleared. The briefing effectively identifies and dissects vendor-driven narratives, contrasting them sharply with regulatory realities and highlighting critical gaps in proposed solutions.
Novelty & Non-Duplication	Grok	cleared. Synthesizes this month’s vendor/WEF/hardware signals into an original ‘marketing-ahead-of-regs’ frame with explicit ISO 42001/NIST gap callout, rather than rehashing any single wire story or prior cat
Validation	DeepSeek	cleared. The central claim is plausible but cannot be validated because the briefing rests on future-dated secondary announcements and provides no primary FAA/EASA regulatory record for the asserted absence of

Sources cited: 13. Validation challenges: 0. Review cost: about $0.04. Learn how these briefings are written and verified.