The TPS must provide audit record generation capability for detection events based on implementation of policy filters, rules, signatures, and anomaly analysis.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-242176	SRG-NET-000113-IDPS-00013	TIPP-IP-000100	SV-242176r1028382_rule	2024-09-16	2

Description
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. While auditing and logging are closely related, they are not the same. Logging is recording data about events that take place in a system, while auditing is the use of log records to identify security-relevant information such as system or user accesses. In short, log records are audited to establish an accurate history. Without logging, it would be impossible to establish an audit trail. TPS has 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.

Description

Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. While auditing and logging are closely related, they are not the same. Logging is recording data about events that take place in a system, while auditing is the use of log records to identify security-relevant information such as system or user accesses. In short, log records are audited to establish an accurate history. Without logging, it would be impossible to establish an audit trail. TPS has 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.

ℹ️ Check
In the Trend Micro SMS interface: 1. Go to the "Admin" tab and select "Server Properties". 2. Select the "Syslog" tab. 3. Navigate to Device Audit >> Device System >> SMS Audit >> SMS system. 4. Review the settings for all syslogs servers. If each syslog server is not configured to use TCP or Encrypted TCP, this is a finding.

✔️ Fix
In the Trend Micro SMS interface 1. Go to the "Admin" tab and select "Server Properties". 2. Select the "syslog" tab. 3. Click "New". 4. Under syslog server, type the hostname or IP address of the syslog server. (If using Encrypted TCP, and depending on the syslog server, enter the hostname, if needed). 5. Click "TCP" to ensure logging data is queued in the case of disconnection of the syslog server. 6. Type the port used by the centralized logging server (traditionally it is port 514 for TCP and 6514 for Encrypted TCP). 7. Under log type, select "Device Audit". 8. Repeat steps to configure all syslog servers. 9. Under facility click "Log Audit". 10. Click Event timestamp under "Include Timestamp in Header". 11. Select "include SMS hostname in header". Repeat this three more times to change the Log Type to include Device System, SMS Audit, and SMS System.

✔️ Fix

In the Trend Micro SMS interface 1. Go to the "Admin" tab and select "Server Properties". 2. Select the "syslog" tab. 3. Click "New". 4. Under syslog server, type the hostname or IP address of the syslog server. (If using Encrypted TCP, and depending on the syslog server, enter the hostname, if needed). 5. Click "TCP" to ensure logging data is queued in the case of disconnection of the syslog server. 6. Type the port used by the centralized logging server (traditionally it is port 514 for TCP and 6514 for Encrypted TCP). 7. Under log type, select "Device Audit". 8. Repeat steps to configure all syslog servers. 9. Under facility click "Log Audit". 10. Click Event timestamp under "Include Timestamp in Header". 11. Select "include SMS hostname in header". Repeat this three more times to change the Log Type to include Device System, SMS Audit, and SMS System.