JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Trusted Extensions Configuration and Administration     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information

Preface

Part I Initial Configuration of Trusted Extensions

1.  Security Planning for Trusted Extensions

2.  Configuration Roadmap for Trusted Extensions

3.  Adding the Trusted Extensions Feature to Oracle Solaris (Tasks)

4.  Configuring Trusted Extensions (Tasks)

5.  Configuring LDAP for Trusted Extensions (Tasks)

Part II Administration of Trusted Extensions

6.  Trusted Extensions Administration Concepts

7.  Trusted Extensions Administration Tools

8.  Security Requirements on a Trusted Extensions System (Overview)

9.  Performing Common Tasks in Trusted Extensions

10.  Users, Rights, and Roles in Trusted Extensions (Overview)

11.  Managing Users, Rights, and Roles in Trusted Extensions (Tasks)

12.  Remote Administration in Trusted Extensions (Tasks)

13.  Managing Zones in Trusted Extensions

14.  Managing and Mounting Files in Trusted Extensions

15.  Trusted Networking (Overview)

16.  Managing Networks in Trusted Extensions (Tasks)

17.  Trusted Extensions and LDAP (Overview)

18.  Multilevel Mail in Trusted Extensions (Overview)

19.  Managing Labeled Printing (Tasks)

20.  Devices in Trusted Extensions (Overview)

21.  Managing Devices for Trusted Extensions (Tasks)

Handling Devices in Trusted Extensions (Task Map)

Using Devices in Trusted Extensions (Task Map)

Managing Devices in Trusted Extensions (Task Map)

How to Configure a Device in Trusted Extensions

How to Revoke or Reclaim a Device in Trusted Extensions

How to Protect Nonallocatable Devices in Trusted Extensions

How to Add a Device_Clean Script in Trusted Extensions

Customizing Device Authorizations in Trusted Extensions (Task Map)

How to Create New Device Authorizations

How to Add Site-Specific Authorizations to a Device in Trusted Extensions

How to Assign Device Authorizations

22.  Trusted Extensions Auditing (Overview)

23.  Software Management in Trusted Extensions

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.  Configuration Checklist for Trusted Extensions

Checklist for Configuring Trusted Extensions

C.  Quick Reference to Trusted Extensions Administration

Administrative Interfaces in Trusted Extensions

Oracle Solaris Interfaces Extended by Trusted Extensions

Tighter Security Defaults in Trusted Extensions

Limited Options in Trusted Extensions

D.  List of Trusted Extensions Man Pages

Trusted Extensions Man Pages in Alphabetical Order

Oracle Solaris Man Pages That Are Modified by Trusted Extensions

Glossary

Index

Customizing Device Authorizations in Trusted Extensions (Task Map)

The following task map describes procedures to change device authorizations at your site.

Task
Description
For Instructions
Create new device authorizations.
Creates site-specific authorizations.
Add authorizations to a device.
Adds site-specific authorizations to selected devices.
Assign device authorizations to users and roles.
Enables users and roles to use the new authorizations.

How to Create New Device Authorizations

If a device does not require an authorization, then, by default, all users can use the device. If an authorization is required, then only authorized users can use the device.

To deny all access to an allocatable device, see Example 21-1. To create and use a new authorization, see Example 21-3.

Before You Begin

You must be in the Security Administrator role in the global zone.

  1. (Optional) Create a help file for each new device authorization.

    Help files are in HTML format. The naming convention is AuthName.html, as in DeviceAllocateCD.html.

  2. Create the device authorizations.
    $ auths add -t "Authorization description" -h /full/path/to/helpfile.html authorization-name
  3. Add the new authorizations to the appropriate rights profiles.
    $ profiles rights-profile
    profiles:rights-profile > add auths="authorization-name"...
  4. Assign the profiles to users and roles.
    # usermod -P "rights-profile" username
    # rolemod -P "rights-profile" rolename
  5. Use the authorizations to restrict access to selected devices.

    Add the new authorizations to the list of required authorizations in the Device Manager. For the procedure, see How to Add Site-Specific Authorizations to a Device in Trusted Extensions.

Example 21-2 Creating Fine-Grained Device Authorizations

In this example, a security administrator for NewCo needs to construct fine-grained device authorizations for the company.

First, the administrator creates the following help files:

Newco.html
NewcoDevAllocateCDVD.html
NewcoDevAllocateUSB.html

Next, the administrator creates a template help file from which the other help files are copied and modified.

<HTML>
-- Copyright 2012 Newco.  All rights reserved.
-- NewcoDevAllocateCDVD.html 
-->
<HEAD>
        <TITLE>Newco Allocate CD or DVD Authorization</TITLE>
</HEAD>
<BODY>
The com.newco.dev.allocate.cdvd authorization enables you to allocate the 
CD drive on your system for your exclusive use.
<p>
The use of this authorization by a user other than the authorized account 
is a security violation.
<p>
</BODY>
</HTML>

After creating the help files, the administrator uses the auths command to create each device authorization. Because the authorizations are used throughout the company, the administrator places the authorizations in the LDAP repository. The command includes the pathname to the help files.

The administrator creates two device authorizations and a Newco authorization header.

Example 21-3 Creating and Assigning Trusted Path and Non-Trusted Path Device Authorizations

By default, the Allocate Devices authorization enables allocation from the Trusted Path and from outside the Trusted Path.

In the following example, site security policy requires restricting remote CD-ROM and DVD allocation. The security administrator creates the com.newco.dev.allocate.cdvd.local authorization. This authorization is for CD-ROM and DVD drives that are allocated with the Trusted Path. The com.newco.dev.allocate.cdvd.remote authorization is for those few users who are allowed to allocate a CD-ROM or DVD drive outside the Trusted Path.

The security administrator creates the help files, adds the device authorizations to the auth_attr database, adds the authorizations to the devices, and then places the authorizations in rights profiles. The root role assigns the profiles to users who are allowed to allocate devices.

How to Add Site-Specific Authorizations to a Device in Trusted Extensions

Before You Begin

You must be in the Security Administrator role, or in a role that includes the Configure Device Attributes authorization. You must have already created site-specific authorizations, as described in How to Create New Device Authorizations.

  1. Follow the How to Configure a Device in Trusted Extensions procedure.
    1. Select a device that needs to be protected with your new authorizations.
    2. Click the Administration button.
    3. Click the Authorizations button.

      The new authorizations are displayed in the Not Required list.

    4. Add the new authorizations to the Required list of authorizations.
  2. To save your changes, click OK.

How to Assign Device Authorizations

The Allocate Device authorization enables users to allocate a device. The Allocate Device authorization, and the Revoke or Reclaim Device authorization, are appropriate for administrative roles.

Before You Begin

You must be in the Security Administrator role in the global zone.

If the existing profiles are not appropriate, the security administrator can create a new profile. For an example, see How to Create a Rights Profile for Convenient Authorizations.