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-33
Establishing Default Protection for a User's Disk
Files
However, the underlying user ID defined for the alias at the remote node is still used in
access decisions based on Safeguard access control lists at that node.
If the remote node is running a product version prior to D30 and does not support user
aliases, the user ID identified by the PAID requesting the access is verified, and
access decisions are based on that user ID.
If the local node is running a product version prior to D30 and does not support user
aliases, the request cannot originate from an alias.
Group Lists
Effective with D30 Safeguard, users and aliases can belong to multiple groups. Each
user and alias has a group list that specifies group membership. Any user or alias can
belong to any group, no matter what kind of a group it is. When a subject is validated at
a remote node, the group list used is the one associated with that user or alias
authentication record at the remote node.
D30 and later Safeguard systems can determine the user ID or alias under which a
user originally logged on at the start of a session even when the PAID is changed
during the session. This original name, known as the login name, is used to determine
the subject’s group list at the remote node. Although the user or alias was validated
under a different PAID at the remote node, the group list is taken from the remote
node’s authentication record associated with the requestor’s login name.
If no group list is specified at the remote node, the group list is empty, and process'
group membership is indicated by its effective group ID. (The effective group ID is the
same as the user's primary group ID unless it has been changed during the session.)
If either the local node or the remote node is running a product version prior to D30
and does not support group lists, the administrative group of the user ID associated
with the requesting PAID is the only group to which the user belongs.
Establishing Default Protection for a User's
Disk Files
The owner of a user authentication record can specify default protection for a user's
disk files. With default protection, when a user creates a disk file, it is automatically
added to the Safeguard database with the specified settings. If no default protection is
specified, new files created by the user are protected by Guardian security unless the
user explicitly adds them to the Safeguard database. You control default protection
with the DEFAULT-PROTECTION attribute of the user authentication record.
You can specify the following DEFAULT-PROTECTION attributes for disk files that a
user creates:
•
A default access control list
•
A default owner of the disk-file authorization record