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-20
Requiring Users to Change Their Passwords
Any user can use the command interpreter PASSWORD program to change his or her
own password. You can also change your password during logon without using the
PASSWORD program. This method of changing your password is described in the
Safeguard User’s Guide.
To continue the example, suppose the date is July 27, 2005, and ADMIN.BOB
changes his password with the PASSWORD command:
8> PASSWORD x87d9
After changing his password, ADMIN.BOB uses the INFO USER command to
determine the next date by which he must change his password:
9> SAFECOM INFO USER admin.bob, GENERAL
The Safeguard software has recalculated the PASSWORD-EXPIRES date. Because
ADMIN.BOB changed his password on July 27 and his PASSWORD-MUST-CHANGE
period is 30 days, his new PASSWORD-EXPIRES date is August 26.
This example illustrates the basic password expiration mechanism. When a
PASSWORD-MUST-CHANGE period is first established or changed for a user, the
Safeguard software calculates a PASSWORD-EXPIRES date by adding the
PASSWORD-MUST-CHANGE period to the current date. Also, whenever the user
changes the password, the Safeguard software calculates a new
PASSWORD-EXPIRES date by adding the PASSWORD-MUST-CHANGE period to
the current date.
The Safeguard configuration attribute PASSWORD-MAY-CHANGE can affect
password expiration and the user's ability to change the password. For a description of
the PASSWORD-MAY-CHANGE attribute, see Section 9, Configuration.
If July 28 passes and ADMIN.BOB forgets to change his password, he cannot log on to
the system after that date because he has no expired password grace period. Unable
to log on, ADMIN.BOB calls his security administrator, SECURITY.SUSAN on July 29,
GROUP.USER USER-ID OWNER LAST-MODIFIED LAST-LOGON STATUS WARNING-MODE
ADMIN.BOB 1,0 200,1 27JUL05, 14:09 27JUL05, 8:02 THAWED OFF
UID = 256
USER-EXPIRES = * NONE *
PASSWORD-EXPIRES = 26AUG05, 0:00
PASSWORD-MAY-CHANGE = * NONE *
PASSWORD-MUST-CHANGE EVERY = 30 DAYS
PASSWORD-EXPIRY-GRACE = * NONE *
LAST-LOGON = 27JUL05, 8:02
LAST-UNSUCESSFUL-ATTEMPT = * NONE *
LAST-MODIFIED = 27JUL05, 14:09
FROZEN/THAWED = THAWED
STATIC FAILED LOGON COUNT = 0
GUARDIAN DEFAULT SECURITY = OOOO
GUARDIAN DEFAULT VOLUME = $SYSTEM.NOSUBVOL