Software systems can be validated as conforming to the CERT Perl Secure Coding Standard. Source code analysis tools, including compilers and static analysis tools, can be certified as able to validate source code as conforming to this standard.
...
The easiest way to validate code as compliant with the CERT Perl Secure Coding standard Standard is to use a certified source code analysis tool.
...
Rules and recommendations in this standard are classified into three levels. (See Risk Assessment.) Emphasis should be placed on conformance Level 1 (L1) rules. Software systems that have been validated as complying with all Level 1 rules are considered to be L1 Conformingconforming. Software systems can be assessed as L1, L2, or fully conforming depending on the set of rules to which the system has been validated.
Rules versus Recommendations
Conformance To claim compliance with this standard, conformance to secure coding rules must be demonstrated to claim compliance with this standard unless an exceptional condition exists. If an exceptional condition is claimed, the exception must correspond to a predefined exceptional condition and the application of this exception must be documented in the source code.
...
Deviations may occur for a specific instance, typically in response to circumstances that arise
during the development process or for a systematic use of a particular construct in a particular circumstance. Systematic deviations are usually agreed upon at the start of a project.
...
To claim compliance with this standard, software developers must be able to produce on request documentation as to which systematic and specific deviations have been permitted during development. 00. Introduction