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-25
Deleting Users
Deleting Users
The primary and secondary owners of a user authentication record can delete that user
with the DELETE USER command. For example, SECURITY.SUSAN can delete
ADMIN.BOB with this command:
=DELETE USER admin.bob
To remove a deleted user from an access control list, you must designate that user by
user ID, not by user name. For example, the following commands remove ADMIN.BOB
(user ID 1,0) from the access control lists for all disk files on the system:
=ALTER DISKFILE $*.*.*, ACCESS 1,0 - *
=ALTER DISKFILE $*.*.*, ACCESS 1,0 - DENY *
Use the same set of commands specifying the other object types to be sure that
ADMIN.BOB is removed from all access control lists.
To remove a user from a diskfile-pattern protection record:
=ALTER DISKFILE-PATTERN $*.*.*, ALL, ACCESS 1,0 - *, ACCESS 1,0 – DENY *
Deleting Administrative Groups
An administrative group that was created with the ADD USER command is deleted
automatically when the last member of the group is deleted. Just as the user name and
user ID of a deleted user can be reassigned to a new user, the group name and
number of a deleted group can be reassigned to a new group. The local super ID (or
anyone authorized to add users) can reassign the deleted group name and number to
a new administrative group by adding the first member of the new group with that
group name or group number.
Automatic deletion does apply to an administrative group created with the ADD
GROUP command. For more information, see Section 3, Managing User Groups.
Note. After deleting a user, the security administrator should notify users to remove the
deleted user ID from access control lists for objects they own. Also, objects that the deleted
user ID owns should be transferred to other owners or deleted. Until all references to a deleted
user ID are removed, the user ID cannot be safely reused.
After these precautions are taken, the deleted user ID can be reassigned to a new user.