CWE-1008
View ProhibitedArchitectural Concepts
Status: Obsolete
This view organizes weaknesses according to common architectural security tactics, as proposed in 2017 as part of an academic "Common Architectural Weakness Enumeration (CAWE)" project. The view was intended to assist architects in identifying potential mistakes that can be made when designing software.
View entries organize the catalogue and should not be used to map the root cause of a vulnerability.
Mapping guidance
This entry is a View. Views are not weaknesses and therefore inappropriate to describe the root causes of vulnerabilities.
Use this View or other Views to search and navigate for the appropriate weakness.
Relationships and members
Notes
Other
The top level categories in this view represent the individual tactics that are part of a secure-by-design approach to software development. The weaknesses that are members of each category contain information about how each is introduced relative to the software's architecture.
Three different modes of introduction are used:
Omission - caused by missing a security tactic when it is necessary.
Commission - refers to incorrect choice of tactics which could result in undesirable consequences.
Realization - appropriate security tactics are adopted but are incorrectly implemented.
Maintenance · CWE 5.0 · 2026-10-28
This view was originally created in 2017, but the CAWE project ended, and this view was not actively maintained afterward.
Content history
Provided the catalog, Common Architectural Weakness Enumeration (CAWE), and research papers for this view.
updated Description, Other_Notes, View_Audience
updated Maintenance_Notes, View_Audience
updated Mapping_Notes
updated Description, References, View_Audience
0 vulnerabilities reference this CWE, most recent first.
No vulnerabilities reference this CWE.
No mitigation information available for this CWE.
No CAPEC attack patterns related to this CWE.