Page History

...

Rules have a consistent structure. Each rule has a unique identifier, which is included in the title. The title of the rules and the introductory paragraphs define the conformance requirements. This is typically followed by one or more sets of noncompliant code examples and corresponding compliant solutions. Each rule also includes a risk assessment and bibliographical references specific to that rule. When applicable, rules also list related vulnerabilities and related guidelines from the following sources:

• Wiki Markup[The CERT C Secure Coding Standard|seccode: CERT C Secure Coding Standard] \[ [Seacord 2008|AA. References#Seacord 2008]\]unmigrated-wiki-markup[
• The CERT C+\+ Secure Coding Standard|cplusplus:CERT C++ Secure Coding Standard] \[ [CERT 2011|AA. References#CERT 2011]\]
• Wiki MarkupISO/IEC TR 24772. Information Technology — — Programming Languages — — Guidance to Avoiding Vulnerabilities in Programming Languages through Language Selection and Use \ [[ISO/IEC TR 24772:2010|AA. References#ISO/IEC TR 24772-2010]\]unmigrated-wiki-markup
• [MITRE CWE|http://cwe.mitre.org/] \[ [MITRE 2011|AA. References#MITRE 2011]\]
• Wiki MarkupSecure Coding Guidelines for the Java Programming Language, version 3.0 \ [[SCG 2009|AA. References#SCG 2009]\]
• The Elements of Java Style [Rogue 2000]