Go to main content

Trusted Extensions Configuration and Administration

Exit Print View

Updated: March 2019
 
 

Configurable Security Features

Trusted Extensions uses the same security features that Oracle Solaris provides, and adds labeling to the network and zones.

Trusted Extensions differs from Oracle Solaris in that you typically administer systems by assuming a limited role.

Roles in Trusted Extensions

In Trusted Extensions, roles are the conventional way to administer the system. Superuser is the root role, and is required for few tasks, such as setting audit flags, changing an account's password, and editing system files. Roles are created just as they are in Oracle Solaris.

    The following roles are typical of a Trusted Extensions site:

  • root role – Created at Oracle Solaris installation

  • Security Administrator role – Created during or after initial configuration by the initial setup team

  • System Administrator role – Created during or after initial configuration by the initial setup team

Role Creation in Trusted Extensions

To administer Trusted Extensions, you create roles that divide system and security functions.

Trusted Extensions Interfaces for Configuring Security Features

In Trusted Extensions, you can extend existing security features. Also, Trusted Extensions provides unique security features.

Extension of Oracle Solaris Security Features by Trusted Extensions

As in Oracle Solaris, privileges cannot be extended.

Unique Trusted Extensions Security Features

Trusted Extensions is unique in labeling the network and zones. Oracle Solaris labels subjects, objects, and processes.