OpenControls Logo

STIG Viewer

STIGViewer Support

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

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-242176TIPP-IP-000100SV-242176r1028382_ruleCCI-001851medium
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.
STIGDate
Trend Micro TippingPoint IDPS Security Technical Implementation Guide2024-09-16

Related Frameworks

9 mappings across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (17) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

END-01Endpoint Device Management (EDM)
1.00
END-04Malicious Code Protection (Anti-Malware)
1.00
END-06Endpoint File Integrity Monitoring (FIM)
1.00
MON-01Continuous Monitoring
1.00
MON-01.1Intrusion Detection & Prevention Systems (IDS & IPS)
1.00
MON-01.3Inbound & Outbound Communications Traffic
1.00
MON-01.4System Generated Alerts
1.00
MON-01.7File Integrity Monitoring (FIM)
1.00
MON-01.8Security Event Monitoring
1.00
MON-03Content of Event Logs
1.00

+7 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (82) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-16Security and Privacy Attributes
1.00
AC-17(1)Monitoring and Control
1.00
AC-17(10)Authenticate Remote Commands
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(10)Shared and Group Account Credential Change
1.00
AC-2(11)Usage Conditions
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00

+72 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.3.1
1.00
3.3.2
1.00
3.3.4
1.00
CCI9 mappings
CCI-000130
1.00
CCI-000131
1.00
CCI-000132
1.00
CCI-000133
1.00
CCI-000134
1.00
CCI-000140
1.00
CCI-000169
1.00
CCI-001851
1.00
CCI-002656
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (4) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

DE.CM-01
1.00
DE.CM-03
1.00
DE.CM-09
1.00
PR.PS-04
1.00

Who does this work

12 NICE work roles and 9 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-242176r1028382_chk)

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 Text (F-45409r1028382_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.