OpenControls Logo

STIG Viewer

STIGViewer Support

The F5 BIG-IP appliance must generate audit records and send records to redundant central syslog servers that are separate from the appliance.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-266075F5BI-DM-300034SV-266075r1024607_ruleCCI-001851high
Description
Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. MCP audit records are generated from various components within the network device. For example, it logs the creation of DNS objects and DNSSEC configuration, including key creations. Satisfies: SRG-APP-000515-NDM-000325, SRG-APP-000360-NDM-000295, SRG-APP-000516-NDM-000350
STIGDate
F5 BIG-IP TMOS NDM Security Technical Implementation Guide2025-06-12

Related Frameworks

3 mappings across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (26) 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
CPL-03Control Conformity Monitoring
1.00
CPL-03.2Functional Review Of Security, Compliance & Resilience Controls
1.00
GOV-05Measures of Performance
1.00
IAO-02Assessments
1.00
IAO-02.4Security Assessment Report (SAR)
1.00
IAO-05Capabilities Deficiency Tracking
1.00
IRO-13Root Cause Analysis (RCA) & Lessons Learned
1.00
MNT-01Maintenance Operations
1.00
MNT-02Controlled Maintenance
1.00

+16 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (39) 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-2(1)Automated System Account Management
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-6(9)Log Use of Privileged Functions
1.00
AU-10Non-repudiation
1.00
AU-12Audit Record Generation
1.00
AU-12(1)System-wide and Time-correlated Audit Trail
1.00
AU-12(3)Changes by Authorized Individuals
1.00
AU-14(1)System Start-up
1.00

+29 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.14.1
1.00
3.14.2
1.00
3.14.3
1.00
CCI3 mappings
CCI-001851
1.00
CCI-001858
1.00
CCI-002605
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

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

ID.IM-01
1.00
ID.IM-02
1.00
ID.IM-03
1.00
PR.PS-02
1.00
ID.RA-01
0.50
ID.RA-08
0.50

Who does this work

16 NICE work roles and 10 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-266075r1024607_chk)

From the BIG-IP GUI: 1. System. 2. Logs. 3. Configuration. 4. Remote Logging. From the BIG-IP Console, issue the following command: tmsh list sys syslog remote-servers Note: This must return at least two remote IP addresses of syslog server. If the BIG-IP appliance does not send audit records to one or more central syslog servers that are separate from the appliance, this is a finding.

Fix Text (F-69901r1023475_fix)

Configure two or more central syslog servers. From the BIG-IP GUI: 1. System. 2. Logs. 3. Configuration. 4. Remote Logging. 5. Add the IP address of a syslog server in the "Remote IP" field, modify the port if necessary, and click "Add". 6. Click "Update". From the BIG-IP Console, issue the following commands: tmsh modify sys syslog remote-servers add { <name> { host <ip address> remote-port <port> } } tmsh save sys config