Presentation is loading. Please wait.

Presentation is loading. Please wait.

Access Control Policies Dan Fleck CS 469: Security Engineering These slides are modified with permission from Bill Young (Univ of Texas) 11 Coming up:

Similar presentations


Presentation on theme: "Access Control Policies Dan Fleck CS 469: Security Engineering These slides are modified with permission from Bill Young (Univ of Texas) 11 Coming up:"— Presentation transcript:

1 Access Control Policies Dan Fleck CS 469: Security Engineering These slides are modified with permission from Bill Young (Univ of Texas) 11 Coming up: Access Control Policies 11

2 Access Control Policies The Bell and LaPadula Model is an example of an Access Control Policy. This is a popular way of conceptualizing and implementing security. The basic idea is to introduce rules that control what accesses (i.e., actions) subjects may take with respect to objects. 22 Coming up: Aside: MAC vs. DAC 22

3 Aside: MAC vs. DAC Specifically, BLP is a mandatory access control system, as distinguished from a discretionary system. Mandatory Access Controls (MAC): rules are enforced on every attempted access, not at the discretion of any system user; Discretionary Access Controls (DAC): rule enforcement may be waived or modified by some users. What that means for BLP is that no access is ever allowed unless it satisfies the Simple Security Property and *-Property. Contrast that with Unix file protection system; Unix implements DAC since file protections can be modified by a file’s owner. 33 Coming up: Access Control Matrix 33

4 Access Control Matrix In general, any access control policy can be represented by an access control matrix (ACM). Given all subjects and objects in the system, the matrix shows explicitly what accesses are allowed for each subject/object pair. 44 Coming up: BLP Access Control Matrix 44

5 BLP Access Control Matrix Suppose we had a BLP system with exactly three subjects and objects with the given labels. Suppose also that H > L. The following is the associated access control matrix. SubjectsLevelObjectsLevel Subj1(H,{A,B,C})Obj1(L,{A,B,C}) Subj2(L,{})Obj2(L,{}) Subj3(L,{A,B})Obj3(L,{B,C}) Obj1Obj2Obj3 Subj1RRR Subj2WR,WW Subj3WR- 55 Coming up: Access Control Matrix Using the dominates relationship, which are R, W, both, neither? 55

6 Access Control Matrix As with any access control policy, you could define an ACM for a large Bell and LaPadula system. However, the matrix would be huge for most realistic systems. The matrix is implicit in the rules (Simple Security and the *- Property), so access permissions can be computed on the fly. 66 Coming up: Real MAC Implementations 66

7 Real MAC Implementations SELinux has MAC options built into the kernel. These are used by default on Red Had (in a limited way) SUSE and Ubuntu apply MAC using AppArmor which focuses on programs (not users) Windows from Vista forward implements Mandatory Integrity Control (MIC) and Integrity Levels which a user/process acts: Low, medium, high, system, trusted installer Apple’s OS X implements MAC using a TrustedBSD implementation Versions of MAC are quite common, although none are used exclusively! Source: http://en.wikipedia.org/wiki/Mandatory_Access_Control Coming up: Lessons 77

8 Lessons BLP is an example of a class of policies called “access control policies.” BLP is also an example of a mandatory policy in that the rules are enforced on every attempted access. Any access control policy can be modeled as an explicit matrix. Most current operating systems use MAC in some limited way. 77 End of presentation 88


Download ppt "Access Control Policies Dan Fleck CS 469: Security Engineering These slides are modified with permission from Bill Young (Univ of Texas) 11 Coming up:"

Similar presentations


Ads by Google