OpenControls Logo

STIG Viewer

STIGViewer Support

The TippingPoint SMS must be configured to send log data to at least two central log servers for the purpose of forwarding alerts to the administrators and the information system security officer (ISSO).

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-242259TIPP-NM-000670SV-242259r1028385_ruleCCI-000366high
Description
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.
STIGDate
Trend Micro TippingPoint NDM Security Technical Implementation Guide2025-03-10

Related Frameworks

19 mappings across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (51) 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.

BCD-05Contingency Plan Root Cause Analysis (RCA) & Lessons Learned
1.00
CFG-01Configuration Management Program
1.00
CFG-02Secure Baseline Configurations
1.00
CHG-04.1Automated Access Enforcement / Auditing
1.00
CPL-03Control Conformity Monitoring
1.00
CPL-03.2Functional Review Of Security, Compliance & Resilience Controls
1.00
CRY-01Use of Cryptographic Controls
1.00
DCH-01Data Protection
1.00
END-01Endpoint Device Management (EDM)
1.00
END-04Malicious Code Protection (Anti-Malware)
1.00

+41 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (100) 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-17(1)Monitoring and Control
1.00
AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-17(9)Disconnect or Disable Access
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-3(3)Mandatory Access Control
1.00
AC-3(7)Role-based Access Control
1.00
AC-4Information Flow Enforcement
1.00
AC-4(1)Object Security and Privacy Attributes
1.00

+90 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (9) 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.1.7
1.00
3.14.1
1.00
3.14.2
1.00
3.14.3
1.00
3.3.1
1.00
3.3.2
1.00
3.3.8
1.00
3.4.1
1.00
3.4.2
1.00
CCI19 mappings
CCI-000018
1.00
CCI-000130
1.00
CCI-000131
1.00
CCI-000132
1.00
CCI-000134
1.00
CCI-000135
1.00
CCI-000169
1.00
CCI-000172
1.00
CCI-000366
1.00
CCI-001403
1.00

+9 more (top 10 by weight shown)

NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (14) 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
ID.IM-01
1.00
ID.IM-02
1.00
ID.IM-03
1.00
PR.DS-10
1.00
PR.PS-01
1.00
PR.PS-02
1.00
PR.PS-04
1.00

+4 more (top 10 by confidence shown)

Who does this work

20 NICE work roles and 11 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-242259r1028385_chk)

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.

Fix Text (F-45492r1028384_fix)

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.