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
Introduction
Safeguard Administrator’s Manual—523317-013
1-4
Who Can Run SAFECOM?
Who Can Run SAFECOM?
Decide who will use SAFECOM. Once a user runs SAFECOM, only the Safeguard
internal restrictions limit the user's capabilities. The Safeguard software imposes
internal restrictions on commands such as ADD USER, ALTER USER, and ADD
DEVICE, and most SAFECOM operations on existing protection records are restricted
to the record owner, the owner's group manager, and the local super ID. However
many SAFECOM commands are unrestricted.
If you want to limit the number of users who can use SAFECOM, you can use either
the standard security system or the Safeguard subsystem to secure the SAFECOM
program object file. Section 10, Installation and Management, describes how to use the
Safeguard subsystem to secure the SAFECOM program object file and the Safeguard
Subsystem Programmatic Interface (SPI).
Analyzing Security Needs
When you first start the SMP (Security Manager Process), all users listed in the
USERID file are automatically put under Safeguard control. The Safeguard software
offers control over additional user attributes, such as the password change
requirement and user expiration date. Decide in advance which users require
additional controls and determine what those controls will be. Section 2, Controlling
User Access, describes these additional user controls.