zscaler_zia: fix reversed source.bytes/destination.bytes in firewall - #19463
Merged
Conversation
efd6
added
Integration:zscaler_zia
Contributor
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
efd6
force-pushed
the
s7266-zscaler_zia
branch
2 times, most recently
from
June 9, 2026 21:29
3a2fdf9 to
af422c0
Compare
efd6
marked this pull request as ready for review
June 9, 2026 22:16
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
The firewall ingest pipeline mapped Zscaler's inbytes field to source.bytes and outbytes to destination.bytes. Zscaler defines inbytes as server-to-client and outbytes as client-to-server, and Zscaler's own field name prefixes encode the intended ECS mapping: cs (client-source), cd (client-destination), ss (server-source), sd (server-destination). The integration already follows this for IP fields (csip -> source.ip), but the byte fields were reversed. Swap the ECS targets so outbytes maps to source.bytes and inbytes maps to destination.bytes, consistent with the IP mapping and with Zscaler's naming convention. This is a breaking change: dashboards, alerts, or detection rules referencing source.bytes or destination.bytes from firewall logs will see swapped values. ref: https://help.zscaler.com/zia/nss-feed-output-format-firewall-logs
Contributor
|
✅ All changelog entries have the correct PR link. |
Contributor
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
History
cc @efd6 |
Contributor
|
Package zscaler_zia - 4.0.0 containing this change is available at https://epr.elastic.co/package/zscaler_zia/4.0.0/ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots