Cybersecurity is becoming an evidence challenge
For safety-critical embedded systems, cybersecurity is about understanding the software at the heart of the product, managing its vulnerabilities and being able to demonstrate how security has been addressed throughout its development lifecycle.
The Real Time Operating System (RTOS) is an important part of that picture.
Ask Us a Question
For pricing, licensing, or any other sales or product related questions, please contact us.
What is RTOS security?
RTOS security refers to the processes, controls and engineering practices used to protect an RTOS and the applications that depend on it from cybersecurity threats.
Effective RTOS security considers how the software is designed, developed, tested and maintained through secure software development practices.
This can include:
- Threat analysis and risk assessment (TARA)
- Security requirements and risk analysis
- Secure design and coding
- Security testing and verification
- Security and software requirement traceability
- Vulnerability management
- Ongoing maintenance and support
The objective is to understand how security has been addressed and what evidence supports that claim.
Does an RTOS need to be connected to the internet to be a security risk?
No. An RTOS may have no direct network interface or cloud connection but it is still an important part of a product’s security architecture.
The RTOS provides the foundation on which the connected application software runs. It manages resources and system services that other software depends on. If that foundational software contains a vulnerability, the potential impact can extend into the wider system.
This is particularly important when the same RTOS is reused across multiple products. A vulnerability in a widely deployed component can affect every product that incorporates it.
Common RTOS security considerations
RTOS security needs to be considered in the context of the complete embedded system. Depending on the architecture and application, this can include:
Memory protection
Memory corruption and invalid memory access can create security vulnerabilities and affect system behaviour.
Privilege and resource access
Software should only have access to the system resources and services it requires.
Interfaces and communications
APIs, communication paths and external interfaces need to be considered as potential routes into the system.
Third-party software
Libraries, middleware and other software components can introduce vulnerabilities into the product supply chain.
Secure boot and software updates
Products may need mechanisms to establish trust during start-up and securely manage software throughout the product lifecycle.
These considerations cannot be separated completely from the wider application architecture. The RTOS is one layer of the overall security model.
Why security evidence matters
Security claims are difficult to assess without supporting evidence.
Customers, procurement teams and auditors may want to understand how an embedded software component was developed, tested and maintained. They may also need evidence that requirements have been addressed and that the software can be traced back to its verification activities.
This makes software assurance an important part of RTOS security.
For safety-critical embedded systems, evidence can include, but is not limited to, risk and hazard analysis, verification and validation results and maintenance processes.
The ability to provide this information gives engineering teams greater visibility into the software they are integrating.
RTOS security: frequently asked questions
How do you secure an RTOS?
RTOS security should be considered throughout the software lifecycle. Typical activities include security requirements, risk analysis, secure design, secure development, code review, security testing, verification and vulnerability management.
What is the relationship between RTOS security and the CRA?
The CRA introduces cybersecurity requirements for products with digital elements. Where an RTOS forms part of such a product, information about its development, vulnerabilities, security practices and maintenance may contribute to the manufacturer’s cybersecurity and compliance activities.
How are RTOS vulnerabilities managed throughout the software lifecycle?
Vulnerability management does not end when an RTOS is released. Suppliers should have processes for reporting, assessing, tracking and communicating security-relevant issues throughout the supported lifetime of the product.
Related blogs on embedded cybersecurity, the CRA and ISO 21434
Stay informed with expert insights on embedded system security, functional safety, and ISO 21434 alignment. These blog articles explore real-world challenges and solutions for securing safety-critical applications.
Outlines how SAFERTOS® and the Enhanced Security Module work together to protect against evolving cyber threats.
Explains how Threat Analysis and Risk Assessment (TARA) is applied in line with ISO 21434 to identify and mitigate risks in automotive software.
Free Demos & Manuals
Download fully functional, time-limited SAFERTOS® demos, plus manuals, datasheets, and more.
