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 Security Groups
Safeguard Administrator’s Manual—523317-013
6-6
Freezing and Thawing Security Groups
Freezing and Thawing Security Groups
A security group can be frozen by the primary owner or by any user with OWNER
authority on the access control list for the group. When a group is frozen, the only
individuals who can execute the commands restricted to that group are the primary
owner, the primary owner's group manager, owners on the access control list, and the
local super ID.
For example, ADMIN.BOB can use this command to suspend the EXECUTE authority
granted to ADMIN.KEVIN and ADMIN.SUE:
=FREEZE SECURITY-GROUP SEC-ADM
ADMIN.BOB then uses the INFO SECURITY-GROUP command to verify the results:
=INFO SECURITY-GROUP SEC-ADM
The display shows:
Until ADMIN.BOB thaws the group authorization record, only he, his group manager,
and the local super ID can execute the commands restricted to the
SECURITY-ADMINISTRATOR group.
To thaw the group, ADMIN.BOB issues this command:
=THAW SECURITY-GROUP SECURITY-ADMINISTRATOR
The SECURITY-OSS-ADMINISTRATOR security group can be frozen by the primary
owner or by any user with OWNER authority on the access control list for the group.
For example,
=FREEZE SECURITY-GROUP SECURITY-OSS-ADMINISTRATOR
To verify the results:
=INFO SECURITY-GROUP SECURITY-OSS-ADMINISTRATOR
The display shows:
LAST-MODIFIED OWNER STATUS
GROUP SECURITY-ADMINISTRATOR
26JAN93, 11:26 200,8 FROZEN
200,5 E
200,6 E
LAST-MODIFIED OWNER STATUS
SECURITY-OSS-ADMINISTRATOR
14MAR06, 1:29 255,5 FROZEN
240,001 O
240,002 E
240,003 O
240,004 E