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
Installation and Management
Safeguard Administrator’s Manual—523317-013
10-8
Starting the SMP
In this example, the backup SMP process is created in CPU 4. If you do not specify a
backup processor, no backup process is created. Once the SMP is running, it
automatically creates these files:
The SMP also starts the SMON processes. It uses this naming convention for the
SMON process names:
$ZS00 - SMON running in CPU 0
$ZS01 - SMON running in CPU 1
$ZS02 - SMON running in CPU 2
$ZS03 - SMON running in CPU 3
.
.
$SYSTEM.SAFE.GUARD Contains object authorization records for all disk
objects (volumes, subvolumes, and disk files) on
$SYSTEM.
$SYSTEM.SAFE.OTHER Contains object authorization records for all local
system objects other than disk (devices,
subdevices, processes, subprocesses, and
OBJECTTYPEs).
$SYSTEM.SAFE.CONFIG Contains the attributes that determine Safeguard
configuration.
$SYSTEM.SAFE.CONFIGP
1
Contains the attributes that stores the new
password configuration information.
$SYSTEM.SAFE.CONFIGA Contains audit configuration information and
terminal definition records.
$SYSTEM.SAFE.A000000n Contains the initial audit files that serve as a
secondary audit pool after other audit pools are
added.
$SYSTEM.SAFE.LUSERID Contains user alias information and OSS user
attributes.
$SYSTEM.SAFE.LUSERIDG Is the alternate key file for LUSERID.
$SYSTEM.SAFE.PATGUARD Contains diskfile patterns.
$SYSTEM.SAFE.LUSERAX
#
Contains password, text description and binary
description records for an alias. Opens in secure
mode.
$SYSTEM.SYSTEM.USERAX
#
Contains password, text description and binary
description records for an user. Opens in secure
mode.
1
The $SYSTEM.SAFE.CONFIGP file is supported only on systems running G06.29 and later G-series RVUs
and H06.06 and later H-series RVUs.
#
The $SYSTEM.SAFE.LUSERAX and $SYSTEM.SYSTEM.USERAX are supported only on systems running
G06.27 and later G-series RVUs and H06.06 and later H-series RVUs.