219
edits
FIPS Operational Environment: Difference between revisions
m
→Access to System Audit Log
| Line 138: | Line 138: | ||
====Access to System Audit Log==== | ====Access to System Audit Log==== | ||
To meet the audit requirements of FIPS 140-2 at Security Level 2, on Red Hat Enterprise Linux 4 and Solaris, the NSS cryptographic module | To meet the audit requirements of FIPS 140-2 at Security Level 2, on Red Hat Enterprise Linux 4 and Trusted Solaris, the NSS cryptographic module can be configured to use the audit mechanism provided by the operating system to audit events. The audit data will be stored in the system audit log. Only the root user can read or modify the system audit log. Auditing is turned off by default. To turn on the auditing capability, you need to set the environment variable NSS_ENABLE_AUDIT to 1. You also need to configure the operating systems audit mechanism. | ||
On Red Hat Enterprise Linux 4, the system audit log is in the <code>/var/log/audit</code> directory. This directory and the log files in it have the following permission bits (the following commands were run as the root user; only the root user can run the second command): | On Red Hat Enterprise Linux 4, the system audit log is in the <code>/var/log/audit</code> directory. This directory and the log files in it have the following permission bits (the following commands were run as the root user; only the root user can run the second command): | ||
| Line 153: | Line 153: | ||
'''Configure the Solaris Auditing:''' | '''Configure the Solaris Auditing:''' | ||
To configure the System | To configure the System mechanism on Solaris the following administration tasks need to be completed. Create the audit class 'fp', then create the audit event 'AUE_FIPS_AUDIT ' and add the class 'fp' to the audit_control file. | ||
Edit /etc/security/audit_class | Edit /etc/security/audit_class | ||