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-24
Specifying Auditing for a User ID
For example, suppose ADMIN.BOB goes on vacation. SECURITY.SUSAN freezes the
ADMIN.BOB user name with the FREEZE USER command and displays the record
with the INFO USER command:
=FREEZE USER admin.bob
=INFO USER admin.bob
The STATUS field in the short INFO USER report shows the status of ADMIN.BOB is
now frozen.
When ADMIN.BOB returns from vacation, SECURITY.SUSAN restores his ability to log
on to the system with the THAW USER command and displays the record with the
INFO USER command:
=THAW USER admin.bob
=INFO USER admin.bob
Now the INFO USER display shows that record for ADMIN.BOB is thawed, and he can
once again log on to the system.
Specifying Auditing for a User ID
The primary and secondary owners of a user authentication record can specify auditing
for three types of events. These attributes are used to specify auditing for user
authentication, such as attempts to log on to the system:
AUDIT-AUTHENTICATE-PASS
AUDIT-AUTHENTICATE-FAIL
These attributes are used to specify auditing for attempts to manage the user
authentication record:
AUDIT-MANAGE-PASS
AUDIT-MANAGE-FAIL
These attributes are used to specify auditing for attempts by the user to perform an
event:
AUDIT-USER-ACTION-PASS
AUDIT-USER-ACTION-FAIL
For more information about specifying these types of auditing, see the Safeguard Audit
Service Manual.
GROUP.USER USER-ID OWNER LAST-MODIFIED LAST-LOGON STATUS WARNING-MODE
ADMIN.BOB 1,0 200,1 5AUG05, 16:45 5AUG05, 8:07 FROZEN OFF
GROUP.USER USER-ID OWNER LAST-MODIFIED LAST-LOGON STATUS WARNING-MODE
ADMIN.BOB 1,0 200,1 15AUG05, 8:15 5AUG05, 8:07 THAWED OFF