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

Hosts Risk Step 1 - Hosts Page - Risky Hosts KPI #119734

Merged
merged 12 commits into from
Dec 6, 2021

Conversation

machadoum
Copy link
Member

@machadoum machadoum commented Nov 25, 2021

issue: #119024
figma

To enable the feature flag, please add the following line to kibana.dev.yml
xpack.securitySolution.enableExperimental: ['riskyHostsEnabled']

What is included:

  • Create Risky Hosts KPI panel
  • Show EuiCallOut message when Host risk transform isn't enabled

Module enabled state

Screenshot 2021-12-01 at 10 09 49

Module disabled state

Untitled

Feature flag disabled state

Screenshot 2021-12-02 at 11 37 51

What is not included:

  • Create host risk score calculation info. "How is host risk calculated"
  • Filter in/out by host risk score
  • Add Host risk classification column to "All Hosts" table (filter and sorting not included)

Checklist

Delete any items that are not applicable to this PR.

@machadoum machadoum force-pushed the siem-explore-issue-119024 branch 5 times, most recently from cdc2f0c to 70f3d7b Compare December 1, 2021 09:01
@machadoum machadoum changed the title Hosts Risk Step 1 - Host Page Hosts Risk Step 1 - Host Page - Risky Hosts KPI Dec 1, 2021
@machadoum machadoum changed the title Hosts Risk Step 1 - Host Page - Risky Hosts KPI Hosts Risk Step 1 - Hosts Page - Risky Hosts KPI Dec 1, 2021
@machadoum machadoum force-pushed the siem-explore-issue-119024 branch from 70f3d7b to 60f8f68 Compare December 1, 2021 09:13
risk: string;
risk_stats: {
Copy link
Member Author

Choose a reason for hiding this comment

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

@ecezalp I am updating the HostsRiskScore interface to match the new version of the transform.

Copy link
Contributor

@ecezalp ecezalp Dec 6, 2021

Choose a reason for hiding this comment

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

I am a bit unsure about the implications - what would happen if someone installed the host risk score module during 7.16 (or 8.0) and then upgraded to 8.1? Do we have a mechanism to tell them that the also need to update the host risk score package? How would they know? Would they get a broken UI (all 0s on the Host Risk Score card, or a javascript error?)

Maybe we don't care at this stage about breaking changes because the feature is experimental, but I think it's still something we should clear with product, what happens if users have an older version of the host risk score package installed. What issue would the users encounter, and how would they know how to fix it?

Copy link
Member Author

@machadoum machadoum Dec 6, 2021

Choose a reason for hiding this comment

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

@ajosh0504 @SourinPaul Could you help us with this question? ⬆️

@machadoum machadoum assigned machadoum and unassigned angorayc Dec 1, 2021
@machadoum machadoum requested a review from angorayc December 1, 2021 09:15
@machadoum machadoum marked this pull request as ready for review December 1, 2021 09:17
@machadoum machadoum requested review from a team as code owners December 1, 2021 09:17
@machadoum machadoum added v8.0.0 auto-backport Deprecated - use backport:version if exact versions are needed Team:Threat Hunting:Explore v8.1.0 Team:Threat Hunting Security Solution Threat Hunting Team and removed v8.0.0 labels Dec 1, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)

@machadoum machadoum added release_note:enhancement release_note:feature Makes this part of the condensed release notes and removed release_note:enhancement labels Dec 1, 2021
@machadoum machadoum force-pushed the siem-explore-issue-119024 branch 2 times, most recently from bb9c9a1 to 450ea37 Compare December 2, 2021 10:18
@machadoum machadoum force-pushed the siem-explore-issue-119024 branch 2 times, most recently from 9436ec1 to 5d07eda Compare December 3, 2021 10:59
@machadoum machadoum force-pushed the siem-explore-issue-119024 branch from 5d07eda to 59611a8 Compare December 6, 2021 09:19
@machadoum
Copy link
Member Author

@elasticmachine merge upstream

Copy link

@monina-n monina-n left a comment

Choose a reason for hiding this comment

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

Design approval 12/6

we might need a follow up pr to update the copy/action of the enable callout

Copy link
Contributor

@charlie-pichette charlie-pichette left a comment

Choose a reason for hiding this comment

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

👍🏼

@machadoum machadoum enabled auto-merge (squash) December 6, 2021 16:47
@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
securitySolution 2800 2807 +7

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
securitySolution 4.6MB 4.6MB +5.9KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
securitySolution 243.7KB 243.9KB +233.0B

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @machadoum

@machadoum machadoum merged commit f2ef652 into elastic:main Dec 6, 2021
@kibanamachine kibanamachine added the backport:skip This commit does not require backporting label Dec 6, 2021
@kibanamachine
Copy link
Contributor

💔 Backport failed

The backport operation could not be completed due to the following error:
There are no branches to backport to. Aborting.

The backport PRs will be merged automatically after passing CI.

To backport manually run:
node scripts/backport --pr 119734

machadoum added a commit that referenced this pull request Dec 13, 2021
* Add Host risk classification column to All hosts table

* Add cypress test to risk column on all hosts table

* Fix unit test

* Add unit test

* Add tooltip to host risk column

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
TinLe pushed a commit to TinLe/kibana that referenced this pull request Dec 22, 2021
* Fix HostsRiskScore interface to match new transform version

This reverts commit c29886c.

Revert "Host Risk Filtering POC"

This reverts commit c1540e54f6ec3d892035bb7aeecb40e5da219ac1.

* Move hosts risk API client to hosts folder structure

* Add Risky Hosts KPI to Hosts page

* Fix type issues and add unit tests

* Add cypress test

* Fix unit test

* Fix cypress tests

* Add 'EuiCallOut' message when Host risk index doesn't exist

* Fix singular hosts internationalization

* Fix conflict with main

* Update risky_hosts es_archives mappings

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
TinLe pushed a commit to TinLe/kibana that referenced this pull request Dec 22, 2021
…120487)

* Add Host risk classification column to All hosts table

* Add cypress test to risk column on all hosts table

* Fix unit test

* Add unit test

* Add tooltip to host risk column

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Deprecated - use backport:version if exact versions are needed backport:skip This commit does not require backporting release_note:feature Makes this part of the condensed release notes Team:Threat Hunting:Explore Team:Threat Hunting Security Solution Threat Hunting Team v8.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants