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-29
Establishing a Community of Network Users
On the remote system, \LA
ADMIN.BOB is given a remote password for his system, \LA:
=ALTER USER 1,0, REMOTEPASSWORD \LA abc
On the local system, \NY
Give ADMIN.BOB a remote password for his system, \LA:
=ALTER USER 1,0, REMOTEPASSWORD \LA abc
Now the network user ADMIN.BOB has two-way access between \NY and \LA. The
difference between one-way access and two-way access for a network user can be
diagrammed as:
ONE-WAY ACCESS (from \LA to \NY):
System \NY System \LA
User Name : ADMIN.BOB User Name : ADMIN.BOB
User ID : 1,0 User ID : 1,0
Remote Password: \NY xyz Remote Password: \NY xyz
With these remote passwords, ADMIN.BOB can access objects on \NY from \LA.
ONE-WAY ACCESS (from \NY to \LA):
System \NY System \LA
User Name : ADMIN.BOB User Name : ADMIN.BOB
User ID : 1,0 User ID : 1,0
Remote password: \LA abc Remote password: \LA abc
With these remote passwords, ADMIN.BOB can access objects on \LA from \NY.
TWO-WAY ACCESS (between \NY and \LA):
System \NY System \LA
User Name : ADMIN.BOB User Name : ADMIN.BOB
User ID : 1,0 User ID : 1,0
Remote password: \NY xyz Remote password: \NY xyz
Remote password: \LA abc Remote password: \LA abc
With these remote passwords, ADMIN.BOB can access objects on \NY from \LA, and
he can access objects on \LA from \NY.
Establishing a Community of Network Users
Because network users must have the same user name and user ID on every node to
which they have access, the assignment of group names to group numbers must be
coordinated at each node. For example, a user at the node \LA named ADMIN.BOB
with a user ID of 1,0 cannot be granted access to any system where the group
number 1 is assigned to a group name other than ADMIN. Also, ADMIN.BOB cannot