F5 BIG-IP SSL and virtual servers
Rules for client-SSL profiles, pools and HTTPS virtual servers. Each rule checks every object of its kind on its own, and fails if even one is wrong. They come from the bigip-ssl-virtual-hardening policy template.
Every example on this page was checked with rConfig Pro's policy engine on Each of the 10 configs below was run through rConfig Pro’s evaluator with the rule above it, and gave the result shown. Configs from a sample are sanitised excerpts. Cards marked written for this page cover objects no sample has. A card marked changed has one line edited to show a failure.
All the rules come from bigip-ssl-virtual-hardening.policy in the policy templates (v1.5.0). Import the whole file with Import Templates (see importing a policy template), or copy one rule into your own definition. The F5 BIG-IP templates page lists the file’s known limitations. Run the rules against the tmsh configuration in brace format.
| Rule | Method | Since |
|---|---|---|
| No SSLv3, TLS 1.0 or TLS 1.1 | evaluate_block |
8.3.0 |
| No DEFAULT or ALL cipher set | evaluate_block |
8.3.0 |
| Every pool has a monitor | evaluate_block |
8.3.0 |
| HTTPS virtual servers use client-SSL | evaluate_block |
8.3.0 |
| HTTPS virtual servers keep SNAT | evaluate_block |
8.3.0 |
No SSLv3, TLS 1.0 or TLS 1.1
SSLv3, TLS 1.0 and TLS 1.1 are old and broken. Each client-SSL profile must turn all three off. The TLS 1.0 check uses a regex so that no-tlsv1.1 does not count as no-tlsv1.
// F5: Every client-SSL profile disables SSLv3 and TLSv1.0/1.1#[evaluate_block]scope: ^ltm profile client-sslall: - no-sslv3 - regex: '/no-tlsv1(\s|$)/m' - no-tlsv1.1ltm profile client-ssl /Common/clientssl_app { ciphers ECDHE+AES-GCM defaults-from /Common/clientssl options { dont-insert-empty-fragments no-sslv3 no-tlsv1 no-tlsv1.1 }}Why: All three old versions are turned off.
ltm profile client-ssl /Common/clientssl_app { ciphers ECDHE+AES-GCM defaults-from /Common/clientssl options { dont-insert-empty-fragments no-sslv3 no-tlsv1.1 }}Why: no-tlsv1 is missing, so TLS 1.0 is still allowed. The result names this profile.
Expected result in rConfig, with this rule as the only rule in a definition:
| Config | Rule result | Overall result |
|---|---|---|
| Passing config | pass | PASS |
| Failing config | fail | FAIL |
Framework mapping. The rule provides evidence towards these controls. It does not certify anything.
| Framework | Reference |
|---|---|
| None recorded | See Compliance frameworks |
Tested with: sample excerpts from TMOS (written for this page). Minimum rConfig 8.3.0 (evaluate_block). Editions: Pro, Vector, Enterprise.
No DEFAULT or ALL cipher set
DEFAULT and ALL let in old, weak ciphers. Each client-SSL profile must name its ciphers on purpose. This rule fails if any profile uses ciphers DEFAULT or ciphers ALL.
// F5: No client-SSL profile falls back to a permissive DEFAULT/ALL cipher set#[evaluate_block]scope: ^ltm profile client-sslnot: any: - ciphers DEFAULT - ciphers ALLltm profile client-ssl /Common/clientssl_app { ciphers ECDHE+AES-GCM defaults-from /Common/clientssl options { dont-insert-empty-fragments no-sslv3 no-tlsv1 no-tlsv1.1 }}Why: The cipher list is chosen on purpose.
ltm profile client-ssl /Common/clientssl_app { ciphers DEFAULT defaults-from /Common/clientssl options { dont-insert-empty-fragments no-sslv3 no-tlsv1 no-tlsv1.1 }}Why: ciphers DEFAULT lets in weak ciphers. The result names this profile.
Expected result in rConfig, with this rule as the only rule in a definition:
| Config | Rule result | Overall result |
|---|---|---|
| Passing config | pass | PASS |
| Failing config | fail | FAIL |
Framework mapping. The rule provides evidence towards these controls. It does not certify anything.
| Framework | Reference |
|---|---|
| None recorded | See Compliance frameworks |
Tested with: sample excerpts from TMOS (written for this page). Minimum rConfig 8.3.0 (evaluate_block). Editions: Pro, Vector, Enterprise.
Every pool has a monitor
Without a health monitor, the BIG-IP keeps sending traffic to a server that is down. This rule checks every ltm pool for a monitor line.
// F5: Every pool has at least one health monitor assigned#[evaluate_block]scope: ^ltm poolall: - monitorltm pool /Common/pool_app { members { /Common/192.0.2.21:443 { address 192.0.2.21 } } monitor /Common/https}Why: The pool has an https monitor.
ltm pool /Common/pool_app { members { /Common/192.0.2.21:443 { address 192.0.2.21 } } monitor /Common/https}ltm pool /Common/pool_legacy { members { /Common/192.0.2.22:80 { address 192.0.2.22 } }}Why: pool_legacy has no monitor. The result names ltm pool /Common/pool_legacy only.
Expected result in rConfig, with this rule as the only rule in a definition:
| Config | Rule result | Overall result |
|---|---|---|
| Passing config | pass | PASS |
| Failing config | fail | FAIL |
Framework mapping. The rule provides evidence towards these controls. It does not certify anything.
| Framework | Reference |
|---|---|
| None recorded | See Compliance frameworks |
Tested with: sample excerpts from TMOS (written for this page). Minimum rConfig 8.3.0 (evaluate_block). Editions: Pro, Vector, Enterprise.
HTTPS virtual servers use client-SSL
A virtual server on port 443 should end the TLS session on the BIG-IP, using a client-SSL profile. This rule checks every ltm virtual. Ones that do not listen on :443 are skipped.
// F5: Every HTTPS (:443) virtual server terminates TLS with a client-SSL profile#[evaluate_block]scope: ^ltm virtualany: - not: "destination /Common/*:443" - clientsslltm virtual /Common/vs_secure_a { destination /Common/192.0.2.10:443 profiles { /Common/ASM_WAF_policy_prod { } /Common/clientssl { } /Common/siem_log_collector { } /Common/netlog_tcp { } /Common/telemetry_asm_security_log_profile { } } source 0.0.0.0/0}ltm virtual /Common/vs_internal_b { destination /Common/192.0.2.9:8080 profiles { /Common/tcp { } } source 192.0.2.0/24}Why: vs_secure_a has a client-SSL profile. vs_internal_b is on port 8080, so it is skipped.
ltm virtual /Common/vs_secure_a { destination /Common/192.0.2.10:443 profiles { /Common/ASM_WAF_policy_prod { } /Common/siem_log_collector { } /Common/netlog_tcp { } /Common/telemetry_asm_security_log_profile { } } source 0.0.0.0/0}Why: It listens on port 443 but has no client-SSL profile. The result names ltm virtual /Common/vs_secure_a.
Expected result in rConfig, with this rule as the only rule in a definition:
| Config | Rule result | Overall result |
|---|---|---|
| Passing config | pass | PASS |
| Failing config | fail | FAIL |
Framework mapping. The rule provides evidence towards these controls. It does not certify anything.
| Framework | Reference |
|---|---|
| None recorded | See Compliance frameworks |
Tested with: sample excerpts from TMOS (lab sample). Minimum rConfig 8.3.0 (evaluate_block). Editions: Pro, Vector, Enterprise.
HTTPS virtual servers keep SNAT
Source address translation sends return traffic back through the BIG-IP. Turning it off on an HTTPS server with type none can break traffic or let it go around the BIG-IP. Servers that are not on :443 are skipped.
// F5: HTTPS virtual servers do not disable source address translation#[evaluate_block]scope: ^ltm virtualany: - not: "destination /Common/*:443" - not: type noneltm virtual /Common/vs_secure_a { destination /Common/192.0.2.10:443 profiles { /Common/ASM_WAF_policy_prod { } /Common/siem_log_collector { } /Common/netlog_tcp { } /Common/telemetry_asm_security_log_profile { } } source 0.0.0.0/0}Why: There is no type none line.
ltm virtual /Common/vs_secure_a { destination /Common/192.0.2.10:443 profiles { /Common/ASM_WAF_policy_prod { } /Common/siem_log_collector { } /Common/netlog_tcp { } /Common/telemetry_asm_security_log_profile { } } source 0.0.0.0/0 source-address-translation { type none }}Why: SNAT is turned off on a port 443 server. The result names ltm virtual /Common/vs_secure_a.
Expected result in rConfig, with this rule as the only rule in a definition:
| Config | Rule result | Overall result |
|---|---|---|
| Passing config | pass | PASS |
| Failing config | fail | FAIL |
Framework mapping. The rule provides evidence towards these controls. It does not certify anything.
| Framework | Reference |
|---|---|
| None recorded | See Compliance frameworks |
Tested with: sample excerpts from TMOS (lab sample). Minimum rConfig 8.3.0 (evaluate_block). Editions: Pro, Vector, Enterprise.
Related reference
- F5 BIG-IP policy templates: every rule in
bigip-ssl-virtual-hardening.policy, its references and known limitations. - Policy Definitions: the definition file format and every method.
- Policy Assignments: run a definition against your devices.
- Policy Compliance Results: read the pass and fail results.