OCTAVESM Process 4 Create Threat Profiles

Slides:



Advertisements
Similar presentations
S3-1 © 2001 Carnegie Mellon University OCTAVE SM Process 3 Identify Staff Knowledge Software Engineering Institute Carnegie Mellon University Pittsburgh,
Advertisements

© 2005 by Carnegie Mellon University Version 1.0 The Security Professionals Conference. - page 1 Pittsburgh, PA Ways to Fit Security Risk Management.
Introduction to Security in Computing Computer and Network Security Semester 1, 2011 Lecture #01.
S2-1 © 2001 Carnegie Mellon University OCTAVE SM Process 2 Identify Operational Area Management Knowledge Software Engineering Institute Carnegie Mellon.
What Is My Role in Information Survivability? Why Should I Care? Julia H. Allen Networked Systems Survivability CERT ® Coordination Center Software Engineering.
Networked Systems Survivability CERT ® Coordination Center Software Engineering Institute Carnegie Mellon University Pittsburgh, PA © 2002 Carnegie.
© 2001 by Carnegie Mellon University PPA-1 OCTAVE SM : Participants Briefing Software Engineering Institute Carnegie Mellon University Pittsburgh, PA
© Carnegie Mellon University The CERT Insider Threat Center.
A Covenant University Presentation By Favour Femi-Oyewole, BSc, MSc (Computer Science), MSc (Information Security) Certified COBIT 5 Assessor /Certified.
Lecture 1: Overview modified from slides of Lawrie Brown.
CERT ® System and Network Security Practices Presented by Julia H. Allen at the NCISSE 2001: 5th National Colloquium for Information Systems Security Education,
Security+ Guide to Network Security Fundamentals
CST 481/598 Many thanks to Jeni Li.  Potential negative impact to an asset  Probability of a loss  A function of three variables  The probability.
Note1 (Intr1) Security Problems in Computing. Overview of Computer Security2 Outline Characteristics of computer intrusions –Terminology, Types Security.
1 An Overview of Computer Security computer security.
S5-1 © 2001 Carnegie Mellon University OCTAVE SM Process 5 Identify Key Components Software Engineering Institute Carnegie Mellon University Pittsburgh,
Introducing Computer and Network Security
EEC 688/788 Secure and Dependable Computing Lecture 2 Wenbing Zhao Department of Electrical and Computer Engineering Cleveland State University
Information Systems Risk Analysis and Management Spyros Kokolakis University of the Aegean IPICS 2005, Chios, July 2005.
Introduction Security is a major networking concern. 90% of the respondents to the 2004 Computer Security Institute/FBI Computer Crime and Security Survey.
Critical Infrastructure Protection (and Policy) H. Scott Matthews March 5, 2003.
Sanjay Goel, School of Business/Center for Information Forensics and Assurance University at Albany Proprietary Information 1 Unit Outline Information.
© 2003 by Carnegie Mellon University page 1 Tailoring OCTAVE ® for K-12 ® OCTAVE is registered with the U.S. Patent and Trademark Office by Carnegie Mellon.
© 2003 by Carnegie Mellon University page 1 Information Security Risk Evaluation for Colleges and Universities Carol Woody Senior Technical Staff Software.
© 2001 by Carnegie Mellon University PSM-1 OCTAVE SM : Senior Management Briefing Software Engineering Institute Carnegie Mellon University Pittsburgh,
What does “secure” mean? Protecting Valuables
© 2001 Carnegie Mellon University S8A-1 OCTAVE SM Process 8 Develop Protection Strategy Workshop A: Protection Strategy Development Software Engineering.
Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin Business Plug-In B6 Information Security.
© 2001 by Carnegie Mellon University SS5 -1 OCTAVE SM Process 5 Background on Vulnerability Evaluations Software Engineering Institute Carnegie Mellon.
OCTAVE-S on TradeSolution Inc.. Introduction Phase 1: Critical Assets and threats Phase 2: Critical IT Components Phase 3: Changes Required in current.
Lesson 7-Managing Risk. Overview Defining risk. Identifying the risk to an organization. Measuring risk.
Chapter 1 Overview The NIST Computer Security Handbook defines the term Computer Security as:
Security+ Guide to Network Security Fundamentals, Third Edition Chapter 9 Performing Vulnerability Assessments.
Risk Assessment Richard Newman. Six Phases of Security Process 1. Identify assets 2. Analyze risk of attack 3. Establish security policy 4. Implement.
Lecture slides prepared for “Computer Security: Principles and Practice”, 3/e, by William Stallings and Lawrie Brown, Chapter 1 “Overview”. © 2016 Pearson.
Security Administration. Links to Text Chapter 8 Parts of Chapter 5 Parts of Chapter 1.
Networked Systems Survivability CERT ® Coordination Center Software Engineering Institute Carnegie Mellon University Pittsburgh, PA © 2002 Carnegie.
IT Security. What is Information Security? Information security describes efforts to protect computer and non computer equipment, facilities, data, and.
Chap1: Is there a Security Problem in Computing?.
CSCE 548 Secure Software Development Security Operations.
Csci5233 computer security & integrity 1 An Overview of Computer Security.
T.A 2013/2014. Wake Up Call! Malware hijacks your , sends death threats. Found in Japan (Oct 2012) Standford University Recent Network Hack May Cost.
Visual 1. 1 Lesson 1 Overview and and Risk Management Terminology.
Introduction and Overview of Information Security and Policy By: Hashem Alaidaros 4/10/2015 Lecture 1 IS 332.
CERT Centers, Software Engineering Institute Carnegie Mellon University Pittsburgh, PA SEI is sponsored by the U.S. Department of Defense ©
Chap 8: Administering Security.  Security is a combination Technical – covered in chap 1 Administrative Physical controls SE571 Security in Computing.
Information Security Governance and Risk Chapter 2 Part 2 Pages 69 to 100.
INTRODUCTION TO COMPUTER & NETWORK SECURITY INSTRUCTOR: DANIA ALOMAR.
Pittsburgh, PA CMMI Acquisition Module - Page M5-1 CMMI ® Sponsored by the U.S. Department of Defense © 2005 by Carnegie Mellon University This.
E-Commerce E-Commerce Security?? Instructor: Safaa S.Y. Dalloul E-Business Level Try to be the Best.
Risk Assessment What is good about the Microsoft approach to threat modeling? What is bad about it? OCTAVE…  Advantage: ___________  Disadvantage: ___________.
Risk Assessment What is good about the Microsoft approach to threat modeling? OCTAVE…  Advantage: ___________  Disadvantage: ___________ What is bad.
Dr. Mark Gaynor, Dr. Feliciano Yu, Bryan Duepner.
Keimyung University 1 Network Control Hong Taek Ju College of Information and Communication Keimyung University Tel:
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
Advanced System Security Dr. Wayne Summers Department of Computer Science Columbus State University
By: Mark Reed.  Protecting information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction.
S7-1 © 2001 Carnegie Mellon University OCTAVE SM Process 7 Conduct Risk Analysis Software Engineering Institute Carnegie Mellon University Pittsburgh,
CS457 Introduction to Information Security Systems
Errors, Fraud, Risk Management, and Internal Controls
CS 450/650 Fundamentals of Integrated Computer Security
Risk Assessment Richard Newman
RISK MANAGEMENT An Overview: NIPC Model
SEC 240 Education on your terms/tutorialrank.com.
Threat Trends and Protection Strategies Barbara Laswell, Ph. D
Cybersecurity compliance for attorneys
INFORMATION SYSTEMS SECURITY and CONTROL
Cybersecurity ATD technical
Security network management
Mohammad Alauthman Computer Security Mohammad Alauthman
Presentation transcript:

OCTAVESM Process 4 Create Threat Profiles Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213 Sponsored by the U.S. Department of Defense Phase 1: Build Asset-Based Threat Profiles Process 4: Create Threat Profiles – During this process, the analysis team consolidates the information gathered during Processes 1 through 3, selects five critical assets, and defines the security requirements and threats to those assets. Materials Required: direct display projector or overhead for slides (optional) slides for Process 4 (optional) worksheets for Process 4 Data Preparation Activities Process 4 requires data consolidation tasks prior to the workshop. One or more analysis team members can consolidate the data. It is not required that the entire team work on consolidating data. The data consolidation tasks are Group Assets by Organizational Level (D4.1) Group Security Requirements by Organizational Level and Asset (D4.2) Group Areas of Concern and Impacts by Organizational Level and Asset (D4.3) For additional guidance about the data consolidation tasks, see the detailed Process Guidelines for Process 4.

OCTAVESM Operationally Critical Threat, Asset, and Vulnerability EvaluationSM Operationally Critical Threat, Asset, and Vulnerability Evaluation and OCTAVE are service marks of Carnegie Mellon University Introduction The risk assessment process in which your organization will be participating is Operationally Critical Threat, Asset, and Vulnerability Evaluation, or OCTAVE. OCTAVE is a self-directed information security evaluation being developed by Carnegie Mellon University.

Strategy and Plan Development OCTAVE Process Phase 1 Organizational View Create Threat Profiles Assets Threats Current Practices Org. Vulnerabilities Security Req. Phase 3 Strategy and Plan Development Planning Risks Protection Strategy Mitigation Plans This slide describes the OCTAVE process and where you are in the process. Build Asset-Based Threat Profiles (Phase 1) is the organizational view. Identify Infrastructure Vulnerabilities (Phase 2) is the technological view. Develop Security Strategy and Plans (Phase 3) is strategy and plan development. This workshop is for Process 4, Create Threat Profiles. The participants in this workshop are the core analysis team members as well as any supplemental personnel. At the beginning of the workshop, the leader will make sure that everyone knows his or her role. In addition, the leader will review what will be accomplished and will make sure that all necessary materials have been gathered and are ready for use. The leader will also make sure sure that everyone knows the projected time to conduct this process and this workshop is approximately 3 - 4 hours. Tech. Vulnerabilities Phase 2 Technological View

Objectives of This Workshop To select critical assets To describe the security requirements for the critical assets To identify threats to the critical assets In this workshop, you will be generating the following: a set of critical assets the security requirements for the critical assets threats to the critical assets

Asset Something of value to the organization information systems software hardware people Select Critical Assets (A4.1) An asset is something of value to the organization. An information security risk evaluation is focused on identifying the information that is important to meeting the mission of the organization. The only way to identify the most meaningful information is to ask the people who work in the organization (all levels of staff, mission-related staff, and support staff). Assets can fall into the following categories: information – documented (paper or electronic) information or intellectual assets used to meet the mission of the organization systems – information systems that process and store information. Systems are a combination of information, software, and hardware assets. Any host, client, server, or network can be considered a system. software – software applications (operating systems, database applications, networking software, office applications, custom applications, etc.) hardware – information technology physical devices (workstations, servers, etc.) people – the people in the organization, including their skills, training, knowledge, and experience

Critical Assets The most important information assets to the organization There will be a large adverse impact to the organization if one of the following occurs: The asset is disclosed to unauthorized people. The asset is modified without authorization. The asset is lost or destroyed. Access to the asset in interrupted. You will work as a team during this activity to select five critical assets. Critical assets are those that are believed to be the most important assets to the organization. The organization will suffer a large adverse impact if the security requirements of these assets are violated. Consider the following questions when selecting critical assets: Which assets will have a large adverse impact on the organization if they are disclosed to unauthorized people? Which assets will have a large adverse impact on the organization if they are modified without authorization? Which assets will have a large adverse impact on the organization if they are lost or destroyed? Which assets will have a large adverse impact on the organization if access to them in interrupted? As you consider the questions, review the information on the following worksheets: Asset Group worksheet (W4.1) Security Requirements Group worksheet (W4.2) Areas of Concern Group worksheet (W4.3)

Identifying Critical Assets Select up to five (5) critical assets. You should discuss the questions among yourselves. Remember that each of you brings a unique perspective to the discussion. When you come to a consensus and select the critical assets, the scribe will start an Asset Profile Workbook (WK) for each critical asset. Turn to the Critical Asset Information section of each Asset Profile Workbook. In addition to selecting critical assets, you must also document your rationale for selecting those assets. To determine the rationale, you need to understand what aspect of the asset is important. This is especially true for the more complex assets (systems) where the assets have multiple characteristics. By understanding the important aspect of the asset and documenting the information, you will be better able to define security requirements and threats later in this workshop. Answering the following question might help you determine what is important about the asset: Why is the asset critical to meeting the mission of your organization? When you come to a consensus, the scribe should record the rationale for each critical asset in the Critical Asset Information section of its Asset Profile Workbook. Note that there is also a place for a description of the asset. The description should include information elicited by the above question. When you come to a consensus, the scribe should add the brief description for each critical asset in the appropriate place in the Critical Asset Information section of its workbook. For additional guidance see the Process Guidelines for Process 4.

Security Requirements Outline the qualities of an asset that are important to protect: confidentiality integrity availability Refine Security Requirements for Critical Assets (A4.2) You will work as a team during this activity to create or refine security requirements for your critical assets. Security requirements outline the qualities of an asset that are important to protect. This helps to form a basis for a protection strategy. Recall that the following are the types of security requirements examined during OCTAVE: confidentiality - the need to keep proprietary, sensitive, or personal information private and inaccessible to anyone who is not authorized to see it integrity – the authenticity, accuracy, and completeness of an asset availability – when or how often an asset must be present or ready for use

Identifying Security Requirements Describe the security requirements for each critical asset. Decide which of the security requirements is most important for each critical asset. Select a critical asset. Turn to the Security Requirements for Critical Assets section of that asset’s Asset Profile Workbook (WK). As you think about security requirements for the critical asset, review the information for that asset contained on the following worksheets: Security Requirements Group worksheet (W4.2) Areas of Concern Group worksheet (W4.3) Remember that if you selected a critical asset that was not identified as an important asset during the earlier workshops, you will not have areas of concern or security requirements information on the above worksheets, and you will have to create security requirements without the benefit of this additional information. When you come to a consensus, the scribe should write the security requirements for the critical asset in the appropriate place in the Security Requirements for Critical Assets section of the workbook. Next, you need to identify the most important security requirement for the critical asset. When you come to a consensus, the scribe should note which security requirement is most important in the Security Requirements for Critical Assets section of the workbook. Move on to the next critical asset. Continue with this activity until you have described the security requirements for all critical assets and have recorded them in the appropriate Asset Profile Workbook. For additional guidance see the Process Guidelines for Process 4.

Threat An indication of a potential undesirable event Identify Threats to Critical Assets (A4.3) A threat is an indication of a potential undesirable event. It refers to a situation where a person could do something undesirable or where a natural occurrence could cause an undesirable outcome. An alternative definition for threat is any circumstance or event with the potential to harm an information system through unauthorized access, destruction, disclosure, modification of data, and/or denial of service.

Threat Properties Asset Access (optional - only relevant for human actors) Actor Motive (optional - only relevant for human actors) Outcome In addition each threat has the following specific properties: asset – something of value to the organization actor – who or what may violate the security requirements (confidentiality, integrity, availability) of an asset motive (optional) – defines whether the actor’s intentions are deliberate or accidental access (optional) – how the asset will be accessed by the actor (network access, physical access) outcome – the immediate outcome (disclosure, modification, destruction, loss, interruption) of violating the security requirements of an asset Note that motive and access are optional. They apply only to human actors. Thus, motive and access are used for the following categories of threat: human actors using network access and human actors using physical access.

Threat Sources Human actors using network access Human actors using physical access System problems Other problems A threat profile defines the range of threats that can affect an asset. Threat profiles contain categories that are grouped according to source. The following list shows the threat categories that are considered in OCTAVE: human actors using network access - These are network-based threats to your critical assets. These threats can be deliberate or accidental in nature. human actors using physical access - These are physical threats to your critical assets. These threats can be deliberate or accidental in nature. system problems – These are problems with your IT systems. Examples include hardware defects, software defects, unavailability of related systems, viruses, malicious code, and other system-related problems. other problems – These are problems that are outside of your control. These can include natural disasters (e.g., floods and earthquakes) that can affect your organization’s IT systems, unavailability of systems maintained by other organizations, and interdependency issues. Interdependency issues include problems with infrastructure services, such as power outages, broken water pipes, and telecommunication outages.

Threat Profile A threat profile contains a range of threat scenarios for the following sources of threats: human actors using network access human actors using physical access system problems other problems The threat profile is visually represented using asset-based threat trees. A threat profile defines the range of threats that can affect an asset. Threat profiles contain categories that are grouped according to source. The following list shows the threat categories that are considered in OCTAVE: human actors using network access human actors using physical access system problems (for systems under your control) other problems (problems due to conditions out of your control) Threats can be visually represented in a tree structure. One tree exists for each threat category. Review the threat trees in the Threat and Risk Profiles section of the Asset Profile Workbook (WK). Note that there is one additional field in the trees – impact. Threat trees contain all fields with the exception of impact. A risk is the threat plus the resulting impact. The tree in this section of the workbook is actually a risk tree. However, during this activity, you will be addressing only the following properties: asset, access, actor, motive, and outcome. Thus, you will be addressing threats. Impact will be addressed during a subsequent workshop.

Human Actors - Network Access disclosure modification loss/destruction interruption accidental deliberate outside inside network asset This viewgraph shows the asset-based threat tree for human actors using network access. asset access actor motive outcome

Human Actors - Physical Access disclosure modification loss/destruction interruption accidental deliberate outside inside physical asset This viewgraph shows the asset-based threat tree for human actors using physical access. asset access actor motive outcome

System Problems asset actor outcome disclosure modification loss/destruction interruption software defects viruses hardware defects system crashes asset This viewgraph shows the asset-based threat tree for system problems (for systems under your control). asset actor outcome

Other Problems asset actor outcome disclosure modification loss/destruction interruption natural disasters third party problems power supply problems telecommunications problems or unavailability asset This viewgraph shows the asset-based threat tree for other problems (problems due to conditions out of your control). ------------------------------------------------------------------------------------------------- The following notes belong with the next slide: Select a critical asset. Turn to the Threat and Risk Profiles section of that asset’s Asset Profile Workbook (WK). Review the areas of concern that affect the critical asset (from the Areas of Concern Group worksheet). For each area of concern, decide which threat tree applies. Then decide which branches of the threat trees should be marked. Note that an area of concern could be mapped to multiple branches. When you come to a consensus, the scribe should mark the appropriate branches of the threat tree in the workbook. Complete the applicable branches for all of the critical asset’s areas of concern. Next you will need to address the unmarked branches. This activity is a gap analysis. Remember that the areas of concern were elicited during earlier workshops. It is unlikely that all threats for an asset would be elicited during those workshops. asset actor outcome

Identifying Threats Review the areas of concern for the critical asset. Use the threat profile to identify threats to each critical asset. Consider the following questions when you are reviewing the unmarked branches of a threat tree: For which remaining branches is there a non-negligible possibility of a threat to the asset? (Mark these branches in the Threat and Risk Profiles section.) For which remaining branches is there a negligible possibility or no possibility of a threat to the asset? (Do not mark these branches in the Threat and Risk Profiles section.) When you come to a consensus, the scribe should mark the appropriate branches of the threat tree in the workbook. Remember to consider all branches for each threat tree. Move on to the next critical asset. Continue with this activity until you have completed all of the threat trees for all critical assets and marked them accordingly in the appropriate Asset Profile Workbook. After you have completed all of the threat trees, look at the outcomes across the threat profile. Compare the outcomes with the security requirements and address any gaps that exist. For additional guidance see the Process Guidelines for Process 4.

Summary We have completed the following in this workshop: selected critical assets described the security requirements for the critical assets identified threats to the critical assets Summary You have completed the workshop for creating threat profiles. The next workshop is part of Phase 2 of OCTAVE (Identify Infrastructure Vulnerabilities). During Phase 2, you will start to examine your infrastructure’s technology components for weaknesses. The leader of this workshop should review what was covered during this workshop. In addition, any issues/action items that were identified during the workshop should be addressed. One action item will be to complete the data consolidation task after the workshop. In this workshop, you identified the following: a set of critical assets the security requirements for the critical assets threats to the critical assets The leader of the next workshop should make sure that everyone knows when it will occur. Data Additions After Process 4 Process 4 requires data consolidation tasks after the workshop. One or more analysis team members can consolidate the data. It is not required that the entire team work on consolidating data. The data consolidation task is Add Areas of Concern to Asset Profile Workbook (X4.1) For additional guidance about the data consolidation task, see the Process Guidelines for Process 4.