As embedded systems have evolved and become interconnected, the risk to the security and functionality of those systems has increased substantially. Whether the risks are from malicious hacking attempts, faulty code, or the physical presence of an adversary, manufacturers of products that use Machine-to-Machine (M2M) communications must ensure the safety and security of those devices.
This whitepaper outlines three must-follow guidelines that embedded software teams should follow to help protect critical M2M systems against failure and malicious attack:
- Address security early and take defensive measures against security threats using threat modeling
- Build security in during development by finding and fixing code vulnerabilities with static analysis and manual code review
- Protect systems from unauthorized changes and malware with application whitelisting