Policy abstraction mechanism

• US 7,185,210 B1
• Filed: 06/24/1996
• Issued: 02/27/2007
• Est. Priority Date: 06/24/1996
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Faden, Glenn
• Primary Examiner(s): BANANKHAH, MAJID A
• Application Number:
  US08/668,892
• Time in Patent Office: 3,900 Days
• Field of Search: 395/670, 395/187.01, 395/186, 395/676, 707/9, 713/200, 713/201, 713/1, 713/202, 711/163, 711/164
• US Class Current: 726/2
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries

Abstract

A secure operating system is disclosed in which all code implementing security functionality resides in a security module separate from the operating system code. Calls involving security functions are made using a format or interface which is standardized for all systems. Such a call identifies, inter alia the response and the access mode which are used to identify a call in a two dimensional table which contains a pointer to the needed security functions. In the way security functions are separately compilable and security solving changes can be made by linking in a new security module. Maintenance of security code is separated from maintenance of the underlying operating system.

Claims

1. Secure computer apparatus comprising:

a. a computer; and

b. a secure operating system on said computer controlling access to one or more systems, comprising;

b1. a common interface used for calls to all security functions, and

b2. a table accessed by variables specified in a call using said interface, each entry in the table pointing to a security policy function appropriate to the variables specified in said call.

2. Apparatus of claim 1 in which a call using said common interface passes variables identifying a resource and an access mode.

3. Apparatus of claim 2 in which a call using said common interface passes one or more of variables pointing to data, identifying attributes of a requestor, identifying portions of security policy to be enforced and specifying miscellaneous functions.

4. A method of organizing a secure operating system, comprising the steps of:

a. providing a common interface used for all requests for security functions;

b. providing a separate file of security functions; and

c. providing a table accessed by information provided in a request for security functions which point to an appropriate security function in said separate file.

5. A method of invoking security functions in a secure operating system, comprising the steps of:

a. providing an element for performing the step of requesting security functions in a program call using an interface common to all systems using security services,

b. providing an element for performing the step of accessing a table based on information provided in said call; and

c. providing an element for performing the step of invoking a security function pointed to by said table.

6. A method of creating a secure operating system, comprising the steps of:

a. providing an element for performing the step of inserting compiler directives at points in operating system code at which security services are needed, the directives accessing a security policy table using resource and access method information;

b. providing an element for performing the step of storing at each entry in said security policy table a pointer to a security function appropriate to the resource and access method; and

c. providing an element for performing the step of storing said table and security functions in a separate file from said operating system code.

7. The method of claim 6 in which said operating system code and said table and security functions are separately compiled.

8. The method of claim 7 in which object code versions of said operating system code and object code versions of said table and security functions are linked together to created an executable version of said secure operating system.

9. A method of changing security policy for a secure operating system, comprising the steps of:

a. changing a security policy table or one or more security functions and recompiling both the security policy table and the one or more security functions; and

b. linking a recompiled security policy table and one or more security functions with an unchanged object code version of said operating system.

10. A method of creating a secure operating system, comprising the step of:

separating all security functions into a file separate from operating code.

11. The method of claim 10 in which all security functions are accessed using requests in a common format.

12. A secure computer system, comprising:

a. a network, and

b. a plurality of computers connected to said network, at least one of said computers having a secure operating system controlling access to said network and to other sub-systems, said operating system having a common interface used for calls to all security functions, and a table accessed by variables specified in a call using said interface, each entry in the table pointing to a security policy function appropriate to the variables specified in said call.

13. A computer product, comprising:

a. a memory medium; and

b. a computer program stored on said memory medium, said computer program containing instructions implementing one or more operating system functions and implementing a common interface used for all requests for security functions;

a separate file of security functions, stored on said memory medium, and a table, stored on said memory medium and accessed by information provided in a request for security functions which points to an appropriate security function in said separate file.

14. A computer program product, comprising:

a. a memory medium; and

b. a separate file of security functions, stored on said memory medium, and a table, stored on said memory medium and accessed by information provided in a request for security functions which points to an appropriate security function in said separate file.

15. A computer program product, comprising:

a. a memory medium; and

b. an operating system stored on said memory medium, said operating system containing instructions implementing a common interface used for all calls for security functions.

16. A computer program product, comprising:

a. a memory medium; and

b. a computer program stored on said memory medium, said computer program containing instructions for requesting security functions in a program call using an interface common to all systems using security services.

17. A computer program product, comprising:

a. a memory medium; and

b. a computer program stored on said memory medium, said program comprising an object code version of operating system code linked together with an object code version of security functions;

wherein the security functions enforce two or more of mandatory access control, discretionary access control, information labeling and auditing policies.