Skip to main content
Information Security

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • I'm not aware of a similar set of top-10 guidelines for hardware devices. Perhaps you might care to take a stab at it, by answering your own question with a candidate list of top-10 concerns? Commented Nov 18, 2012 at 23:03
  • Might do later. I can only think of 3 or 4 that really apply directly to hardware implementations, but I'll put some research in and try to dig up more. Commented Nov 19, 2012 at 8:31
  • Buffer overflows protection, validating inputs, etc. All secure coding policies should apply to embedded systems. Commented Nov 19, 2012 at 16:29
  • @D.W. I've added an answer based on some research. Commented Nov 20, 2012 at 9:58
  • 1
    “Embedded systems or hardware devices” covers a huge swathe of different expectations and environments, from elevator controllers to smartphones, from network routers to credit cards… You should pick one (the same way OWASP concentrates on client/server web applications). Also, are you targeting the device as a whole, or the hardware design and construction (I guess the device, from your answer)? Commented Nov 20, 2012 at 17:59