Source
Logs, audit trail & incident response — found from sitemap — Zscaler Private Access
Checked for Zscaler Private Access on 10 Nov 2026
- Page
- https://help.zscaler.com/zpa/about-log-streaming-service
- Checked
- 10 Nov 2026, 12:15 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:fdf77aad97c306edd8605f3a203da6c168261267fb7c19a2bf87a0aba18c33d4
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Lss purpose Report an error
“The Log Streaming Service (LSS) provides a better understanding of the information coming from the Private Access (ZPA) service by allowing you to create log receivers that receive information about App Connectors and users.”
-
Lss capabilities Report an error
“Forward your diagnostics and status logs to a SIEM. Store logs for longer than the cloud retention period. Create analytical charts and graphs using your own in-house SIEM. Create events and alerts using third-party log correlation.”
-
Retention user logs Report an error
“Zscaler retains User Activity, User Status, and App Connector log information for rolling periods of at least 14 days during the subscription term.”
-
Retention audit logs Report an error
“Zscaler retains audit log information for at least 6-month periods during the subscription term.”
-
Lss admin console limit Report an error
“For access to logs beyond the 14 days they are available in the Zscaler Admin Console, setting up the LSS is necessary.”
-
Lss architecture Report an error
“LSS is deployed using two components: a log receiver and an App Connector. LSS resides in the Zero Trust Exchange (ZTE) and initiates a log stream through a Public Service Edge for Private Access. The App Connector resides in your company's enterprise environment. It receives the log stream and then forwards it to a log receiver.”
-
Siem support Report an error
“Zscaler supports third-party SIEM integrations for the LSS. To learn more, see the Private Access and Splunk Deployment Guide and Zscaler and Splunk Deployment Guide.”
-
Nss distinction Report an error
“the Nanolog Streaming Service (NSS) resides in Internet & SaaS (ZIA) and allows streaming of traffic logs from the Zscaler Nanolog to your SIEM.”
-
Mutual TLS Report an error
“It is possible to use mutual TLS encryption between the log receiver and the App Connector, which you can enable when configuring a log receiver.”
-
TLS receiver requirements Report an error
“Has a client certificate for mutual TLS encryption that uses a public root CA.”
-
Connector prerequisite Report an error
“Your App Connectors must be deployed prior to configuring a log receiver.”
-
Retransmission window Report an error
“After the connection is restored, it can retransmit the last 15 minutes of the log data. However, the delivery of that log data is not guaranteed.”
-
Connection loss behavior Report an error
“The LSS does not transmit any log data generated during a connection loss between Private Access and the App Connectors.”
-
Siem connection loss behavior Report an error
“With the exception of audit log data, the LSS does not transmit any log data generated during a connection loss between the App Connector and the SIEM.”
-
B2b log obfuscation Report an error
“To prevent the inadvertent sharing of sensitive data, logging data is obfuscated as part of the Business-to-Business (B2B) Federation process before sharing resources between companies.”
-
B2b split log redaction Report an error
“There are two copies of the relevant log data generated: one copy goes to the guest partner, and the other goes to the host partner.”
-
B2b regional storage Report an error
“Each party's relevant log data is stored in their respective regions.”
-
Log receiver page location Report an error
“On the Log Receivers page (Data Explorer > Log Streaming > Log Receivers)”
-
Log receiver management Report an error
“Add a new log receiver. Filter the information that appears in the table.”
-
Log receiver fields Report an error
“Name: The name of the receiver. Click the name to view details for each Log Receiver. Domain Name or IP Address: The domain name or IP address for the receiver. TCP Port: The TCP port number for the receiver. TLS Encryption: Indicates that TLS encryption is enabled or disabled for the receiver. Log Type: The log type the receiver is capturing (e.g., User Activity, User Status, App Connector Status, Browser Access).”
-
Deception receivers restriction Report an error
“If a log receiver is configured using Zscaler Deception, then the copy, edit, and delete options are unavailable.”
-
Streaming policy Report an error
“After you select which log type to capture, you can configure a streaming policy for the information.”
-
Log types Report an error
“Log Type: The log type the receiver is capturing (e.g., User Activity, User Status, App Connector Status, Browser Access).”
Scores citing this record
- The DevOps Engineer Logs, audit trail & incident response
- The DevOps Engineer European sovereignty
- The IT Lead Access model & connectivity
- The IT Lead Logs, audit trail & incident response
- The IT Lead European sovereignty
- The MSP Technician Logs, audit trail & incident response
- The MSP Technician European sovereignty
- The Operations Manager Logs, audit trail & incident response
- The Operations Manager Architecture, reliability & security assurance
- The Operations Manager European sovereignty
- The Information Security Officer Logs, audit trail & incident response
- The Information Security Officer Architecture, reliability & security assurance
- The Information Security Officer European sovereignty
- The Skeptic Logs, audit trail & incident response
- The Skeptic Architecture, reliability & security assurance
- The Skeptic European sovereignty