+V-AA-B Stream B: Architecture Mitigation
---+V-AA-1-B Evaluate architecture for typical threats
---+V-AA-2-B Structurally verify the architecture for identified threats
---+V-AA-3-B Feed review results back to improve reference architectures

V-AA-B Stream B: Architecture Mitigation

Architecture mitigation focuses on ensuring that all threats identified during Threat Assessment are adequately mitigated, and existing reference architectures updated to address any unhandled threats.

1. Panoramica

V-AA-1-B Evaluate architecture for typical threats

Maturity level 1 objective of the practice: Review the architecture to ensure baseline mitigations are in place for typical risks.

Benefit: Assurance that the architecture protects against typical security threats.

Short description: Ad-hoc review of the architecture for unmitigated security threats.

Review the architecture for typical security threats. Security-savvy technical staff conduct this analysis with input from architects, developers, managers, and business owners as needed, to ensure the architecture addresses all common threats which development teams lacking specialized security expertise may have overlooked.

Typical threats in an architecture can relate to incorrect assumptions in, or overly reliance on, the provisioning of security mechanisms such as authentication, authorization, user and rights management, secure communication, data protection, key management and log management. Threats, on the other hand, can also relate to known limitations of, or issues in, technological components or frameworks that are part of the solution and for which insufficient mitigation has been put in place.
V-AA-2-B Structurally verify the architecture for identified threats

Maturity level 2 objective of the practice: Review the complete provision of security mechanisms in the architecture.

Benefit: All identified threats to the application are adequately handled.

Short description: Analyze the architecture for known threats.

Systematically review each threat identified during the Threat Assessment activities and examine how the architecture mitigates them. Use a standardized process for analyzing system architectures and the flow of data within them. This is typically linked to the threat model used (e.g. STRIDE) in order to identify the relevant security objectives which address each type of threat. For each threat, identify the design-level features of the architecture which counter it and assess their effectiveness in doing so.

Where available, review architectural decision records to understand the architectural constraints and tradeoffs made during design. Take their impact into consideration along with any security assumptions on which the safe operation of the system relies and re-evaluate them.

Enrich your previously created threat model such that each threat and its estimated impact are linked to the corresponding counter measure. Produce a mapping document, or dashboard in a specialized tool, to make the information available and visible to the relevant stakeholders.
V-AA-3-B Feed review results back to improve reference architectures

Maturity level 3 objective of the practice: Review the architecture effectiveness and feedback results to improve the security of the architecture.

Benefit: Continuous improvement of enterprise architecture based on architecture reviews

Short description: Feed the architecture review results back into the enterprise architecture, organization design principles and patterns, security solutions and reference architectures.

As an organization, you can further improve your software security posture by understanding which threats remain unaddressed in the software architectures and adapting your tactics to prevent this. Formalize a process to use recurring architecture findings as a trigger to identify the causes of gaps in the security assessment and deal with them. Feed findings back to the Design phase by creating, or updating relevant reference architectures, existing security solutions, or organization design principles and patterns.

1.1 Riferimenti

1.2 Requisiti identificati

1.3 Regolamentazioni correlate

2. Requisiti identificati

Requisiti

3. Regolamentazioni correlate

Regolamentazioni
  • 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.