CSE331: Introduction to Networks and Security Lecture 33 Fall 2002.

Slides:



Advertisements
Similar presentations
Dr. Kalpakis CMSC 421, Operating Systems. Fall 2008 URL: Security.
Advertisements

Communications of the ACM (CACM), Vol. 32, No. 6, June 1989
Lecture: Malicious Code CIS 3360 Ratan K. Guha. Malicious Code2 Overview and Reading Assignments Defining malicious logic Types Action by Viruses Reading.
CSE331: Introduction to Networks and Security Lecture 34 Fall 2002.
30/04/2015Tim S Roberts COIT13152 Operating Systems T1, 2008 Tim S Roberts.
CSE331: Introduction to Networks and Security Lecture 32 Fall 2002.
Week 6 - Friday.  What did we talk about last time?  Viruses and other malicious code.
Computer Viruses and Worms* *Referred to slides by Dragan Lojpur, Zhu Fang at Florida State University.
1 Computer Security Instructor: Dr. Bo Sun. 2 Course Objectives Understand basic issues, concepts, principles, and mechanisms in computer network security.
Section 3.2: Operating Systems Security
Secure Operating Systems Lesson 0x11h: Systems Assurance.
Security  The Security Problem  Authentication  Program Threats  System Threats  Securing Systems  Intrusion (unwanted involvement) Detection  Encryption.
Silberschatz, Galvin and Gagne  Operating System Concepts The Security Problem A system is secure iff its resources are used and accessed as.
1 Protection Protection = access control Goals of protection Protecting general objects Example: file protection in Linux.
Attacking Malicious Code: A Report to the Infosec Research Council Kim Sung-Moo.
19.1 Silberschatz, Galvin and Gagne ©2003 Operating System Concepts with Java Chapter 19: Security The Security Problem Authentication Program Threats.
Security Presented by : Qing Ma. Introduction Security overview security threats password security, encryption and network security as specific.
Security strategy. What is security strategy? How an organisation plans to protect and respond to security attacks on their information technology assets.
________________ CS3235, Nov 2002 Viruses Adapted from Pfleeger[Chap 5]. A virus is a program [fragment] that can pass on malicious code [usually itself]
Security A system is secure if its resources are used and accessed as intended under all circumstances. It is not generally possible to achieve total security.
What we will cover… Protection and Security in OS.
Silberschatz, Galvin and Gagne  Operating System Concepts Module 19: Security The Security Problem Authentication Program Threats System Threats.
Protection and Security CSCI 444/544 Operating Systems Fall 2008.
Java Security. Topics Intro to the Java Sandbox Language Level Security Run Time Security Evolution of Security Sandbox Models The Security Manager.
Copyright © 2002 ProsoftTraining. All rights reserved. Operating System Security.
Chapter 15: Security (Part 1). The Security Problem Security must consider external environment of the system, and protect the system resources Intruders.
Operating Systems Protection & Security.
Silberschatz and Galvin  Operating System Concepts Module 20: Security The Security Problem Authentication Program Threats System Threats Threat.
14.1 Silberschatz, Galvin and Gagne ©2009 Operating System Concepts with Java – 8 th Edition Chapter 14: Protection.
CMSC 414 Computer (and Network) Security Lecture 14 Jonathan Katz.
More Network Security Threats Worm = a stand-alone program that can replicate itself and spread Worms can also contain manipulation routines to perform.
Terminology Worm –A computer program that duplicates itself over computer networks. Virus –A computer program that inspects it’s environment and copies.
1.2 Security. Computer security is a branch of technology known as information security, it is applied to computers and networks. It is used to protect.
CS 3204 Operating Systems Godmar Back Lecture 26.
Security Architecture and Design Chapter 4 Part 3 Pages 357 to 377.
Protection and Security Questions answered in this lecture: How can a system authenticate a user? How are access rights specified? What are common security.
Operating system Security By Murtaza K. Madraswala.
ITIS 1210 Introduction to Web-Based Information Systems Chapter 47 How Viruses Work.
Security CS Introduction to Operating Systems.
©Ian Sommerville 2004Software Engineering Case Studies Slide 1 The Internet Worm Compromising the availability and reliability of systems through security.
Protection and Security Sarah Diesburg Operating Systems COP 4610.
Trusted OS Design and Evaluation CS432 - Security in Computing Copyright © 2005, 2010 by Scott Orr and the Trustees of Indiana University.
Crisis And Aftermath Eugene H. Spafford 이희범.  Introduction  How the worm operated  Aftermath Contents.
1 Security. 2 Linux is not secure No computer system can ever be "completely secure". –make it increasingly difficult for someone to compromise your system.
A Failure to Learn from the Past Presented by Chad Frommeyer CSC 493/593 Professors Charles E. Frank/James Walden.
Computer Security Threats CLICKTECHSOLUTION.COM. Computer Security Confidentiality –Data confidentiality –Privacy Integrity –Data integrity –System integrity.
14.1 Silberschatz, Galvin and Gagne ©2009 Operating System Concepts with Java – 8 th Edition Protection.
Understand Malware LESSON Security Fundamentals.
The Internet Worm Incident Eugene H. Spafford  Attack Format –Worm vs. Virus  Attack Specifications –Worm operation –Infection and propagaion  Topics.
INTRODUCTION TO COMPUTER & NETWORK SECURITY INSTRUCTOR: DANIA ALOMAR.
An Evening with Berferd Bill Cheswick, USENIX 1990 Presented by Chris Grier.
1 Computer Security Instructor: Dr. Bo Sun. 2 Course Objectives Understand basic issues, concepts, principles, and mechanisms in computer network security.
Page 1 Viruses. Page 2 What Is a Virus A virus is basically a computer program that has been written to perform a specific set of tasks. Unfortunately,
Security-Enhanced Linux Stephanie Stelling Center for Information Security Department of Computer Science University of Tulsa, Tulsa, OK
1 Network Security. 2 Security Services Confidentiality: protection of any information from being exposed to unintended entities. –Information content.
Security Architecture and Design Chapter 4 Part 4 Pages 377 to 416.
The Internet Worm Compromising the availability and reliability of systems through security failure.
Viruses and Other Malicious Content
Operating system Security
Official levels of Computer Security
12: Security The Security Problem Authentication Program Threats
Internet Worms, SYN DOS attack
THE ORANGE BOOK Ravi Sandhu
SECURITY IN THE LINUX OPERATING SYSTEM
Operating System Security
Security.
Operating System Concepts
Operating System Concepts
Crisis and Aftermath Morris worm.
Chapter 14: Protection.
Presentation transcript:

CSE331: Introduction to Networks and Security Lecture 33 Fall 2002

CSE331 Fall Announcements Final Exam Location –Moore 212 –Tues. 17 Dec. –8:30 – 10:30 AM

CSE331 Fall Recap Malicious Programs –Computer Virus Defenses Today: –Computer Worms –Other malicious code

CSE331 Fall Internet Worms November 2, 1988 Robert T. Morris Jr. unleashed Internet worm –Graduate student at Cornell University –Convicted in 1990 of violating Computer Fraud and Abuse Act –$10,000 fine, 3 yr. Suspended jail sentence, 400 hours of community service –Son of the chief scientist at the National Computer Security Center -- part of the National Security Agency –Today he’s a professor at MIT

CSE331 Fall Morris Worm Transmission Find user accounts on the target machine –Dictionary attack on /etc/passwd –If it found a match, it would log in and try the same username/password on other local machines Exploit bug in fingerd –Classic buffer overflow attack Exploit trapdoor in sendmail –Programmer left DEBUG mode in sendmail, which allowed sendmail to execute an arbitrary shell command string.

CSE331 Fall Morris Worm Infection Sent a small loader to target machine –99 lines of C code –It was compiled on the remote platform (cross platform compatibility) –The loader program transferred the rest of the worm from the infected host to the new target. –Used authentication! To prevent sys admins from tampering with loaded code. –If there was a transmission error, the loader would erase its tracks and exit.

CSE331 Fall Morris Worm Stealth When loader obtained full code –It put into main memory and encrypted –Original copies were deleted from disk –(Even memory dump wouldn’t expose worm) Worm periodically changed its name and process ID

CSE331 Fall Effects Resource exhaustion –Denial of service –There was a bug in the loader program that caused many copies of the worm to be spawned per host System administrators cut their network connections –Couldn’t use internet to exchange fixes! 6,000 networks were shut down or disconnected –Down for several days –Damage estimates: $100,000 — $97 Million

CSE331 Fall Worms (In General) Self-contained running programs –Unlike viruses Infection strategy more active –Exploit buffer overflows –Exploit bad password choice Defenses –Monitor system resources –Proper access control

CSE331 Fall Trapdoors A trapdoor is a secret entry point into a module –Affects a particular system Inserted during code development –Accidentally (forget to remove debugging code) –Intentionally (maintenance) –Maliciously (an insider creates a hole)

CSE331 Fall Trojan Horse A program that pretends to be do one thing when it does another –Or does more than advertised Login Prompts –Trusted path Accounting software Example: –Game that doubles as a sshd process.

CSE331 Fall Salami Attacks Programs that compute money are targets of this attack –Use subtle rounding errors –Often distribute errors among many transactions –Accumulate small amounts of money Example: –6.5% (annual) interest on $ for 31 days is $ –Instead of rounding to $0.55, round to $0.54 –Funnel the extra penny somewhere else

CSE331 Fall Covert Channels Program that leaks confidential information intentionally via secret channels. Not that hard to leak a small amount of data –A 64 bit shared key is quite small! Example channels –Adjust the formatting of output: use the “\t” character for “1” and 8 spaces for “0” –Vary timing behavior based on key

CSE331 Fall Differential Power Analysis Read the value of a DES password off of a smartcard by watching power consumption! This figure shows simple power analysis of DES encryption. The 16 rounds are clearly visible.

CSE331 Fall Defenses for Covert Channels Code review –This is an audit! Automated program analysis –Type systems that let programmers specify confidentiality labels But, not much you can do against a determined insider

CSE331 Fall Multilevel Security Department of Defense Trusted Computer System Evaluation Criteria (TCSEC) –Known as the Orange Book –Circa 1985 Multiple levels of security –Public < Classified < Secret < Top Secret

CSE331 Fall TCSEC Ratings Division (D): Minimal Protection –This division contains only one class. It is reserved for those systems that have been evaluated but that fail to meet the requirements for a higher evaluation class. Division (C): Discretionary Protection –Classes in this division provide for discretionary (need-to-know) protection and, through the inclusion of audit capabilities, for accountability of subjects and the actions they initiate.

CSE331 Fall TCSEC Ratings Division (B): Mandatory Protection –The notion of a TCB that preserves the integrity of sensitivity labels and uses them to enforce a set of mandatory access control rules is a major requirement in this division. Systems in this division must carry the sensitivity labels with major data structures in the system. The system developer also provides the security policy model on which the TCB is based and furnishes a specification of the TCB. Evidence must be provided to demonstrate that the reference monitor concept has been implemented.

CSE331 Fall TCSEC Ratings Division (A): Verified Protection –This division is characterized by the use of formal security verification methods to assure that the mandatory and discretionary security controls employed in the system can effectively protect classified or other sensitive information stored or processed by the system. Extensive documentation is required to demonstrate that the TCB meets the security requirements in all aspects of design, development and implementation.