By default, how are links protected by Targeted Threat Protection URL Protect rewritten?

Links protected by Targeted Threat Protection URL Protect are rewritten as HTTPS by default. This is crucial for ensuring a secure transmission of data over the internet. The use of HTTPS indicates that the connection is encrypted, providing confidentiality and integrity of the data being exchanged between the user and the destination server. This helps protect users from potential threats, such as man-in-the-middle attacks, where an attacker might attempt to intercept or alter communications.

Moreover, using HTTPS by default aligns with industry standards for security and privacy, as many web services now predominantly support HTTPS connections. This enhances user trust and further mitigates risks associated with unprotected HTTP links.

Other protocols listed, such as HTTP or FTP, do not provide the same level of security and are not suitable for protecting sensitive information, which is why they are not the default choice in targeted threat protection scenarios. This reinforces the importance of using HTTPS to maintain a secure browsing environment in the context of email security and threat protection mechanisms.