The IEEE Center for Secure Design intends to shift some of the focus in security from finding bugs to identifying common design flaws — all in the hope that software architects can learn from others’ mistakes. To read more about what the Center for Secure Design is, read the facts.
Center for Secure Design participants — from industry, research, and government — identified the top flaws found in their own internal design reviews, or that were available from external data. Many of the flaws that made the list have been well known for decades, but continue to persist.
Most software built and released typically comes with a set of defects — implementation bugs and design flaws. While there has been a larger focus on finding bugs rather than on identifying flaws, this document intends to shift some of the focus in security from finding bugs to identifying design flaws in the hope that software architects can learn from others’ mistakes.
In the Center for Secure Design‘s latest document, we look at how the Top 10 Software Security Design Flaws can be approached within a specific, albeit fictitious, wearable fitness tracking system: the WearFit. We base our analysis as much on real-world systems as possible, providing a broad analysis of threats facing users of wearable fitness-tracking devices.
Avoiding the Top 10 Software Security Design Flaws is released under the Creative Commons Attribution-ShareAlike 3.0 license. Read more here.
Stay on top of the Center’s activities by following @ieeecsd on Twitter.