Fortinet SSL DEEP inspection verification

[fortired213413]

I have setup Deep inspection on the FortiGate and the traffic is matching the correct policy.

I have taken the pcap on the FGT while the client is accessing the server and from the pcap how we can know the device doing decrypting/encrypting the packet to ensure ssl inspection working properly or not.

I want to understand from the packet capture level only.

[AnthonyH]

Hello fortired213413,

One way would be to setup a Decrypted Traffic Mirror which can be enabled in the policy. Then take a WireShark capture (Network -> Diagnostics) on the interface you have configured for the mirror: https://community.fortinet.com/t5/FortiGate/Technical-Tip-Mirroring-SSL-inspected-traffic/ta-p/18945...

[sjoshi]

Hi,

While accessing the website you should be able to see the FGT DPI certificate and not the website server certificate

[Webspacekit]

To verify Fortinet SSL Deep Inspection, check the SSL Inspection profile in Security Profiles > SSL/SSH Inspection and ensure it's set to Deep Inspection with the correct CA certificate. Confirm that the profile is applied to relevant firewall policies in Policy & Objects > IPv4 Policy. Review logs in Log & Report > SSL Inspection for "decrypt" entries. Use diag debug commands to inspect real-time traffic and ensure no SSL-related errors. Finally, test with tools like Wireshark to verify SSL decryption is happening properly.

[pminarik]

> from the pcap how we can know

Assuming you want to find out purely based on pcaps:

In order for the FGT to DPI the traffic, it must participate in the TLS hanshake and offer its own keying material (from which encryption keys are derived), thus a DPI'd TLS session cannot be the same on both sides (client↔FGT, FGT↔server).

This means that you need packet captures of both sides. 'diag sniffer packet any "host <server-ip> and port <server-port>" 6 0' a should be sufficient.

In TLS 1.3, the keying material is transported in the key_share extension in ClientHello and ServerHello messages.

In TLS 1.2, it is transported in ServerKeyExchange and ClientKeyExchange messages.

If using TLS 1.2, the easy tell-tale sign is to export the server's certificate from the pcap. If this certificate is signed by a CA that is used by the FGT to DPI, you have an an easy confirmation.

Lastly, you could probably also do a simple byte-to-byte comparison of the TLS handshake payloads on both sides. If they're identical, DPI did not happen.