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
Controlling User Access
Safeguard Administrator’s Manual—523317-013
2-37
Establishing Guardian Defaults
Then she issues the INFO USER command with the CI option to check the results:
INFO USER admin.jeff, CI
The display shows:
Now SAFECOM is started automatically whenever ADMIN.JEFF logs on at a
Safeguard terminal. For more information, see Section 7, Securing Terminals.
The INFO USER display shows that you can specify other optional attributes relating to
the default command interpreter. For more information about these attributes, see the
Safeguard Reference Manual.
Establishing Guardian Defaults
When you add a user authentication record to the Safeguard database, you can
specify the Guardian default file-security string and the saved default volume and
subvolume for that user. The Guardian default file-security string is given to any of the
user’s disk files that are not under Safeguard protection. The user’s Guardian-saved
default volume and subvolume are established each time the user logs on to the
system or enters a VOLUME command without any parameters.
The GUARDIAN DEFAULT SECURITY attribute controls the Guardian default
file-security string. When you set this attribute in the Safeguard user authentication
record, it accomplishes the same function as using the DEFAULT program to set the
security string. For more information about the security string and the DEFAULT
program, see the Safeguard User’s Guide.
The GUARDIAN DEFAULT VOLUME attribute controls the Guardian-saved default
volume and subvolume. When you set this attribute in the Safeguard user
authentication record, it accomplishes the same function as using the DEFAULT
program to set the user’s saved default volume and subvolume.
Setting the File-Security String
If you do not specify a value for the GUARDIAN DEFAULT SECURITY attribute when
you add a Safeguard user authentication record, that user is given a Guardian default
security string of OOOO. This string indicates that when Guardian default protection is
applied, only the local file owner, the owner’s group manager, and the super ID have
READ, WRITE, EXECUTE, and PURGE authority.
GROUP.USER USER-ID OWNER LAST-MODIFIED LAST-LOGON STATUS WARNING-MODE
ADMIN.JEFF 1,12 200,1 15AUG05, 11:54 12AUG05, 16:02 THAWED OFF
CI-PROG = $SYSTEM.SYSTEM.SAFECOM
CI-LIB = * NONE *
CI-NAME = * NONE *
CI-SWAP = * NONE *
CI-CPU = * NONE *
CI-PRI = * NONE *
CI-PARAM-TEXT =