Opened 8 months ago
Closed 8 months ago
#13086 closed Other (rejected)
Access while using Zscaler
| Reported by: | ICORDERO | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | Other |
| Keywords: | block, timeout, zscaler, whitelist | Cc: | ICORDERO |
| Component version: | Operating system type: | Windows | |
| Operating system version: | Microsoft Windows 10 Enterprise |
Description
We use Zscaler as proxy, traffic is reaching FileZilla using Zsclaer ranges (like ATL DC 104.129.206.0/23) and we are not getting access. We confirmed that whitelisting needs to be done in FileZilla to ensure access from Zscaler works.
Attachments (2)
Change History (3)
by , 8 months ago
| Attachment: | Zscaler IP.jpg added |
|---|
comment:1 by , 8 months ago
| Resolution: | → rejected |
|---|---|
| Status: | new → closed |
If you hide behind a "Zero trust" proxy that doesn't ensure traffic routed through it is actually genuine, don't act surprised if traffic from that proxy isn't trusted. If you are a legitimate business and do not do anything malicious, you do not need to hide behind a proxy.
Massive amounts of malicious traffic has been coming from Zscaler address ranges, the CIDR you mentioned is no exception. Zscaler has in the past not responded to emails sent to the abuse contact address listed in the ASN databases, meaning that they condone all abuse committed through their network. As result traffic from all Zscaler ASNs has now been blocked indefinitely.
IP Address details