[zscaler_zia] Add ZScaler ZIA package.#2459
Conversation
d827d56 to
4acb04e
Compare
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
efd6
left a comment
There was a problem hiding this comment.
Query: update ECS version to 8.0.0 here?
|
|
||
| ZScaler response format: | ||
| ```json | ||
| \{ "sourcetype" : "zscalernss-dns", "event" :\{"datetime":"%s{time}","user":"%s{elogin}","department":"%s{edepartment}","location":"%s{elocation}","reqaction":"%s{reqaction}","resaction":"%s{resaction}","reqrulelabel":"%s{reqrulelabel}","resrulelabel":"%s{resrulelabel}","dns_reqtype":"%s{reqtype}","dns_req":"%s{req}","dns_resp":"%s{res}","srv_dport":"%d{sport}","durationms":"%d{durationms}","clt_sip":"%s{cip}","srv_dip":"%s{sip}","category":"%s{domcat}","deviceowner":"%s{deviceowner}","devicehostname":"%s{devicehostname}"\}\} |
There was a problem hiding this comment.
Query why the outer braces are escaped here and below.
There was a problem hiding this comment.
Basically, it is the default syntax that the user has to put in the response format configuration section in the ZScaler.
There was a problem hiding this comment.
OK so they are not really JSON, but rather opaque strings that just happen to resolve to JSON when fed to the configuration. I'd suggest that the json syntax marker be removed and some additional text be added explaining how the string should be used.
Note that these look different to the ZPA response format strings that lack the \-escaped braces (see here). Is this expected; are they actually different or is it just an accident of documentation editing?
There was a problem hiding this comment.
Firstly, We have removed the JSON marker from the section as it is not a valid JSON. Additionally, The SOP for the end-user is mentioned clearly in the README.md file.
Secondly, to answer your second comment, yes, the response formats for both ZIA and ZPA are different. For both ZIA and ZPA it is required that the exact string, which we have given in the user guide is to be put in the Response Format section.
There was a problem hiding this comment.
Thank you for clarifying. I think that the user instructions for use of the response format strings could be expanded a little. I doesn't need a lot, just where they should be pasted.
There was a problem hiding this comment.
Sure, I will update the steps to be simpler, and I will also add a step where it describes where to put the given response format.
|
/test |
- Corrected the case in vendor name
|
/test |
1 similar comment
|
/test |
packages/zscaler_zia/data_stream/alerts/_dev/test/pipeline/test-alerts.log-expected.json
Outdated
Show resolved
Hide resolved
packages/zscaler_zia/data_stream/alerts/_dev/test/pipeline/test-common-config.yml
Outdated
Show resolved
Hide resolved
packages/zscaler_zia/data_stream/alerts/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
packages/zscaler_zia/data_stream/firewall/_dev/test/pipeline/test-firewall.log-expected.json
Outdated
Show resolved
Hide resolved
packages/zscaler_zia/data_stream/web/_dev/test/pipeline/test-web.log-expected.json
Outdated
Show resolved
Hide resolved
packages/zscaler_zia/data_stream/web/_dev/test/pipeline/test-web.log-expected.json
Outdated
Show resolved
Hide resolved
packages/zscaler_zia/data_stream/alerts/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
packages/zscaler_zia/data_stream/dns/_dev/test/pipeline/test-common-config.yml
Outdated
Show resolved
Hide resolved
|
- Removed dynamic_fields section from pipeline tests - Updated ecs version to 8.0.0 - Converted values of network.protocol to lowercase. - Updated mappings - Added newline in logfiles - Re-generated pipeline test expacted files.
cf91193 to
edc02f8
Compare
|
/test |
|
/test |
|
/test |
There are now Zscaler ZIA and Zscaler ZPA integrations that are specific Zscaler products. This package is being marked as deprecated. The new integrations are not generated parsers based on rsa2elk. Relates #2459
What does this PR do?
Checklist
changelog.ymlfile.manifest.ymlfile to point to the latest Elastic stack release (e.g.^7.16.2).How to test this PR locally
Screenshots