SECURITY CONFIG File

Contents
vmx32besp
Contents
As part of installation, the SECURITY CONFIG file is created for you on the
VM:Secure
A - disk. You cannot use these records in this file in any other configuration file.
To make any changes to the AUTOPASS record, take down
VM:Secure
and make the changes manually in the file. The changes take effect when
VM:Secure
is brought back up. For the remaining records, you can change them dynamically and the changes take effect immediately.
SECURITY CONFIG File Records
The following table lists the records that can appear in the SECURITY CONFIG file and indicates whether they are required, recommended, or optional.
Record
Use
Quantity Allowed
AUTOEXP
Recommended if using the Rules Facility; ignored otherwise
1
AUTOPASS
Optional. AUTOPASS cannot be changed while
VM:Secure
is running.
1
DISPRULE
Optional if using the Rules Facility; ignored otherwise
1
ENABLE
Used for controlling optional Rules Facility security interfaces
1
GROUP
Recommended if using the Rules Facility; ignored otherwise
Multiple
JOURNAL
Optional
1
NORULE
Required if using the Rules Facility; ignored otherwise
1
PWSUPRES
Optional but recommended
1
Sample SECURITY CONFIG File
* JOURNAL 1 2 DISPRULE ALL * NORULE ACCEPT * GROUP DEVEL