We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byZander Boley
Modified about 1 year ago
wwwTASK.to © Toronto Area Security Klatch 2007 Threat Modeling With STRIDE and DREAD Chuck Ben-Tzur Security Consultant Sentry Metrics March 27, 2007
wwwTASK.to © Toronto Area Security Klatch 2007 (Application) Threat Modeling A process to identify threats to the system, the associated risks and determine the correct controls to produce effective countermeasures The output is a list of rated threats. The threat model helps you to focus on the most potent threats Aimed to be used at the design phase of a system. However, usually implemented at the testing phase (vulnerability assessment) Not only for web applications. Can be (and should be...) applied to different type of systems (e.g. networks)
wwwTASK.to © Toronto Area Security Klatch 2007 Threat Modeling (cont.) The threat modeling process (introduced by Microsoft around 2002) Identify Assets Create architecture overview (subsystems, trust boundaries, data flow) Decompose the application (Build a security profile) Identify the threats (STRIDE) Document the threats Rate the threats (DREAD)
wwwTASK.to © Toronto Area Security Klatch 2007 STRIDE A methodology for identifying and categorizing threats S S poofing identity T T ampering with data R R epudiation I I nformation disclosure D D enial of service E E levation of privileges “Business” oriented – easier for non-technical persons to relate to Expand (can replace) the “map by mechanisms and subsystems” approach Can be used also to identify threats (e.g. as pen. test checklist)
wwwTASK.to © Toronto Area Security Klatch 2007 DREAD A methodology for risk rating. Each vulnerability is graded in all of the following categories: D D amage potential 0 – Leaking Trivial Info, 5 – Sensitive, 10 – Admin level R R eproducibility 0 – Very difficult to reproduce, 5 – three steps, 10 – web browser E E xploitability 0 – very skilled, 5 – can be automated, 10 – novice programmer A A ffected Users 0 – few users, 5 – some users, 10 – all users D D iscoverability 0 – unlikely, 5 – accessible only to few users, 10 - published The risk overall rate calculation formula: Rating = (D + R + E + A + D) / 5 ThreatDREADRate Attacker obtains authentication credentials by monitoring the network High SQL commands injected into application10 59High
wwwTASK.to © Toronto Area Security Klatch 2007 DREAD (cont.)
wwwTASK.to O perationally C ritical T hreat A sset and V ulnerability E valuation Risk-based strategic assessment and planning technique for security Key differences: Organization focused (as opposed to system) Security practices (not technology specific) Strategic issues (not relating to tactical aspects) Self direction (security experts) Flexible - can be tailored for small and large organizations Focuses on the design and strategic planning of the organization Input is from both internal business and technical resources Not suitable for ad-hoc vulnerability assessments © Toronto Area Security Klatch 2007 The OCTAVE Option
wwwTASK.to © Toronto Area Security Klatch 2007 Resources Threat Modeling Microsoft Threat Analysis & Modeling v b7d &displaylang=en Octave Good book on the subject Threat Modeling (Microsoft Professional)
Application Security Best Practices At Microsoft Ensuring the lowest possible exposure and vulnerability to attacks Published: January 2003.
© 2012 ISO27k Forum. ISO Roadmap © 2012 ISO27k Forum ISO27001 ISO27001 formally specifies how to establish an Information Security Management.
Security for Developers Threat Modeling and the Security Development Lifecycle Steven Borg & Richard Hundhausen Accentient, Inc.
Inside Microsofts Secure Windows Initiative Steve Lipner Director of Security Engineering Strategy Security Business Unit Microsoft Corporation.
Nick Coblentz OWASP CLASP Overview.
1 ® MD Manitoba Telecom Services Inc. Used under license. / Utilisé en vertu d’une licence. MTS Allstream Inc. proprietary. Use pursuant to company instructions./
IT Security Auditing. Topics Defining IT Audit Risk Analysis Internal Controls Steps of an IT Audit Preparing to be Audited Auditing IT Applications Who.
Michael Howard Microsoft employee for 17 years Always in security Worked on the SDL since inception.
CSE 6324: Advanced Topics in Software Engineering Paper Presentation on An Overview of Security Practices in Agile Software Development - Naieem Khan.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 10 Practical Database Design Methodology and Use of UML Diagrams.
Security Policy. TOPICS Objectives WLAN Security Policy General Security Policy Functional Security Policy Conclusion.
1 9 Moving to Design Lecture Analysis Objectives to Design Objectives Figure 9-2.
Management Consulting Caribbean Community (CARICOM) Secretariat Jerry Blenman Managing Director Calidad Investment & Financial Services Inc Business Development.
Manage an IT Project. Aim This presentation is prepared to support and give a general overview of the ‘How to Manage and IT Project’ Guide and should.
Types of Information systems BY, Ikhlaq Ikhlaq. IS ACTIVE DIFFERENT LEVELS Operational-level systems Operational-level systems Support operational managers.
Systems Analysis and Design 8 th Edition Chapter 7 Development Strategies.
Federal Information System Controls Audit Manual (FISCAM)
PLANNING THE AUDIT Individual audits must be properly planned to ensure: Appropriate and sufficient evidence is obtained to support the auditors opinion;
Software Development QA Best Practices May 20, 2010 Suzette Hackl, CSM Senior Project Manager Skyline Technologies, Inc.
Dr. Chen, Electronic Commerce Pearson/Prentice Hall & Dr. Chen, Electronic Commerce Chapter 14 E-Commerce Strategy and Global EC.
2007 INSTITUTIONAL CLIENT CONFERENCE Innovative Leadership, Creative Solutions © 2007 Northern Trust Corporation N O R T H E R N T R U S T Simon Willcox.
Data Analysis Chapter 11..powerful professional development tool that can lead to school improvement.
© John Beveridge CobiT Update NSAA IT Conference Richmond, VA John W. Beveridge September 27, 2007.
Security Threats and Protection Mechanisms. Learning Objectives Internet security issues (intellectual property rights, client, communication channels,
©Ian Sommerville 2000Dependable systems specification Slide 1 Chapter 17 Critical Systems Specification.
Module 2: National IEA process design and organization.
Towards Application Security Design | Process | Organization –Software Development Process –Security Design Process & Artifacts –Security Team composition.
Introduction to Network Security INFSCI 1075: Network Security Amir Masoumzadeh.
Network Security Chapter 1 - Introduction. Chapter 1 – Introduction The art of war teaches us to rely not on the likelihood of the enemy's not coming,
Khadiga Eissa Ebead Abdalla Agricultural Research Corporation (ARC) Biotechnology and Biosafety Research Center BBRC)) Agricultural Biotechnology Knowledge.
© 2016 SlidePlayer.com Inc. All rights reserved.