3 Must-Follow Guidelines for Mitigating M2M Software Security Risks
sponsored by Klocwork

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:

  1. Address security early and take defensive measures against security threats using threat modeling
  2. Build security in at the development stage by finding and fixing code vulnerabilities with static analysis and code review
  3. Protect systems from unauthorized changes and malware with application whitelisting
(THIS RESOURCE IS NO LONGER AVAILABLE.)
 
Available Resources from Klocwork
See what other users are reading via our Daily Top 50 Report
.

About TechTarget:

TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines

All Rights Reserved, Copyright 2000 - 2014, TechTarget | Read our Privacy Statement