Protection & Security Introduction to Operating Systems: Module 16.

Slides:



Advertisements
Similar presentations
Protection Goals of Protection Domain of Protection Access Matrix
Advertisements

Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition, Chapter 14: Protection.
30/04/2015Tim S Roberts COIT13152 Operating Systems T1, 2008 Tim S Roberts.
Informationsteknologi Thursday, October 11, 2007Computer Systems/Operating Systems - Class 161 Today’s class Security.
6/2/2015B.Ramamurthy1 Security B.Ramamurthy. 6/2/2015B.Ramamurthy2 Computer Security Collection of tools designed to thwart hackers Became necessary with.
Protection. Goals of Protection Operating system consists of a collection of objects, hardware or software Each object has a unique name and can be accessed.
Bilkent University Department of Computer Engineering
1999 Chapter 8-Protection Goals of Protection Domain of Protection Access Matrix Implementation of Access Matrix Revocation of Access Rights Capability-Based.
Reasons for Protection n Prevent users from accessing information they shouldn’t have access to. n Ensure that each program component uses system resources.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition, Chapter 14: Protection.
U NIVERSITY OF M ASSACHUSETTS, A MHERST Department of Computer Science Emery Berger University of Massachusetts, Amherst Operating Systems CMPSCI 377 Lecture.
Security Chapter 15. Computer and Network Security Requirements Confidentiality –Requires information in a computer system only be accessible for reading.
Chapter 14: Protection.
Chapter 14: Protection.
Silberschatz, Galvin and Gagne ©2013 Operating System Concepts – 9 th Edition Chapter 14: Protection.
Dr. Kalpakis CMSC 421, Operating Systems. Fall 2008 URL: Protection.
1 Kyung Hee University Prof. Choong Seon HONG Network Control.
Page 19/4/2015 CSE 30341: Operating Systems Principles Raid storage  Raid – 0: Striping  Good I/O performance if spread across disks (equivalent to n.
Operating Systems Protection & Security.
U NIVERSITY OF M ASSACHUSETTS, A MHERST Department of Computer Science Emery Berger University of Massachusetts, Amherst Operating Systems CMPSCI 377 Lecture.
14.1 Silberschatz, Galvin and Gagne ©2009 Operating System Concepts with Java – 8 th Edition Chapter 14: Protection.
Protection.
14.1 Silberschatz, Galvin and Gagne ©2005 Operating System Concepts Chapter 14: Protection Goals of Protection Principles of Protection Domain of Protection.
29.1 Lecture 29 Security I Based on the Silberschatz & Galvin’s slides And Stallings’ slides.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition, Chapter 14: Protection.
Chapter 14: Protection Silberschatz, Galvin and Gagne ©2005 AE4B33OSS Chapter 14: Protection Goals of Protection Principles of Protection Domain.
Silberschatz, Galvin, and Gagne  Applied Operating System Concepts Module 18: Protection Goals of Protection Domain of Protection Access Matrix.
Silberschatz, Galvin and Gagne  Operating System Concepts Chapter 18: Protection Goals of Protection Objects and Domains Access Matrix Implementation.
14.1 Silberschatz, Galvin and Gagne ©2009 Operating System Concepts with Java – 8 th Edition Chapter 14: Protection.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition, Protection (Chapter 14)
Cosc 4740 Chapter 13: Protection. Goals of Protection Operating system consists of a collection of objects, hardware or software Each object has a unique.
Protection Nadeem Majeed Choudhary
CE Operating Systems Lecture 21 Operating Systems Protection with examples from Linux & Windows.
Modul ke: Fakultas Program Studi Proteksi SISTEM OPERASI Misbahul Fajri, ST., MTI. 14 FASILKOM Teknik Informatika.
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,
1 Chapter 9 Intruders. 2 Outline Intruders –Intrusion Techniques –Password Protection –Password Selection Strategies –Intrusion Detection Statistical.
Chapter 14: Protection Silberschatz, Galvin and Gagne ©2005 Operating System Concepts – 7 th Edition, Apr 11, 2005 Chapter 14: Protection Goals.
Chapter 14: Protection Silberschatz, Galvin and Gagne ©2005 Operating System Concepts – 7 th Edition, Apr 11, 2005 Goals of Protection Operating.
Chapter 14: Protection Silberschatz, Galvin and Gagne ©2005 Operating System Concepts Goals of Protection Operating system consists of a collection.
Silberschatz, Galvin and Gagne ©2013 Operating System Concepts – 9 th Edition Chapter 14: Protection.
11.1 CSE Department MAITSandeep Tayal 11: Protection Goals of Protection Domain of Protection Access Matrix Implementation of Access Matrix Revocation.
INTRODUCTION TO COMPUTER & NETWORK SECURITY INSTRUCTOR: DANIA ALOMAR.
Computer threats, Attacks and Assets upasana pandit T.E comp.
CSE Operating System Principles Protection.
1 Security Chapter Information Assurance and Security Confidentiality  Not available or visible to unauthorized parties Integrity  Only modifiable.
18.1 Silberschatz, Galvin and Gagne ©2003 Operating System Concepts with Java Chapter 18: Protection Goals of Protection Domain of Protection Access Matrix.
Chapter 17: System Protection Silberschatz, Galvin and Gagne ©2005 Operating System Concepts Chapter 17: Protection Goals of Protection Principles.
Saurav Karmakar. Chapter 14: Protection  Goals of Protection  Principles of Protection  Domain of Protection  Access Matrix  Implementation of Access.
Operating Systems Protection Alok Kumar Jagadev.
Chapter 14: System Protection
Operating System Concepts
Chapter 14: Protection.
Chapter 14: Protection.
CE Operating Systems Lecture 21
Chapter 14: Protection.
Chapter 14: Protection.
Chapter 14: Protection.
Chapter 14: Protection.
Chapter 14: Protection.
Chapter 14: Protection.
Chapter 14: Protection.
Protection and Security
Chapter 14: Protection.
Chapter 14: Protection.
Chapter 14: Protection.
Operating System Concepts
Presentation transcript:

Protection & Security Introduction to Operating Systems: Module 16

Protection & Security Security policy  Who has access to information?  Access matrix Protection mechanism  How is the security policy enforced?  Authentication mechanism External: maps actual user to logical user Internal authentication: maps process to (user) access rights  Authorization mechanism Determines if logical user has access to computer –An implementation of an access matrix

Computer Security Prevention of unauthorized access to computer resources The collection of tools used impose security  Became necessary with the introduction of the computer  Today automated tools are used

Network Security Protect data during transmission Includes telephone transmission and local area networks

Computer Security Requirements Secrecy  information in a computer system be accessible for reading by authorized parties only Integrity  assets can be modified by authorized parties only Availability  assets should be available to authorized parties

Types of Threats: Interruption An asset of the system is destroyed of becomes unavailable or unusable Destruction of hardware Cutting of a communication line Disabling the file management system

Types of Threats: Interception An unauthorized party gains access to an asset Wiretapping to capture data in a network Illicit copying of files or programs

Types of Threats: Modification An unauthorized party not only gains access but tampers with an asset Changing values in a data file Altering a program so that it performs differently Modifying the content of messages being transmitted in a network

Types of Threats: Fabrication An unauthorized party inserts counterfeit objects into the system Insertion of spurious messages in a network Addition of records to a file

Computer System Assets Hardware  threats include accidental and deliberate damage Software  threats include deletion, alteration, damage  backups of the most recent versions can maintain high availability

Computer System Assets Data  involves files  threats include unauthorized reading of data  statistical analysis can lead to determination of individual information which threatens privacy

Computer System Assets Communication Lines and Networks  threats include eavesdropping and monitoring  a telephone conversion, an electronic mail message, and a transferred file are subject to these threats  encryption masks the contents of what is transferred so even if obtained by someone, they would be unable to extract information

Computer System Assets Communication Lines and Networks  masquerade takes place when one entity pretends to be a different entity  message stream modification means that some portion of a legitimate message is altered, delayed, or reordered  denial of service prevents or inhibits the normal use or management of communications facilities  disable network or overload it with messages

Potential Targets for Security Attacks Any communication links  insert and capture transmission  observe transmission Hardware  modifications  gain access  monitor the electromagnetic emanations

Attacks from Intruders Real and growing problem Globalization Move to client/server architecture  companies have traditionally key data on mainframes or stand-alone PCs where it is easy to guard Cracker’s steep learning curve  crackers share information

Authentication External (user) authentication  Uncover a malicious masquerade  Password  ID badge  Retina scan  Network authentication Internal authorization (resource protection)  Confinement  Allocating rights

Techniques for Learning Passwords Try default password used with standard accounts shipped with computer Exhaustively try all short passwords Try words in dictionary or a list of likely passwords Collect information about users and use these items as passwords

Techniques for Learning Passwords Try user’s phone numbers, social security numbers, and room numbers Try license plate numbers Use a Trojan horse to bypass restrictions on access Tap the line between a remote user and the host system

ID Provides Security Determines whether the user is authorized to gain access to a system Determines the privileges accorded to the user  guest or anonymous accounts have mover limited privileges than others ID is used for discretionary access control  a user may grant permission to files to others by ID

Password Selection Strategies Computer generated passwords  users have difficulty remembering them  need to write it down  have history of poor acceptance Eliminate guessable passwords while allowing the user to select a password that is memorable

Password Selection Strategies Reactive password checking strategy  system periodically runs its own password cracker to find guessable passwords  system cancels passwords that are guessed and notifies user  consumes resources to do this  hacker can use this on their own machine with a copy of the password file

Password Selection Strategies Proactive password checker  the system checks at the time of selection if the password is allowable  with guidance from the system users can select memorable passwords that are difficult to guess

Intrusion Detection Assume the behavior of the intruder differs from the legitimate user Statistical anomaly detection  collect data related to the behavior of legitimate users over a period of time  statistical tests are used to determine if the behavior is not legitimate behavior  attempt to define normal, or proper behavior

Intrusion Detection Rule-based detection  rules are developed to detect deviation form previous usage pattern  expert system searches for suspicious behavior  attempt to define proper behavior

Intrusion Detection Audit record  native audit records  all operating systems include accounting software that collects information on user activity  detection-specific audit records  collection facility can be implemented that generates audit records containing only that information required by the intrusion detection system

Protection Domain Structure Access-right = where rights-set is a subset of all valid operations that can be performed on the object. A Protection Domain = a set of access-rights

Domain Implementation (UNIX) System consists of 2 domains:  User  Supervisor UNIX  Domain = user-id  Domain switch accomplished via file system.  Each file has associated with it a domain bit (setuid bit).  When file is executed and setuid = on, then user-id is set to owner of the file being executed. When execution completes user-id is reset.

Domain Implementation (Multics) Let D i and D j be any two domain rings. Inner rings have greater authority than outer rings Calls to inner ring functions cause an authorization check If j < I  D i  D j Multics Rings

Access Matrix View protection as a matrix (access matrix) Rows represent domains Columns represent objects Access(i, j) is the set of operations that a process executing in Domain i can invoke on Object j

Access Matrix

Use of Access Matrix If a process in Domain D i tries to do “op” on object O j, then “op” must be in the access matrix. Can be expanded to dynamic protection.  Operations to add, delete access rights.  Special access rights:  owner of O i  copy op from O i to O j  control – D i can modify D j access rights  transfer – switch from domain D i to D j

Use of Access Matrix (Cont.) Access matrix design separates mechanism from policy.  Mechanism  Operating system provides access-matrix + rules.  If ensures that the matrix is only manipulated by authorized agents and that rules are strictly enforced.  Policy  User dictates policy.  Who can access what object and in what mode.

Implementation of Access Matrix Each column = Access-control list for one object Defines who can perform what operation.  Domain 1 = Read, Write  Domain 2 = Read  Domain 3 = Read Each Row = Capability List (like a key) Fore each domain, what operations allowed on what objects. Object 1 – Read Object 4 – Read, Write, Execute Object 5 – Read, Write, Delete, Copy

Access Matrix With Domains as Objects

Revocation of Access Rights Access List – Delete access rights from access list.  Simple  Immediate Capability List – Scheme required to locate capability in the system before capability can be revoked.  Reacquisition  Back-pointers  Indirection  Keys

Capabilities A capability is an pair Each process possesses a table of capabilities It can only perform an action on an object if it possesses a capability which allows that action This corresponds to an entry in the access matrix, but each process has its own domain

Capability-Based Systems Mach OS (foundation of Macintosh OS X)  Uses ports as capabilities  One thread can manipulate another if it is able to send a message to the target threads appropriate port  Each thread has multiple ports, which accepts messages of a particular type  Ports are OS objects, allocated by request Windows NT  Handles are associated with access rights A process may only access an executive object to which it has a handle; handles are allocated by the OS