Chapter 23: Vulnerability Analysis

Slides:



Advertisements
Similar presentations
Chapter 3 (Part 1) Network Security
Advertisements

A Taxonomy of Computer Program Security Flaws C. E. Landwehr, A. R. Bull, J. P. McDermott and W.S. Choi -- Presented by: Feng Hui Luo ACM Computing Surveys,
Lecture 14 Program Flaws CS 450/650 Fundamentals of Integrated Computer Security Slides are modified from Csilla Farkas and Brandon Phillips.
1 Vulnerability Analysis CSSE 490 Computer Security Mark Ardis, Rose-Hulman Institute April 26, 2004.
CMSC 414 Computer and Network Security Lecture 24 Jonathan Katz.
1 Building with Assurance CSSE 490 Computer Security Mark Ardis, Rose-Hulman Institute May 10, 2004.
Chap 3: Program Security.  Programming errors with security implications: buffer overflows, incomplete access control  Malicious code: viruses, worms,
Security Architecture Dr. Gabriel. Security Database security: –degree to which data is fully protected from tampering or unauthorized acts –Full understanding.
Vulnerability Analysis
Information Systems Security Computer System Life Cycle Security.
Chapter 13 Processing Controls. Operating System Integrity Operating system -- the set of programs implemented in software/hardware that permits sharing.
CSCE 201 Attacks on Desktop Computers: Malicious Code Hardware attacks.
CS 325: Software Engineering April 14, 2015 Software Security Security Requirements Software Security in the Life Cycle.
Analyzing and Detecting Network Security Vulnerability Weekly report 1Fan-Cheng Wu.
Lecture 14 Overview. Program Flaws Taxonomy of flaws: – how (genesis) – when (time) – where (location) the flaw was introduced into the system 2 CS 450/650.
CSCE 522 Lecture 12 Program Security Malicious Code.
Operating system Security By Murtaza K. Madraswala.
Program Security Week-2. Programming Fault: When a human makes a mistake, called an error, in performing some software activity, the error may lead to.
Software Security and Security Engineering (Part 2)
Chapter 1 Ethical Hacking Overview. Objectives After reading this chapter and completing the exercises, you will be able to: Describe the role of an ethical.
Program Security Malicious Code Program Security Malicious Code.
APPLICATION PENETRATION TESTING Author: Herbert H. Thompson Presentation by: Nancy Cohen.
1 IS 2150 / TEL 2810 Information Security & Privacy James Joshi Associate Professor, SIS Lecture 9 Oct 30, 2013 Authentication, Identity Vulnerability.
14.1/21 Part 5: protection and security Protection mechanisms control access to a system by limiting the types of file access permitted to users. In addition,
Malicious Logic and Defenses. Malicious Logic Trojan Horse – A Trojan horse is a program with an overt (documented or known) effect and covert (undocumented.
CPSC 6126 Computer Security Information Assurance.
1 IS 2150 / TEL 2810 Introduction to Security James Joshi Associate Professor, SIS Lecture 9 Nov 25, 2008 Authentication, Identity Malicious Code, Vulnerability.
Unix Security Assessing vulnerabilities. Classifying vulnerability types Several models have been proposed to classify vulnerabilities in UNIX-type Oses.
Vulnerability Analysis Stefanie Wilcox. Vulnerabilities zHardware zSoftware zData.
Database Security and Auditing: Protecting Data Integrity and Accessibility Chapter 1 Security Architecture.
1 Assurance, Malicious Code Vulnerability Analysis Nov 30, 2006 Lecture 9 IS 2150 / TEL 2810 Introduction to Security.
Introduction to Security Dr. John P. Abraham Professor UTPA.
Vulnerability Analysis
14.1 Silberschatz, Galvin and Gagne ©2009 Operating System Concepts with Java – 8 th Edition Protection.
Design Principles and Common Security Related Programming Problems
Chapter 23: Vulnerability Analysis Dr. Wayne Summers Department of Computer Science Columbus State University
Chapter 19: Building Systems with Assurance Dr. Wayne Summers Department of Computer Science Columbus State University
Exam 2 Review CS461/ECE422 Fall Exam guidelines Same as for first exam A single page of supplementary notes is allowed  8.5x11. Both sides. Write.
Writing Secure Programs. Program Security CSCE Farkas/Eastman - Fall Program Flaws Taxonomy of flaws: how (genesis) when (time) where (location)
Chapter 29: Program Security Dr. Wayne Summers Department of Computer Science Columbus State University
Vulnerability Analysis Dr. X. Computer system Design Implementation Maintenance Operation.
Software Security Q: What does it mean to say that a program is secure? A: There is a sufficient amount of trust that the program maintains _____________,
November 1, 2004Introduction to Computer Security ©2004 Matt Bishop Slide #20-1 Chapter 20: Vulnerability Analysis Background Penetration Studies Example.
June 1, 2004Computer Security: Art and Science ©2004 Matt Bishop Slide #23-1 Chapter 23: Vulnerability Analysis Background Penetration Studies Example.
Chapter 24: Auditing Dr. Wayne Summers Department of Computer Science Columbus State University
Vulnerability Analysis
Chapeter20. Vulnerability Analysis
CSCE 548 Secure Software Development Risk-Based Security Testing
Chapter 23: Vulnerability Analysis
Chap 20. Vulnerability Analysis
Software Security Testing
Operating system Security
CSE565: Computer Security Lecture 27 Program Security
Network security.
Text Book: Security in Computing
Chapter 19: Building Systems with Assurance
Program Security Jagdish S. Gangolly School of Business
Chapter 17: Confinement Problem
جلسه دوم مبانی امنیت (3) ارائه دهنده: حسین محمدحسن زاده 15 اسفند 1391
Chapter 28: User Security
VA/PT.
Chapter 22: Malicious Logic
Chapter 29: Program Security
Advanced System Security
Vulnerability Analysis
IS 2150 / TEL 2810 Information Security & Privacy
Chapter 14: Protection.
Presentation transcript:

Chapter 23: Vulnerability Analysis Dr. Wayne Summers Department of Computer Science Columbus State University Summers_wayne@colstate.edu http://csc.colstate.edu/summers

Penetration Studies Test for evaluating strengths of all security controls on the computer system (tiger team attack, red team attack) Authorized attempt to violate constraints stated in security policy Layering of Tests External attacker with no knowledge of system External attacker with access to the system Internal attacker with access to the system

Penetration Studies Flaw Hypothesis Methodology Information Gathering Flaw Testing Flaw Generalization Flaw Elimination

Vulnerability Classification Goal of vulnerability analysis is to develop methodologies that provide Ability to specify, design, and implement a computer system without vulnerabilities Ability to analyze a computer system to detect vulnerabilities Ability to address any vulnerabilities introduced during the operation of the computer system Ability to detect attempted exploitations of vulnerabilities

Frameworks Research Into Secure Operating Systems (RISOS) – classified flaws Incomplete parameter validation (buffer overflow) Inconsistent parameter validation Implicit sharing of privileged/confidential data Asynchronous validation/inadequate serialization (race conditions/time-of-check to time-of-use) Inadequate identification/authentication/authorization Violable prohibition/limit (bound conditions) Exploitable logic error

Frameworks Protection Analysis Model (pattern-directed protection evaluation) Improper protection domain initialization and enforcement Improper choice of initial protection domain Improper isolation of implementation detail Improper change Improper naming Improper deallocation or deletion Improper validation Improper sychronization Improper indivisibility Improper sequencing Improper choice of operand / operation

Frameworks NRL Taxonomy Flaws by genesis Intentional Malicious Trojan horse Trapdoor Logic/time bomb Nonmalicious Covert channel Other Unintentional (RISOS taxonomy)

Frameworks NRL Taxonomy Flaws by time of introduction Development Requirement/specification/design Source code Object code Maintenance Operation

Frameworks NRL Taxonomy Flaws by location Software Hardware Operating System System initialization Memory management Process management/scheduling Device management File management Identification/authentication Other/unknown Support Privileged utilities Unprivileged utilities Application Hardware