Copyright © Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE USC CSci599 Trusted Computing -Lecture Twelve Project Discussion – Managing Domains 6 April 2007 Dr. Clifford Neuman University of Southern California Information Sciences Institute

Copyright © Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE Announcements Mid-term exams returned today Additional lecture audio posted –(thanks Rob Huber)

Copyright © Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE Presentations Nilesh Maheshwari Chandrasekar Sivaraman Jason Smith Chitanya Hazarey

Copyright © Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE Managing Domains What is a security domain –That part of a system for which entities have the same access to the same objects. –In a typical OS, all Kernel access is in a common domain, and each user level process is in a separate domain. –In TVSA managing domains means determining when a process or function can join a virtual system.

Copyright © Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE Possible ways to manage domains Certificate based –Developers issue certs that allow functions/components to join domain. Joint concurrence –Entities joining must all subsequently agree to new elements joining Third party endorsement –Designated entities that can attest to ability to enforce certain common policies Blended approaches

Copyright © Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE Do we need a policy language Consider the statements (in class exercise) Who can join What must they agree to do How do we decided on changes Do we have multiple levels of trustworthiness Does this define additional rings