Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.

Slides:



Advertisements
Similar presentations
Sachin Rawat Crypsis SDL Threat Modeling.
Advertisements

Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
Cryptography and Network Security 2 nd Edition by William Stallings Note: Lecture slides by Lawrie Brown and Henric Johnson, Modified by Andrew Yang.
Lesson Title: Threat Modeling Dale R. Thompson Computer Science and Computer Engineering Dept. University of Arkansas 1 This.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation.
Risk Assessment What is RISK?  requires vulnerability  likelihood of successful attack  amount of potential damage Two approaches:  threat modeling.
Bridging the gap between software developers and auditors.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
Engineering Secure Software. Uses of Risk Thus Far  Start with the functionality Use cases  abuse/misuse cases p(exploit), p(vulnerability)  Start.
September 10, 2012Introduction to Computer Security ©2004 Matt Bishop Slide #1-1 Chapter 1: Introduction Components of computer security Threats Policies.
Networked Systems Survivability CERT ® Coordination Center Software Engineering Institute Carnegie Mellon University Pittsburgh, PA © 2002 Carnegie.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike.
1 Cryptography and Network Security Third Edition by William Stallings Lecturer: Dr. Saleem Al_Zoubi.
1 An Overview of Computer Security computer security.
Security Engineering II. Problem Sources 1.Requirements definitions, omissions, and mistakes 2.System design flaws 3.Hardware implementation flaws, such.
July 1, 2004Computer Security: Art and Science © Matt Bishop Slide #1-1 Chapter 1: Introduction Components of computer security Threats Policies.
April 1, 2004ECS 235Slide #1 Chapter 1: Introduction Components of computer security Threats Policies and mechanisms The role of trust Assurance Operational.
Application Threat Modeling Workshop
Threat Modeling for Cloud Computing (some slides are borrowed from Dr. Ragib Hasan) Keke Chen 1.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
Architecting secure software systems
1 Threat Modeling at Symantec OWASP WWW, Irvine, CA, January 28, 2011 Threat Modeling at Symantec Edward Bonver Principal Software Engineer, Symantec Product.
Security Risk Assessment Applied Risk Management July 2002.
Computer Security “Measures and controls that ensure confidentiality, integrity, and availability of IS assets including hardware, software, firmware,
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
Risk Assessment and Management. Objective To enable an organisation mission accomplishment, by better securing the IT systems that store, process, or.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation.
Chapter 1 Overview The NIST Computer Security Handbook defines the term Computer Security as:
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
APPLICATION PENETRATION TESTING Author: Herbert H. Thompson Presentation by: Nancy Cohen.
Information Security What is Information Security?
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
Module 6: Designing Security for Network Hosts
Hands-On Threat Modeling with Trike v1. Generating Threats.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike.
Lecture slides prepared for “Computer Security: Principles and Practice”, 3/e, by William Stallings and Lawrie Brown, Chapter 1 “Overview”. © 2016 Pearson.
Module 11: Designing Security for Network Perimeters.
Practical Threat Modeling for Software Architects & System Developers
Csci5233 computer security & integrity 1 An Overview of Computer Security.
Visual 1. 1 Lesson 1 Overview and and Risk Management Terminology.
Module 2: Designing Network Security
What is RISK?  requires vulnerability  likelihood of successful attack  amount of potential damage Two approaches:  threat modeling  OCTAVE Risk/Threat.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation.
INTRODUCTION TO COMPUTER & NETWORK SECURITY INSTRUCTOR: DANIA ALOMAR.
M2M Service Layer – DM Server Security Group Name: OMA-BBF-oneM2M Adhoc Source: Timothy Carey, Meeting Date:
Chapter 1: Security Governance Through Principles and Policies
Module 7: Designing Security for Accounts and Services.
July 1, 2004Computer Security: Art and Science © Matt Bishop Slide #1-1 Chapter 1: Introduction Components of computer security Threats Policies.
Presented by Mike Sues, Ethical Hack Specialist Threat Modeling.
November 1, 2004Introduction to Computer Security ©2004 Matt Bishop Slide #1-1 Chapter 1: Introduction Components of computer security Threats Policies.
UNIT-4 Computer Security Classification 2 Online Security Issues Overview Computer security – The protection of assets from unauthorized access, use,
Copyright 2007 © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
Threat Modeling: Employing the 5 Ws Security Series, December 13, 2013 Jeff Minelli Penn State ITS
Advanced System Security Dr. Wayne Summers Department of Computer Science Columbus State University
Matthias Rohr Practical Threat Modeling with Microsofts Threat Modeling Tool 2016.
Threat Modeling for Cloud Computing
Basic Terms and Concepts – 1/3
Threat Modeling - An Overview All Your Data is Mine
Evaluating Existing Systems
Threat modeling Aalto University, autumn 2013.
Evaluating Existing Systems
Off-line Risk Assessment of Cloud Service Provider
Chapter 1: Introduction
Must cost less than possible Impact
Engineering Secure Software
Copyright Gupta Consulting, LLC.
Engineering Secure Software
Presentation transcript:

Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP Foundation OWASP Threat Modeling - Overview Megha Anand itsmeghaanand-at-gmail-dot-com

OWASP 2 Agenda  Terminology  Terminology Example  Threat Modeling  Benefits  Who  Process Overview  Business Security Objectives  Model the System  Application Decomposition  Threat Profile  STRIDE & its Relation  Threat Tree  Risk Assessment  Example

OWASP Terminology  Asset: Things to protect (tangible or intangible)  Entry/Exit Points: Ways to get at an asset  Threat: Risks to an asset  Attack / exploit: An action taken that harms an asset  Vulnerability: Specific ways to execute the attack  Risk: Likelihood that vulnerability could be exploited  Mitigation / Countermeasure: Something that addresses a specific vulnerability We can mitigate vulnerabilities… …but the threat still exists!!! 3

OWASP Terminology Example 4 Asset – ATM Machine

OWASP Terminology Example Use Case  Customer withdraws cash from ATM  Checks balance in his/her account  Transfers cash to some other account 5

OWASP Terminology Example 6 Attacker – Burglar

OWASP Terminology Example 7 Threat – Denial of Service Attack – Physically tempered Vulnerability – Plastic made Closed

OWASP Terminology Example Security Controls  Guard  CCTV Cameras  ATM Machine should be made of Steel/Iron But threat still persists!!! 8

OWASP Take Away!!! Key Point: We can reduce the risk but cannot rid of completely!!! Assumption: Lets engage in repetitive penetration testing Question: During Development? At deployment? After deployment? 9

OWASP Threat Modeling Its an iterative process which helps in  Simplifies qualitative risk assessment  Identify security objective  Create security profile of application  Identify & prioritize threats  Visualizing & documenting threats 10

OWASP Benefits 11 CostTime Quality

OWASP Cost 12 Less Very High

OWASP Time 13 Requirement Gathering or Early stages of SDLC

OWASP Post Production 14

OWASP Quality 15

OWASP Who 16  Developers  Security Consultants  Architects  IT Project Managers

OWASP Process Overview  Identify business security objectives  Decompose Application  Understand attacker & abuse cases  Threat Analysis  Risk Analysis  Security controls 17

OWASP Business Security Objective  It’s a high level overview of what security issues need to be addressed in order to maintain business objective.  Generate security objective with help of - Confidentiality - Integrity - Availability 18

OWASP Model the System  Entry Points  Assets  Roles & Identities  Trust Levels 19

OWASP Decompose Application DFD Components 20 Web Server Request Response External Entity - Entry point of application

OWASP Decompose Application DFD Components 21 Web Server Request Response Process - Perform an Action

OWASP Decompose Application DFD Components 22 Web Server Request Response Data store - Where data is stored

OWASP Decompose Application DFD Components 23 Web Server Request Response Data Flows - Direction of Data Movement

OWASP Decompose Application DFD Components 24 Web Server Request Response Trust Boundary – Physical or Logical

OWASP Example 25

OWASP Simple Approach - Threat Profile  Where to BEGIN??? 26 Confidentiality (who can read) Integrity (who can write) Availability (who can access) Network Server Application

OWASP STRIDE - Threat categories  Spoofing  Tempering  Repudiation  Information Disclosure  Denial of Service  Escalation of Privileges 27

OWASP Threat Categories & Security Control  Spoofing Authentication  TemperingIntegrity  Repudiation Non – repudiation  Information DisclosureConfidentiality  Denial of Service Availability  Escalation of PrivilegeAuthorization 28

OWASP Threat – Element Relation 29 DFD ComponentSTRIDE Entity Process Data Flow Data Store

OWASP Threat Tree 30

OWASP Risk Assessment Simplest Approach  Low, Medium, High  Impact/Likelihood Matrix 31 LowMediumHigh Low Medium LowMediumHigh MediumHigh

OWASP Practical Example 32

OWASP 33