OpenControls Logo

STIG Viewer

STIGViewer Support

The F5 BIG-IP appliance must be configured to use TCP when sending log records to the central audit server.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-266258F5BI-FW-300013SV-266258r1024873_ruleCCI-000366medium
Description
If the default UDP protocol is used for communication between the hosts and devices to the central log server, then log records that do not reach the log server are not detected as a data loss. The use of TCP to transport log records to the log servers improves delivery reliability.
STIGDate
F5 BIG-IP TMOS Firewall Security Technical Implementation Guide2024-09-09

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

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

CFG-01Configuration Management Program
1.00
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.7File Integrity Monitoring (FIM)
1.00
CFG-02Secure Baseline Configurations
0.50
CFG-02.7Approved Configuration Deviations
0.50
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-12Session Termination
1.00
AC-16(1)Dynamic Attribute Association
1.00
AC-17(1)Monitoring and Control
1.00
AC-2Account Management
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(11)Usage Conditions
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-24(1)Transmit Access Authorization Information
1.00
AC-25Reference Monitor
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 (2) 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.4.1
1.00
3.4.2
1.00
CCI1 mapping
CCI-000366
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (5) 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-09
1.00
PR.PS-01
1.00
PR.DS-10
0.50
PR.PSPlatform Security
0.50
PR.PS-05
0.50

Who does this work

10 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-266258r1024873_chk)

From the BIG-IP GUI: 1. System. 2. Logs. 3. Configuration. 4. Log Destinations. 5. <Name>. 6. Verify "Protocol" is set to TCP. From the BIG-IP Console, type the following command(s): tmsh list sys log-config destination remote-high-speed-log <Name> protocol Note: Verify this is set to "tcp". If the BIG-IP appliance is not configured to use TCP when sending log records to the central audit server, this is a finding.

Fix Text (F-70085r1024021_fix)

From the BIG-IP GUI: 1. System. 2. Logs. 3. Configuration. 4. Log Destinations. 5. Click the name of the log destination. 6. Set "Protocol" to TCP. 7. Click "Update". From the BIG-IP Console, type the following commands: tmsh modify sys log-config destination remote-high-speed-log <Name> protocol tcp