Safeguard Administrator's Manual (G06.24+, H06.03+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction
- 2 Controlling User Access
- Introduction
- Using SAFECOM to Establish a Local User Community
- Using SAFECOM to Manage User Access to Your System
- Changing the Owner of a User Authentication Record
- Granting a User Temporary Access to Your System
- Requiring Users to Change Their Passwords
- Granting a Grace Period for Changing an Expired Password
- Forcing Immediate Expiration of a User’s Password
- Freezing a User's Ability to Access the System
- Specifying Auditing for a User ID
- Deleting Users
- Deleting Administrative Groups
- Using SAFECOM to Establish a Network of Users
- Using Safeguard With Nodes With Standard Security
- Identifying Network Users
- Granting a Network User Access to Objects on Your System
- Establishing a Community of Network Users
- Changes to the PAID During a User’s Session
- Additional Considerations for Aliases and Groups
- Additional Considerations for ACCESS with Network Specific Subject IDs
- Establishing Default Protection for a User's Disk Files
- Specifying a Default Command Interpreter for a User
- Establishing Guardian Defaults
- Assigning an Alias to a User
- 3 Managing User Groups
- 4 Securing Volumes and Devices
- 5 OBJECTTYPE Control
- 6 Managing Security Groups
- 7 Securing Terminals
- 8 Warning Mode
- 9 Configuration
- Safeguard Attributes
- Configuring User Authentication
- Configuring Password Control
- Configuring Device Control
- Configuring Process Control
- Configuring Disk-File Control
- Configuring Safeguard Auditing
- Configuring a Default Command Interpreter
- Configuring Communication With $CMON
- Configuring Logon Dialog
- Configuring Exclusive Access at Safeguard Terminals
- Configuring Warning Mode
- Configuring Persistence
- Configuring Attributes for Node Specific Subjects in ACLs
- 10 Installation and Management
- Safeguard Components
- Process Considerations for the SMP and SAFECOM
- Safeguard Subsystem Management Commands
- General Installation Procedure
- Installing the Safeguard Software
- Starting the SMP
- Converting to the Safeguard Subsystem
- Updating the Safeguard Software
- Guidelines for Securing the Safeguard Subsystem
- Monitoring the Safeguard Subsystem
- A SAFECOM Command Syntax
- Index
Securing Volumes and Devices
Safeguard Administrator’s Manual—523317-013
4-4
Considerations for Devices and Subdevices
Considerations for Devices and Subdevices
By default, only super-group users (255,*) can add devices and subdevices to the
Safeguard database. If necessary, ownership can be transferred to another user
responsible for protection of that device or subdevice.
Until a device or subdevice is added to the Safeguard database, any process can open
that device or subdevice for input or output. After a device or subdevice is under
Safeguard control, only processes executing on behalf of users on the access control
list can access the device or subdevice.
Valid access authorities for devices and subdevices are:
This command adds an authorization record for the device $LASER and gives READ
and WRITE authority to all users who are members of groups 24 and 25:
=ADD DEVICE $laser, ACCESS 24,* (R,W); 25,* (R,W)
The Safeguard software does not check access control lists for subdevices unless it is
configured to check them. (For more information, see Configuring Device Control on
page 9-9.)
READ The authority to open a device or subdevice for input
WRITE The authority to open a device or subdevice for output
OWNER The authority to change the authorization record