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
SAFECOM Command Syntax
Safeguard Administrator’s Manual—523317-013
A-2
Common Syntax Elements
node-spec
can take any of these forms:
* | node-name | node-number
node-name
specifies the system name.
node-number
specifies the Expand node number.
sec-group-list
has the form:
{ sec-group-spec }
{ ( sec-group-spec [ , sec-group-spec ] ... ) }
sec-group-spec
can be any of:
SECURITY-ADMINISTRATOR
SYSTEM-OPERATOR
SECURITY-OSS-ADMINISTRATOR
object-list
has the form:
{ object-spec }
{ ( object-spec [ , object-spec ] ... ) }
object-spec
For disk files, can be either a fully or a partially qualified disk file name, or a
disk file set.
For diskfile patterns, can be a template representing a fully qualified name.
For volumes, can be either a fully or a partially qualified volume name.
For subvolumes, can be either a fully or a partially qualified subvolume name,
or a subvolume set.
For devices, can be either a fully or a partially qualified device name.
For subdevices, can be either a fully or a partially qualified subdevice name.
For processes, can be either a fully or a partially qualified process name.
Note. The SECURITY-OSS-ADMINISTRATOR security group is supported only on systems
running G06.29 and later G-series RVUs and H06.08 and later H-series RVUs.