Flaws found during a code review must be tracked in a defect tracking system.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-222650 | APSC-DV-003190 | SV-222650r508029_rule | Medium |
| Description |
|---|
| 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. |
| STIG | Date |
|---|---|
| Application Security and Development Security Technical Implementation Guide | 2020-09-30 |
Details
| Check Text ( C-24320r493858_chk ) |
|---|
| 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 (F-24309r493859_fix) |
|---|
| Track software defects in a defect tracking system. |