Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[zscaler_zia.web] url.original parsing is incorrect when scheme is missing #3480

Closed
andrewkroh opened this issue Jun 7, 2022 · 2 comments · Fixed by #3571
Closed

[zscaler_zia.web] url.original parsing is incorrect when scheme is missing #3480

andrewkroh opened this issue Jun 7, 2022 · 2 comments · Fixed by #3571
Assignees
Labels
bug Something isn't working, use only for issues Integration:zscaler_zia Zscaler Internet Access

Comments

@andrewkroh
Copy link
Member

When url.original field (eurl) does not contain a scheme then the rest of the url.* fields are incorrect. Particularly url.domain is missing.

@andrewkroh andrewkroh added bug Something isn't working, use only for issues Team:Security-External Integrations Integration:zscaler_zia Zscaler Internet Access labels Jun 7, 2022
@elasticmachine
Copy link

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@andrewkroh
Copy link
Member Author

andrewkroh commented Jun 7, 2022

One idea would be to use the proto field and the eurl fields to create ECS url.full. Then derive the rest of the URL fields from that url.full: {proto}://{eurl} value. Then I expect the URI Parts processor would function correctly.

https://www.elastic.co/guide/en/ecs/current/ecs-url.html#field-url-full

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working, use only for issues Integration:zscaler_zia Zscaler Internet Access
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants