Security architecture frameworks
Download as PPTX, PDF22 likes9,039 views
This document discusses security architecture frameworks and concepts. It outlines different frameworks for security architecture like TOGAF, SABSA, and FAIR. It then discusses key concepts in security architecture like assets, threats, domains, risks, and security measures. Risks can come from assets, threats, or domains and security architecture aims to reduce business risks from IT through frameworks, standards, and applying the right security measures.
Security architecture frameworks
- 2. Agenda Frameworks and Standards Different ways of looking at Risk Impact Assurance
- 3. O Desafio está aumentando... 120% 100% 80% 60% 40% 20% 0% PERCENTAGE OF IT BUDGET DEVOTED TO SECURITY Percentage of IT budget devoted to security 1990 Today 2040
- 4. Security and Architecture IT Architecture is about using IT to meet business needs Security is about reducing business risk Security Architecture is about reducing business risk from IT
- 5. Security Architecture Frameworks and Standards TOGAF Next Everything TOGAF 9 Process, Content TOGAF 8 Process Only IAF Content Only SABSA Security Specific Zachman Content Only FAIR Risk Analysis
- 6. Security Measures vs. Risks Threat Uses Access Path To perform Asset Impact Deterrence Prevention Detection Containment Attack Against Which results in Recovery Risk Security Measures Deters Controls Detects Recovers Limits
- 7. Security Concepts in an Architecture Framework Context: Why do I need to be Secure? Concept: What security do I need? Logical/Physical: How will I be secure? Threats Stakeholders Drivers Assets Domains Access Routes Risks Requirements Policies Services Measures
- 8. Different Types of Risk Domains Assets Threats • Risks are unexpected or uncertain events • Risks trigger impacts if they occur • Real-world systems have many risks • Security measures mitigate the risks • The cost of a security measure must be less than the value of the risks it mitigates
- 9. Asset Risk Assets are things the business values Stakeholders are people and organisations that have an interest in assets Stakeholders have objectives - things they want to enforce - laws, contracts, ethical rules, principles, policies Confidentiality, Integrity, Availability, Non-repudiation Stakeholders can be negative For every asset/objective combination, there is a risk this will not be enforced Looking at risk in this way helps you to concentrate on what is of value Domains Assets Threats
- 10. Threat Risk Threat Agents are people, organisations or events with access to your assets Threat agents can be legitimate Employees, Customers or illegitimate Hackers, criminals Or unexpected events Component failure, flood, earthquake Threat agents can make mistakes, or can deliberately attack you, or can happen unexpectedly This leads to an objective not being met Looking at risk in this way helps you to concentrate on possible loss scenarios Domains Assets Threats
- 11. Domain Risk Domains are the places where assets are stored: Networks, servers, processes, databases, files, sites, boxes Domains are accessed by threat agents via access routes Access routes need to be secured Guided by common sense and good practice Non-secured access routes are a source of risk Looking at risk in this way helps you to concentrate on how an attacker would get in Domains Assets Threats
- 12. Anatomy of an Attack Threat Agent Stakeholders Actions By Threat Agent Actions by Stakeholders Legitimate Access - Event Illegitimate Access - Impact Security Breach Occurs Asset Breach Detected and Stopped Timeline
- 13. Impact
- 14. Security measures are justified by risks but… Risks are difficult to enumerate systematically The impact of a risk is difficult to estimate Real systems generate enormous numbers of risks It’s not practical to design security countermeasures as responses to risks Most security practitioners don’t start with a list of risks Instead, they start with good practice and common sense And only list risks when a business case is needed
- 15. Assurance How do I know I’m secure? Testing Penetration Testing Evaluation (Vs ISO 15408) Risk Analysis Maturity Modelling Certification (Vs ISO 27001)
- 16. Security Architecture Service Delivery Framework ROLES Security Advisor Security Engagement Manager Security Architect Security Auditor CAPGEMINI PROCESSES ARTEFACTS Advisory Work Initiation Example Security Policies, Standards Sizing Tools Request Templates Reporting Resource Management Industrialised Design Quality Assurance Governance Added Value Report Templates Architecture Design Templates Waiver & Exemption Templates Risk Assessment Tools Detailed Design Virtualised Platform Pattern Mobile Devices Pattern Cloud Architecture Pattern IAM Architecture Pattern Etc. New Starter Pack Value IT Tools Controls Review Etc. New Project Project: Security Initiation Architecture Design Security Review Detailed Design & Build DELIVERABLES • Project Initiation • Information Classification • Risk Assessment • Business Impact Assessment • Security Architecture Resource Request • Requirements Definition • Outline Solution Design • Full Solution Design • Waivers & Exemptions • Controls Review • Detailed Design Security Designer
- 17. Conclusion: What makes up a security architecture Threat Agents Security Architecture Access Routes Domains Assets Stakeholders Objectives Risks Measures Impacts
- 18. www.capgemini.com The information contained in this presentation is proprietary. © 2013 Capgemini. All rights reserved. About Capgemini With more than 130,000 people in 44 countries, Capgemini is one of the world's foremost providers of consulting, technology and outsourcing services. The Group reported 2013 global revenues of EUR 10.1 billion. Together with its clients, Capgemini creates and delivers business and technology solutions that fit their needs and drive the results they want. A deeply multicultural organization, Capgemini has developed its own way of working, the Collaborative Business ExperienceTM, and draws on Rightshore®, its worldwide delivery model. Learn more about us at www.capgemini.com. Rightshore® is a trademark belonging to Capgemini
Editor's Notes
- #17: To enable this, we are in the processes of defining what we are calling a security architecture delivery framework To be clear – this is not about reinventing TOGAF or IAF. This is about using those best practices, and creating: On the right hand side there – a whole toolkit of templates, patterns and other artifacts that can be reused across different accounts It’s about having processes defined about how we provide these services. These processes are not just how one individual architect works, it is the whole set of surrounding processes about how to engage and assure and report on the architecture services we provide And finally it is about our people, making sure we have clear roles and responsibilities, and people working effectively as part of a team, equipped with the knowledge and the tools they need to do their job effectively It is a lot of work and a major Capgemini investment to create something like this, but we have a core framework in place already, and are now extending the artifacts within the framework on an ongoing (daily) basis. This is here and now, now future stuff. It is simply industrialising and exploiting our strong track record in security architecture delivery.