SLEM 5 must generate audit records for all uses of the "ssh-keysign" command.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
---|---|---|---|---|---|---|
medium | V-261443 | SRG-OS-000037-GPOS-00015 | SLEM-05-654100 | SV-261443r996736_rule | 2024-06-04 | 1 |
Description |
---|
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
ℹ️ Check |
---|
Verify SLEM 5 generates an audit record for all uses of the "ssh-keysign" command with the following command: > sudo auditctl -l | grep -w '/usr/lib/ssh/ssh-keysign' -a always,exit -S all -F path=/usr/lib/ssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged-ssh-keysign If the command does not return any output, this is a finding. Note: The "key=" value is arbitrary and can be different from the example output above. |
✔️ Fix |
---|
Configure SLEM 5 to generate an audit record for all uses of the "ssh-keysign" command. Add or modify the following line in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/lib/ssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-keysign To reload the rules file, restart the audit daemon: > sudo systemctl restart auditd.service or issue the following command: > sudo augenrules --load |