zscaler_zia.firewall: Fix source/destination ip mapping - #11613
Conversation
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
🚀 Benchmarks reportTo see the full report comment with |
|
�� Build Succeeded
cc @kcreddy |
| field: source.nat.ip | ||
| tag: set_source_nat_ip_from_zscaler_zia_firewall_tunnel_ip | ||
| copy_from: zscaler_zia.firewall.tunnel.ip | ||
| ignore_empty_value: true |
There was a problem hiding this comment.
@kcreddy , Is this also part of the required change? cause I thought we were just removing the proxy address mapping from source and destination, adding geoip proc and updating related ips.
There was a problem hiding this comment.
@ShourieG, yes it is also one of the asks from the SDH. I've updated the PR description.
|
Package zscaler_zia - 3.3.0 containing this change is available at https://epr.elastic.co/search?package=zscaler_zia |
|
thank you team, I'll follow up with the customer. |
[zscaler_zia] Fix source/destination ip mapping in `firewall` logs. Currently the ECS `source.ip` and `destination.ip` are copied not only from ZScaler client's source and destination ips, but also from the proxy server's source and destination ips. From security detection point of view, the flow is clearly defined if `source.ip` and `destination.ip` are mapped only from client's perspective instead of mixing them with proxy's source and destination ips. Also, the current array representation of `source.ip` and `destination.ip` makes it unable to be used with `geoip` processor. This PR: - Removes the mapping from proxy server's source and destination to ECS `source.ip` and `destination.ip` respectively. - Adds `source.nat.ip` from zscaler's `tsip` field. - Adds `geoip` processor to `source.ip` and `destination.ip`. - Updates `related.ip` to reflect from custom fields of proxy's source and destination ips.
[zscaler_zia] Fix source/destination ip mapping in `firewall` logs. Currently the ECS `source.ip` and `destination.ip` are copied not only from ZScaler client's source and destination ips, but also from the proxy server's source and destination ips. From security detection point of view, the flow is clearly defined if `source.ip` and `destination.ip` are mapped only from client's perspective instead of mixing them with proxy's source and destination ips. Also, the current array representation of `source.ip` and `destination.ip` makes it unable to be used with `geoip` processor. This PR: - Removes the mapping from proxy server's source and destination to ECS `source.ip` and `destination.ip` respectively. - Adds `source.nat.ip` from zscaler's `tsip` field. - Adds `geoip` processor to `source.ip` and `destination.ip`. - Updates `related.ip` to reflect from custom fields of proxy's source and destination ips.




Proposed commit message
Fix source/destination ip mapping in
firewalllogs.Currently the ECS
source.ipanddestination.ipare copied not only fromZScaler client's source and destination ips, but also from the proxy server's
source and destination ips. From security detection point of view, the flow is clearly defined
if
source.ipanddestination.ipare mapped only from client's perspective instead of mixingthem with proxy's source and destination ips. Also, the current array representation of
source.ipanddestination.ipmakes it unable to be used withgeoipprocessor.This PR:
source.ipanddestination.iprespectively.source.nat.ipfrom zscaler'stsipfield.geoipprocessor tosource.ipanddestination.ip.related.ipto reflect from custom fields of proxy's source and destination ips.Reference: https://help.zscaler.com/zia/nss-feed-output-format-firewall-logs
Checklist
changelog.ymlfile.How to test this PR locally
Pipeline tests
cd packages/zscaler_zia && elastic-package stack down && elastic-package build && elastic-package stack up --version=8.13.0 -d -v && eval "$(elastic-package stack shellinit)" && elastic-package test pipeline --generate -v --data-streams=firewallSystem tests
cd packages/zscaler_zia && elastic-package stack down && elastic-package build && elastic-package stack up --version=8.13.0 -d -v && eval "$(elastic-package stack shellinit)" && elastic-package test system --generate -v --data-streams=firewall