|
||||||||||||||||||||||||||||||||||||||||
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) Handling Devices in Trusted Extensions (Task Map) Using Devices in Trusted Extensions (Task Map) Customizing Device Authorizations in Trusted Extensions (Task Map) 24. Trusted Extensions Auditing (Overview) 25. Software Management in Trusted Extensions (Tasks) Creating and Managing a Security Policy Site Security Policy and Trusted Extensions Computer Security Recommendations Physical Security Recommendations Personnel Security Recommendations Additional Security References B. Using CDE Actions to Install Zones in Trusted Extensions Associating Network Interfaces With Zones by Using CDE Actions (Task Map) Preparing to Create 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 |
Managing Devices in Trusted Extensions (Task Map)The following task map describes procedures to protect devices at your site.
How to Configure a Device in Trusted ExtensionsBy default, an allocatable device has a label range from ADMIN_LOW to ADMIN_HIGH and must be allocated for use. Also, users must be authorized to allocate the device. These defaults can be changed. Before You BeginYou must be in the Security Administrator role in the global zone.
How to Revoke or Reclaim a Device in Trusted ExtensionsIf a device is not listed in the Device Allocation Manager, it might already be allocated or it might be in an allocate error state. The system administrator can recover the device for use. Before You BeginYou must be in the System Administrator role in the global zone. This role includes the solaris.device.revoke authorization.
How to Protect Nonallocatable Devices in Trusted ExtensionsThe No Users option in the Allocatable By section of the Device Configuration dialog box is used most often for the frame buffer and printer, which do not have to be allocated to be used. Before You BeginYou must be in the Security Administrator role in the global zone.
Example 23-1 Preventing Remote Allocation of the Audio DeviceThe No Users option in the Allocatable By section prevents remote users from hearing conversations around a remote system. The security administrator configures the audio device in the Device Allocation Manager as follows: Device Name: audio For Allocations From: Trusted Path Allocatable By: Authorized Users Authorizations: solaris.device.allocate Device Name: audio For Allocations From: Non-Trusted Pathh Allocatable By: No Users How to Configure a Serial Line for LoginsBefore You BeginYou must be in the Security Administrator role in the global zone.
Example 23-2 Restricting the Label Range of a Serial PortAfter creating a serial login device, the security administrator restricts the label range of the serial port to a single label, Public. The administrator sets the following values in the Device Administration dialog boxes. Device Name: /dev/term/[a|b] Device Type: tty Clean Program: /bin/true Device Map: /dev/term/[a|b] Minimum Label: Public Maximum Label: Public Allocatable By: No Users How to Configure an Audio Player Program for Use in Trusted CDEThe following procedure enables an audio player to open automatically in a Trusted CDE workspace when a user inserts a music CD. For the user's procedure, see the example in How to Allocate a Device in Trusted Extensions in Solaris Trusted Extensions User’s Guide. Note - In a Trusted GNOME workspace, users specify the behavior of removable media just as they specify it in a non-trusted workspace. Before You BeginYou must be in the System Administrator role in the global zone.
Example 23-3 Configuring an Audio Player Program for UseIn the following example, the system administrator makes the workman program available to all users of a system. The workman program is an audio player program. # /etc/rmmount.conf file action cdrom action_workman.so /usr/local/bin/workman How to Prevent the File Manager From Displaying After Device AllocationBy default, the File Manager displays when a device is mounted. If you are not mounting devices that have file systems, you might want to prevent the File Manager from displaying. Before You BeginYou must be in the System Administrator role in the global zone.
How to Add a Device_Clean Script in Trusted ExtensionsIf no device_clean script is specified at the time a device is created, the default script, /bin/true, is used. Before You BeginHave ready a script that purges all usable data from the physical device and that returns 0 for success. For devices with removable media, the script attempts to eject the media if the user does not do so. The script puts the device into the allocate error state if the medium is not ejected. For details about the requirements, see the device_clean(5) man page. You must be in the System Administrator role in the global zone.
|
|||||||||||||||||||||||||||||||||||||||
|