Protection and Security Protection is any mechanism for controlling the access of processes to the resources of a computer system. This mechanism must.

Slides:



Advertisements
Similar presentations
Operating System Security
Advertisements

1 cs691 chow C. Edward Chow Confidentiality Policy CS691 – Chapter 5 of Matt Bishop.
Jan. 2014Dr. Yangjun Chen ACS Database security and authorization (Ch. 22, 3 rd ed. – Ch. 23, 4 th ed. – Ch. 24, 6 th )
CMSC 414 Computer (and Network) Security Lecture 13 Jonathan Katz.
Access Control Methodologies
Title of Selected Paper: Design and Implementation of Secure Embedded Systems Based on Trustzone Authors: Yan-ling Xu, Wei Pan, Xin-guo Zhang Presented.
Database Management System
Access Control Intro, DAC and MAC System Security.
6/2/2015B.Ramamurthy1 Security B.Ramamurthy. 6/2/2015B.Ramamurthy2 Computer Security Collection of tools designed to thwart hackers Became necessary with.
Security Fall 2009McFadyen ACS How do we protect the database from unauthorized access? Who can see employee salaries, student grades, … ? Who can.
Security Fall 2006McFadyen ACS How do we protect the database from unauthorized access? Who can see employee salaries, student grades, … ? Who can.
CS-550 (M.Soneru): Protection and Security - 1 [SaS] 1 Protection and Security.
1 CSE 380 Computer Operating Systems Instructor: Insup Lee and Dianna Xu University of Pennsylvania Fall 2003 Lecture Note: Protection Mechanisms.
User Domain Policies.
Lecture 7 Access Control
Distributed Computer Security 8.2 Discretionary Access Control Models - Sai Phalgun Tatavarthy.
Lecture slides prepared for “Computer Security: Principles and Practice”, 2/e, by William Stallings and Lawrie Brown, Chapter 4 “Overview”.
7-Access Control Fundamentals Dr. John P. Abraham Professor UTPA.
CMSC 414 Computer and Network Security Lecture 19 Jonathan Katz.
D ATABASE S ECURITY Proposed by Abdulrahman Aldekhelallah University of Scranton – CS521 Spring2015.
Operating Systems Protection & Security.
CS426Fall 2010/Lecture 191 Computer Security CS 426 Lecture 19 Discretionary Access Control.
© G. Dhillon, IS Department Virginia Commonwealth University Principles of IS Security Formal Models.
Switch off your Mobiles Phones or Change Profile to Silent Mode.
Session 2 - Security Models and Architecture. 2 Overview Basic concepts The Models –Bell-LaPadula (BLP) –Biba –Clark-Wilson –Chinese Wall Systems Evaluation.
Security+ All-In-One Edition Chapter 19 – Privilege Management Brian E. Brzezicki.
Computer Security: Principles and Practice First Edition by William Stallings and Lawrie Brown Lecture slides by Lawrie Brown Chapter 4 – Access Control.
G53SEC 1 Access Control principals, objects and their operations.
Li Xiong CS573 Data Privacy and Security Access Control.
CE Operating Systems Lecture 21 Operating Systems Protection with examples from Linux & Windows.
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,
UNIX System Protection. Unix History Developed by Dennis Ritchie and Ken Thompson at AT&T Bell Labs Adapted some ideas from the Multics project in 1969.
Academic Year 2014 Spring Academic Year 2014 Spring.
COEN 350: Network Security Authorization. Fundamental Mechanisms: Access Matrix Subjects Objects (Subjects can be objects, too.) Access Rights Example:
Access Control Lesson Introduction ●Understand the importance of access control ●Explore ways in which access control can be implemented ●Understand how.
14.1 Silberschatz, Galvin and Gagne ©2009 Operating System Concepts with Java – 8 th Edition Protection.
Access Control: Policies and Mechanisms Vinod Ganapathy.
Privilege Management Chapter 22.
Computer Security: Principles and Practice
Database Management Systems, 2 nd Edition, R. Ramakrishnan and J. Gehrke1 Security Lecture 17.
Computer Science and Engineering Computer System Security CSE 5339/7339 Session 16 October 14, 2004.
LINUX Presented By Parvathy Subramanian. April 23, 2008LINUX, By Parvathy Subramanian2 Agenda ► Introduction ► Standard design for security systems ►
CSE Operating System Principles Protection.
Database Security. Introduction to Database Security Issues (1) Threats to databases Loss of integrity Loss of availability Loss of confidentiality To.
Database Security Database System Implementation CSE 507 Some slides adapted from Navathe et. Al.
Access Controls Mandatory Access Control by Sean Dalton December 5 th 2008.
PREPARED BY: MS. ANGELA R.ICO & MS. AILEEN E. QUITNO (MSE-COE) COURSE TITLE: OPERATING SYSTEM PROF. GISELA MAY A. ALBANO PREPARED BY: MS. ANGELA R.ICO.
22 feb What is Access Control? Access control is the heart of security Definitions: * The ability to allow only authorized users, programs or.
IST 210 Security. IST 210 Introduction to DB Security Secrecy: Users should not be able to see things they are not supposed to. E.g., A student can’t.
Database System Implementation CSE 507
Protection and Security
Access Control Model SAM-5.
Access Control CSE 465 – Information Assurance Fall 2017 Adam Doupé
Protection and Security
Chapter 14: Protection Modified by Dr. Neerja Mhaskar for CS 3SH3.
Chapter 14: System Protection
Computer Data Security & Privacy
Chapter 14: Protection.
Protection and Security
Chapter 14: Protection.
CE Operating Systems Lecture 21
UNIX System Protection
OS Access Control Mauricio Sifontes.
Chapter 14: Protection.
Chapter 14: Protection.
Protection and Security
Access Control.
Computer Security Access Control
Chapter 14: Protection.
Presentation transcript:

Protection and Security Protection is any mechanism for controlling the access of processes to the resources of a computer system. This mechanism must provide a means for specification of the control to be imposed and a means of enforcement. Security ensures user authentication preventing malicious destruction or alteration of the information stored in a computer system.

Protection A general protection system may be subdivided in three levels  models  policies  mechanisms

Models The protection model defines the subjects, the objects to which the subjects may access and the access rights, that is the operations by which subjects can access to objects. The subjects are the active part of the system (processes) The objects are the passive part of the system (physical and logical resources). A subject may have access rights either to objects or other subjects (a process can control other processes).

A process may have different access rights to objects, depending on what task is currently doing. The particular set of rigts a process has at any given time is referred to as its protection domain.

Policies The protection policy defines the rules by which the subjects can access to the objects: Discretional Access Control (DAC). The owner of an object controls the access rigthts for that object. ( UNIX). Mandatory Access Control (MAC). The access rigths are centrally managed (ex, hospital organizations). Rules are defined in order to establish the access rights of the users. The rules cannot be modified by the users. Role Based Access Control (RABC). Specific access rights are assigned to useres depending to their role in the organization. A user can belong to different roles..

Mechanisms and policies are different concepts Example: UNIX provides a mechanism to define for each file three bits ( read, write and execute) for the owner of the file, for the group and for the others The user defines the value of the three bits (policy)

Changing the protection state Standard dual mode (monitor-user mode) Two protection state:user mode and monitor o kernel mode. Domain changing associated to the system calls When a process must execute a privileged instruction (access to files, I/O operations…) a change of domain happens. It is not possible to have protection among users.

Unix The domain is associated with the user. The change of domain corresponds to the temporary change of the identiy among users. To each file are associated the owner identification (user-id) and a domain bit (set-uid). When a user A (user-id=A) begins the execution of a file, whose owner is B (user-id=B) and the set-uid=on for the file, the user-id of A is set temporary to B. When the execution completes the initial conditions are restored.

read,writeexecutewrite executeread,write S1 S2 Access matrix O1 O2 O3

Access matrix implementation : - Matrix dimension - Sparse matrix Access Control List (ACL). The matrix may be decomposed by columns: to each object an access control list is associated. It contains all the subjects that can access the object and the permitted access rigths. Capability List The matrix is decomposed by rows: to each subject is associated a list that contains the objects accessible by the the subject and the relative access rights.

Access list The access list for each object is represented by the set of informations only for the subjects with a not empty set of rights for the object. When an operation M must be executed on an object Oj by the subject Si, the access list is examined looking for with M belonging to Rk If the condition is not satisfied, a default list is examined. If the answer is negative, a error codition occurs. The default list contains the access rigths that can be executed by every subject.

User groups. SID(subject identifier), GID (group identifier). The ACL entry : SID 1, GID 1 : SID 2, GID 2 : Role concept. A user can belong to different groups and then with different set of rigts. When the user access the object he must specify the belonging group.

CAPABILITY LIST The capability list, for each subject, is the object list together with the allowed accesses for each of them to which the subject can access. Every element of the list is named capability. Every capability guarantees to the owner some access rigts on an object. In order to execute an operation M on an object O it is necessary that : - The subject can access the object - M is one of allowed rigths

F1F2F3F4F5F6PR1PR2 -- RRWERW -- W subject FileRPointer to F3 FileRWXPointer to F4 FileRWPointer to F5 PrinterWPointer to printer PR1 Typerigthsobject capability list for the subject

Comparison A protection system realized using only one of two methods, ACL or capability list, normally presents efficency problems ACL. The information about the access rigths owned by a subject is dispersed in the various ACL relative to the system objects. every access to the same object by a subject implies a search in the list. Capability list. In order to remove an object, whose access rights belong to more subjects, it is necessary to search in all the relative capability lists. Adopted solution: Utilization of a combination of the two methods.

Example: Unix O.S fd=open(, ) ACL: the access is allowed? If the answer is positive a new entry is created in the open files table associated to the process, constituted by fd and the access rights (capabilty). fd is returned to the process (i-node corrisponding to the new open file). All the next operations on the file are executed by using fd and verifiyng that the access rigths are allowed.

Multilevel security The majority of the operating systems allow single users to define users that can read or write their files and their objects. (Discretionary Access Control, DAC). In some environments a more stringent security is required (commonly found in military,hospitals, companies..). Rules are defined relatively the possibilty to have access to informations and these rules cannot be modified without special permissions. (Mandatory Access Control, MAC)

Bell-La Padula Model Designed to manage the security in a military environment. Security Levels of the documents: - unclassified - confidential - secret - top secret People are assigned to the levels corresponding to the types of documents that they are authorized to examine.

The model is equally applicable in other areas, where information can be organized into gross categories and users can be granted authorization to access certain categories of data. Por example, the highest level of security might be for strategic corporate planning documents and data, accessible by only corporate officers and their staff; next might come sensitive financial and personnel data, accessible only by administrators personnel, corporate officers, and so on.

A multilevel secure system must enforce the following rules: No read up: A subject can only read an object of less or equal security level. (simple security property) No write down: a subject can only write into an object of greater or equal security level (*-property) The subjects can read downward and write upward, but the contrary is not allowed. The two rules, if properly enforced, provide multilevel security

Security level E 6 43C 2B 1A D read write objectprocess

Trojan Horse Defense In the example a troian horse is used to get around the standard security mechanism based on the access control list (ACL). A user named Bob created a file containing the critical sensitive character string “CPE1704TKS”, with read/write permission provided only to processes belonging to Bob. A hostile user, Alice, gains legitimate access to the system and installs both a troian horse program and a private file used in the attack as a “back pocket”. Alice gives read/write permission to himself for this file and gives to Bob write only permission.

Alice now induces Bob to invoke the troian horse program, perhaps by advertising it as a useful utility. When the program detects that it is being executed by Bob, it reads the sensitive character string from Bob’ file and copies it into Alice’ back pocket file. Both the read and write operations satisfy the constraints imposed by Access Control List. Alice then has only to access Bob’ file at a later time to learn the value of the string.

Use of a multilevel protection. Two security levels, confidential and public. To Bob’ processes and files the confidential security level is assigned. To Alice’ processes and files the public level is assigned. When the trojan horse program is activated by Bob, the Bob security level is assigned to the program and it it possible for it to see the sensitive string of characters (no read up rule). When the program tries to store it in a public file ( back pocket file) the *property is violated and the attempt is not allowed. The security policy takes priority over ACL mechanism

Steganography Is the art and science of writing hidden messages in such a way that no one, apart from the sender and intended recipient, suspects the existence of the message, a form of security through obscurity. Generally, messages will appear to be something else: images, articles, shopping lists, or some other covertext. Images utilization. Each pixel is composed by three 8 bit numbers, one for each red, green and blu intensity. The pixel color is obtained by the linear overlapping of the three colors.

The coding method utilizes the less significant bits as a hidden channel. Impossibility to distinguish 7 bit colors from 8 bit colors. Example: 1024x768 pixel image ( byte). The text to be transmitted is compressed (if it is necessary ) encrypted and inserted into the less significative bits of each color.