How and Why is RunSafe Working to Achieve Safety of Flight Certification for Its Memory Protection Tools

In this video, we discuss RunSafe's efforts to achieve safety of flight certification with the support of AFuzion. We break down the two components of RunSafe Code: the ground component, which requires qualification under DO-330, and the in-flight component, which follows DO-178 certification guidelines. By meeting these stringent standards, RunSafe ensures that its Code is suitable for critical flight systems, providing the highest levels of safety and reliability.

RunSafe’s Path to Ensuring Flight Safety Certification

In today’s RunSafe Security Minute, we’re exploring how RunSafe is working to achieve safety of flight certification in aviation safety. With the expertise of AFuzion, a leader in avionics software development, we are making significant strides toward this goal.

RunSafe Code is divided into two main components, each serving a different purpose. The first component functions on the ground and requires qualification rather than certification. This process is guided by DO-330, which involves tool qualification essential for certifying airborne systems. We aim to achieve Tool Qualification Level 1, the highest level, allowing our Code to be used in the development of critical flight software.

The second component operates during flight and must adhere to the certification guidelines outlined in DO-178. As a module, RunSafe provides all necessary documentation for DO-178 certification at Design Assurance Level A (DAL A) to the airborne system’s owner. This ensures that RunSafe Code can be integrated into any system requiring a safety of flight, ensuring top-tier aviation safety.

CRA Readiness: Which Vulnerabilities Actually Put Your Product at Risk?

Oct 14, 2026

Not Every Vulnerability Poses the Same Risk Finding a CVE is only the first step. For embedded product teams, the real challenge is determining which vulnerabilities actually affect their products, whether they can be exploited, and what action to take. In Part 3 of...

CRA Readiness: Build an SBOM You Can Act On

Sep 14, 2026

Under the Cyber Resilience Act, having an SBOM is only the beginning. Manufacturers need to know exactly what software is in each product release and be able to quickly determine which products are affected when a new vulnerability emerges. For embedded software, that...

Operational Software Assurance

Sep 14, 2026

Security Cannot Stop When Software Ships Critical software can remain deployed for years or even decades. During that time, new vulnerabilities emerge, threats evolve, and AI is accelerating both vulnerability discovery and exploit development. But patching, testing,...