OpenControls Logo

STIG Viewer

STIGViewer Support

The F5 BIG-IP appliance must be running an operating system release that is currently supported by the vendor.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-266080F5BI-DM-300041SV-266080r1024886_ruleCCI-000366high
Description
Network devices running an unsupported operating system lack current security fixes required to mitigate the risks associated with recent vulnerabilities.
STIGDate
F5 BIG-IP TMOS NDM Security Technical Implementation Guide2025-06-12

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-266080r1024886_chk)

From the BIG-IP GUI: 1. System. 2. Configuration. 3. Device. 4. General. 5. Verify "Version" is currently supported according to the vendor support site. From the BIG-IP console, type the following command(s): tmsh list cm device version Note: Verify the version is currently supported on the vendor's website. If the BIG-IP appliance is not running an operating system release that is currently supported by the vendor, this is a finding.

Fix Text (F-69906r1023490_fix)

If the release is not a supported version, then update the version. From the BIG-IP GUI: 1. Import .iso. a. System. b. Software Management. c. Image List. d. Import .iso of supported BIG-IP operating system. e. Import the corresponding .iso.sig file. f. Install. 2. Switch boot location to new install. a. System. b. Software Management. c. Boot Locations. d. Select new install location. e. Optionally change "Install Configuration" to "Yes". f. Activate.