Safeguard Administrator's Manual (G06.24+, H06.03+)

Table Of Contents
Controlling User Access
Safeguard Administrator’s Manual523317-013
2-36
Eliminating Default Protection for a User
Assume that SECURITY.SUSAN wants to specify default auditing for all files that
ADMIN.JEFF creates. To do so, she sets DEFAULT-PROTECTION to include auditing
of all successful attempts to access Jeff's disk files:
=ALTER USER 1,12, DEFAULT-PROTECTION &
=AUDIT-ACCESS-PASS ALL
Then she displays the record to verify the DEFAULT-PROTECTION audit settings:
=INFO USER 1,12, DEFAULT-PROTECTION
Eliminating Default Protection for a User
If you decide to eliminate default protection for a user, specify the
DEFAULT-PROTECTION attribute with no default attributes following it.
For example, SECURITY.SUSAN issues this command to eliminate default protection
for ADMIN.JEFF:
=ALTER USER 1,12, DEFAULT-PROTECTION
Now any new files created by ADMIN.JEFF are protected by Guardian security unless
they are explicitly added to the Safeguard database.
Specifying a Default Command Interpreter for
a User
When a user logs on at a Safeguard terminal, a specific command interpreter (process)
is started automatically after the user has been authenticated. You can designate this
command interpreter in the user authentication record for each user.
For example, assume that ADMIN.JEFF uses SAFECOM for most of his daily activities
and that his terminal is controlled by the Safeguard software. SECURITY.SUSAN can
specify SAFECOM as the default command interpreter in Jeff's user authentication
record.
To do so, she uses the ALTER USER command to specify the name of the SAFECOM
object file on Jeff's system:
ALTER USER admin.jeff, CI-PROG $system.system.safecom
GROUP.USER USER-ID OWNER LAST-MODIFIED LAST-LOGON STATUS WARNING-MODE
ADMIN.JEFF 1,12 200,1 15AUG05, 9:35 12AUG05, 16:02 THAWED OFF
SUBJECT DEFAULT-PROTECTION SECTION
OWNER= 200,1
AUDIT-ACCESS-PASS = ALL AUDIT-MANAGE-PASS = NONE
AUDIT-ACCESS-FAIL = NONE AUDIT-MANAGE-FAIL = NONE
001,012 R,W,E,P, O
001, * R, E