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-39
Assigning an Alias to a User
To verify the results of the command, SECURITY.SUSAN issues this INFO USER
command:
=INFO USER admin.jeff, GENERAL
Assigning an Alias to a User
A user can be given alternate names, called aliases. Each alias assigned to a user can
have its own set of unique user attributes. For example, a single user can have several
aliases, and each alias can have a different command interpreter specified. This allows
the user to choose among several command interpreters by logging on with the
appropriate alias to start a session.
An alias can be used to log on to the system, but an alias name cannot appear on an
access control list. Because aliases cannot be specified on access control lists, all
Safeguard access mediation for an alias is based on the underlying user ID.
Special restrictions apply to the use of the ADD ALIAS command to assign an alias to
a user. To add an alias for a particular user, a person must have the authority to both
add and alter that user’s authentication record. The specific restrictions regarding use
of the ADD ALIAS command are:
•
If an OBJECTTYPE USER record exists, the person executing the ADD ALIAS
command must meet these two qualifications:
°
Have CREATE (C) authority on the OBJECTTYPE USER access control list
°
Be the owner of the underlying user ID or be the group manager of the owner
of the underlying user ID
•
If an OBJECTTYPE USER record does not exist, the person executing the ADD
ALIAS command must meet these two qualifications:
°
Be the group manager of the underlying user ID
°
Be the owner of the underlying user ID or be the group manager of the owner
of the underlying user ID
GROUP.USER USER-ID OWNER LAST-MODIFIED LAST-LOGON STATUS WARNING-MODE
ADMIN.JEFF 1,12 200,1 15AUG05, 11:54 12AUG05, 16:02 THAWED OFF
UID = 268
USER-EXPIRES = * NONE *
PASSWORD-EXPIRES = 28AUG05, 0:00
PASSWORD-MAY-CHANGE = * NONE *
PASSWORD-MUST-CHANGE EVERY = 30 DAYS
PASSWORD-EXPIRY-GRACE = * NONE *
LAST-LOGON = 12AUG05, 16:02
LAST-UNSUCESSFUL-ATTEMPT = * NONE *
LAST-MODIFIED = 15AUG05, 11:54
FROZEN/THAWED = THAWED
STATIC FAILED LOGON COUNT = 0
GUARDIAN DEFAULT SECURITY = NUNU
GUARDIAN DEFAULT VOLUME = $SECURE.JEFF