Document Information
Preface
Part I Initial Configuration of Trusted Extensions
1. Security Planning for Trusted Extensions
2. Configuration Roadmap for Trusted Extensions
3. Adding Solaris Trusted Extensions Software to the Solaris OS (Tasks)
4. Configuring Trusted Extensions (Tasks)
5. Configuring LDAP for Trusted Extensions (Tasks)
6. Configuring a Headless System With Trusted Extensions (Tasks)
Part II Administration of Trusted Extensions
7. Trusted Extensions Administration Concepts
8. Trusted Extensions Administration Tools
9. Getting Started as a Trusted Extensions Administrator (Tasks)
10. Security Requirements on a Trusted Extensions System (Overview)
11. Administering Security Requirements in Trusted Extensions (Tasks)
12. Users, Rights, and Roles in Trusted Extensions (Overview)
13. Managing Users, Rights, and Roles in Trusted Extensions (Tasks)
14. Remote Administration in Trusted Extensions (Tasks)
15. Trusted Extensions and LDAP (Overview)
16. Managing Zones in Trusted Extensions (Tasks)
17. Managing and Mounting Files in Trusted Extensions (Tasks)
18. Trusted Networking (Overview)
19. Managing Networks in Trusted Extensions (Tasks)
20. Multilevel Mail in Trusted Extensions (Overview)
21. Managing Labeled Printing (Tasks)
22. Devices in Trusted Extensions (Overview)
23. Managing Devices for Trusted Extensions (Tasks)
24. Trusted Extensions Auditing (Overview)
25. Software Management in Trusted Extensions (Tasks)
A. Site Security Policy
Creating and Managing a Security Policy
Site Security Policy and Trusted Extensions
Computer Security Recommendations
Physical Security Recommendations
Personnel Security Recommendations
Common Security Violations
Additional Security References
B. Using CDE Actions to Install Zones in Trusted Extensions
Associating Network Interfaces With Zones by Using CDE Actions (Task Map)
Creating Labeled Zones by Using CDE Actions (Task Map)
C. Configuration Checklist for Trusted Extensions
Checklist for Configuring Trusted Extensions
D. Quick Reference to Trusted Extensions Administration
Administrative Interfaces in Trusted Extensions
Solaris Interfaces Extended by Trusted Extensions
Tighter Security Defaults in Trusted Extensions
Limited Options in Trusted Extensions
E. List of Trusted Extensions Man Pages
Trusted Extensions Man Pages in Alphabetical Order
Solaris Man Pages That Are Modified by Trusted Extensions
Glossary
Index
|
Preparing to Create Zones by Using CDE Actions (Task Map)
The following task map describes the tasks for preparing the system for zone
creation. For a discussion of zone creation methods, see Planning for Zones in Trusted Extensions.
Specify Zone Names and Zone Labels by Using a CDE ActionYou do not have to create a zone for every label in
your label_encodings file, but you can. The tnzonecfg database enumerates the labels that
can have zones created for them on this system.
- Navigate to the Trusted_Extensions folder.
- Click mouse button 3 on the background.
- From the Workspace menu, choose Applications → Application Manager.
- Double-click the Trusted_Extensions folder icon.
- For every zone, name the zone.
- Double-click the Configure Zone action.
- At the prompt, provide a name.
Tip - Give the zone a similar name to the zone's label. For example, the
name of a zone whose label is CONFIDENTIAL : INTERNAL USE ONLY would be internal.
- Repeat the Configure Zone action for every zone.
For example, the default label_encodings file contains the following labels: PUBLIC
CONFIDENTIAL: INTERNAL USE ONLY
CONFIDENTIAL: NEED TO KNOW
CONFIDENTIAL: RESTRICTED
SANDBOX: PLAYGROUND
MAX LABEL Although you could run the Configure Zone action six times to create one
zone per label, consider creating the following zones:
On a system for all users, create one zone for the PUBLIC label and three zones for the CONFIDENTIAL labels.
On a system for developers, create a zone for the SANDBOX: PLAYGROUND label. Because SANDBOX: PLAYGROUND is defined as a disjoint label for developers, only systems that developers use need a zone for this label.
Do not create a zone for the MAX LABEL label, which is defined to be a clearance.
- Open the Trusted Network Zones tool.
The tools in the Solaris Management Console are designed to prevent
user error. These tools check for syntax errors and automatically run commands in
the correct order to update databases.
- Start the Solaris Management Console.
# /usr/sbin/smc &
- Open the Trusted Extensions toolbox for the local system.
- Choose Console → Open Toolbox.
- Select the toolbox that is named This Computer (this-host: Scope=Files, Policy=TSOL).
- Click Open.
- Under System Configuration, navigate to Computers and Networks.
Provide a password when prompted.
- Double-click the Trusted Network Zones tool.
- For each zone, associate the appropriate label with a zone name.
- Choose Action → Add Zone Configuration.
The dialog box displays the name of a zone that does not have
an assigned label.
- Look at the zone name, then click Edit.
- In the Label Builder, click the appropriate label for the zone name.
If you click the wrong label, click the label again to deselect it,
then click the correct label.
- Save the assignment.
Click OK in the Label Builder, then click OK in the Trusted Network
Zones Properties dialog box. You are finished when every zone that you want is listed in
the panel, or the Add Zone Configuration menu item opens a dialog box
that does not have a value for Zone Name. TroubleshootingIf the Trusted Network Zones Properties dialog box does not prompt for a
zone that you want to create, either the zone network configuration file does
not exist, or you have already created the file.
Check that the zone network configuration file does not already exist. Look in the panel for the name.
If the file does not exist, run the Configure Zone action to supply the zone name. Then, repeat Step 5 to create the file.
Specify Labels for Network Interfaces by Using the Solaris Management ConsoleYou turn your host and other already-defined hosts into labeled hosts. These hosts
are defined as sending and receiving labeled CIPSO packets. You only need to
add systems that are not known by your LDAP server.
- Display the computers that are known by the system.
In the Solaris Management Console, navigate to Computers. This tool is in the Computers and Networks tool set.
- In the panel, double-click your host.
- Copy the IP address.
- Open Security Templates, then cipso.
- Explicitly assign the host to the cipso template
- Click the Hosts Assigned to Template tab.
If you completed Make the Global Zone an LDAP Client in Trusted Extensions, the LDAP server is assigned to the cipso security
template.
- Paste the host's IP address into the IP Address field.
- Type the host name into the Hostname field.
- Click the Add button.
- Click OK.
- Repeat Step 1 to Step 5 for every host.
In the default configuration, every host that is not explicitly labeled is defined
as an unlabeled host. Every unlabeled host can be contacted at boot at
the label ADMIN_LOW. This is not a secure configuration. To modify the default
configuration, see How to Limit the Hosts That Can Be Contacted on the Trusted Network. Next StepsCreating Labeled Zones by Using CDE Actions (Task Map) See AlsoFor procedures, see Configuring Trusted Network Databases (Task Map). For overview information, see Chapter 18, Trusted Networking (Overview).
|