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

[Security Solution] Machine learning permissions failure #88341

Open
trexx opened this issue Jan 14, 2021 · 2 comments
Open

[Security Solution] Machine learning permissions failure #88341

trexx opened this issue Jan 14, 2021 · 2 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:ML Rule Security Solution ML Rule feature impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@trexx
Copy link

trexx commented Jan 14, 2021

Describe the bug:
Viewing any pages within the Security solution sub pages results in an error message when machine learning is disabled.
Error with message "Machine learning permissions failure Not Found"

Error: Not Found at Fetch._callee3$ (https://elasticsearch/35949/bundles/core/core.entry.js:6:59535) at l (https://elasticsearch/35949/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:380:1740519) at Generator._invoke (https://elasticsearch/35949/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:380:1740272) at Generator.forEach.e.<computed> [as next] (https://elasticsearch/35949/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:380:1740876) at fetch_asyncGeneratorStep (https://elasticsearch/35949/bundles/core/core.entry.js:6:52652) at _next (https://elasticsearch/35949/bundles/core/core.entry.js:6:52968)

Kibana/Elasticsearch Stack version: 7.10.0

Server OS version: Fedora CoreOS 33

Browser and Browser OS versions: 88.0.705.41

Elastic Endpoint version: N/A

Original install method (e.g. download page, yum, from source, etc.): Official docker images

Functional Area (e.g. Endpoint management, timelines, resolver, etc.): UI

Steps to reproduce:

  1. Disable ml via xpack.ml.enabled: false
  2. Restart kibana
  3. View Security solution subpages

Current behavior:
Error message is displayed

Expected behavior:
Notify user that feature requires ML enabled or no error message.

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context (logs, chat logs, magical formulas, etc.):
xpack.ml.enabled is false

@trexx trexx added Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. bug Fixes for quality problems that affect the customer experience labels Jan 14, 2021
@kevinlog kevinlog added the Team:Defend Workflows “EDR Workflows” sub-team of Security Solution label Jan 14, 2021
@kevinlog
Copy link
Contributor

@peluja1012 @spong - would this have to do with ML rules? If so, could you take a look at this?

@kevinlog kevinlog added the Team:Detections and Resp Security Detection Response Team label Jan 22, 2021
@spong
Copy link
Member

spong commented Jan 25, 2021

Yeah, this looks specific to the ML Jobs Settings UI, and so ML Rules as well. We just need to wrap our ML permissions call with a check to see if ML is even enabled. Adding to our backlog.

@spong spong added Feature:ML Rule Security Solution ML Rule feature and removed Team:Defend Workflows “EDR Workflows” sub-team of Security Solution labels Jan 25, 2021
@peluja1012 peluja1012 added Team:Detection Rule Management Security Detection Rule Management Team impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. labels Mar 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:ML Rule Security Solution ML Rule feature impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Development

No branches or pull requests

4 participants