View-800: Weaknesses in the 2010 CWE/SANS Top 25 Most Dangerous Programming Errors
By following the Top 25, developers will be able to significantly reduce the number of weaknesses that occur in their software.
If a software developer claims to be following the Top 25, then customers can use the weaknesses in this view in order to formulate independent evidence of that claim.
Educators can use this view in multiple ways. For example, if there is a focus on teaching weaknesses, the educator could focus on the Top 25.
|CWE-808||2010 Top 25 - Weaknesses On the Cusp|
|CWE-803||2010 Top 25 - Porous Defenses|
|CWE-802||2010 Top 25 - Risky Resource Management|
|CWE-801||2010 Top 25 - Insecure Interaction Between Components|