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
Managing User Groups
Safeguard Administrator’s Manual—523317-013
3-4
Transferring Group Ownership
The display shows:
Now any access control list entry that contains the entry 144,* is interpreted by the
Safeguard software to include all members of group 144, including TEST.PHIL,
TEST.JUNE, and Group-Super.
Suppose that ADMIN.DON later decides that the user TEST.PHIL no longer needs
access to the protected files. He enters this command to remove TEST.PHIL from the
group:
=ALTER GROUP PROG4, MEMBER -test.phil
The minus sign at the beginning of the member list specifies that the users in the list
are to be removed from the group.
Transferring Group Ownership
You can transfer ownership of a group definition record to another user. For example,
ADMIN.DON enters this command to give ownership of the PROG4 group definition
record to ADMIN.FRAN (16,3):
=ALTER GROUP PROG4, OWNER admin.fran
To verify the results:
=INFO GROUP PROG4
The display shows:
ADMIN.FRAN is now responsible for managing membership in the PROG4 group.
However, ADMIN.FRAN has no authority to manage the user authentication records of
the group members. The owner of a user authentication record retains responsibility for
the administration of that user.
In this instance, ADMIN.DON retains administrative responsibility for PROG4.SUSAN
because he added her user authentication record with the ADD USER command. The
PROG4 group is the administrative group for PROG4.SUSAN.
GROUP NAME NUMBER OWNER LAST-MODIFIED
PROG4 144 16,24 23JUL94, 11:49
AUTO-DELETE = OFF
DESCRIPTION = Maintenance programmers for Inventory System
MEMBER = PROG4.SUSAN
MEMBER = TEST.PHIL
MEMBER = TEST.JUNE
MEMBER = Group-Super
GROUP NAME NUMBER OWNER LAST-MODIFIED
PROG4 144 16,3 26JUL94, 13:20