Skip to main content
Information Security

Return to Answer

added 1 character in body
Source Link
schroeder ♦
schroeder ♦
  • 132.1k
  • 55
  • 307
  • 348

You make an assumption: that the ISP can read TLS-encrypted data. They can't unless your ISP/country demands TLS inspection at the ISP level. If there is this level of inspection, there are very few personal protections.

The metadata is in the logs. You can assume that all employees with access to the logs can read them. But thethen, since the actual content of the traffic is encrypted, that's a limited impact.

You make an assumption: that the ISP can read TLS-encrypted data. They can't unless your ISP/country demands TLS inspection at the ISP level. If there is this level of inspection, there are very few personal protections.

The metadata is in the logs. You can assume that all employees with access to the logs can read them. But the, since the actual content of the traffic is encrypted, that's a limited impact.

You make an assumption: that the ISP can read TLS-encrypted data. They can't unless your ISP/country demands TLS inspection at the ISP level. If there is this level of inspection, there are very few personal protections.

The metadata is in the logs. You can assume that all employees with access to the logs can read them. But then, since the actual content of the traffic is encrypted, that's a limited impact.

Source Link
schroeder ♦
schroeder ♦
  • 132.1k
  • 55
  • 307
  • 348

You make an assumption: that the ISP can read TLS-encrypted data. They can't unless your ISP/country demands TLS inspection at the ISP level. If there is this level of inspection, there are very few personal protections.

The metadata is in the logs. You can assume that all employees with access to the logs can read them. But the, since the actual content of the traffic is encrypted, that's a limited impact.