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
Controlling User Access
Safeguard Administrator’s Manual—523317-013
2-15
Using SAFECOM to Manage User Access to Your
System
Using SAFECOM to Manage User Access to
Your System
The owner of a user authentication record can use SAFECOM to control these aspects
of the user's ability to access the system:
•
Ownership of the record can be transferred to another user.
•
The user can be granted temporary access to the system.
•
The user can be required to change his or her password periodically.
•
The user can be granted a grace period during which his or her expired password
can be changed.
•
The user's ability to access the system can be frozen (temporarily suspended).
•
Users or administrative groups can be deleted from the system.
The next subsections describe how to establish these controls.
Changing the Owner of a User Authentication Record
Many of the security attributes stored in a user authentication record can be changed
with the ALTER USER command. However, only the primary and secondary owners of
the authentication record, the primary owner's group manager, or the local super ID
can change these attributes.
Because security is controlled by record owners, not by users themselves, each
system or network protected by the Safeguard software can assign one or more user
IDs to security administrators. If ownership of user authentication records is transferred
to a security administrator, the security administrator then has complete control of the
system-access controls that the Safeguard software enforces for those users.
For example, ADMIN.MANAGER could give the user authentication record for
ADMIN.BOB to a security administrator (SECURITY.SUSAN) with the following
sequence of SAFECOM commands. ADMIN.MANAGER begins by displaying the
current user attributes defined for ADMIN.BOB:
=INFO USER admin.bob
This INFO display shows that the user authentication record for ADMIN.BOB is
currently owned by 1,255 (ADMIN.MANAGER). ADMIN.MANAGER now gives the user
authentication record for ADMIN.BOB to SECURITY.SUSAN with this command:
=ALTER USER admin.bob, OWNER security.susan
GROUP.USER USER-ID OWNER LAST-MODIFIED LAST-LOGON STATUS WARNING-MODE
ADMIN.BOB 1,0 1,255 17JUN05, 11:22 * NONE * THAWED OFF