SABSA vs. TOGAF in a RMF NIST 800-30 context

Enterprise
Security
Architecture for
Cyber Security
M.M.Veeraragaloo
5th September 2013

Outline
• Cyber Security Overview
• TOGAF and Sherwood Applied Business Security
Architecture (SABSA)
o Overview of SABSA
o Integration of TOGAF and SABSA
• Enterprise Security Architecture Framework
The Open Group EA Practitioners Conference - Johannesburg 2013 2

Cyber Security
3
1. What is Cyber Security?
2. How is Cyber Security related to information security?
3. How do I protect my company from malicious attacks?
The Four Types of Security Incidents
1. Natural Disaster
2. Malicious Attack (External Source)
3. Internal Attack
4. Malfunction and Unintentional Human Error
Information security - the "preservation of confidentiality, integrity and availability
of information" (ISO/IEC 27001:2005);
"Cyber Security is to be free from danger or damage caused by disruption or fall-out of
ICT or abuse of ICT. The danger or the damage due to abuse, disruption or fall-out can
be comprised of a limitation of the availability and reliability of the ICT, breach of the
confidentiality of information stored in ICT or damage to the integrity of that
information.” (The National Cyber Security Strategy 2011, Dutch Ministry of Security
and Justice)

Cyber Security in Perspective
4The Open Group EA Practitioners Conference - Johannesburg 2013
No official position about the differences between Cyber Security and Information Security
Risk Management
(ISO/IEC 27001:2005);
Information Security
ISO/IEC 2700:2009
Information Technology
Business Continuity
(BS 25999-2:2007).
Cyber Security
Source: 9 Steps to Cyber Security – The Manager’s Information Security Strategy Manual (Dejan Kosutic)

Cyber Security in South Africa
5Source: SA-2012-cyber-threat (Wolf Pack) [ 2012/2013 The South African Cyber Threat Barometer]

TOGAF & SABSA
9/9/2013Footer Text 6

SABSA Overview

SABSA Meta Model

SABSA Matrix

SABSA Life Cycle
In the SABSA Lifecycle, the development of the contextual and conceptual layers is grouped into an activity called Strategy &
Planning. This is followed by an activity called Design, which embraces the design of the logical, physical, component, and
service management architectures. The third activity is Implement, followed by Manage & Measure. The significance of the
Manage & Measure activity is that once the system is operational, it is essential to measure actual performance against targets,
to manage any deviations observed, and to feed back operational experience into the iterative architectural development process.

SABSA Taxonomy of ICT Business Attributes

SABSA Taxonomy of General Business Attributes

SABSA Operational Risk Model

SABSA integrated with
TOGAF

A Central Role for Requirements Management
Linking the Business Requirements (Needs) to the Security Services – which TOGAF does in the “Requirements
Management” Phase and SABSA does via the Business Attributes Profile. These Artefacts needs to be linked to ensure
traceability from Business Needs to Security Services.

Requirements Management in TOGAF
using SABSA Business Attribute Profiling
Business Attribute Profiling: This describes the level of
protection required for each business capability.
• Requirements Catalog: This stores the architecture
requirements of which security requirements form an integral
part. The Business Attribute Profile can form the basis for all
quality requirements (including security requirements) and
therefore has significant potential to fully transform the current
TOGAF requirements management approach.
•Business and Information System Service Catalogs: TOGAF
defines a business service catalog (in Phase B: Business
Architecture) and an information system service catalog (Phase
C: Information Systems Architecture). The creation of the
information system services in addition to the core concept of
business services is intended to allow more sophisticated
modelling of the service portfolio.
• The Security Service Catalog: As defined by the SABSA
Logical Layer, this will form an integral part of the TOGAF
Information System Service Catalogs.

The Business Attribute Profile Mapped onto the TOGAF
Content Meta Model

SABSA Life Cycle and TOGAF ADM

Mapping TOGAF and SABSAAbstraction
Layers

Mapping of TOGAF to SABSA Strategy and
Planning Phase
As the SABSA phases extend beyond the core phases of the TOGAF ADM, the scoping provided by
the SABSA Domain Model extends beyond these core phases of TOGAF, both in terms of solution
design and system and process management during the operational lifecycle.

Overview of Security Related Artifacts in the TOGAF ADM

Preliminary Phase – Security Artifacts

Phase A - Architecture Vision – Security Artifacts

Phase B – Business Architecture – Security Artifacts

Phase C – Information Systems Architecture – Security Artifacts

Phase D – Technology Architecture – Security Artifacts

Phase G – Implementation Governance – Security Artifacts

Phase H – Architecture Change Management – Security Artifacts

Enterprise Security
Architecture - Framework

ICT service providers must consider the whole
market. Four dimensions to put in one line
Service Models
 Cloud (XaaS)
 Hosting
 Managed Service
 Monitoring
Frameworks
 ISO 27002
 NIST
 ISF
Requirements
 national/intern. law
 industries
 SOX, PCI DSS…
 customers
Service Types
 Desktop
 Communication
 Collaboration
 Computing
LogonLogonLogon
Service Provider

ICT service providers must consider the whole
market. Four dimensions to put in one line
4) Mapping Model to demonstrate fulfillment of
all types of security requirements
3) Hierarchy of Security Standards
delivering information on each level of detail
2) Modular and Structured approach
that serves all possible models
and offerings
1) Produce Standardized Security measures for
industrialized ICT production
Enterprise Security Architecture
» shaping the security of ICT service provisioning «
deliver assurance to customers and provide directions for production

From Requirements to ICT Services.
Standardisation is Key
requirements identification
requirements consolidation
conception, integration
operations, maintenance
Corporate Governance, Risk, &
Compliance
customer requirements
(Automotive, Finance, Public, …)
partially
overlap
standard options full custom
no-go
industrialized services
(established platforms and processes)
customer-specific
services

Framework for Enterprise Security
Architecture
Requirements (corporate and customer)
Framework for ESA
Enablement (ISMS)
 security management process and
reference model (mainly ISO 27001)
Enforcement (Practices)
 controls / techniques
(mainly ISO 27002)
 specific standards
impact analysis for
non-framework
requirements
Enterprise Security Architecture
Industrialized ESA Services
 processes including roles for new
business, changes and operational
services
 technology platform
 evidence (monitoring, analytics
and reporting)
custom services
(specific service and
realization for a
customer)

Framework for ESA.
The Enablement Framework with ISMS activities.
Define scope and
ISMS policy
Define risk assessment approach
Identify risks, derive control obj.
& controls
Approve residual risks
Draw up statement of
applicability (SoA)
P1
P2
P3
P4
P5
Implement risk handling plan &
controls
Define process for monitoring the
effectiveness of controls
Develop security awareness
D1
D2
D3
Lead ISMS and steer fundsD4
Implement methods to identify /
handle security incidentsD5
Monitoring & review security
incidents
Review risk assessment approach
C1
Evaluate effectiveness of the
controls implemented
C2
C3
Perform and document ISMS
audits
C4
Carry out management
evaluations
C5
Implement appropriate corrective
and preventative controls
Communicate activities &
improvements
Ensure improvements achieve
targets
Implement identified
improvements in ISMS
A1
A2
A3
A4
Activities of the Enablement Framework

Considering: Plan – Build – Run.
Sales, Service, Production, (Integration).
ESA reflects three types of business:
Customer Projects – Operations – Platform Preparation
 Bid, Transition, Transformation
 Set-up for operations
 Major Changes
New Business & Major Changes
(Project Business)
 Service Delivery Management
 Provide industrialized and customer specific ICT
Services
 Evidence
Operations
(Daily Business)
 Define Offering and SDEs
 Initial set-up of ESA (creation and extension)
 Maintenance of ESA (improvements)
ESA Platform
EnterpriseSecurityArchitecture
forICTServices

How?Standards
3
Who?Rolesetc.
2
 Define Offering and Service Delivery Elements
 Initial set-up of ESA
 Maintenance
ESA Technology Platform
 Bid, Transition,
Transformation
 Major Changes
New Business & Change
(Project Business)
 Provide ICT Services
 Evidence
Operations
(Daily Business)
What?Workareas
1

Cooperation: Implementation of Roles.
Customer Projects, Portfolio, and Operations.
Security Manager
Customer
ICT SRC Manager
Security Architects and Experts
(engineering)
Customer Security Manager
Operations Manager
Operations Personnel
step-by-step transfer of business
Project (bid,
transition, transformation)
Operations
(CMO+FMO)
requirements requirements
governance
Offering Manager

How?Standards
3
Who?Rolesetc.
2
 Define Offering and Service Delivery Elements
 Initial set-up of ESA
 Maintenance
ESA Technology Platform
 Bid, Transition,
Transformation
 Major Changes
New Business & Change
(Project Business)
 Provide ICT Services
 Evidence
Operations
(Daily Business)
What?Workareas
1

Corporate and Product Security
incorporated in one Hierarchy
Corporate Security Rule Base
Corporate Security Policy
ICT Security Standards
ICT Security Principles
ICT Security Baselines
Refinement Pyramid of Standards Requirements for
ICT Service Provisioning
(“product security”)
ISO 27001
Certificate
Detailed
customer
inquiry
Software
settings,
configuration
Examples
Certification and Audit
Security Measures
Security Implementation

Demonstrating that Customer
Requirements are met
Customer Requirements
R1
R2
R3
R4
R5
C1 C2 C3 C4 C5 C6 C7
Set of Controls
(contractual )
Requirements are met
(Suitability)
Controls of ESA and its
ICT Security Standards
Service type:
 Desktop
 Communication
 Collaboration
 Computing

Evidenceand
CustomerRelation
ServiceManagement
Wide Area Network
Security
Customer and users Data Center
User LAN
Periphery
Remote User
Access
User Identity
Management
Mobile Work-
place Security
Office Work-
place Security
Corporate
Provider Access
Gateway and
Central Services
Provider Identity
Management
Data Center
Security
Data Center
Networks
Computer Systems
Security
Application and
AM Security
VM and S/W
Image Mngt.
Database and
Storage Security
Operations
Support Security
Networks
Asset and Configu-
ration Management
Business Continuity
Management
Security Patch
Management
Hardening, Provisio-
ning & Maintenance
Change and Problem
Management
Customer Communi
cation and Security
System Development
Life-Cycle
Systems Acquisition
and Contracting
Risk Management
Logging, Monitoring &
Security Reporting
Incident Handling and
Forensics
Vulnerability
Assessment, Mitigation
Plan
Release Mngt. and
Acceptance Testing
Certification and 3rd
Party Assurance
Administration Network
Security
Security
Taxonomy.

EAS – Meta Model
Queries,
Analysis,
Portfolios,
etc.
Stakeholder
Views
“Model World”
Architecture
Repository
“Real World”
Enterprise
applications
teams &
information
Industry Glossaries
Industry Reference Models
Application Models
Application Glossaries
“Meta-Model”
Common Language
“Standardized”
Content, e.g. business
processes, applications
etc.
“Integrated and
consistent Views”
Stakeholder specific
views & reports

ICT Security Services and Solutions
Enterprise
Security
Management
Identity
and Access
Management
ICT
Infrastructure
Security
 Architecture and Processes
 Applications, Risk and Compliance
 Security and Vulnerability Management
 Users and Identities
 Smart Cards
 Trust Centers
Business
Enablement
Enabling the managed use
of ICT resources and IT
applications with digital
identities, roles and rights.
Business
Integration
Embedding security in
processes, defining goals
and responsibilities,
ensuring good
governance and
compliance.
 Workplace, Host and Storage Security
 Network Security
 Physical Security
Business
Protection
Defending from hostile
action: protecting
networks, IT applications,
data and building security

44
If you have one last breath
use it to say...
The Open Group EA Practitioners Conference - Johannesburg 2013

SABSA vs. TOGAF in a RMF NIST 800-30 context

More Related Content

What's hot (20)

Viewers also liked (17)

Similar to SABSA vs. TOGAF in a RMF NIST 800-30 context (20)

More from David Sweigert (20)

Recently uploaded (20)

SABSA vs. TOGAF in a RMF NIST 800-30 context