| Description |
This article describes the reason why PCI scan fails due to TLS v1.0 even though the minimum TLS version of 1.3 is configured for web admin and SSL VPN. |
| Scope |
FortiGate. |
| Solution |
In some cases, the min TLS version of 1.3 is used for web-GUI and SSL VPN, but the PCI scans still fail because TLS v1.0 is used.
X.X.X.X:3389 Negotiated with the following insecure cipher suites: TLS 1.0 ciphers: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHATLS_RSA_WITH_AES_256_CBC_SHA
Double-checking configuration in this scenario, found that there is a VIP on port 3389 for RDP to a server behind a FortiGate:
config firewall vip edit "RDP-ADMIN-In" set extip “X.X.X.X” set mappedip "X.X.X.X” set extintf "port1" set portforward enable set extport 3389 set mappedport 3389 next
Since the destination server is not FortiGate one cannot control the TLS version used. This configuration should be checked on the internal server that is doing RDP in this scenario. |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.