Many embedded systems require developers to prioritise performance, which can in some instances result in security being considered to be a lower priority than it should be. As most of these systems are conceived and designed for a specific purpose, unconventional techniques are often employed by developers which introduce new and sometimes unknown classes of threats, not generally present in non-embedded devices.

IRM's Embedded Systems testing typically includes the assessment of software components such as:

• Operating system core
• Memory management subsystem
• Third party APIs
• Bespoke communications protocols

Three distinct phases allow for a comprehensive review of your embedded system by performing test case generation, static source code analysis and black box testing techniques.