[8.17] Add codeowner for prebuilt Security ML jobs (#223449) (#223540)

# Backport

This will backport the following commits from `main` to `8.17`:
- [Add codeowner for prebuilt Security ML jobs
(#223449)](https://github.com/elastic/kibana/pull/223449)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT
[{"author":{"name":"Susan","email":"23287722+susan-shu-c@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-12T12:47:32Z","message":"Add
codeowner for prebuilt Security ML jobs (#223449)\n\n## Summary\n\nAdd
the Security ML team to codeowners
of\n`x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules/security_*`\n-\n[link](https://github.com/elastic/kibana/tree/main/x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules)\n\nThis
is in order for Security ML to be notified of changes to the\n[Prebuilt
ML detections
for\nSecurity](https://www.elastic.co/docs/reference/data-analysis/machine-learning/ootb-ml-jobs-siem)\nwhich
they are responsible for. The security jobs' folders are prefixed\nwith
`security_`, such as `security_windows`.\n\n\n### Checklist\n\nCheck the
PR satisfies following conditions. \n\nReviewers should verify this PR
satisfies this list as well.\n\n- [ ] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n- [ ] [See some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Nick
Partridge
<nicholas.partridge@elastic.co>","sha":"c7d274052973c2e5e3089b6b44e6df51a773579b","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.1.0"],"title":"Add
codeowner for prebuilt Security ML
jobs","number":223449,"url":"https://github.com/elastic/kibana/pull/223449","mergeCommit":{"message":"Add
codeowner for prebuilt Security ML jobs (#223449)\n\n## Summary\n\nAdd
the Security ML team to codeowners
of\n`x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules/security_*`\n-\n[link](https://github.com/elastic/kibana/tree/main/x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules)\n\nThis
is in order for Security ML to be notified of changes to the\n[Prebuilt
ML detections
for\nSecurity](https://www.elastic.co/docs/reference/data-analysis/machine-learning/ootb-ml-jobs-siem)\nwhich
they are responsible for. The security jobs' folders are prefixed\nwith
`security_`, such as `security_windows`.\n\n\n### Checklist\n\nCheck the
PR satisfies following conditions. \n\nReviewers should verify this PR
satisfies this list as well.\n\n- [ ] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n- [ ] [See some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Nick
Partridge
<nicholas.partridge@elastic.co>","sha":"c7d274052973c2e5e3089b6b44e6df51a773579b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223449","number":223449,"mergeCommit":{"message":"Add
codeowner for prebuilt Security ML jobs (#223449)\n\n## Summary\n\nAdd
the Security ML team to codeowners
of\n`x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules/security_*`\n-\n[link](https://github.com/elastic/kibana/tree/main/x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules)\n\nThis
is in order for Security ML to be notified of changes to the\n[Prebuilt
ML detections
for\nSecurity](https://www.elastic.co/docs/reference/data-analysis/machine-learning/ootb-ml-jobs-siem)\nwhich
they are responsible for. The security jobs' folders are prefixed\nwith
`security_`, such as `security_windows`.\n\n\n### Checklist\n\nCheck the
PR satisfies following conditions. \n\nReviewers should verify this PR
satisfies this list as well.\n\n- [ ] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n- [ ] [See some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Nick
Partridge
<nicholas.partridge@elastic.co>","sha":"c7d274052973c2e5e3089b6b44e6df51a773579b"}}]}]
BACKPORT-->

Co-authored-by: Susan <23287722+susan-shu-c@users.noreply.github.com>
Co-authored-by: Nick Partridge <nicholas.partridge@elastic.co>
This commit is contained in:
Kibana Machine 2025-06-12 16:45:18 +02:00 committed by GitHub
parent 73ec8e0948
commit b2e5263e41
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

3
.github/CODEOWNERS vendored
View file

@ -1300,6 +1300,9 @@ x-pack/test_serverless/**/test_suites/observability/ai_assistant @elastic/obs-ai
/x-pack/test_serverless/**/test_suites/**/ml/ @elastic/ml-ui
/x-pack/test_serverless/**/test_suites/common/management/transforms/ @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.
/x-pack/test/accessibility/apps/group2/transform.ts @elastic/ml-ui
/x-pack/test/api_integration/apis/aiops/ @elastic/ml-ui