-
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
[ML] Adding v3 modules for Security_Linux and Security_Windows and Deprecating v1 + v2 #131166
Conversation
removed references to deprecated v1 modules which no longer exist
remove references to deprecated module and modify module names to match the latest v3 modules being committed.
think this is what the linter wants
…into bfilar-ml-refactor
@peteharverson @pheyos, the SecML team will coordinate w/ @spong to identify the engineering stakeholders for failing tests. We will seek to resolve these in the coming weeks. |
Pinging @elastic/ml-ui (:ml) |
Sounds good! We have this issue for tracking the rework of these tests in support of the v3 modules: #128318 Ideally we'd like to coordinate that rework as part of this PR to ensure coverage, but if they need to happen as a follow-up as to not block you folks that's fine as well too. So feel free to skip any Security Solution tests (maybe add a |
@elasticmachine merge upstream |
add the Security: Windows prefix which was missing
missing bracket
...l/server/models/data_recognizer/modules/security_windows/ml/v3_windows_anomalous_script.json
Outdated
Show resolved
Hide resolved
the prefix was in the wrong place
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.
Tested job creation works inside the ML job wizard. LGTM.
💚 Build SucceededMetrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
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.
Text strings LGTM
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.
Checked out, tested locally, and verified functionality of the new v3 modules
within the Security Solution app. Was able to install and start a job from the ML Job Settings
UI, and then created a detection rule referencing the job without issue.
Note I: I did see one warning in the Kibana console after initiating the install, which hits the /api/ml/modules/setup/security_windows_v3
API with this payload:
Payload
Kibana Console Warning
[2022-05-17T14:50:44.805-06:00][WARN ][plugins.ml] Data recognizer could not estimate model memory limit {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"[Overall] cardinality estimate required for [by_field_name] [winlog.event_data.ServiceName] but not supplied"}],"type":"illegal_argument_exception","reason":"[Overall] cardinality estimate required for [by_field_name] [winlog.event_data.ServiceName] but not supplied"},"status":400}
@peteharverson, is there something we need to update on our end with this request, or is this expected?
Note II: With regards to the skipped tests, we have this issue for tracking #128318 and @banderror will be following up with a PR to unskip these tests and move them to the new v3 modules
.
All that said, LGTM from the Security Solution side of the house! 😀 Excited for the consolidation here -- thanks @bfilar & @randomuserid!
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.
Just looking at the exceptions cypress test (code owners) - if we can track that skip that'd be great.
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.
LGTM! Looks @elastic/security-solution-platform only needed to review a skipped test.
@spong in the data set you are using for your tests, are there any docs with |
Ahh, that's indeed the case, my sample data does not include those fields either. Thanks for confirming Pete! 🙂 |
Summary
security_linux
andsecurity_windows
- for use within the Security app.Files/Job Artifacts:
2 updated manifest
.json
files - for both linux and windowsUpdated/new ML Job configurations for 26 jobs - each with associated datafeed configuration files:
security_linux: 14 jobs
security_windows: 12 jobs
Tests:
Individual job test tracking stats available here: https://docs.google.com/spreadsheets/d/1JOUIVsitaMdEdhM3WT2Eag4ELI-rI2Jec7bXildJsdQ/edit#gid=0
@randomuserid to also post more updates as needed to this issue + regarding tests, thanks