11
ssl/tls decryption
Last updated
Secures network communication
Hashes - data integrity
Certificates - authentication
Prevent Malware introduction and data exfiltration
We should decrypt network traffic - most web traffic is encrypted
This helps the firewall to gain visibility into the network
Follows PKI
Uses digital certificate to verify and prove the owner of public key
Device trusts the intermediate CA, and intermediate CA trusts the Root CA
Self Signed (Firewall generates a certificate, then this certificate is imported into the browser of the client device)
CA Signed Certificate
CA creates a certificate and Public/Private Key
Import this certificate and public/private key into the firewall
Firewall generates a CSR and public/private key, exported to a CSR file
CSR file given to the CA for signing, and file is returned with the CA's signature.
This signed file is then imported into the firewall
Free, do not need to pay
Relies on CA
Browser does not initially trust the certificate
Client browser will directly trust the certificate
Device creates public/private key pair
Device encrypts information about its identity using its private key
Sends the encrypted information and public key to the CA
CA returns with a signed certificate
Can be done using thel (OSCP) or Certificate revocation list (CRL)
SSL Forward Proxy (Outbound)
Process:
SSL client initiates a SSL handshake
Firewall intercepts the handshake request and re-issues its own handshake request to the server
SSL server responds with its certificate(signed by a common CA that both SSL server and Firewall have access to -> allows firewall to use CA to validate the certificate and identity of the server)
Firewall copies server certificate and signs it with its own and public key.
SSL client uses forward trust certificate of firewall to validate firewall identity, using a CA common to both the firewall and the SSL client
If firewall cannot verify the server certificate, the firewall signs the server certificate with a forward untrust certificate to inform the SSL client that the SSL server certificate could not be verified.
In this case, SSL client will see a block page warning the website it is trying to connect to is not trusted by the firewall that is acting as an SSL Proxy.
SSL Inbound Inspection
This process is only done when the firewall has access to the certificate and private key of the SSL server.
Requires:
Both SSL Server and SSL Client to have a common CA-> for SSL Client to validate the server identity
Server private key and certificate must be imported into the firewall
Process:
SSL client initiates a SSL handshake
SSL Server responds with its certificate
SSL Client uses the common CA to validate certificate and server identity
Firewall does not proxy the connection between client and server. But does use the certificate and private key of the SSL server to decrypt and inspect data flowing between client and server
SSH Decryption
This uses both forward proxy and inbound inspection
Does more granular controls
Applied on decrypted traffic
Device > Certificate Management > SSL Decryption Exclusion
Breaks into 2 sessions
Replaces Decryption Broker
Identifies non-decrypted TLS, decrypted TLS and non-TLS packet can forward these traffic to another third party tool for analysis