STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 1 hour ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to F5 BIG-IP TMOS NDM Security Technical Implementation Guide

V-266083

CAT II (Medium)

The F5 BIG-IP appliance must obtain its public key certificates from an appropriate certificate policy through an approved service provider.

Rule ID

SV-266083r1024615_rule

STIG

F5 BIG-IP TMOS NDM Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-000366CCI-001159

Discussion

For user certificates, each organization obtains certificates from an approved, shared service provider, as required by OMB policy. For federal agencies operating a legacy public key infrastructure cross-certified with the Federal Bridge Certification Authority at medium assurance or higher, this Certification Authority (CA) will suffice.

Check Content

From the BIG-IP GUI:
1. System.
2. Certificate Management.
3. Device Certificate Management.
4. Device Certificate.
5. Verify the Issuer is an approved CA.

From the BIG-IP console, type the following command:

openssl x509 -in /config/httpd/conf/ssl.crt/server.crt -text

Note: Verify the issuer is an approved CA.

If the BIG-IP appliance does not obtain its public key certificates from an appropriate certificate policy through an approved service provider, this is a finding.

Fix Text

From the BIG-IP GUI:
1. System.
2. Certificate Management.
3. Device Certificate Management.
4. Device Certificate Signing Request.
5. Click "Renew".
6. Select "Certificate Authority" in "Issuer" and complete the form.
7. Copy or download and submit CSR to an approved CA.
8. Import the certificate via Device Certificate Management >> Device Certificate >> Import.