DG/UX System Provides mandatory access controls Initially

Slides:



Advertisements
Similar presentations
Information Flow and Covert Channels November, 2006.
Advertisements

1 cs691 chow C. Edward Chow Confidentiality Policy CS691 – Chapter 5 of Matt Bishop.
I NFORMATION S ECURITY : C ONFIDENTIALITY P OLICIES (C HAPTER 4) Dr. Shahriar Bijani Shahed University.
CS591 – Chapter 5.2/5.4 of Security in Computing
Slide #5-1 Chapter 5: Confidentiality Policies Overview –What is a confidentiality model Bell-LaPadula Model –General idea –Informal description of rules.
1 Confidentiality Policies CSSE 490 Computer Security Mark Ardis, Rose-Hulman Institute March 18, 2004.
Confidentiality Policies  Overview  What is a confidentiality model  Bell-LaPadula Model  General idea  Informal description of rules  Formal description.
Security Fall 2009McFadyen ACS How do we protect the database from unauthorized access? Who can see employee salaries, student grades, … ? Who can.
June 1, 2004Computer Security: Art and Science © Matt Bishop Slide #5-1 Chapter 5: Confidentiality Policies Overview –What is a confidentiality.
April 20, 2004ECS 235Slide #1 DG/UX System Provides mandatory access controls –MAC label identifies security level –Default labels, but can define others.
CPSC 668Set 10: Consensus with Byzantine Failures1 CPSC 668 Distributed Algorithms and Systems Fall 2006 Prof. Jennifer Welch.
Security Fall 2006McFadyen ACS How do we protect the database from unauthorized access? Who can see employee salaries, student grades, … ? Who can.
1 cs691 chow C. Edward Chow Confidentiality Policy CS691 – Chapter 5 of Matt Bishop.
November 1, 2004Introduction to Computer Security ©2004 Matt Bishop Slide #5-1 Chapter 5: Confidentiality Policies Overview –What is a confidentiality.
The UNIX File System.
Sicurezza Informatica Prof. Stefano Bistarelli
User Domain Policies.
1 Efficient Discovery of Conserved Patterns Using a Pattern Graph Inge Jonassen Pattern Discovery Arwa Zabian 13/07/2015.
April 15, 2004ECS 235Slide #1 Policy Languages Express security policies in a precise way High-level languages –Policy constraints expressed abstractly.
7/15/2015 5:04 PM Lecture 4: Bell LaPadula James Hook CS 591: Introduction to Computer Security.
Mandatory Flow Control Bismita Srichandan. Outline Mandatory Flow Control Models Information Flow Control Lattice Model Multilevel Models –The Bell-LaPadula.
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.
1 IS 2150 / TEL 2810 Introduction to Security James Joshi Assistant Professor, SIS Lecture 5 September 27, 2007 Security Policies Confidentiality Policies.
CSC 8310 Programming Languages Meeting 2 September 2/3, 2014.
Lesson 7-Creating and Changing Directories. Overview Using directories to create order. Managing files in directories. Using pathnames to manage files.
1 Confidentiality Policies September 21, 2006 Lecture 4 IS 2150 / TEL 2810 Introduction to Security.
1 IS 2150 / TEL 2810 Information Security & Privacy James Joshi Associate Professor, SIS Lecture 6 Oct 2-9, 2013 Security Policies Confidentiality Policies.
© G. Dhillon, IS Department Virginia Commonwealth University Principles of IS Security Formal Models.
1 A pattern language for security models Eduardo B. Fernandez and Rouyi Pan Presented by Liping Cai 03/15/2006.
1 Announcement: End of Campaign Celebration When: Wednesday, October 1, 15:30 Where: New building site (NW corner 3 rd & University) Please attend and.
Linux+ Guide to Linux Certification, Second Edition
Data Structures TREES.
Slide #5-1 Confidentiality Policies CS461/ECE422 Computer Security I Fall 2010 Based on slides provided by Matt Bishop for use with Computer Security:
Linux+ Guide to Linux Certification, Third Edition
Linux+ Guide to Linux Certification, Third Edition
1 IS 2150 / TEL 2810 Introduction to Security James Joshi Associate Professor, SIS Lecture 5 September 29, 2009 Security Policies Confidentiality Policies.
M180: Data Structures & Algorithms in Java Trees & Binary Trees Arab Open University 1.
1/15/20161 Computer Security Confidentiality Policies.
Mandatory Access Control and SE Linux CS 460 Cyber Security Lab Spring ‘10.
November 1, 2004Introduction to Computer Security ©2004 Matt Bishop Slide #5-1 Confidentiality Policies Overview –What is a confidentiality model Bell-LaPadula.
1 Part 5. Permission Rules for Two-Level Systems Controlling access (visibility or scope) of static references. Analogous to “private” in C/C++/Java.
Windows 2003 Architecture, Active Directory & DNS Lecture # 3 Hassan Shuja 02/14/2006.
Design and Implementation MAC in Security Operating System CAI Yi, ZHENG Zhi-rong, SHEN Chang-xiang Presented By, Venkateshwarlu Jangili. 1.
Naming CSCI 6900/4900. Names & Naming System Names have unique importance –Resource sharing –Identifying entities –Location reference Name can be resolved.
Lecture 14 Page 1 CS 111 Online File Systems: Naming, Reliability, and Advanced Issues CS 111 On-Line MS Program Operating Systems Peter Reiher.
Database Security Database System Implementation CSE 507 Some slides adapted from Navathe et. Al.
22 feb What is Access Control? Access control is the heart of security Definitions: * The ability to allow only authorized users, programs or.
Lecture 2 Page 1 CS 236 Online Security Policies Security policies describe how a secure system should behave Policy says what should happen, not how you.
LECTURE 10 Semantic Analysis. REVIEW So far, we’ve covered the following: Compilation methods: compilation vs. interpretation. The overall compilation.
Linux Filesystem Management
Database System Implementation CSE 507
Access Control Model SAM-5.
Access Control CSE 465 – Information Assurance Fall 2017 Adam Doupé
Data Structures and Design in Java © Rick Mercer
Parsing & Context-Free Grammars
Basic Security Theorem
Computer Security Confidentiality Policies
IS 2150 / TEL 2810 Introduction to Security
Chapter 5: Confidentiality Policies
Confidentiality Models
Confidentiality Policies
Policy Languages Express security policies in a precise way
Trust Models CS461/ECE422.
Chapter 5: Confidentiality Policies
Chapter 5: Confidentiality Policies
Computer Security Confidentiality Policies
IS 2150 / TEL 2810 Information Security & Privacy
Presentation transcript:

DG/UX System Provides mandatory access controls Initially MAC label identifies security level Default labels, but can define others Initially Subjects assigned MAC label of parent Initial label assigned to user, kept in Authorization and Authentication database Object assigned label at creation Explicit labels stored as part of attributes Implicit labels determined from parent directory April 20, 2004 ECS 235

MAC Regions IMPL_HI is “maximum” (least upper bound) of all levels IMPL_LO is “minimum” (greatest lower bound) of all levels April 20, 2004 ECS 235

Directory Problem Process p at MAC_A tries to create file /tmp/x /tmp/x exists but has MAC label MAC_B Assume MAC_B dom MAC_A Create fails Now p knows a file named x with a higher label exists Fix: only programs with same MAC label as directory can create files in the directory Now compilation won’t work, mail can’t be delivered April 20, 2004 ECS 235

Multilevel Directory Directory with a set of subdirectories, one per label Not normally visible to user p creating /tmp/x actually creates /tmp/d/x where d is directory corresponding to MAC_A All p’s references to /tmp go to /tmp/d p cd’s to /tmp/a, then to .. System call stat(“.”, &buf) returns inode number of real directory System call dg_stat(“.”, &buf) returns inode of /tmp April 20, 2004 ECS 235

Object Labels Requirement: every file system object must have MAC label Roots of file systems have explicit MAC labels If mounted file system has no label, it gets label of mount point Object with implicit MAC label inherits label of parent April 20, 2004 ECS 235

Object Labels Problem: object has two names /x/y/z, /a/b/c refer to same object y has explicit label IMPL_HI, b has explicit label IMPL_B Case 1: hard link created while file system on DG/UX system Creating hard link requires explicit label If implicit, label made explicit Moving a file makes label explicit April 20, 2004 ECS 235

Object Labels Case 2: hard link exists when file system mounted No objects on paths have explicit labels: paths have same implicit labels An object on path acquires an explicit label: implicit label of child must be preserved Change to directory label makes child labels explicit before the change April 20, 2004 ECS 235

Object Labels Symbolic links are files, and treated as such When resolving symbolic link, label of object is label of target of the link System needs access to the symbolic link itself April 20, 2004 ECS 235

Using MAC Labels Simple security condition implemented *-property not fully implemented Process MAC must equal object MAC Writing allowed only at same security level Overly restrictive in practice April 20, 2004 ECS 235

MAC Tuples Up to 3 MAC ranges (one per region) MAC range is a set of labels with upper, lower bound Upper bound must dominate lower bound of range Examples [(Secret, {NUC}), (Top Secret, {NUC})] [(Secret, ), (Top Secret, {NUC, EUR, ASI})] [(Confidential, {ASI}), (Secret, {NUC, ASI})] April 20, 2004 ECS 235

MAC Ranges [(Secret, {NUC}), (Top Secret, {NUC})] [(Secret, ), (Top Secret, {NUC, EUR, ASI})] [(Confidential, {ASI}), (Secret, {NUC, ASI})] (Top Secret, {NUC}) in ranges 1, 2 (Secret, {NUC, ASI}) in ranges 2, 3 [(Secret, {ASI}), (Top Secret, {EUR})] not valid range as (Top Secret, {EUR}) dom (Secret, {ASI}) April 20, 2004 ECS 235

Objects and Tuples Objects must have MAC labels Example May also have MAC label If both, tuple overrides label Example Paper has MAC range: [(Secret, {EUR}), (Top Secret, {NUC, EUR})] April 20, 2004 ECS 235

MAC Tuples Process can read object when: Example Object MAC range (lr, hr); process MAC label pl pl dom hr Process MAC label grants read access to upper bound of range Example Peter, with label (Secret, {EUR}), cannot read paper (Top Secret, {NUC, EUR}) dom (Secret, {EUR}) Paul, with label (Top Secret, {NUC, EUR, ASI}) can read paper (Top Secret, {NUC, EUR, ASI}) dom (Top Secret, {NUC, EUR}) April 20, 2004 ECS 235

MAC Tuples Process can write object when: Example Object MAC range (lr, hr); process MAC label pl pl  (lr, hr) Process MAC label grants write access to any label in range Example Peter, with label (Secret, {EUR}), can write paper (Top Secret, {NUC, EUR}) dom (Secret, {EUR}) and (Secret, {EUR}) dom (Secret, {EUR}) Paul, with label (Top Secret, {NUC, EUR, ASI}), cannot read paper (Top Secret, {NUC, EUR, ASI}) dom (Top Secret, {NUC, EUR}) April 20, 2004 ECS 235

Formal Model Definitions S subjects, O objects, P rights Defined rights: r read, a write, w read/write, e empty M set of possible access control matrices C set of clearances/classifications, K set of categories, L = C  K set of security levels F = { ( fs, fo, fc) } fs(s) maximum security level of subject s fc(s) current security level of subject s fo(o) security level of object o April 20, 2004 ECS 235

More Definitions Hierarchy functions H: OP(O) Requirements Example oi ≠ oj  h(oi )  h(oj ) =  There is no set { o1, …, ok }  O such that, for i = 1, …, k, oi+1 h(oi ) and ok+1 = o1. Example Tree hierarchy; take h(o) to be the set of children of o No two objects have any common children (#1) There are no loops in the tree (#2) April 20, 2004 ECS 235

States and Requests V set of states R set of requests for access Each state is (b, m, f, h) b is like m, but excludes rights not allowed by f R set of requests for access D set of outcomes y allowed, n not allowed, i illegal, o error W set of actions of the system W  R  D  V  V April 20, 2004 ECS 235

History X = RN set of sequences of requests Y = DN set of sequences of decisions Z = VN set of sequences of states Interpretation At time t  N, system is in state zt–1 V; request xt R causes system to make decision yt D, transitioning the system into a (possibly new) state zt V System representation: (R, D, W, z0) X  Y  Z (x, y, z) (R, D, W, z0) iff (xt, yt, zt–1, zt) W for all t (x, y, z) called an appearance of (R, D, W, z0) April 20, 2004 ECS 235

Example S = { s }, O = { o }, P = { r, w } C = { High, Low }, K = { All } For every f  F, either fc(s) = ( High, { All }) or fc(s) = ( Low, { All }) Initial State: b1 = { (s, o, r) }, m1  M gives s read access over o, and for f1  F, fc,1(s) = (High, {All}), fo,1(o) = (Low, {All}) Call this state v0 = (b1, m1, f1, h1)  V. April 20, 2004 ECS 235

First Transition Now suppose in state v0: S = { s, s´ } Suppose fc,1(s´) = (Low, {All}) m1  M gives s and s´ read access over o As s´ not written to o, b1 = { (s, o, r) } z0 = v0; if s´ requests r1 to write to o: System decides d1 = y New state v1 = (b2, m1, f1, h1)  V b2 = { (s, o, r), (s´, o, w) } Here, x = (r1), y = (y), z = (v0, v1) April 20, 2004 ECS 235

Second Transition Current state v1 = (b2, m1, f1, h1)  V b2 = { (s, o, r), (s´, o, w) } fc,1(s) = (High, { All }), fo,1(o) = (Low, { All }) s´ requests r2 to write to o: System decides d2 = n (as fc,1(s) dom fo,1(o)) New state v2 = (b2, m1, f1, h1)  V So, x = (r1, r2), y = (y, n), z = (v0, v1, v2), where v2 = v1 April 20, 2004 ECS 235