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
Configuration
Safeguard Administrator’s Manual—523317-013
9-20
Configuring Communication With $CMON
Configuring Communication With $CMON
You can set attributes in the configuration record to specify the manner in which the
Safeguard software communicates with $CMON during processing at a Safeguard
terminal.
These attributes relate to $CMON:
CMON
ON specifies that the Safeguard software is to communicate with the $CMON
process during the following events: logon, illegal logon attempts, logoff, and
newprocess of the command interpreter. If CMON is OFF, there is no
communication with $CMON during these events. The initial value is OFF.
CMONTIMEOUT
Specifies the number of seconds that the Safeguard software is to wait for any
$CMON operation. The default is 30 seconds.
CMONERROR
ACCEPT specifies that failures to communicate with $CMON for any reason are
ignored. DENY specifies that failures to communicate with $CMON result in the
current authentication being denied. The default is ACCEPT.
Use the ALTER SAFEGUARD command to change any of these attributes. For
example, this command specifies that the $CMON timeout period is to be changed to
15 seconds:
=ALTER SAFEGUARD, CMONTIMEOUT 15
Configuring Logon Dialog
These attributes specify aspects of the logon dialog:
BLINDLOGON
ON specifies that passwords will not be accepted if they are typed on the same line
as the user name and that they must be entered on a separate line following the
password prompt. OFF specifies that passwords can be entered on the same line
as the user name during logon. The initial value is OFF.
NAMELOGON
ON specifies that only a user name (group name.member name) is accepted when
a user logs on. OFF specifies that a user can enter either a user name (group
name.member name) or a user ID (group number,member number). The initial
value is ON.