ATTENTION: The new home of the Digital Forensics Wiki is at https://forensicswiki.xyz/. Yeah, it's a silly name, but it was cheap.
This wiki will be going offline permanently in the near future. An exact date will be announced soon. Thank you for being a part of this community.
If you wish to work on the new forensicswiki, please join the Google Group forensicswiki-reborn
SSL (TLS) forensics is the process of capturing information exchanged through SSL (TLS) connections and trying to make sense of it in some kind of forensics capacity.
TLS (Transport Layer Security) provides authentication and encryption for many network protocols, such as: POP, IMAP, SMTP, HTTP. However, it is possible to tunnel almost every TCP-based protocol through TLS using such tools as stunnel.
Generally, many TLS realizations require only server to be authenticated using signed certificate.
Data exchanged through SSL (TLS) connections can be decrypted by performing man-in-the-middle attack. Attacker can modify TLS handshake and provide new certificates (with attacker's encryption keys).
Many commercial network forensics systems can perform such an attack:
- Mera Systems Sleek Buster (supports signed forged certificates)
- E-Detective HTTPS/SSL Network Packet Forensics Device
As well as some open-source tools:
- ettercap (unsupported, last version - 2005/05/29)
- dsniff (obsolete, last stable version - 2000/12/17)
The TLS protocol also leaks some significant information:
- Current date and time on a TLS client and server (old versions of Firefox and Thunderbird leak system's uptime);
- Original data size.