This checklist provides an overall view of the major configuration tasks for Trusted Extensions. The smaller tasks are outlined within the major tasks. The checklist does not replace following the steps in this guide.
The following list summarizes what is required to enable and configure Trusted Extensions at your site. Tasks that are covered elsewhere are cross-referenced.
Decide the root password.
Decide the PROM or BIOS security level.
Decide the PROM or BIOS password.
Decide if attached peripherals are permitted.
Decide if access to remote printers is permitted.
Decide if access to unlabeled networks is permitted.
Install the Oracle Solaris OS.
Enable Trusted Extensions. See Installing and Enabling Trusted Extensions.
Load the appropriate Trusted Extensions package set, either for a system that runs a multilevel desktop or for a system that does not.
Run the labeladm enable options command to enable the Trusted Extensions service.
(Optional) Run the labeladm encodings encodings-file command to install your encodings file.
(Optional) Customize the global zone. See Setting Up the Global Zone in Trusted Extensions.
If using a DOI different from 1, set the DOI in the /etc/system file and in every security template.
Verify and install your site's label_encodings file.
Add labeled zones. See Creating Labeled Zones.
Configure two labeled zones automatically.
Configure your labeled zones manually.
Create labeled workspace.
Configure the LDAP naming service. See Configuring LDAP for Trusted Extensions.
Create either a Trusted Extensions proxy server or a Trusted Extensions LDAP server. The files naming service requires no configuration.
Configure interfaces and routing for the global zone and for labeled zones. See Configuring the Network Interfaces in Trusted Extensions.
Configure the network. See Labeling Hosts and Networks.
Identify single-label hosts and limited-range hosts.
Determine the labels to apply to incoming data from unlabeled hosts.
Customize the security templates.
Assign individual hosts to security templates.
Assign subnets to security templates.
Perform further configurations.
Configure network connections for LDAP.
Assign the LDAP server or proxy server to the cipso host type in all security templates.
Assign LDAP clients to the cipso host type in all security templates.
Make the local system a client of the LDAP server.
Configure local users and local administrative roles. See Creating Roles and Users in Trusted Extensions.
Create the Security Administrator role.
Create a local user who can assume the Security Administrator role.
Create other roles and possibly other local users to assume these roles.
Create home directories at every label that the user can access. See Creating Centralized Home Directories in Trusted Extensions.
Create home directories on an NFS server.
Create local ZFS home directories that can be encrypted.
(Optional) Prevent users from reading their lower-level home directories.
Configure printing. See Configuring Labeled Printing.
Configure devices. See Handling Devices in Trusted Extensions.
Assign the Device Management profile or the System Administrator profile to a role.
To make devices usable, do one of the following:
Per system, make devices allocatable.
Assign the Allocate Device authorization to selected users and roles.
Configure Oracle Solaris features.
Configure system security values.
Enable particular LDAP clients to administer LDAP.
Configure users in LDAP.
Configure network roles in LDAP.
Mount and share file systems. See Managing and Mounting Files in Trusted Extensions.