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
Configuration
Safeguard Administrator’s Manual—523317-013
9-9
Configuring Device Control
before July 17, the user should ask the owner of the user authentication record to
change the password.
Configuring Device Control
If access control lists exist for both devices and subdevices, the Safeguard software
must know which one to use. You can set the attributes that control how this is
determined.
These Safeguard attributes relate to device access control lists:
CHECK-DEVICE
Access control lists are checked at the device level. The initial value is ON.
CHECK-SUBDEVICE
Access control lists are checked at the subdevice level. The initial value is OFF.
DIRECTION-DEVICE
Determines which direction to search for an access control list when both
CHECK-DEVICE and CHECK-SUBDEVICE are ON. The value can be either
DEVICE-FIRST or SUBDEVICE-FIRST. This attribute is used in conjunction with
COMBINATION-DEVICE. (For more information, see the following note.) The initial
value is DEVICE-FIRST.
COMBINATION-DEVICE
Determines how to resolve conflicts between device and subdevice access control
lists. This attribute is used in conjunction with DIRECTION-DEVICE. (For more
information, see the following note.) The value can be FIRST-ACL, FIRST-RULE,
or ALL. The initial value is FIRST-ACL.
ACL-REQUIRED-DEVICE
If no access control list is found, access is denied. If this attribute is OFF, and no
access control list is found, Guardian rules apply. The initial value is OFF.
Note. COMBINATION-DEVICE resolves conflicts between access control lists if
CHECK-DEVICE and CHECK-SUBDEVICE are both ON. The Safeguard software searches for
an access control list in the order determined by DIRECTION-DEVICE. If you want to use the
first access control list it finds, specify FIRST-ACL. If you want the search to continue until it
finds an access control list that involves the user ID (either ACCESS or DENY), specify
FIRST-RULE. If you want to allow access only if specified on both access control lists, specify
ALL.