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-34
Establishing a Default Access Control List
Default auditing specifications
If default protection is specified for a user's disk files, the Safeguard software
automatically creates protection records for that user's files even if the user has not
been granted authority to add disk files to the Safeguard database. A user can be
granted or denied such authority with the OBJECTTYPE DISKFILE command, which is
described in Section 5, OBJECTTYPE Control.
Establishing a Default Access Control List
Assume that SECURITY.SUSAN owns the authentication record for ADMIN.JEFF,
user ID 1,12. She can establish a default access control list that applies to any disk
files that ADMIN.JEFF creates. Because the authentication record for ADMIN.JEFF
already exists, SECURITY.SUSAN uses the ALTER USER command to change the
record to include DEFAULT-PROTECTION:
=ALT USER 1,12, DEFAULT-PROTECTION ACCESS \200.1,12 *; 1,* (R,E)
This command gives all authorities to ADMIN.JEFF and gives READ and EXECUTE
authority to any other member of group 1, the ADMIN group. These authorities apply
only to disk files that ADMIN.JEFF creates after DEFAULT-PROTECTION is specified.
To check the DEFAULT-PROTECTION settings, SECURITY.SUSAN issues the INFO
USER command with the DEFAULT-PROTECTION option:
=INFO USER 1,12, DEFAULT-PROTECTION
The display shows:
Because ADMIN.JEFF was given all authorities, including OWNER authority, he can
change the protection on his individual files if he wants to. He cannot change the
DEFAULT-PROTECTION, however, because he does not own the user authentication
record for ADMIN.JEFF.
Note. Before using DEFAULT-PROTECTION, you might need to convert the USERID file. For
more information, see Section 10, Installation and Management.
Note. Specifying DEFAULT-PROTECTION when CHECK-DISKFILE-PATTERN is set to
ONLY results in the creation of extraneous normal protection records, which will not be
examined because ONLY only looks at pattern protection records.
GROUP.USER USER-ID OWNER LAST-MODIFIED LAST-LOGON STATUS WARNING-MODE
ADMIN.JEFF 1,12 200,1 15AUG05, 8:55 12AUG05, 16:02 THAWED OFF
SUBJECT DEFAULT-PROTECTION SECTION
OWNER= 1,12
AUDIT-ACCESS-PASS = NONE AUDIT-MANAGE-PASS = NONE
AUDIT-ACCESS-FAIL = NONE AUDIT-MANAGE-FAIL = NONE
001,012 R,W,E,P, O
001, * R, E
\200.001,012 R,W,E,P, O