What type of web traffic does Zscaler consider non-RFC compliant?

Zscaler considers traffic that doesn't meet internet protocols as non-RFC compliant because RFCs (Request for Comments) are a series of documents that describe the standards and protocols for the internet. When web traffic deviates from these established protocols, it can lead to unexpected behavior, security vulnerabilities, or inefficiencies in how data is handled over the network. Non-compliant traffic may include issues like incorrect formatting, which can hinder processing by security devices or services, such as Zscaler’s cloud-based security solutions that rely on adherence to these standards to effectively monitor and secure traffic.

In contrast, the other options represent specific scenarios or characteristics of traffic rather than a violation of protocol compliance. Traffic from mobile devices may use standards compliant with the protocols but could be subject to different configurations or restrictions based on the device's capabilities. Traffic from international sources might adhere to RFC standards but could be subject to geolocation or compliance policies. All encrypted traffic also can be compliant with RFC standards, as encryption mechanisms themselves follow specific protocols that maintain compliance; it's the contents and how the encrypted data is handled that may introduce complexities, not the encryption itself. Thus, compliance with internet protocols is the critical factor for Zscaler's determination of non-compliant traffic.