CyberFlood: Why doesn’t Wireshark detect encrypted scenarios as TLS?

CyberFlood: Why doesn’t Wireshark detect encrypted scenarios as TLS?

NOTE: In CyberFlood, when you enable Supplemental Settings > Security (SSL/TLS), the scenarios that use TCP will be encrypted. (This is supported for various protocols in CyberFlood besides HTTP.) If you download the PCAP file using Wireshark and analyze the traffic, there might be some confusion when the server port is not 443. Wireshark identifies all traffic as the TCP protocol, not TLS, because the Wireshark configuration uses SSL/TLS Ports: 443 (only) by default. To see the TLS traffic, you can update the Wireshark configuration by adding the server ports used by the scenarios to the SSL/TLS Ports, as follows: • Edit > Preferences > Protocols > HTTP • Add server ports to the SSL/TLS Ports field NOTES: • Configuring SSL/TLS Ports in the HTTP protocol (as described above) allows you to see the TLS traffic in any scenario type, even if the scenario uses a protocol other than HTTP (such as, FTP, SMTP, and others). • After you have analyzed the traffic, you might want to remove the newly added server ports from the SSL/TLS Ports field in Wireshark, if you want to ensure that non-TLS traffic for those ports/protocols is not incorrectly interpreted as TLS, when TLS is not in use.