The C++ rules and recommendations in this wiki are a work in progress and reflect the current thinking of the secure coding community. Because this is a development website, many pages are incomplete or contain errors. As rules and recommendations mature, they are published in report or book form as official releases. These releases are issued as dictated by the needs and interests of the secure software development community.
Secure Coding in C and C++ identifies the root causes of today's most widespread software vulnerabilities, shows how they can be exploited, reviews the potential consequences, and presents secure alternatives.
want to request privileges to participate in standards development
We acknowledge the contributions of the followingfolks, and we look forward to seeing your name here as well.
Rules vs. Recomendations
This coding standard consists of rules and recommendations, collectively referred to as guidelines. Rules are meant to provide normative requirements for code, whereas recommendations are meant to provide guidance that, when followed, should improve the safety, reliability, and security of software systems. Learn more about the differences.
Linking to Our Pages
Link to guidelines using the Tiny Link under Tools→Link to this Page... (This URL will not change if the name of the guideline changes.)
Information for Editors
To eliminate a section from the lists above, label it section and void.
To have a section listed as a recommendation, label it section and recommendation.
To have a section listed as a rule, label it section and rule.