UCF STIG Viewer Logo

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


Overview

Finding ID Version Rule ID IA Controls Severity
V-217216 SLES-12-020320 SV-217216r854118_rule Low
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. 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
STIG Date
SLES 12 Security Technical Implementation Guide 2022-09-13

Details

Check Text ( C-18444r622370_chk )
Verify the SUSE operating system generates an audit record for all uses of the "ssh-keysign" command.

Check that the following command call is being audited by performing the following command on the system rules in "/etc/audit/audit.rules":

# sudo grep -i ssh-keysign /etc/audit/audit.rules

-a always,exit -F path=/usr/lib/ssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-ssh-keysign

If the command does not return any output or the returned line is commented out, this is a finding.
Fix Text (F-18442r622371_fix)
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