From e4908d4923944d3639a04aea6c706ede2e419cb2 Mon Sep 17 00:00:00 2001 From: Susan <23287722+susan-shu-c@users.noreply.github.com> Date: Thu, 12 Jun 2025 08:47:32 -0400 Subject: [PATCH] Add codeowner for prebuilt Security ML jobs (#223449) ## Summary Add the Security ML team to codeowners of `x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules/security_*` - [link](https://github.com/elastic/kibana/tree/main/x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules) This is in order for Security ML to be notified of changes to the [Prebuilt ML detections for Security](https://www.elastic.co/docs/reference/data-analysis/machine-learning/ootb-ml-jobs-siem) which they are responsible for. The security jobs' folders are prefixed with `security_`, such as `security_windows`. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Nick Partridge (cherry picked from commit c7d274052973c2e5e3089b6b44e6df51a773579b) --- .github/CODEOWNERS | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index f3405616c3d92..8443bfd320ebd 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -1544,6 +1544,9 @@ packages/kbn-monaco/src/esql @elastic/kibana-esql /x-pack/test_serverless/**/test_suites/common/management/transforms/ @elastic/ml-ui /x-pack/test/api_integration/services/ml.ts @elastic/ml-ui +# Security Machine Learning +x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules/security_* @elastic/security-ml + # Additional plugins and packages maintained by the ML team. ^/src/platform/test/examples/response_stream/*.ts @elastic/ml-ui /x-pack/test/accessibility/apps/group2/transform.ts @elastic/ml-ui