The F5 BIG-IP appliance must obtain its public key certificates from an appropriate certificate policy through an approved service provider.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-266083 | F5BI-DM-300044 | SV-266083r1024615_rule | CCI-000366 | medium |
| Description | ||||
| 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. | ||||
| STIG | Date | |||
| F5 BIG-IP TMOS NDM Security Technical Implementation Guide | 2025-06-12 | |||
Related Frameworks
4 paths across 3 frameworks
Related Frameworks
NIST 800-531 mapping
CM-6
1.00
- DISA · V1R2 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1712 mappings
3.4.1
1.00
- DISA · V1R2 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
3.4.2
1.00
- DISA · V1R2 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-000366
1.00
- DISA · V1R2 · disa_xccdf · related
Details
Check Text (C-266083r1024615_chk)
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 (F-69909r1023499_fix)
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.