| 1 |
This group of rules are meant to be used with the augenrules program. |
| 2 |
The augenrules program expects rules to be located in /etc/audit/rules.d/ |
| 3 |
The rules will get processed in a specific order based on their natural |
| 4 |
sort order. To make things easier to use, the files in this directory are |
| 5 |
organized into groups with the following meanings: |
| 6 |
|
| 7 |
10 - Kernel and auditctl configuration |
| 8 |
20 - Rules that could match general rules but we want a different match |
| 9 |
30 - Main rules |
| 10 |
40 - Optional rules |
| 11 |
50 - Server Specific rules |
| 12 |
70 - System local rules |
| 13 |
90 - Finalize (immutable) |
| 14 |
|
| 15 |
There is one set of rules, 31-privileged.rules, that should be regenerated. |
| 16 |
There is a script in the comments of that file. You can uncomment the commands |
| 17 |
and run the script and then rename the resulting file. |
| 18 |
|
| 19 |
The rules are not meant to be used all at once. They are pieces of a policy |
| 20 |
that should be thought out and individual files copied to /etc/audit/rules.d/ |
| 21 |
For example, if you wanted to set a system up in the STIG configuration, copy |
| 22 |
rules 10-base-config, 30-stig, 31-privileged, and 99-finalize. You can add |
| 23 |
more if you like. Also, not all arches have the same syscalls. It is expected |
| 24 |
that the rules be fine tuned for the arch they are deployed on. For example, |
| 25 |
aarch64 does not have the open syscall. It should just be deleted from the |
| 26 |
rules. |
| 27 |
|
| 28 |
Once you have the rules in the rules.d directory, you can load them by running |
| 29 |
augenrules --load |
| 30 |
|