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-30
Establishing a Community of Network Users
be granted access to any system on which the user ID 1,0 is assigned to another user
name, such as, ADMIN.CAROL. (The use of user aliases as network users can alter
this behavior, as described at the end of this subsection.)
Coordination of group names and numbers across a network also means that an
administrative group can be defined as a network group or as a local group. A local
group is unique to one node. For example, Figure 2-1 shows a network on which the
group number 1, ADMIN, is defined on every node of the network, while group number
2 is assigned to the SOFTWARE group on \SF and \LA and to the SALES group on
\NY and \DA.
In the network user community shown in Figure 2-1, ADMIN.BOB is defined on every
node on the network and thus has access to every node on the network. But
SOFTWARE.JOE has access only to \SF and \LA, and SALES.FRED has access only
to \NY and \DA. In fact, network access is effectively segmented between the
SOFTWARE and SALES groups. No member of the SOFTWARE group can access
objects on \NY or \DA, and no member of the SALES group can access objects on \SF
or \LA.
For each node illustrated in Figure 2-1, a partial list of the system users on each node
is shown, along with the user ID, user name, and all remote passwords defined for the
user.