Most comprehensive MISRA coding standards compliance

With increased connectivity of applications and devices, OEMS in the automotive, aerospace, defense, medical, industrial automation, energy, and rail transportation sectors are demanding new assurance that software has been developed to the highest security standards.

14 new security guidelines

MISRA C guidelines define a subset of the C language suitable for developing any application with high-integrity or high-reliability requirements. Originally designed to promote the use of the C language in safety-critical embedded applications within the automotive industry, MISRA guidelines have now gained widespread acceptance for safety-, life-, and mission-critical applications in a wide range of industries.

As the connectivity of safety-critical and IoT systems elevates the security risk of embedded devices, MISRA today published new documents to address these risks. MISRA C:2012 Addendum 2 maps the coverage of MISRA C:2012 against ISO/IEC TS 17961:2013 “C Secure” rules and justifies the viewpoint that MISRA C is equally applicable in a security-related environment as it is in a safety-related one. MISRA C:2012 Amendment 1 defines fourteen additional MISRA security rules that will help developers avoid coding practices that can introduce security vulnerabilities and to write code that is more understandable and maintainable.

Comprehensive compliance

LDRA’s MISRA compliance checking tools give developers immediate and comprehensive coverage of both documents. This not only offers the most comprehensive adoption of the MISRA C:2012 standard, but also—thanks to integration within the LDRA tool suite—enables customers to check against other security or safety standards, such as CWE, Cert, and industry-specific standards. Developers also gain advantages by automating their coding standards compliance within their overall software analysis and testing process.

As developers add features to their products, constrained budgets and schedules can easily make software the weak link for malicious entities to gain access to sensitive data and take over systems. By following the additional, just-announced MISRA guidelines, developers can more thoroughly analyse their code and can assure regulatory authorities that they followed safe and secure coding practices. For customers in especially critical industries such as automotive, security threats have led OEMs to establish stringent requirements for developers to prove that their software meets the highest standards for security as well as safety.