+V15.1 Secure Coding and Architecture Documentation
---+V15.1.1 Verify that application documentation defines risk based remediation time frames for 3rd party …
---+V15.1.2 Verify that an inventory catalog, such as software bill of materials (SBOM), is maintained of all …
---+V15.1.3 Verify that the application documentation identifies functionality which is time-consuming or …
---+V15.1.4 Verify that application documentation highlights third-party libraries which are considered to be …
---+V15.1.5 Verify that application documentation highlights parts of the application where "dangerous …

V15.1 Secure Coding and Architecture Documentation

Many requirements for establishing a secure and defensible architecture depend on clear documentation of decisions made regarding the implementation of specific security controls and the components used within the application.

This section outlines the documentation requirements, including identifying components considered to contain "dangerous functionality" or to be "risky components."

A component with "dangerous functionality" may be an internally developed or third-party component that performs operations such as deserialization of untrusted data, raw file or binary data parsing, dynamic code execution, or direct memory manipulation. Vulnerabilities in these types of operations pose a high risk of compromising the application and potentially exposing its underlying infrastructure.

A "risky component" is a 3rd party library (i.e., not internally developed) with missing or poorly implemented security controls around its development processes or functionality. Examples include components that are poorly maintained, unsupported, at the end-of-life stage, or have a history of significant vulnerabilities.

This section also emphasizes the importance of defining appropriate timeframes for addressing vulnerabilities in third-party components.

1. Prezentare generală

Titlu Standard
V15.1.1 Verify that application documentation defines risk based remediation time frames for 3rd party …

Verify that application documentation defines risk based remediation time frames for 3rd party component versions with vulnerabilities and for updating libraries in general, to minimize the risk from these components.

V15.1.2 Verify that an inventory catalog, such as software bill of materials (SBOM), is maintained of all …

Verify that an inventory catalog, such as software bill of materials (SBOM), is maintained of all third-party libraries in use, including verifying that components come from pre-defined, trusted, and continually maintained repositories.

V15.1.3 Verify that the application documentation identifies functionality which is time-consuming or …

Verify that the application documentation identifies functionality which is time-consuming or resource-demanding. This must include how to prevent a loss of availability due to overusing this functionality and how to avoid a situation where building a response takes longer than the consumer's timeout. Potential defenses may include asynchronous processing, using queues, and limiting parallel processes per user and per application.

V15.1.4 Verify that application documentation highlights third-party libraries which are considered to be …

Verify that application documentation highlights third-party libraries which are considered to be "risky components".

V15.1.5 Verify that application documentation highlights parts of the application where "dangerous …

Verify that application documentation highlights parts of the application where "dangerous functionality" is being used.

1.1 Referințe

1.2 Cerințe identificate

1.3 Reglementări asociate

2. Cerințe identificate

Cerințe
Sursă Cerință

3. Reglementări asociate

Reglementări
Sursă Reglementare
  • OWASP -

    EN: Publications of the OWASP Foundation, https://owasp.org/. OWASP® is a registered trademark of the OWASP Foundation, Inc.; GRCA is not affiliated with, nor endorsed by, the OWASP Foundation. Only the versions published by OWASP are authoritative.

    DE: Veröffentlichungen der OWASP Foundation, https://owasp.org/. OWASP® ist eine eingetragene Marke der OWASP Foundation, Inc.; GRCA steht in keiner Verbindung zur OWASP Foundation und wird von ihr nicht unterstützt. Maßgeblich sind allein die von OWASP veröffentlichten Fassungen.