+RV.3.2 Analyze the root causes over time to identify patterns, such as a particular secure coding practice not being followed consistently.
|
RV.3.2 Analyze the root causes over time to identify patterns, such as a particular secure coding practice not being followed consistently.
StatementAnalyze the root causes over time to identify patterns, such as a particular secure coding practice not being followed consistently. Example 1:Record lessons learned through root cause analysis in a wiki that developers can access and search. Example 2:Add mechanisms to the toolchain to automatically detect future instances of the root cause. Example 3:Update manual processes to detect future instances of the root cause.
1. Vue d’ensemble
1.1 Références
1.2 Exigences identifiées
1.3 Réglementations associées
2. Exigences identifiées
Exigences
| Source |
Exigence |
3. Réglementations associées
Réglementations
| Source |
Réglementation |
Tickets liés
|