Flaws found during a code review must be tracked in a defect tracking system.

From Application Security and Development Security Technical Implementation Guide

Associated with: CCI-003197

SV-85001r1_rule Flaws found during a code review must be tracked in a defect tracking system.

Vulnerability discussion

This requirement is meant to apply to developers or organizations that are doing application development work.If flaws are not tracked they may possibly be forgotten to be included in a release. Tracking flaws in the configuration management repository will help identify code elements to be changed, as well as the requested change.

Check content

This requirement is meant to apply to developers or organizations that are doing application development work. If application development is not being done or managed by the organization, this requirement is not applicable. Ask the application representative to demonstrate that the configuration management repository captures flaws in the code review process. The configuration management repository may consist of a separate application for capturing code defects. If there is no configuration management repository or the code review flaws are not captured in the configuration management repository, this is a finding.

Fix text

Track software defects in a defect tracking system.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.