> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/siem-integrations/content-security/zscaler.md).

# Zscaler

ThreatDefence integrates with **Zscaler Internet Access (ZIA)** and **Zscaler Private Access (ZPA)** platforms to ingest logs related to web traffic, application access, and content security enforcement.

Logs provide visibility into user activity, blocked traffic, policy enforcement, and threat prevention events.

***

## Integration Method

Zscaler logs are forwarded to ThreatDefence via **Syslog**.\
For configuration, please follow the [Onboarding Syslog Data Guide](/appliances/syslog-forwarder/onboarding-syslog-data.md).

***

## Prerequisites

* Administrative access to the Zscaler portal.
* TD Syslog forwarder deployed in your environment.
* Outbound connectivity from the forwarder to ThreatDefence platform.

***

## Next Steps

1. Configure Zscaler to forward logs via syslog to your ThreatDefence Syslog Forwarder VM.
2. Ensure correct port mapping (60000+ per source).
3. Submit a request to [**support@threatdefence.com**](mailto:support@threatdefence.com) with:
   * Log source IP(s)
   * Device type (ZIA or ZPA)

ThreatDefence will validate parsing and enable dashboards for Zscaler logs.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.threatdefence.com/siem-integrations/content-security/zscaler.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.