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-35
Establishing Default Ownership
Establishing Default Ownership
You can specify two types of ownership with DEFAULT-PROTECTION. You specify
one with the OWNER attribute of the user record, and you specify the other with
OWNER authority in an access control list. Both types of owners can modify the disk
file authorization record after it is created. However, only the primary owner, specified
by the OWNER attribute, can set the PROGID attribute to protect program code. Also,
if the disk file is removed from the Safeguard database, the primary owner becomes
the Guardian owner.
If no primary owner is specified, as in the previous example, the primary owner is the
user for which DEFAULT-PROTECTION is being specified: in this case, ADMIN.JEFF.
However, if SECURITY.SUSAN needs to be the primary owner of all new files that
ADMIN.JEFF creates, she can specify her user ID for the OWNER attribute. For
example:
=ALTER USER 1,12, DEFAULT-PROTECTION OWNER 200,1
SECURITY.SUSAN displays the authentication record for ADMIN.JEFF to verify that
she is the default owner of any files he creates:
=INFO USER 1,12, DEFAULT-PROTECTION
The display shows:
Specifying Default Audit Attributes
DEFAULT PROTECTION also includes these four audit attributes for disk files:
•
AUDIT-ACCESS-PASS
•
AUDIT-ACCESS-FAIL
•
AUDIT-MANAGE-PASS
•
AUDIT-MANAGE-FAIL
These audit attributes are explained in detail in the Safeguard Audit Service Manual.
GROUP.USER USER-ID OWNER LAST-MODIFIED LAST-LOGON STATUS WARNING-MODE
ADMIN.JEFF 1,12 200,1 15AUG05, 9:05 12AUG05, 16:02 THAWED OFF
SUBJECT DEFAULT-PROTECTION SECTION
OWNER= 200,1
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