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
Safeguard Administrator’s Manual—523317-013
10-1
10 Installation and Management
This section is intended for the security administrator or trusted user who is
responsible for installing, supervising, and maintaining the Safeguard subsystem.
This section includes an overview of the Safeguard software components, procedures
for installing the Safeguard subsystem, and guidelines for securing the Safeguard
software.
Safeguard Components
Before you install the Safeguard software, you should have a basic understanding of its
software components. The Safeguard software consists of a number of processes and
security database files. The processes cooperate to manage the contents of the
security database, to authenticate users attempting to log on to the system, and to
authorize all attempts to access protected objects.
These Safeguard components reside on every system where the Safeguard software
is installed:
•
The subject database, which contains a user authentication record for every user
who is authorized to use the system.
•
The object database, which contains object authorization records for every disk
file, disk volume, disk subvolume, device, subdevice, process, subprocess, and
OBJECTTYPE that has been placed under Safeguard protection.
•
SMP (Security Manager Process, with the process name $ZSMP), which is
responsible for managing all changes to the subject and object databases and for
authenticating user logon attempts.
•
SAFECOM, the Safeguard command interpreter (SAFECOM provides an
interactive command interface to the SMP).
•
SMON (Security Monitor), which is responsible for authorizing all attempts to
access protected objects. A separate SMON process runs in each processor in a
Safeguard protected system. Each SMON is responsible for authorizing all access
to objects controlled by I/O processes running in its processor and to all processes
with Safeguard protected names running in its processor.
The Security Manager Process (SMP)
The SMP runs on every system on which the Safeguard software is installed. The SMP
has three major responsibilities:
•
Security database management
•
User authentication
•
Security Monitor (SMON) process management