Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.x] [Security Solution] - Feat Add
Severity
and risk_score
to t…
…he Siem migrations (#211202) (#212118) # Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] - Feat Add `Severity` and `risk_score` to the Siem migrations (#211202)](#211202) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2025-02-21T16:24:44Z","message":"[Security Solution] - Feat Add `Severity` and `risk_score` to the Siem migrations (#211202)\n\n## Summary\n\nHandles below Features:\n- https://github.com/elastic/security-team/issues/11837\n\n\nThis PR adds `risk_score` and `severity` based on below 3 rules\n- `Rule Severity` should be mapped to Splunk's `alert.severity`.\n- `Rule Severity` values should be mapped as mentioned in below section\nMapping Elastic Security Rule's Severity with Splunk's Severity\n\n> \n> |Splunk's Severity| Elastic Rule Severity |\n> |---|---|\n> |1- Info|Low|\n> |2-Low|Low|\n> |3-Medium|Medium|\n> |4-High|High|\n> |5-Critical|Critical|\n\n- Elastic Security Rule's `Risk Score` derived from the `Severity` of\nthe Rulet based on below mapping(\n[Source](https://www.elastic.co/guide/en/security/current/rules-ui-create.html#rule-ui-basic-params)\n)\n\n\n\n\n\n## Desk Testing\n\n\n[splunk_rules_test_severity.json](https://github.com/user-attachments/files/18825855/splunk_rules_test_severity.json)\n\n\n1. Use the above attached test file which has the `alert.severity`\nexported from Splunk.\n2. Check the Severity of the translated rule should match the mapping\ngiven above. Expect results like below :\n\n<img width=\"1474\" alt=\"Screenshot 2025-02-17 at 14 19 23\"\nsrc=\"https://github.com/user-attachments/assets/a8459c71-3208-480e-8049-05293a0a3d2a\"\n/>\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] 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- [x] [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\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>","sha":"74ef9fcdee2086bf2c48a35c5c15fb0997fc41dd","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] - Feat Add `Severity` and `risk_score` to the Siem migrations","number":211202,"url":"https://github.com/elastic/kibana/pull/211202","mergeCommit":{"message":"[Security Solution] - Feat Add `Severity` and `risk_score` to the Siem migrations (#211202)\n\n## Summary\n\nHandles below Features:\n- https://github.com/elastic/security-team/issues/11837\n\n\nThis PR adds `risk_score` and `severity` based on below 3 rules\n- `Rule Severity` should be mapped to Splunk's `alert.severity`.\n- `Rule Severity` values should be mapped as mentioned in below section\nMapping Elastic Security Rule's Severity with Splunk's Severity\n\n> \n> |Splunk's Severity| Elastic Rule Severity |\n> |---|---|\n> |1- Info|Low|\n> |2-Low|Low|\n> |3-Medium|Medium|\n> |4-High|High|\n> |5-Critical|Critical|\n\n- Elastic Security Rule's `Risk Score` derived from the `Severity` of\nthe Rulet based on below mapping(\n[Source](https://www.elastic.co/guide/en/security/current/rules-ui-create.html#rule-ui-basic-params)\n)\n\n\n\n\n\n## Desk Testing\n\n\n[splunk_rules_test_severity.json](https://github.com/user-attachments/files/18825855/splunk_rules_test_severity.json)\n\n\n1. Use the above attached test file which has the `alert.severity`\nexported from Splunk.\n2. Check the Severity of the translated rule should match the mapping\ngiven above. Expect results like below :\n\n<img width=\"1474\" alt=\"Screenshot 2025-02-17 at 14 19 23\"\nsrc=\"https://github.com/user-attachments/assets/a8459c71-3208-480e-8049-05293a0a3d2a\"\n/>\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] 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- [x] [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\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>","sha":"74ef9fcdee2086bf2c48a35c5c15fb0997fc41dd"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211202","number":211202,"mergeCommit":{"message":"[Security Solution] - Feat Add `Severity` and `risk_score` to the Siem migrations (#211202)\n\n## Summary\n\nHandles below Features:\n- https://github.com/elastic/security-team/issues/11837\n\n\nThis PR adds `risk_score` and `severity` based on below 3 rules\n- `Rule Severity` should be mapped to Splunk's `alert.severity`.\n- `Rule Severity` values should be mapped as mentioned in below section\nMapping Elastic Security Rule's Severity with Splunk's Severity\n\n> \n> |Splunk's Severity| Elastic Rule Severity |\n> |---|---|\n> |1- Info|Low|\n> |2-Low|Low|\n> |3-Medium|Medium|\n> |4-High|High|\n> |5-Critical|Critical|\n\n- Elastic Security Rule's `Risk Score` derived from the `Severity` of\nthe Rulet based on below mapping(\n[Source](https://www.elastic.co/guide/en/security/current/rules-ui-create.html#rule-ui-basic-params)\n)\n\n\n\n\n\n## Desk Testing\n\n\n[splunk_rules_test_severity.json](https://github.com/user-attachments/files/18825855/splunk_rules_test_severity.json)\n\n\n1. Use the above attached test file which has the `alert.severity`\nexported from Splunk.\n2. Check the Severity of the translated rule should match the mapping\ngiven above. Expect results like below :\n\n<img width=\"1474\" alt=\"Screenshot 2025-02-17 at 14 19 23\"\nsrc=\"https://github.com/user-attachments/assets/a8459c71-3208-480e-8049-05293a0a3d2a\"\n/>\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] 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- [x] [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\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>","sha":"74ef9fcdee2086bf2c48a35c5c15fb0997fc41dd"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co>
- Loading branch information