| This rule was developed in part by <participant names here> at the October 20-22, 2017 OurCS Workshop (http://www.cs.cmu.edu/ourcs/register.html). For more information about this statement, see the About the OurCS Workshop page. |
|---|
| This guideline is under construction. |
In this space, describe the overall rule.
This noncompliant code example shows an application that ...
TBD |
In this compliant solution ...:
TBD |
...You may enter more pairs of noncompliant code examples and compliant solutions, to exemplify different types. Once done with initial code examples, delete this section of purple-font text.
Summary of risk assessment.
Rule | Severity | Likelihood | Remediation Cost | Priority | Level |
|---|---|---|---|---|---|
TBD |
|
|
|
|
|
Tool | Version | Checker | Description |
|---|---|---|---|
| TBD |
|
TBD: Hyperlink text below "the CERT website", with link: https://www.kb.cert.org/vulnotes/bymetric?searchview&query=FIELD+KEYWORDS+contains+<RULE_ID> where <RULE_ID> has the 3-letter rule type followed by "-" and this guideline number. Then, remove this purple-font paragraph.
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
Fill in the table below with at least one entry, and remove this purple-font line.
| TBD name of guideline taxonomy (e.g., MITRE CWE) | TBD the ID/name of a single entry in that taxonomy |
| [TBD] |