-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Conversation
cdc2f0c
to
70f3d7b
Compare
70f3d7b
to
60f8f68
Compare
risk: string; | ||
risk_stats: { |
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.
@ecezalp I am updating the HostsRiskScore
interface to match the new version of the transform.
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.
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?
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.
@ajosh0504 @SourinPaul Could you help us with this question? ⬆️
Pinging @elastic/security-threat-hunting (Team:Threat Hunting) |
bb9c9a1
to
450ea37
Compare
x-pack/plugins/security_solution/public/hosts/components/kpi_hosts/risky_hosts/index.tsx
Outdated
Show resolved
Hide resolved
9436ec1
to
5d07eda
Compare
This reverts commit c29886c. Revert "Host Risk Filtering POC" This reverts commit c1540e54f6ec3d892035bb7aeecb40e5da219ac1.
5d07eda
to
59611a8
Compare
@elasticmachine merge upstream |
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.
Design approval 12/6
we might need a follow up pr to update the copy/action of the enable callout
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.
👍🏼
💚 Build Succeeded
Metrics [docs]Module Count
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: cc @machadoum |
💔 Backport failedThe backport operation could not be completed due to the following error: The backport PRs will be merged automatically after passing CI. To backport manually run: |
* 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>
* 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>
…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>
issue: #119024
figma
To enable the feature flag, please add the following line to
kibana.dev.yml
xpack.securitySolution.enableExperimental: ['riskyHostsEnabled']
What is included:
Module enabled state
Module disabled state
Feature flag disabled state
What is not included:
Checklist
Delete any items that are not applicable to this PR.