What is SABSA?
SABSA is a Security Architecture Framework. It is optimized for comprehensive top-down traceability - from business strategy to technical security controls.
The SABSA model drives the SABSA Development Process that develops the security architecture domain of your enterprise architecture. First, you understand the strategic context creating foundational business requirements. Step-by-step you extend the chain of traceability through the entire security architecture.
The basic questions are answered
- what is being considered
- when is the activity performed
- how is the activity performed
- who performs the activity
- where is the activity performed
Asking the questions top-down ensures you have continually developed architecture specifications. For example, What at the Contextual Layer traces directly to What at the Component Layer.
SABSA's tools were built from practical experience, and work together. Some of the most important include the SABSA Model, the SABSA Business Attributes Profile, the SABSA Risk Model, and the SABSA Domain Model.
How Does SABSA Stack-Up as an Architecture Framework?
When evaluating SABSA, we need to know what to look for. When evaluating enterprise architecture frameworks, look for the essential scaffolding.
What to look for in an Enterprise Architecture Framework
Tools and method are the core of an optimized enterprise architecture framework.
Tools can include:
- Analytic Models
- Viewpoint Library
- Reference Architectures
- Architecture Specifications
- Deliverables
Method will address:
- Architecture Development Method
- Transition to Implementation
- Implementation Governance
- Enterprise Architecture Work Management
When compared to all the things needed in an optimized framework, BIAN is a great set of reference architectures. However, for an architecture framework it has holes. This does not mean there are no BIAN framework uses cases. It means that an optimized framework needs more.
SABSA Framework |
|
Tools | |
Analytic Models | Limited
SABSA Lifecycle Model SABSA Business Attributes Profile SABSA Assurance Model |
Viewpoint Library | The six fundamental questions and the perspectives provide the start of a solid ViewPoint Library
The SABSA model was built using the Zachman Framework |
Reference Architecture | SABSA only includes one reference model - the SABSA Business Attributes Profile
the other models inside SABSA are a wonderful foundation for an organization specific reference models:
|
Architecture Specifications | Missing
The Service Management Architecture does support definition of Security Controls and other Security Standards |
Deliverables | Missing |
Method | |
Architecture Development Method | Lightweight.
SABSA certification training provides a traverse from the business strategy (Business View) to a logical security architecture (Designer's View) |
Transition to Implementation | Lightweight.
The Service Management layer is implementation focused. However, SABSA is silent on concepts like Gaps and Work Packages. |
Implementation Governance | Missing |
Enterprise Architecture Work Management | Missing |
TOGAF vs. SABSA - Put them together
The idea of TOGAF vs. SABSA is absurd. The two architecture frameworks work together smoothly. They work together by design. Your security architecture is part of your enterprise architecture. SABSA addresses developing part of the enterprise architecture.
Let's start with TOGAF. TOGAF is larger than SABSA because it covers all architecture domains. TOGAF is an end-to-end enterprise architecture framework that provides essential scaffolding and is short on detailed how-to instruction. Possible enterprise architecture use cases prevent TOGAF from detailed how-to.
SABSA covers one architecture domain. It is a specific method supporting enterprise security architecture. It provides a series of integrated models, methods, and processes. We can independently use these or as a holistic technique. SABSA is a domain architecture framework.
Instead of SABSA vs. TOGAF, think of TOGAF plus SABSA. Think enterprise architecture with world-class risk and security.
Thinking enterprise architecture plus world-class security architecture led the SABSA Institute and The Open Group to collaborate. First with the TOGAF and SABSA Integration Paper, then the TOGAF Series Guide on Integrating Risk and Security into TOGAF.
SABSA plus TOGAF allows enhancing your enterprise architecture with the best security architecture approach.
Leverage SABSA in Enterrise Architecture
SABSA vs. TOGAF - Using SABSA Business Attributes Profile
SABSA Business Attributes Profile is at the heart of the SABSA method. This ‘requirements engineering’ technique makes SABSA truly unique and provides the linkage between business requirements and technology / process design. If you take nothing else away, Business Attributes Profiling is the most powerful tool for creating translated, standardized and ‘normalized’ set of business requirements.
Like other excellent reference tools, the taxonomy provides a checklist of possibility. Instead of brainstorming from a blank piece of paper, start with a standard list. Spend your time on analysis. Decide whether to include an attribute. Once included, identify the metrics for performance targets.
SABSA vs. TOGAF - Using the SABSA Risk Model
SABSA explicitly ties threat and opportunity together in the SABSA Risk Model. Rather than limiting consideration of risk to minimizing potential threat, SABSA balances risk thinking. Everything we do creates opportunities and threats.
Embed SABSA's ‘risk thinking’ within an enterprise architecture team to be instinctive about the enterprise culture. Achieve balance between realizing opportunities for gains while minimizing losses. Apply an architecturally structured and comprehensive approach
SABSA vs. TOGAF - Using the SABSA Domain Model
Risk management is about balancing potential gains against potential loss. The SABSA Domain Model integrates and aligns risk silos. Test who realizes the benefit with who bears the cost. You holistically embed risk management into all levels and perspectives of enterprise.
Failing to ensure the cost and benefit decisions are made by an appropriate decision maker destroys risk management. Someone who only bears cost, always errs on the side of avoiding potential loss. Cost free benefit owners create massive potential downside for others.
Conclusion
TOGAF vs SABSA is a false choice. Both work together. SABSA is the world's leading security architecture framework. TOGAF is a modular enterprise architecture framework that is easily extensible to use domain best-practice.
The SABSA Institute and The Open Group Architecture Forum have been working to end the false choice. We develop better enterprise architecture with best practice security architecture.