...
Rules and recommendations included in this standard CERT C Programming Language Secure Coding Standard are designed to be operating system and platform independent. However, the best available solutions to these secure coding problems are often platform specific. In most cases, we have attempted to this standard provide appropriate compliant solutions for POSIX-compliant and Windows operating systems. In many cases, compliant solutions have also been provided for specific platforms such as Linux or OpenBSD. Occasionally, we also point out implementation-specific behaviors when these behaviors are of interest.
Rationale
| Wiki Markup |
|---|
A secure coding standard for the C programming language can create the highest value for the longest period of time by focusing on C99 and the relevant post-C99 technical reports. In addition, because considerably more |
money and effort is devoted to develop new code than maintaining existing code, the highest return on investment comes from influencing programmers who are developing new code \[[Seacord 03|AA. C References#Seacord 03]\]. Maintaining existing code is still an important concern, however. |
The C standard documents existing practice where possible. That is, most features must be tested in an implementation before being included in the standard. The CERT C secure coding standard has a different purpose. When existing practice serves this purpose, that is fine, but the goal is to create a new set of best practices, and that includes introducing some concepts that are not yet widely known. To put it a different way, the CERT C secure coding guidelines are attempting to drive change rather than just document it.
...