SABSA and TOGAF Integration White Paper (W117) Overview
This White Paper documents an approach to enhance the TOGAF enterprise architecture methodology with the SABSA security architecture approach and thus create one holistic architecture methodology using SABSA and TOGAF integration.
The following aspects are highlighted:
- Overview of TOGAF and SABSA integration – why bolster Enterprise Architecture with security architecture and why use SABSA?
- Operational risk and its relevance to enterprise architecture – why incorporating the concept of operational risk is essential to modern enterprise architecture design.
- A central role for requirements management – how to perform requirements management using SABSA Business Attribute Profiling.
- Creating an enterprise architecture with integrated security – how to align SABSA concepts to the TOGAF ADM.
- TOGAF and SABSA Integration benefits for practitioners – how to enhance SABSA-based projects by introducing TOGAF concepts.
This White Paper is intended to guide enterprise and security architects in fully integrating security and risk management into enterprise-level architectures, to stimulate review comments and inform the global architecture community of proposed new content from the SABSA perspective for a future edition of the TOGAF standard.
The ultimate goal is that the security architecture is fully integrated in the enterprise architecture. The TOGAF Architecture Development Method (ADM) is the heart of TOGAF and is therefore the designated place for SABSA security architecture integration. The following sections describe the way SABSA can be integrated into the ADM. Both SABSA and TOGAF are business-driven; therefore, it is only natural to use this business-driven aspect as the binding element between the two.
Just as the ADM is the core process model of TOGAF, so is the SABSA Lifecycle the core process model of SABSA. Mapping one to the other, it becomes obvious that both models have partly overlapping and partly differing phases.