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-5
Adding Users to the System
An administrative group is defined implicitly when the first member of that group is
added to the system. By default, only the local super ID can define a new
administrative group with the ADD USER command. If your installation has group
managers (with member number 255), you might want to add that user as the first
group member. The group manager can then add other new members to the group.
(Alternatively, you can use the OBJECTTYPE USER command to define a special set
of users who have the authority to add other users to the Safeguard database. For
more information, see Section 5, OBJECTTYPE Control.)
To create a new administrative group, the local super ID assigns a unique group name
to a previously unused group number. From that point on, the association between the
group number and the group name is fixed. Any other users added to the group must
be assigned the group name defined for that group number. Examples in this section
show how to define administrative groups.
It is also possible to explicitly create a group that can serve as an administrative group
before adding users to it. Use the ADD GROUP command, as described in Section 3,
Managing User Groups.
Adding Users to the System
When a new user is added to a system with the Safeguard software, whoever adds the
user can define several security attributes for the user. The Safeguard subsystem uses
these attributes to control user access to the system.
Table 2-1 on page 2-6 describes the user security attributes and gives the predefined
default value for each attribute. The predefined attribute values are in effect when you
start a SAFECOM process.