Rule ID
SV-242259r1028385_rule
Version
V2R3
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. Auditing account changes provides the necessary reconciliation that account management procedures are being followed. Without this audit trail, personnel without the proper authorization may gain access to critical network nodes. Associating event types, date/time of the event, identity of any individual or process associated with the event, source/destination of the event, location of the event, and the outcome of the event provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured network device. Both the SMS and TPS have the capability to capture and log detected security violations and potential security violations. DOD requires TCP at a minimum, but if operational needs permit, Encrypted TCP (also called TLS Syslog) is also supported.
1. Navigate to Admin >> Server properties >> Syslog. 2. Verify the configuration enables TCP or Encrypted TCP. 3. Verify Device Audit, Device System, SMS Audit, and SMS System log types are enabled and configured. If syslog is not configured to use TCP or Encrypted TCP or does not include the four log types, this is a finding.
1. Navigate to Admin >> Server properties >> Syslog >> New. 2. Click "enable". 3. Click "TCP" or "Encrypted TCP". 4. Under Log Type, select "Device Audit". 5. Facility is "Log Audit". 6. Timestamp: SMS Current Time. 7. Check "Include SMS hostname in Header". 8. Click "OK". 9. Repeat these steps for the following three other Log Types: Device System, SMS Audit, and SMS System. 10. Repeat steps to configure a second Syslog server IP host information. Note: Syslog servers used must be configured to alert system administrator and ISSO upon detection of unauthorized access, modification, or deletion of audit information.