Check: APSC-DV-003190
Application Security and Development STIG:
APSC-DV-003190
(in versions v5 r3 through v4 r2)
Title
Flaws found during a code review must be tracked in a defect tracking system. (Cat II impact)
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.
Additional Identifiers
Rule ID: SV-222650r918120_rule
Vulnerability ID: V-222650
Group Title: SRG-APP-000516
Expert Comments
CCIs
| Number | Definition |
|---|---|
| CCI-000366 |
The organization implements the security configuration settings. |
| CCI-003161 |
The organization requires the developer of the information system, system component, or information system service to track security flaws within the system, component, or service. |
| CCI-003197 |
The organization requires the developer of the information system, system component, or information system service to document the results of the dynamic code analysis. |