1. Reasons for Protection n Prevent users from accessing information they shouldn’t have access to. n Ensure that each program component uses system resources in ways consistent with the stated policies for the uses of these resources.

2. Protection n Operating system consists of a collection of objects, hardware or software. n Each object has a unique name and can be accessed through a well defined set of operations. Protection problem – ensure that each object is accessed correctly and only by those processes that are allowed to do so.

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

4. Domain Implementation n Assume dual mode model of the OS: – User – Supervisor n UNIX – Domain = user-id – Domain switch accomplished via file system. n Each file has associated with it a domain bit (setuid bit). n When file is executed and setuid = on, then user-id is set to owner of the file being executed. When execution completes, the user-id is reset.

5. Multics Rings n Let D i and D j be any two domain rings. n If j < i  D i  D j

6. Access Matrix n Protection can be viewed as an access matrix: – Rows are domains. – Columns are objects. – Entry is the set of access rights. Entry access(i,j) defines the set of operations that a process, executing in domain D i, can invoke on object O j.

7. Access Matrix (cont)

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

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

10. Access Matrix With Domains as Objects

11. Access Matrix with Copy Rights

12. Access Matrix With Owner Rights

13. Modified Access Matrix

14. Implementation of Access Matrix n Each column = Access-control list for one object Defines who can perform what operation. Domain 1 = Read, Write Domain 2 = Read Domain 3 = Read

15. Implementation of Access Matrix (cont) n Each Row = Capability List (like a key) For each domain, what operations allowed on what objects. Object 1 – Read Object 4 – Read, Write, Execute Object 5 – Read, Write, Delete, Copy

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

17. Capability Based Systems n Hydra – Fixed set of access rights known to and interpreted by the system. – Interpretation of user defined rights performed solely by user's program; system provides access protection for use of these rights.

18. Capability Based Systems (cont) n Cambridge CAP System – Data capability – provides standard read, write, execute of individual storage segments associated with object. – Software capability – interpretation left to the subsystem, through its protected procedures.

19. Language Based Protection n Specification of protection in a programming language allows the high level description of policies for the allocation and use of resources. n Language implementation can provide software for protection enforcement when automatic hardware supported checking is unavailable.

20. Language Based Protection (cont) n Interpret protection specifications to generate calls on whatever protection system is provided by the hardware and the operating system.