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-3
SAFECOM Command Syntax
For subprocesses, can be either a fully or a partially qualified subprocess
name.
For OBJECTTYPE, there is no object-spec.
object-spec can contain * and ? wild-card characters except in ADD
commands for devices, subdevices, processes, and subprocesses.
object-name
is the name of an existing protected object of the same type as the object-type
of the command; used in the LIKE clause.
terminal-name
is a fully or partially qualified device or subdevice name.
user-attribute
is any valid security attribute for users. A complete list of user attributes is given
under the SET USER command.
object-attribute
is any valid security attribute for the appropriate object-type of the command. A
complete list of object attributes is given under the SET object-type command.
SAFECOM Command Syntax
These diagrams show the syntax of each SAFECOM command:
ADD object-type object-list [ , ]
[ LIKE object-name | object-attribute ]
[ , object-attribute ] ...
ADD ALIAS alias [ , ]
{ group-name.user-name | group-num,user-num }
[ LIKE user | user-attribute ]
[ , user-attribute ] ...
ADD AUDIT POOL $vol.subvol [ , ]
[ file-spec [ , file-spec ]...] [ LIKE [ $vol.subvol ] ]