Safeguard Administrator's Manual (G06.29+, H06.08+, J06.03+)

Installation and Management
Safeguard Administrator’s Manual—523317-029
10-12
Guidelines for Securing the Safeguard Subsystem
Guidelines for Securing the Safeguard
Subsystem
After you install the Safeguard subsystem, take steps to ensure the security of its
components. To do so:
1. Secure the SAFECOM program object file as necessary. If you create an access
control list for SAFECOM, you can restrict the use of the command interpreter to
certain users. Protecting the SAFECOM object file has no effect on users of the
Safeguard Subsystem Programmatic Interface (SPI).
To restrict the use of SAFECOM, you must add a disk file authorization record for
the SAFECOM file and specify an access control list that names the qualified
users. Give EXECUTE authority to each user who needs to use the command
interpreter.
Depending on your security policy, the use of SAFECOM might be unrestricted, or
it might be limited to only a few qualified personnel.
For example, if all users are expected to use Safeguard to secure their files, they
must be able to execute SAFECOM. This command allows such access:
=ADD DISKFILE $SYSTEM.SYSnn.SAFECOM, ACCESS *.* e
If your security policy is restrictive so that the Safeguard software is to be used by
only a few individuals, specify only individuals on the access control list. For
example, this command provides EXECUTE authority to only users who are
members of the group SECURE:
=ADD DISKFILE $SYSTEM.SYSnn.SAFECOM, ACCESS secure.* e
Also make sure no other copies of SAFECOM (other SYSnn) are secured less
restrictively.
For example, if you want a diskfile having process access records and the new
process that is launched from that diskfile to inherit process access record from the
same, and for the same owner of the record and disk file, this command allows
such access:
=ADD DISKFILE $SYSTEM.SYSnn.SAFECOM, PROCESS-ACCESS TEST.USER
(R,W,C)
2. For each object type, determine which individual objects on the system are
sensitive and should be protected. Some of these objects are:
•
Sensitive disk files, such as the Safeguard audit files, the USERID file, and
certain files used by your applications.
•
Sensitive disk volumes and subvolumes such as the system disk ($SYSTEM)
and system subvolume ($SYSTEM.SYSnn), as well as all important production
and application disks.
•
Sensitive devices, including certain terminals, printers, or communication lines.