Page History

Include Page

	seccode:Secure Coding Space Homepage Notices
	seccode:Secure Coding Space Homepage Notices

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.

The CERT C++ Coding Standard does not currently expose any recommendations; all C++ recommendations have been removed (moved to The Void section) due to quality concerns pending further review and development.

If you wish to be more involved and directly edit content on the site, you still need to request an account and edit privileges.

Front Matter

Content by Label

showLabels	false
max	99
spaces	@self
showSpace	false
sort	title
reverse	true
cql	label = "front-matter" and space = currentSpace()
labels	+intro

Rules

Content by Label

showLabels	false
max	99
spaces	@self
showSpace	false
sort	title
cql	label = "rule-list" and label != "void" and space = currentSpace()
labels	+rule-list,-void

Back Matter

Content by Label

showLabels	false
max	99
spaces	@self
showSpace	false
sort	title
cql	label = "bm" and label not in ("cwe-sans","void") and space = currentSpace()
labels	+bm -void -cwe-sans

Panel

borderColor	#B0B1BA
bgColor	#fafafa
titleColor	#ffffff
borderWidth	1
titleBGColor	#B0B1BA
borderStyle	solid
title	Secure C++ Coding Books and Downloads

Image Added The CERT C++ Coding Standard, 2016 Edition provides rules to help programmers ensure that their C++ code reduces security flaws by following secure coding best practices. It is downloadable as a PDF. (errata)

Image AddedThe CERT C++ Coding Standard references and relies on the CERT C Coding Standard. The CERT C Coding Standard, 2016 Edition provides rules to help programmers ensure that their code complies with the new C11 standard and earlier standards, including C99. It is downloadable as a PDF. (errata)

Image Added

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.

Panel

borderColor	#B0B1BA
bgColor	#fafafa
titleColor	#ffffff
borderWidth	1
titleBGColor	#B0B1BA
borderStyle	solid
title	Contact Us

Contact us if you

have questions about this wiki
have recommendations for standards in development
want to request privileges to participate in standards development

Panel

borderColor	#B0B1BA
bgColor	#fafafa
titleColor	#ffffff
borderWidth	1
titleBGColor	#B0B1BA
borderStyle	solid
title	Thank You!

We acknowledge the contributions of the following folks, and we look forward to seeing your name here as well.

Include Page

	seccode:Understand the Difference Between Rules and Recommendations
	seccode:Understand the Difference Between Rules and Recommendations

Info

title	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.)

Info

title	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.

C++ inherits a host of opportunities for type violations from C and adds a few of its own.
– Bjarne Stroustrup, "A rationale for semantically enhanced library languages"

01. Preprocessor (PRE)

02. Declarations (DCL)

03. Expressions (EXP)

04. Integers (INT)

05. Floating Point Arithmetic (FLP)

06. Arrays (ARR)

10. Environment (ENV)

07. Errors and Exceptions (ERR)

08. Memory Management (MEM)

09. Object Orientation (OBJ)

07. Characters and Strings (STR)

11. Signals (SIG)