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-16
Granting a User Temporary Access to Your System
Then SECURITY.SUSAN checks the INFO display:
=INFO USER admin.bob
Now the display shows that 200,1 (SECURITY.SUSAN) owns the user authentication
record for ADMIN.BOB. ADMIN.MANAGER has thus limited the ability to change the
user authentication record for ADMIN.BOB to only three users: SECURITY.SUSAN,
her group manager, and the super ID. Now that she owns this user authentication
record, SECURITY.SUSAN can use the ALTER USER command to control the ability
of ADMIN.BOB to access the system.
Granting a User Temporary Access to Your System
Occasionally, an installation needs to limit the period that a user has access to the
system. For example, if you hire a contract programmer for only a few weeks, the
security administrator might want to limit that programmer's ability to access the
system to the term of employment.
To control the length of time that a user can access the system, specify a USER-
EXPIRES date for the user. The USER-EXPIRES attribute is contained in every user
authentication record. Its default value is no expiration date.
For example, assume you are the manager of the SOFTWARE group (user ID 4,255).
The following sequence of SAFECOM commands adds a user whose ability to access
the system expires on December 19, 2005.
Reset the default user attributes to predefined values:
=RESET USER
Set default values for the USER-EXPIRES and PASSWORD attributes:
=SET USER USER-EXPIRES Dec 19 2005
=SET USER PASSWORD b9v7
GROUP.USER USER-ID OWNER LAST-MODIFIED LAST-LOGON STATUS WARNING-MODE
ADMIN.BOB 1,0 200,1 20JUN05, 11:25 * NONE * THAWED OFF