Security Management Guide (G06.24+, H06.03+)

Safeguard System Security
Security Management Guide—522283-008
3-6
Controlling User Access
Controlling Backups With Safeguard Access Control Lists
To back up a file through BACKUP, a user must have READ access to that file. To back
up the entire system, the user must have READ access to all files.
You might want to create a special backup ID that is used only for backups. Give the ID
read-only access to all files and give the password to a trusted user responsible for
backups.
Rather than creating or modifying access control lists for every file on the system, you
might want to grant READ access to all volumes on the system. Then the Safeguard
CHECK-VOLUME configuration attribute must be turned on to activate checking at the
VOLUME level. For more information about configuring the Safeguard software, see
the Safeguard Administrator’s Manual.
Controlling Other Privileged Users
Take the following measures to control other privileged users:
•
Keep the size of the super group as small as possible. Instead, grant the
operations staff only the authorities they need. Use OBJECTTYPE access control
lists on objects to control super-group authorities.
•
Establish a procedure for removing privileged user IDs upon termination. If the
privileged ID has network access, notify the other nodes.
•
Freeze privileged users during vacations or other periods of absence. Use the
FREEZE USER command.
Controlling User Access
When a user ID is added through SAFECOM, the user ID is defined by a Safeguard
user authentication record. The following subsection describes how to add users
through SAFECOM and how to control user access through the attributes of the user
authentication record.
Many of a user’s privileges are determined by object authorization records rather than
by the user authentication record. For example, a user’s ability to run a program can
be determined by the access control list on the program file or the process name the
program runs under. For more information on these aspects of user privilege, see
Securing Objects on page 3-11.
Note. The super ID should be reserved for emergencies and nonroutine situations. When an
emergency arises, you might need the super ID to be as unrestricted as possible. Through
SYSGEN, you can make the super ID undeniable. Then the Safeguard software ignores explicit
denials of access authorities for the super ID. For information on how to specify an undeniable
super ID, see the Safeguard Administrator’s Manual.