This resource is no longer available
3 Must-Follow Guidelines for Mitigating M2M Software Security Risks
Embedded systems are omnipresent, residing in everything from dishwashers to automobiles to medical devices. As they have evolved and become interconnected, the security risks to those systems have increased substantially.
Whether from malicious hacking attempts, faulty code or the physical presence of an adversary, manufacturers of products that allow for Machine-to-Machine (M2M) communications must ensure the safety and security of these devices.
This paper outlines three important 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 at the development stage by finding and fixing code vulnerabilities with static analysis and code review
- Protect systems from unauthorized changes and malware with application whitelisting