Cyber Physiology Analysis Framework Concept

Slides:



Advertisements
Similar presentations
Chapter 24 Quality Management.
Advertisements

Pat Langley Computational Learning Laboratory Center for the Study of Language and Information Stanford University, Stanford, California USA
Pat Langley Computational Learning Laboratory Center for the Study of Language and Information Stanford University, Stanford, California USA
Saumya Debray The University of Arizona Tucson, AZ
ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
Lecture # 2 : Process Models
Alternate Software Development Methodologies
CHESS: A Systematic Testing Tool for Concurrent Software CSCI6900 George.
Dynamic Service Composition with QoS Assurance Feb , 2009 Jing Dong UTD Farokh Bastani UTD I-Ling Yen UTD.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5.
Formal Methods 1. Software Engineering and Formal Methods  Every software engineering methodology is based on a recommended development process  proceeding.
Proceso kintamybių modeliavimas Modelling process variabilities Donatas Čiukšys.
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
Annual SERC Research Review, October 5-6, By Jennifer Bayuk Annual SERC Research Review October 5-6, 2011 University of Maryland Marriott Inn and.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Software Testing.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
COP 4620 / 5625 Programming Language Translation / Compiler Writing Fall 2003 Lecture 10, 10/30/2003 Prof. Roy Levow.
1 ECE 453 – CS 447 – SE 465 Software Testing & Quality Assurance Instructor Kostas Kontogiannis.
Copyright 2004 Compsim LLC The Right Brain Architecture of a Holonic Manufacturing System Application of KEEL ® Technology to Holonic Manufacturing Systems.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
Auther: Kevian A. Roudy and Barton P. Miller Speaker: Chun-Chih Wu Adviser: Pao, Hsing-Kuo.
1 Introduction to Software Engineering Lecture 1.
SEMINAR WEI GUO. Software Visualization in the Large.
Eureka: A Framework for Enabling Static Malware Analysis the 13 th European Symposium on Research in Computer Security (ESORICS) conference 2008 WANG Zhi.
Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University July 21, 2008WODA.
Geoinformatics 2006 University of Texas at El Paso Evaluating BDI Agents to Integrate Resources Over Cyberinfrastructure Leonardo Salayandía The University.
Understanding the Behavior of Java Programs Tarja Systa Software Systems Lab. Tampere Univ. Sookmyung Women’s Univ. PSLAB Choi, yoon jeong.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
HNDIT23082 Lecture 06:Software Maintenance. Reasons for changes Errors in the existing system Changes in requirements Technological advances Legislation.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
Visual Studio Team System overview Pierre Greborio Software Architect – PEWay Microsoft MVP – Solutions Architect.
A Binary Agent Technology for COTS Software Integrity Anant Agarwal Richard Schooler InCert Software.
1 CEN 4020 Software Engineering PPT4: Requirement analysis.
Application Development in Engineering Optimization with Matlab and External Solvers Aalto University School of Engineering.
2000 Research Overview Dr. Kim Mens Programming Technology Lab Vrije Universiteit Brussel.
Viewpoint Modeling and Model-Based Media Generation for Systems Engineers Automatic View and Document Generation for Scalable Model- Based Engineering.
Software Design Process. What is software? mid-1970s executable binary code ‘source code’ and the resulting binary code 1990s development of the Internet.
SOFTWARE TESTING TRAINING TOOLS SUPPORT FOR SOFTWARE TESTING Chapter 6 immaculateres 1.
CIS 375 Bruce R. Maxim UM-Dearborn
Stony Brook University Data Strategy
16CS202 & Software Engineering
Business process management (BPM)
Component and Deployment
Requirements Engineering
Malware Reverse Engineering Process
Business System Development
Defeat Tomorrow’s Threats Today
Computer Aided Software Engineering (CASE)
Business process management (BPM)
Malware Reverse Engineering Process
Active Cyber Security, OnDemand
A brief overview of the contribution
Week 10: Object Modeling (1)Use Case Model
Business System Development
UML dynamic Modeling (Behavior Diagram)
Recall The Team Skills Analyzing the Problem (with 5 steps)
Vanquishing the Measurement Dragon
Speech Capture, Transcription and Analysis App
Chapter 13 Quality Management
Analysis models and design models
VUzzer: Application-aware Evolutionary Fuzzing
Dynamic Program Analysis
Lecture 06:Software Maintenance
Department of Computer Science Abdul Wali Khan University Mardan
Concepts & Thoughts on Operational Resiliency (Feb 11)
Detecting Attacks Against Robotic Vehicles:
Presentation transcript:

Cyber Physiology Analysis Framework Concept II.F Summary Slides Vision: Create an operational framework for automated identification of malware behavior, function, and intent, even those with previously unseen capabilities. Innovative Claims: A malware trait library that describes the discrete functions and behaviors of malware through mathematical representations, rule sets, and descriptions. A library that codifies complex patterns within malware that indicates aggregate functions and behaviors. This is the heart of what is missing today. Runtime behavior tracing, physical memory reconstruction and dataflow tracing for automated, and more efficient code execution and analysis. Visual representations of malware that allow for easy interaction and understanding of the malware behaviors, functions, and intent. Through analyst views and the Cyber Physiology Profile Reasoning models that automatically identify unknown traits and patterns and can determine malwares behavior, function, and intent of previously unseen specimens. Advanced and automated static analysis techniques to normalize binary logic extracted from various sources that will enable trigger and logic dependency analyses to drive a new form of statically-informed dynamic path exploration. Sources include packed binaries, memory dumps, or embedded within data content

Cyber Physiology Analysis Framework Contract/Proposal Specifics Intellectual Property – No proprietary claim on proposed deliverables Data Rights Summary – Unlimited government data rights. Deliverables: Specimen Collection Harvesters for Windows and Linux Malware Traits Library for Windows and Linux Malware Genomes Library for Windows and Linux Prototype Static Memory and Runtime Tracer for Data Flow analysis and increased code branch execution Prototype Belief Engine for automated analysis of malware (even of unknown types)

Cyber Physiology Analysis Framework Schedule/Cost Phase 1 Period 1a (base) $2,601,202M Period 1b (Option 1) $2,659,929M Total Phase 1 $5,261,131M Phase 2 Period 2a (Option 2) $2,251,993M Period 2b (Option 3) $1,806,061M Total Phase 2 $4,058,054M Program Totals $9,319,185M Proposed Contract Type: Cost Plus Fixed Fee

Cyber Physiology Analysis Framework Complete Automated Malware Enumeration Malware analysis is very Manual, Difficult, and Slow Main Achievement: Automatically Determine Malware Behavior, Function, and Intent through: -Traits Library – mathematical representations of function and behavior -Genomes Library – Complex patterns of traits that connote aggregate behavior and functions -Data Flow Resolution – through integrating static memory and runtime tracing -Probability Models – Define new traits and patterns automatically based on data models How it Works: Combination of static memory and runtime tracing captures malware low-level data, compared against traits and patterns libraries, automated over time using maturing data-sets and probability reasoning Assumptions and Limitations: Highly modular malware limits analysis Analysis systems could be corrupted Malware analysis of 40 per week by a good analyst to 10,000+ per day Discern intent in minutes rather than days. Malware understanding requires no skill in reverse engineering or malware analysis STATUS QUO QUANTITATIVE IMPACT Need mathematical representations Of behavior and function Traits Library – mathematical Representations of code function Genomes Library – patterns of traits that connote complex behavior and Function Automated Analysis using probability Models Data Flow Resolution Malware Physiology Profiles NEW INSIGHTS Complex patterns can represent behavior END-OF-PHASE GOAL Malware analysis not just about code but data flow Automation likely requires probability Net Defense and Mission Assurance are not achievable without a scalable and insightful malware analysis capability