SLES-12-020320 - The SUSE operating system must generate audit records for all uses of the ssh-keysign command.

Information

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.

Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215

Solution

Configure the SUSE operating system to generate an audit record for all uses the 'ssh-keysign' command.

Add or update the following rules 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!=4294967295 -k privileged-ssh-keysign

The audit daemon must be restarted for the changes to take effect.

# sudo systemctl restart auditd.service

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_SLES_12_V2R13_STIG.zip

Item Details

Category: AUDIT AND ACCOUNTABILITY, MAINTENANCE

References: 800-53|AU-3, 800-53|AU-12a., 800-53|AU-12c., 800-53|MA-4(1)(a), CAT|III, CCI|CCI-000130, CCI|CCI-000169, CCI|CCI-000172, CCI|CCI-002884, Rule-ID|SV-217216r854118_rule, STIG-ID|SLES-12-020320, STIG-Legacy|SV-92035, STIG-Legacy|V-77339, Vuln-ID|V-217216

Plugin: Unix

Control ID: 9c528d13d69751c72bf241a4ed9ef821a28660b9c9bc42600fe9bd6936f9b090