Skip to content

[Wiz] Added Dashboards for all the Data Streams #8154

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

Merged
merged 5 commits into from
Oct 13, 2023
Merged

[Wiz] Added Dashboards for all the Data Streams #8154

merged 5 commits into from
Oct 13, 2023

Conversation

mohitjha-elastic
Copy link
Collaborator

Type of change

  • Enhancement

What does this PR do?

  • Add dashboards for all the data streams.
  • Set unknown to the event.outcome in the pipeline.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.

How to test this PR locally

Clone integrations repo.
Install the elastic package locally.
Start elastic stack using the elastic package.
Move to integrations/packages/wiz directory.
Run the following command to run tests.

Automated Test

test-file.txt

@mohitjha-elastic mohitjha-elastic requested a review from a team as a code owner October 10, 2023 13:24
@elasticmachine
Copy link

elasticmachine commented Oct 10, 2023

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-10-13T12:26:16.917+0000

  • Duration: 19 min 35 sec

Test stats 🧪

Test Results
Failed 0
Passed 18
Skipped 0
Total 18

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@jamiehynds
Copy link

@mohitjha-elastic for the Audit dashboard, could we replace the 'Total Audit' visualisation with 'Audit Events by User', with a pie-chart, breaking down the audit events by user.id. This is likely more useful than displaying the total number of audit events, and can identify Wiz admins/users who have performed the most actions within the Wiz console.

This [Wiz](https://www.wiz.io/) integration enables your security team to continuously prioritize critical risks based on a deep cloud analysis across misconfigurations, network exposure, secrets, vulnerabilities, malware, sensitive data and identities to build a single prioritized risk view for your cloud.

Use the Wiz integration to collect and parse data from Wiz api.
Wiz continuously prioritizes critical risks based on a deep cloud analysis across misconfigurations, network exposure, secrets, vulnerabilities, malware, and identities to build a single prioritized view of risk for your cloud. This [Wiz](https://www.wiz.io/) integration enables you to consume and analyze Wiz data within Elastic Security, including issues, vulnerability data and audit events, providing you with visibility and context for your cloud environments within Elastic Security.

## Data streams

The Wiz integration collects three types of data: Audit, Issue and Vulnerability.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we remove the audit, issue and vulnerability sentences below as this sentence already covers the fact that we support audit, issue and vulnerability.

@elasticmachine
Copy link

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

@efd6
Copy link
Contributor

efd6 commented Oct 10, 2023

/test

@elasticmachine
Copy link

elasticmachine commented Oct 10, 2023

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 100.0% (3/3) 💚
Files 100.0% (3/3) 💚 3.301
Classes 100.0% (3/3) 💚 3.301
Methods 100.0% (39/39) 💚 7.382
Lines 94.011% (1146/1219) 👍 5.622
Conditionals 100.0% (0/0) 💚

changes:
- description: Add dashboards for all the data streams.
type: enhancement
link: hhttps://github.com/elastic/integrations/pull/8154
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
link: hhttps://github.com/elastic/integrations/pull/8154
link: https://github.com/elastic/integrations/pull/8154

"customLabel": true,
"dataType": "number",
"isBucketed": false,
"label": "Count of Audit",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"label": "Count of Audit",
"label": "Count of Audit Events",

@kcreddy
Copy link
Contributor

kcreddy commented Oct 11, 2023

/test

Copy link
Contributor

@kcreddy kcreddy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. We can merge after Jamie's approval.

"id": "",
"params": {
"fontSize": 12,
"markdown": "Navigation\n\n[Wiz Vulnerability (This page)](#/dashboard/wiz-927c36f0-6358-11ee-a265-c3569aa0cebf)\n\n[Wiz Issue](#/dashboard/wiz-d8f91a20-6363-11ee-a265-c3569aa0cebf)\n\n[Wiz Audit](#/dashboard/wiz-be3fd3f0-6358-11ee-9db4-21f79f2e6273)\n\n[Integration Page](/app/integrations/detail/wiz-0.1.0/overview)\n\nOverview\n\nThis dashboard shows Vulnerability overview related to the Wiz Integration.\n\nThis dashboard is made to provide general statistics and show the detection of ingested vulnerabilities.\n\nIt provides information about vulnerability and vulnerability assets. It also displays the distribution of vulnerabilities according to detection method and status. It also contains details regarding count of vulnerabilities over time.",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we change the navigation to the latest version ?
wiz-0.1.0/overview -> wiz-0.2.0/overview

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mohitjha-elastic is Event ID the only field we can use in the Issue Details and Issues over Time? Anything that's more human readable like 'Issue Name' or something along those lines? Can we also adjust 'Issues over Timestamp' to 'Issues over Time' (sounds better). Sorry the last minute adjustment.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @jamiehynds,
We do not have any other fields like the issue name or others so we have been using the Event ID only. However, the Event ID is the Issue ID but we are using the ECS name in the dashboard, let me know if you want us to replace the name Event ID with Issue ID.

No worries, will adjust Issues over Timestamp to Issue over Time.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mohitjha-elastic ok, if the Event ID is the best we can do we can leave it there for now. Would be great to hyperlink each Event ID so users could go to the Wiz console from the dashboard in order to view more information about the Event, but not sure if that's possible?

We can go ahead and merge, but Wiz may have suggestions during the validation process and we can make adjustments if necessary

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess it won't be possible to redirect from the Event ID to the Wiz console.
Also, we have adjusted the Issues over Timestamp to Issue over Time.

@P1llus P1llus merged commit c493cf1 into elastic:main Oct 13, 2023
@elasticmachine
Copy link

Package wiz - 0.2.0 containing this change is available at https://epr.elastic.co/search?package=wiz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants