+RV.3 Analyze Vulnerabilities to Identify Their Root Causes
---+RV.3.1 Analyze identified vulnerabilities to determine their root causes.
---+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.3 Review the software for similar vulnerabilities to eradicate a class of vulnerabilities, and proactively fix them rather than waiting for external …
---+RV.3.4 Review the SDLC process, and update it if appropriate to prevent (or reduce the likelihood of) the root cause recurring in updates to the software or …

RV.3 Analyze Vulnerabilities to Identify Their Root Causes

Statement

Help reduce the frequency of vulnerabilities in the future.

1. Yleiskatsaus

Otsikko Standardi
RV.3.1 Analyze identified vulnerabilities to determine their root causes.

Statement

Analyze identified vulnerabilities to determine their root causes.

Example 1:

Record the root cause of discovered issues.

Example 2:

Record lessons learned through root cause analysis in a wiki that developers can access and search.

RV.3.2 Analyze the root causes over time to identify patterns, such as a particular secure coding practice not being followed consistently.

Statement

Analyze 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.

RV.3.3 Review the software for similar vulnerabilities to eradicate a class of vulnerabilities, and proactively fix them rather than waiting for external …

Statement

Review the software for similar vulnerabilities to eradicate a class of vulnerabilities, and proactively fix them rather than waiting for external reports.

Example 1:

See PW.7 and PW.8.

RV.3.4 Review the SDLC process, and update it if appropriate to prevent (or reduce the likelihood of) the root cause recurring in updates to the software or …

Statement

Review the SDLC process, and update it if appropriate to prevent (or reduce the likelihood of) the root cause recurring in updates to the software or in new software that is created.

Example 1:

Record lessons learned through root cause analysis in a wiki that developers can access and search.

Example 2:

Plan and implement changes to the appropriate SDLC practices.

1.1 Viittaukset

1.2 Tunnistetut vaatimukset

1.3 Liittyvät säädökset

2. Tunnistetut vaatimukset

Vaatimukset
Lähde Vaatimus

3. Liittyvät säädökset

Säädökset
Lähde Sääntely

Linkitetyt tehtävät

  • NIST -

    EN: Publications of the National Institute of Standards and Technology (NIST), U.S. Department of Commerce, https://www.nist.gov/, from their electronic versions (OSCAL; SP 800-63-4 from its HTML version, https://pages.nist.gov/800-63-4/). Works of NIST employees are not subject to copyright protection in the United States (17 U.S.C. § 105); the OSCAL content is dedicated to the public domain worldwide (CC0 1.0); outside the United States NIST grants the right to reprint its technical series publications in all formats (NIST copyright statement). Republished courtesy of the National Institute of Standards and Technology; each document names its citation. Divided into sections and converted into the GRCA format, the wording unchanged. Only the versions published by NIST are authoritative.

    DE: Veröffentlichungen des National Institute of Standards and Technology (NIST), U.S. Department of Commerce, https://www.nist.gov/, aus ihren elektronischen Fassungen (OSCAL; SP 800-63-4 aus ihrer HTML-Fassung, https://pages.nist.gov/800-63-4/). Werke von NIST-Beschäftigten sind in den USA urheberrechtlich nicht geschützt (17 U.S.C. § 105); die OSCAL-Inhalte sind weltweit gemeinfrei gestellt (CC0 1.0); außerhalb der USA räumt das NIST das Recht ein, seine Technical-Series-Publikationen in allen Formaten neu zu veröffentlichen (Copyright-Hinweis des NIST). „Republished courtesy of the National Institute of Standards and Technology“; jedes Dokument nennt seine Zitierangabe. In Abschnitte aufgeteilt und in das GRCA-Format umgewandelt, der Wortlaut unverändert. Maßgeblich sind allein die vom NIST veröffentlichten Fassungen.