Lifecycle Models for Survivable Systems

Similar documents
Sustaining Software-Intensive Systems - A Conundrum

Revising the National Strategy for Homeland Security

Vacancy Announcement

Supply Chain Risk Management

Procedure: 3.4.1p2. (II.D.2a.) Business Continuity Planning

CMMI: The DoD Perspective

The Journey of Commercialization

8. Data Acquisition: Provide self-monitoring facility environments that become a source of research data and information.

CYBER ATTACK SCENARIO

UNCLASSIFIED. FY 2016 Base FY 2016 OCO

Cyber Resiliency FAQ

Test and Evaluation of Highly Complex Systems

Mission Threads: Bridging Mission and Systems Engineering

The State of US Voting System Security DEFCON Voting Machine Hacking Village July 2017

Bay Area UASI. Introduction to the Bay Area UASI (Urban Areas Security Initiative) Urban Shield Task Force Meeting

Integrating Software Architecture Evaluation in a DoD System Acquisition

Cybersecurity TEMP Body Example

Risk themes from ATAM data: preliminary results

Unit 2: Requirements for Continuity Planning

Overview of the New Introduction to CMMI Course and Changes to the Intermediate Concepts and Instructor Training Courses

Applying CMMI for Services (CMMI-SVC) to Health Care

UNCLASSIFIED. FY 2017 Base FY 2017 OCO. Quantity of RDT&E Articles Program MDAP/MAIS Code: 493

Reducing System Acquisition Risk with Software Architecture Analysis and Evaluation

COTS Selection and Adoption in a Small Business Environment. How Do You Downsize the Process?

Rapid Innovation Fund (RIF) Program

Keep on Keepin On Arkansas Continuity of Operations Program

Pittsburgh, /7/2014. Cyber Vulnerabilities in the Intangible World

SEVEN SEVEN. Credentialing tips designed to help keep costs down and ensure a healthier bottom line.

DOD INSTRUCTION ACCOUNTABILITY AND MANAGEMENT OF INTERNAL USE SOFTWARE (IUS)

Applying the Goal-Question-Indicator- Metric (GQIM) Method to Perform Military Situational Analysis

When and Where to Apply the Family of Architecture- Centric Methods

The CMMI Product Suite and International Standards

Lessons Learned from the MSG- 128 Study on Incremental Implementation of NATO Mission Training through Distributed Simulation Operations

Guide to the SEI Partner Network

Success through Offshore Outsourcing. Kartik Jayaraman Director Enterprise Relationships (Strategic Accounts)

School Earthquake Preparedness Guidebook

AGI Technology for EW and AD Dominance

Intelligence Operations (HMSY 1340) Online. Credit: 3 semester credit hours (3 hours lecture)

WARFIGHTER MODELING, SIMULATION, ANALYSIS AND INTEGRATION SUPPORT (WMSA&IS)

[Discussion Draft] [DISCUSSION DRAFT] SEPTEMBER 9, H. R. ll

Cyber Attack: The Department Of Defense s Inability To Provide Cyber Indications And Warning

New DoD Approaches on the Cyber Survivability of Weapon Systems

HIE Implications in Meaningful Use Stage 1 Requirements

Towards faster implementation and uptake of open government

Department of Defense DIRECTIVE

Coflight efdp Angelo Corsaro, Ph.D. Software Technologies Scientist

Why Isn t Someone Coding Yet (WISCY)? Avoiding Ineffective Requirements

Subj: INFORMATION MANAGEMENT/INFORMATION TECHNOLOGY POLICY FOR FIELDING OF COMMERCIAL OFF THE SHELF SOFTWARE

Department of Defense INSTRUCTION. SUBJECT: Physical Security Equipment (PSE) Research, Development, Test, and Evaluation (RDT&E)

Patient Safety Reporting System for Nursing Homes Patient Safety Authority Commonwealth of Pennsylvania. Government to Business (G to B)

UNCLASSIFIED. UNCLASSIFIED Army Page 1 of 7 R-1 Line #9

Title IV E Eligibility CPI Specialty Track

Department of Defense DIRECTIVE

UNCLASSIFIED. UNCLASSIFIED Navy Page 1 of 7 R-1 Line #16

Outsourced Product Development

Mission Thread Workshop (MTW): Preparation and Execution

Community Emergency Management Program

Meeting Today s Healthcare Security Challenges with Integrated Technologies

Information Technology Management

December 17, 2003 Homeland Security Presidential Directive/Hspd-8

9/10/2016. What is a Cycle? Learning Objectives

CHAMPS. Community Hazard Assessment & Mitigation Planning System. An Introduction

Human Systems Integration (HSI)

CYBER SECURITY PROTECTION. Section III of the DOD Cyber Strategy

Countering Weapons of Mass Destruction Other Transaction Agreement

ICT and Disaster Risk Reduction Division ESCAP

HealthCare IT Solutions. Supporting Medicaid from Start to Future

KSBCL/SYS 2 020/ Date: 22/03/2014. Notice for Time Extension. Sub: Information Security Management System Implementation

UNCLASSIFIED R-1 ITEM NOMENCLATURE

Carnegie Mellon University Notice

Quality Assurance (QA) Work Plan. Advance Corrections Initiative

Joint Staff J7 Cyberspace Environment Division / Joint Information Operations Range (JIOR) Overview

SCAMPI B&C Tutorial. Software Engineering Process Group Conference SEPG Will Hayes Gene Miluk Jack Ferguson

University of Pittsburgh

UNCLASSIFIED. UNCLASSIFIED Army Page 1 of 12 P-1 Line #51

John R. Harrald, Ph.D. Director, Institute for Crisis, Disaster, and Risk Management The George Washington University.

Software Architecture and Product Quality

SAFE SCHOOL ZONE EMERGENCY RESPONSE AND CRISIS MANAGEMENT FOR SCHOOLS AND COMMUNITIES

Training and Evaluation Outline Report

Training and Evaluation Outline Report

UNCLASSIFIED. UNCLASSIFIED R-1 Line Item #152 Page 1 of 15

Air Force Science & Technology Strategy ~~~ AJ~_...c:..\G.~~ Norton A. Schwartz General, USAF Chief of Staff. Secretary of the Air Force

130 FERC 61,211 UNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION

UNCLASSIFIED. UNCLASSIFIED Air Force Page 1 of 7 R-1 Line #198

Protecting US Military s Technical Advantage: Assessing the Impact of Compromised Unclassified Controlled Technical Information

Future Force Capabilities

Chapter FM 3-19

CYBERWAR: Strategic Information Warfare By Robert K. Hiltbrand Originally published Spring 1999

Outsourcing Risk Management. UniCredit Group Experience

1. Definitions. See AFI , Air Force Nuclear Weapons Surety Program (formerly AFR 122-1).

UNCLASSIFIED. UNCLASSIFIED Air Force Page 1 of 5 R-1 Line #199

Army IAMD Modular Open Systems Approach

Air Force Institute of Technology

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

Castles in the Clouds: Do we have the right battlement? (Cyber Situational Awareness)

Training and Evaluation Outline Report

OEM & Police. FY 2017 Proposed Budget Work Session. Tuesday, March 22, 2:30 4:30 pm

The best days in this job are when I have the privilege of visiting our Soldiers, Sailors, Airmen,

Joint Information Environment. White Paper. 22 January 2013

Advanced Explosive Ordnance Disposal Robotic System (AEODRS)

Transcription:

Lifecycle Models for Survivable s Rick Linger Carnegie Mellon University Pittsburgh, PA 15213-3890 Sponsored by the U.S. Department of Defense 2000 by Carnegie Mellon University Version 2 SNA Tutorial - page 1

Survivability Concepts 2000 by Carnegie Mellon University Version 1 ISW2000 - page 2

Survivability Defined Survivability is the ability of a system to fulfill its mission, in a timely manner, in the presence of attacks, failures, or accidents. No amount of security can guarantee systems will not be penetrated Survivability focus is on mission continuity under adverse conditions 2000 by Carnegie Mellon University Version 1 ISW2000 - page 3

The Three Rs of Survivability Resistance capability to deter attacks Recognition capability to recognize attacks and damage Recovery capability to provide essential services during attack and recover full services after attack 2000 by Carnegie Mellon University Version 1 ISW2000 - page 4

Survivable Network Analysis SYSTEM: Essential services Essential service usage scenarios Essential architecture components ENVIRONMENT: Intrusion strategies Intrusion usage scenarios Architecture softspots 3Rs analysis Survivability Map recommendations Compromisible architecture components 2000 by Carnegie Mellon University Version 1 ISW2000 - page 5

Survivability Impact on Traditional Development Life Cycle 2000 by Carnegie Mellon University Version 1 ISW2000 - page 6

Survivability Impact - 1 Lifecycle Activities Mission Definition Concept of Operations Key Survivability Elements Analysis of mission criticality and consequences of failure Definition of system capabilities in adverse environments Examples Estimation of cost impact of denial of service attacks Enumeration of critical mission functions that must withstand attacks Project Planning Integration of survivability into lifecycle activities and work products Identification of defensive coding techniques for implementation Definition Specification Definition of survivability requirements from mission perspective Specification of essential service and intrusion scenarios Definition of access requirements for critical system assets during attacks Definition of steps that compose critical system transactions 2000 by Carnegie Mellon University Version 1 ISW2000 - page 7

Survivability Impact - 2 Lifecycle Key Survivability Elements Examples Activities Architecture Design Implementation Testing Evolution Integration of survivability strategies into architecture definition Development and verification of survivability strategies Application of survivability coding and implementation techniques Treatment of intruders as users in testing and certification Improvement of survivability to prevent degradation over time Creation of network facilities for replication of critical data assets Correctness verification of data encryption algorithms Definition of methods to avoid buffer overflow vulnerabilities Addition of intrusion usage to usage models for statistical testing Evolution of architecture in response to changing threat environment 2000 by Carnegie Mellon University Version 1 ISW2000 - page 8

Survivability Impact Survivability Develop/Test Survivability Operations Development/ Evolution Traditional Life Cycle / Survivability Legacy Software, Survivability Strategies Testing/ Evaluation Operation/ Administration Usage/ Intrusion Usage Model Development/ Evolution Survivability Evolution 2000 by Carnegie Mellon University Version 1 ISW2000 - page 9

Survivability Impact on Contemporary Development Life Cycle 2000 by Carnegie Mellon University Version 1 ISW2000 - page 10

Contemporary Life Cycle Iteration of customer requirements, COTS market capabilities, and system architecture Customer Context Architecture and Engineering Cycle Integration Market Context Reconciliation Life cycle of continuous system evolution Iteration 1 Iteration 2 Iteration 3 Iteration 4 2000 by Carnegie Mellon University Version 1 ISW2000 - page 11

Survivability Impact Reconcile mission survivability with COTS capabilities Assess COTS vendors for survivability focus Evaluate survivability of COTS products Achieve survivability in system integration Treat architecture as survivability integrator Maintain survivability as COTS products evolve 2000 by Carnegie Mellon University Version 1 ISW2000 - page 12