iEstablishing a solid architecture is essential for a secure software system. The solid architecture provides structure from which all of the features can be provided. Without the solid architecture, pieces get tacked on here and there, and soon the system is full of vulnerabilities. Fortunately, some solid foundations are available that have proven themselves over time. These design patterns provide a guide on which architectural concerns and principles can be applied to form the basis for a secure system. Recognizing which pattern to apply to a specific development effort depends on understanding the nature of the system being developed, being familiar with the different design patterns, and being able to apply the pattern to the problem.

Assignment Requirements

Answer the following prompt$($s$)$:

Research and identify an instance of when poor architectural decisions resulted in$,$ or contributed to$,$ the introduction of vulnerabilities in a system that were subsequently exploited.

Fully address the prompt$($s$)$ in this case study and provide valid rationale for your choices by substantiating your thoughts with credible sources that are properly cited and referenced.

Flawed System Title:

Additional Identification Information $($versions$,$ etc. to make specific$)$:

Date$/$Year Created$/$Designed:

General Description of the Purpose, Scope, and Intended Function of the System $($one to two paragraphs$)$:

Description of the Design Flaw $($one to three paragraphs; include drawings as relevant$)$:

Date$/$Year of First Known Exploit $($if any, else zero$-$day release$)$:

Description of the Exploit $($one to three paragraphs; include drawings as relevant, and estimated cost$)$:

Analysis of Factors Contributing to the Exploit $($one to three paragraphs$)$:

Changes$/$Fixes$/$Efforts to Address the Vulnerability, also Rate their Probable Effectiveness:

Sources of Information: