-
Notifications
You must be signed in to change notification settings - Fork 444
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
[prisma_cloud] Add Dashboards for all the Data Streams and Update the Test Logs #8391
Conversation
1. Update test logs for audit and incident audit data stream. 2. Add one ecs mapping of the incident_audit.data to os.full 3. Add dashboards for all the data streams. 4. Change incident_audit.data.attack.techniques from nested array to array.
/test |
🌐 Coverage report
|
tag: append_prisma_cloud_incident_audit_data_attack_techniques | ||
value: '{{{_ingest._value}}}' | ||
allow_duplicates: false | ||
append: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we confident about this change? That the data from the API is never nested?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@efd6 We got the responses from the Palo Alto Prisma Cloud in which this data is never nested. Hence we decided to go with this.
Let me know your thoughts on this.
Package prisma_cloud - 0.4.0 containing this change is available at https://epr.elastic.co/search?package=prisma_cloud |
Type of change
What does this PR do?
1. Add Support for the dashboards of all the data streams.
2. Update test logs for the incident audit data stream.
Previously we did not have the test data so we added
strings
in the fields, now we have updated the test logs.3. Change incident_audit.data.attack.techniques from nested array to array.
In the API Document, it is mentioned in the schema that this field would be a nested array but in the live responses we are
getting incident_audit.data.attack.techniques as an array so we have implemented this change.
4. Add one ECS mapping in the Incident Audit Data Stream.
Mapped os.full with the incident_audit.data.os.
Checklist
changelog.yml
file.All changes
How to test this PR locally
Clone integrations repo.
Install the elastic package locally.
Start the elastic stack using the elastic package.
Move to integrations/packages/prisma_cloud directory.
Run the following command to run tests.
elastic-package test -v
Automated Test
test_logs.txt