This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
aix:aixpert [2021/01/01 21:21] 127.0.0.1 external edit |
aix:aixpert [2024/09/06 23:40] (current) manu [AIX Security Expert (howto)] |
||
---|---|---|---|
Line 21: | Line 21: | ||
When you use auditing, the file etc/security/aixpert/check_report.txt, will keep a trace of all changes outsite aixpert. | When you use auditing, the file etc/security/aixpert/check_report.txt, will keep a trace of all changes outsite aixpert. | ||
+ | <cli prompt='>'> | ||
+ | root@aixtest /etc/security/aixpert> aixpert -l l -n -o /etc/security/aixpert/custom/my_low.xml -a -o /etc/security/aixpert/custom/my_shortinfo.xml | ||
+ | </cli> | ||
+ | ===== Custom rules ===== | ||
+ | Create a custom security rule | ||
+ | <cli prompt='#'> | ||
+ | # aixpert –l high –n –o /tmp/high_security.xml | ||
+ | </cli> | ||
+ | |||
+ | Now you can edit the file /tmp/high_security.xml and remove the security settings which are not required to you environments. The security settings under the xml file will have the description and the script it will use to implement the security setting. | ||
+ | |||
+ | Once you have completed the editing you can consider it as a baseline security for your system. | ||
+ | |||
+ | Now apply the security setting to your system by | ||
+ | <cli prompt='#'> | ||
+ | # aixpert –f /tmp/high_security.xml | ||
+ | </cli> | ||
+ | |||
+ | If you find something gone wrong, you could undo all the changes by | ||
+ | <cli prompt='#'> | ||
+ | # aixpert –u | ||
+ | </cli> | ||
+ | |||
+ | Now to put a check every day to find the security is not compromised you can use | ||
+ | <cli prompt='#'> | ||
+ | # aixpert –c | ||
+ | </cli> |