Download
chapter 14 protection n.
Skip this Video
Loading SlideShow in 5 Seconds..
Chapter 14: Protection PowerPoint Presentation
Download Presentation
Chapter 14: Protection

Chapter 14: Protection

139 Vues Download Presentation
Télécharger la présentation

Chapter 14: Protection

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Chapter 14: Protection

  2. Objectives • Discuss the goals and principles of protection in a modern computer system • Explain how protection domains combined with an access matrix are used to specify the resources a process may access • Examine capability and language-based protection systems

  3. Goals of Protection • Operating system consists of a collection of objects, hardware or software • 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.

  4. Principles of Protection • Guiding principle – principle of least privilege • Programs, users and systems should be given just enough privileges to perform their tasks

  5. Domain Structure • Access-right = <object-name, rights-set>where rights-set is a subset of all valid operations that can be performed on the object. • Domain = set of access-rights

  6. Associating a process to a domain • Static If we want to adhere to a least privilege policy, we must be able to change the contents of a domain to avoid giving a process more rights than necessary. The process is assigned a domain and the contents of this domain change over the lifetime of the process • Dynamic Enable a process to switch from one domain to another. More complex!

  7. 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.

  8. Domain Implementation (MULTICS) • Let Di and Djbe any two domain rings. • If j < I Di  Dj

  9. 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 Domaini can invoke on Objectj

  10. Access Matrix

  11. Use of Access Matrix • If a process in Domain Ditries to do “op” on object Oj, 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 Oi • copy op from Oi to Oj • control – Di can modify Dj access rights • transfer – switch from domain Di to Dj

  12. Access Matrix of Figure A With Domains as Objects Figure B

  13. Copy • Rights with a * can be copied from one domain (row) to another • Example D2 with the right read for F2 in the next slide • Two variants • A right can be copied from access(i, j) to access(k, j) and then removed from access (i, j) – transfer • Propagation of the copy may be restricted – with R* is copied, R is created

  14. Access Matrix with Copy Rights

  15. Owner • Allows addition and removal of rights • If Access(i, j) contains owner then a process executing in domain Di can add and remove any entry in column j

  16. Access Matrix With Owner Rights

  17. Control Control • Copy and Owner allowed changes to a column • Control applicable only to Domain objects • If access(i, j) includes the control right, then a process in Domain Di can remove any right in row j

  18. Access Matrix of Figure A With Domains as Objects Figure B

  19. Modified Access Matrix of Figure B

  20. 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.

  21. 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

  22. Implementing an Access Matrix • Mostly sparse matrix • Global Table – set of ordered triplets <domain, object, rights> Large. Cannot be kept in memory • Access Lists for Objects. List for each object contains <Domain,rights> • Capability Lists for Domains, <Object, Operation>

  23. Access Control • Protection can be applied to non-file resources • Solaris 10 provides role-based access control to implement least privilege • Privilege is right to execute system call or use an option within a system call • Can be assigned to processes • Users assigned roles granting access to privileges and programs

  24. Role-based Access Control in Solaris 10

  25. 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

  26. Capability-Based Systems • 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. • 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.

  27. Language-Based Protection • Specification of protection in a programming language allows the high-level description of policies for the allocation and use of resources. • Language implementation can provide software for protection enforcement when automatic hardware-supported checking is unavailable. • Interpret protection specifications to generate calls on whatever protection system is provided by the hardware and the operating system.

  28. Protection in Java 2 • Protection is handled by the Java Virtual Machine (JVM) • A class is assigned a protection domain when it is loaded by the JVM. • The protection domain indicates what operations the class can (and cannot) perform. • If a library method is invoked that performs a privileged operation, the stack is inspected to ensure the operation can be performed by the library.

  29. Stack Inspection

  30. End of Chapter 14