Weaknesses Addressed by the CERT C Secure Coding Standard
View ID: 734 (View: Graph)
Status: Incomplete
View Data
View Objective
CWE entries in this view (graph) are fully or partially eliminated by
following the CERT C Secure Coding Standard. Since not all rules map to specific
weaknesses, this view is incomplete.
View Metrics
CWEs in this view
Total CWEs
Total
103
out of
791
Views
0
out of
22
Categories
15
out of
106
Weaknesses
86
out of
651
Compound_Elements
2
out of
12
View Audience
Stakeholder
Description
Developers
By following the CERT C Secure Coding Standard, developers will be
able to fully or partially prevent the weaknesses that are identified in
this view. In addition, developers can use a CWE coverage graph to
determine which weaknesses are not directly addressed by the standard,
which will help identify and resolve remaining gaps in training, tool
acquisition, or other approaches for reducing weaknesses.
Software Customers
If a software developer claims to be following the CERT C Secure
Coding standard, then customers can search for the weaknesses in this
view in order to formulate independent evidence of that claim.
Educators
Educators can use this view in multiple ways. For example, if there is
a focus on teaching weaknesses, the educator could link them to the
relevant Secure Coding Standard.
Weaknesses Addressed by the CERT C Secure Coding Standard (primary)734
Relationship Notes
The relationships in this view were determined based on specific
statements within the rules from the standard. Not all rules have direct
relationships to individual weaknesses, although they likely have chaining
relationships in specific circumstances.
References
"The CERT C Secure Coding Standard". Addison-Wesley Professional. 2008-10-14.
View Data 
