Security Architecture
One of the key outcomes of the Security Architecture process is a solution that has been properly aligned (and documented) with the collaborative input of all key stakeholders. The artifacts that come out of this process are extremely valuable tools in consistently aiding traceability and accountability for all decisions that have gone into the planning, building, and running of a solution throughout its lifecycle.
Leveraging the Sherwood Applied Business Security Architecture (SABSA®) framework, we answer the "six W's" (what, why, how, who, where, and when) to address the perspectives of the:
Leveraging the Sherwood Applied Business Security Architecture (SABSA®) framework, we answer the "six W's" (what, why, how, who, where, and when) to address the perspectives of the:
- Business (Contextual Architecture)
- Architect (Conceptual Architecture )
- Designer (Logical Architecture)
- Builder (Physical Architecture)
- Tradesman (Component Architecture)
- Facilities Manager (Operational Architecture)
Sherwood, J., et al. (2005). Enterprise Security Architecture: A Business-Driven Approach
