[Security Solution] Updates kibana MITRE data to v17.1#231375
Merged
dplumlee merged 6 commits intoelastic:mainfrom Sep 2, 2025
Merged
[Security Solution] Updates kibana MITRE data to v17.1#231375dplumlee merged 6 commits intoelastic:mainfrom
v17.1#231375dplumlee merged 6 commits intoelastic:mainfrom
Conversation
Contributor
|
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
Contributor
|
Pinging @elastic/security-solution (Team: SecuritySolution) |
Contributor
|
Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management) |
xcrzx
approved these changes
Aug 21, 2025
Contributor
xcrzx
left a comment
There was a problem hiding this comment.
Tested the changes locally. New MITRE values appear both in the rule editing form and in the MITRE coverage dashboard. LGTM 👍
Contributor
|
@dplumlee What is blocking the PR from being merged? |
This was referenced Sep 2, 2025
dplumlee
added a commit
to dplumlee/kibana
that referenced
this pull request
Sep 2, 2025
) ## Summary Addresses: elastic#166152 for `9.2.0` Updates MITRE ATT&CK mappings to `v17.1`. Last update was to `v16.1` in elastic#215026. To update, I modified https://github.com/elastic/kibana/blob/1d54622d8318295d9d0509b34c1b36c811a2382e/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v17.1` tag. Then ran `yarn extract-mitre-attacks` from the root `security_solution` plugin directory, and then `node scripts/i18n_check.js --fix` from Kibana root to regen the i18n files. ### Note This PR also adds guards to the test generation script so that it prevents duplicate data being generated and causing tests breaking after running this script. Another step in hopefully making this data generation and related testing entirely automated. ## Acceptance Criteria - [x] User can map and use new MITRE techniques in Security Solution - [ ] The user-facing documentation is updated with the new version - [ ] [MITRE ATT&CK® coverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html) page - [ ] elastic/docs-content#2518 ## Test Criteria - [x] Verify that new techniques (see the changelog link above) are available for mapping on the Rule Creation page under "Advanced settings" - [x] Verify that new techniques are available on the MITRE ATT&CK coverage page --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit 1f33388) # Conflicts: # x-pack/platform/plugins/private/translations/translations/de-DE.json
This was referenced Sep 2, 2025
Contributor
Author
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
dplumlee
added a commit
to dplumlee/kibana
that referenced
this pull request
Sep 2, 2025
) ## Summary Addresses: elastic#166152 for `9.2.0` Updates MITRE ATT&CK mappings to `v17.1`. Last update was to `v16.1` in elastic#215026. To update, I modified https://github.com/elastic/kibana/blob/1d54622d8318295d9d0509b34c1b36c811a2382e/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v17.1` tag. Then ran `yarn extract-mitre-attacks` from the root `security_solution` plugin directory, and then `node scripts/i18n_check.js --fix` from Kibana root to regen the i18n files. ### Note This PR also adds guards to the test generation script so that it prevents duplicate data being generated and causing tests breaking after running this script. Another step in hopefully making this data generation and related testing entirely automated. ## Acceptance Criteria - [x] User can map and use new MITRE techniques in Security Solution - [ ] The user-facing documentation is updated with the new version - [ ] [MITRE ATT&CK® coverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html) page - [ ] elastic/docs-content#2518 ## Test Criteria - [x] Verify that new techniques (see the changelog link above) are available for mapping on the Rule Creation page under "Advanced settings" - [x] Verify that new techniques are available on the MITRE ATT&CK coverage page --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit 1f33388) # Conflicts: # x-pack/platform/plugins/private/translations/translations/de-DE.json
dplumlee
added a commit
to dplumlee/kibana
that referenced
this pull request
Sep 2, 2025
) ## Summary Addresses: elastic#166152 for `9.2.0` Updates MITRE ATT&CK mappings to `v17.1`. Last update was to `v16.1` in elastic#215026. To update, I modified https://github.com/elastic/kibana/blob/1d54622d8318295d9d0509b34c1b36c811a2382e/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v17.1` tag. Then ran `yarn extract-mitre-attacks` from the root `security_solution` plugin directory, and then `node scripts/i18n_check.js --fix` from Kibana root to regen the i18n files. ### Note This PR also adds guards to the test generation script so that it prevents duplicate data being generated and causing tests breaking after running this script. Another step in hopefully making this data generation and related testing entirely automated. ## Acceptance Criteria - [x] User can map and use new MITRE techniques in Security Solution - [ ] The user-facing documentation is updated with the new version - [ ] [MITRE ATT&CK® coverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html) page - [ ] elastic/docs-content#2518 ## Test Criteria - [x] Verify that new techniques (see the changelog link above) are available for mapping on the Rule Creation page under "Advanced settings" - [x] Verify that new techniques are available on the MITRE ATT&CK coverage page --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit 1f33388) # Conflicts: # x-pack/platform/plugins/private/translations/translations/de-DE.json
kowalczyk-krzysztof
pushed a commit
to kowalczyk-krzysztof/kibana
that referenced
this pull request
Sep 3, 2025
) ## Summary Addresses: elastic#166152 for `9.2.0` Updates MITRE ATT&CK mappings to `v17.1`. Last update was to `v16.1` in elastic#215026. To update, I modified https://github.com/elastic/kibana/blob/1d54622d8318295d9d0509b34c1b36c811a2382e/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v17.1` tag. Then ran `yarn extract-mitre-attacks` from the root `security_solution` plugin directory, and then `node scripts/i18n_check.js --fix` from Kibana root to regen the i18n files. ### Note This PR also adds guards to the test generation script so that it prevents duplicate data being generated and causing tests breaking after running this script. Another step in hopefully making this data generation and related testing entirely automated. ## Acceptance Criteria - [x] User can map and use new MITRE techniques in Security Solution - [ ] The user-facing documentation is updated with the new version - [ ] [MITRE ATT&CK® coverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html) page - [ ] elastic/docs-content#2518 ## Test Criteria - [x] Verify that new techniques (see the changelog link above) are available for mapping on the Rule Creation page under "Advanced settings" - [x] Verify that new techniques are available on the MITRE ATT&CK coverage page --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
dplumlee
added a commit
that referenced
this pull request
Sep 3, 2025
…) (#233791) # Backport This will backport the following commits from `main` to `9.1`: - [[Security Solution] Updates kibana MITRE data to `v17.1` (#231375)](#231375) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis Plumlee","email":"56367316+dplumlee@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-09-02T19:58:40Z","message":"[Security Solution] Updates kibana MITRE data to `v17.1` (#231375)\n\n## Summary\n\nAddresses: #166152 for `9.2.0`\n\nUpdates MITRE ATT&CK mappings to `v17.1`. Last update was to `v16.1` in\nhttps://github.com//pull/215026.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/1d54622d8318295d9d0509b34c1b36c811a2382e/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v17.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n### Note\n\nThis PR also adds guards to the test generation script so that it\nprevents duplicate data being generated and causing tests breaking after\nrunning this script. Another step in hopefully making this data\ngeneration and related testing entirely automated.\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/2518\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1f333883e526413a4ae9b6bb5e95d2765a6c67f7","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","backport:version","Feature:Rule MITRE ATT&CK®","v9.2.0","v9.1.4","v9.0.7","v8.18.7","v8.19.4"],"title":"[Security Solution] Updates kibana MITRE data to `v17.1`","number":231375,"url":"https://github.com/elastic/kibana/pull/231375","mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v17.1` (#231375)\n\n## Summary\n\nAddresses: #166152 for `9.2.0`\n\nUpdates MITRE ATT&CK mappings to `v17.1`. Last update was to `v16.1` in\nhttps://github.com//pull/215026.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/1d54622d8318295d9d0509b34c1b36c811a2382e/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v17.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n### Note\n\nThis PR also adds guards to the test generation script so that it\nprevents duplicate data being generated and causing tests breaking after\nrunning this script. Another step in hopefully making this data\ngeneration and related testing entirely automated.\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/2518\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1f333883e526413a4ae9b6bb5e95d2765a6c67f7"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","9.0","8.18","8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/231375","number":231375,"mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v17.1` (#231375)\n\n## Summary\n\nAddresses: #166152 for `9.2.0`\n\nUpdates MITRE ATT&CK mappings to `v17.1`. Last update was to `v16.1` in\nhttps://github.com//pull/215026.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/1d54622d8318295d9d0509b34c1b36c811a2382e/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v17.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n### Note\n\nThis PR also adds guards to the test generation script so that it\nprevents duplicate data being generated and causing tests breaking after\nrunning this script. Another step in hopefully making this data\ngeneration and related testing entirely automated.\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/2518\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1f333883e526413a4ae9b6bb5e95d2765a6c67f7"}},{"branch":"9.1","label":"v9.1.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
dplumlee
added a commit
that referenced
this pull request
Sep 3, 2025
…) (#233792) # Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Updates kibana MITRE data to `v17.1` (#231375)](#231375) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis Plumlee","email":"56367316+dplumlee@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-09-02T19:58:40Z","message":"[Security Solution] Updates kibana MITRE data to `v17.1` (#231375)\n\n## Summary\n\nAddresses: #166152 for `9.2.0`\n\nUpdates MITRE ATT&CK mappings to `v17.1`. Last update was to `v16.1` in\nhttps://github.com//pull/215026.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/1d54622d8318295d9d0509b34c1b36c811a2382e/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v17.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n### Note\n\nThis PR also adds guards to the test generation script so that it\nprevents duplicate data being generated and causing tests breaking after\nrunning this script. Another step in hopefully making this data\ngeneration and related testing entirely automated.\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/2518\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1f333883e526413a4ae9b6bb5e95d2765a6c67f7","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","backport:version","Feature:Rule MITRE ATT&CK®","v9.2.0","v9.1.4","v9.0.7","v8.18.7","v8.19.4"],"title":"[Security Solution] Updates kibana MITRE data to `v17.1`","number":231375,"url":"https://github.com/elastic/kibana/pull/231375","mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v17.1` (#231375)\n\n## Summary\n\nAddresses: #166152 for `9.2.0`\n\nUpdates MITRE ATT&CK mappings to `v17.1`. Last update was to `v16.1` in\nhttps://github.com//pull/215026.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/1d54622d8318295d9d0509b34c1b36c811a2382e/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v17.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n### Note\n\nThis PR also adds guards to the test generation script so that it\nprevents duplicate data being generated and causing tests breaking after\nrunning this script. Another step in hopefully making this data\ngeneration and related testing entirely automated.\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/2518\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1f333883e526413a4ae9b6bb5e95d2765a6c67f7"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","9.0","8.18","8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/231375","number":231375,"mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v17.1` (#231375)\n\n## Summary\n\nAddresses: #166152 for `9.2.0`\n\nUpdates MITRE ATT&CK mappings to `v17.1`. Last update was to `v16.1` in\nhttps://github.com//pull/215026.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/1d54622d8318295d9d0509b34c1b36c811a2382e/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v17.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n### Note\n\nThis PR also adds guards to the test generation script so that it\nprevents duplicate data being generated and causing tests breaking after\nrunning this script. Another step in hopefully making this data\ngeneration and related testing entirely automated.\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/2518\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1f333883e526413a4ae9b6bb5e95d2765a6c67f7"}},{"branch":"9.1","label":"v9.1.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
dplumlee
added a commit
that referenced
this pull request
Sep 3, 2025
) (#233793) # Backport This will backport the following commits from `main` to `8.19`: - [[Security Solution] Updates kibana MITRE data to `v17.1` (#231375)](#231375) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis Plumlee","email":"56367316+dplumlee@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-09-02T19:58:40Z","message":"[Security Solution] Updates kibana MITRE data to `v17.1` (#231375)\n\n## Summary\n\nAddresses: #166152 for `9.2.0`\n\nUpdates MITRE ATT&CK mappings to `v17.1`. Last update was to `v16.1` in\nhttps://github.com//pull/215026.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/1d54622d8318295d9d0509b34c1b36c811a2382e/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v17.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n### Note\n\nThis PR also adds guards to the test generation script so that it\nprevents duplicate data being generated and causing tests breaking after\nrunning this script. Another step in hopefully making this data\ngeneration and related testing entirely automated.\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/2518\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1f333883e526413a4ae9b6bb5e95d2765a6c67f7","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","backport:version","Feature:Rule MITRE ATT&CK®","v9.2.0","v9.1.4","v9.0.7","v8.18.7","v8.19.4"],"title":"[Security Solution] Updates kibana MITRE data to `v17.1`","number":231375,"url":"https://github.com/elastic/kibana/pull/231375","mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v17.1` (#231375)\n\n## Summary\n\nAddresses: #166152 for `9.2.0`\n\nUpdates MITRE ATT&CK mappings to `v17.1`. Last update was to `v16.1` in\nhttps://github.com//pull/215026.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/1d54622d8318295d9d0509b34c1b36c811a2382e/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v17.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n### Note\n\nThis PR also adds guards to the test generation script so that it\nprevents duplicate data being generated and causing tests breaking after\nrunning this script. Another step in hopefully making this data\ngeneration and related testing entirely automated.\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/2518\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1f333883e526413a4ae9b6bb5e95d2765a6c67f7"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","9.0","8.18","8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/231375","number":231375,"mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v17.1` (#231375)\n\n## Summary\n\nAddresses: #166152 for `9.2.0`\n\nUpdates MITRE ATT&CK mappings to `v17.1`. Last update was to `v16.1` in\nhttps://github.com//pull/215026.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/1d54622d8318295d9d0509b34c1b36c811a2382e/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v17.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n### Note\n\nThis PR also adds guards to the test generation script so that it\nprevents duplicate data being generated and causing tests breaking after\nrunning this script. Another step in hopefully making this data\ngeneration and related testing entirely automated.\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/2518\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1f333883e526413a4ae9b6bb5e95d2765a6c67f7"}},{"branch":"9.1","label":"v9.1.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
dplumlee
added a commit
that referenced
this pull request
Sep 3, 2025
) (#233795) # Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Updates kibana MITRE data to `v17.1` (#231375)](#231375) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis Plumlee","email":"56367316+dplumlee@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-09-02T19:58:40Z","message":"[Security Solution] Updates kibana MITRE data to `v17.1` (#231375)\n\n## Summary\n\nAddresses: #166152 for `9.2.0`\n\nUpdates MITRE ATT&CK mappings to `v17.1`. Last update was to `v16.1` in\nhttps://github.com//pull/215026.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/1d54622d8318295d9d0509b34c1b36c811a2382e/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v17.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n### Note\n\nThis PR also adds guards to the test generation script so that it\nprevents duplicate data being generated and causing tests breaking after\nrunning this script. Another step in hopefully making this data\ngeneration and related testing entirely automated.\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/2518\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1f333883e526413a4ae9b6bb5e95d2765a6c67f7","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","backport:version","Feature:Rule MITRE ATT&CK®","v9.2.0","v9.1.4","v9.0.7","v8.18.7","v8.19.4"],"title":"[Security Solution] Updates kibana MITRE data to `v17.1`","number":231375,"url":"https://github.com/elastic/kibana/pull/231375","mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v17.1` (#231375)\n\n## Summary\n\nAddresses: #166152 for `9.2.0`\n\nUpdates MITRE ATT&CK mappings to `v17.1`. Last update was to `v16.1` in\nhttps://github.com//pull/215026.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/1d54622d8318295d9d0509b34c1b36c811a2382e/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v17.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n### Note\n\nThis PR also adds guards to the test generation script so that it\nprevents duplicate data being generated and causing tests breaking after\nrunning this script. Another step in hopefully making this data\ngeneration and related testing entirely automated.\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/2518\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1f333883e526413a4ae9b6bb5e95d2765a6c67f7"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","9.0","8.18","8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/231375","number":231375,"mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v17.1` (#231375)\n\n## Summary\n\nAddresses: #166152 for `9.2.0`\n\nUpdates MITRE ATT&CK mappings to `v17.1`. Last update was to `v16.1` in\nhttps://github.com//pull/215026.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/1d54622d8318295d9d0509b34c1b36c811a2382e/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v17.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n### Note\n\nThis PR also adds guards to the test generation script so that it\nprevents duplicate data being generated and causing tests breaking after\nrunning this script. Another step in hopefully making this data\ngeneration and related testing entirely automated.\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/2518\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1f333883e526413a4ae9b6bb5e95d2765a6c67f7"}},{"branch":"9.1","label":"v9.1.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
ymao1
pushed a commit
to ymao1/kibana
that referenced
this pull request
Sep 4, 2025
) ## Summary Addresses: elastic#166152 for `9.2.0` Updates MITRE ATT&CK mappings to `v17.1`. Last update was to `v16.1` in elastic#215026. To update, I modified https://github.com/elastic/kibana/blob/1d54622d8318295d9d0509b34c1b36c811a2382e/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v17.1` tag. Then ran `yarn extract-mitre-attacks` from the root `security_solution` plugin directory, and then `node scripts/i18n_check.js --fix` from Kibana root to regen the i18n files. ### Note This PR also adds guards to the test generation script so that it prevents duplicate data being generated and causing tests breaking after running this script. Another step in hopefully making this data generation and related testing entirely automated. ## Acceptance Criteria - [x] User can map and use new MITRE techniques in Security Solution - [ ] The user-facing documentation is updated with the new version - [ ] [MITRE ATT&CK® coverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html) page - [ ] elastic/docs-content#2518 ## Test Criteria - [x] Verify that new techniques (see the changelog link above) are available for mapping on the Rule Creation page under "Advanced settings" - [x] Verify that new techniques are available on the MITRE ATT&CK coverage page --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
nastasha-solomon
added a commit
to elastic/docs-content
that referenced
this pull request
Sep 10, 2025
🟢 **NOTE TO SELF:** Merge this on Tuesday, Sep 3, 20205 and then open PRs for #2791 ## Summary Updates the 9.x and Serverless docs to show that detection rules will use the MITRE ATT&CK® version v17.1 in 9.2 and next weeks' Serverless release. Because we need to show that earlier versions of 9.x (specifically 9.0.0-9.0.6 and 9.1.0-9.1.3) use an older version of MITRE ATT&CK® (v16.1), I created a table to show how the versions are mapped. ## Related - Doc issue: elastic/kibana#166152 - Dev PR: elastic/kibana#231375 ## Preview https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/2518/solutions/security/detect-and-alert/mitre-attandckr-coverage --------- Co-authored-by: Nastasha Solomon <nastasha.solomon@elastic.co> Co-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>
6 tasks
dplumlee
added a commit
that referenced
this pull request
Dec 19, 2025
## Summary Addresses: #166152 for `9.3.0` Updates MITRE ATT&CK mappings to [`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/). Last update was to `v17.1` in #231375. To update, I modified https://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v18.1` tag. Then ran `yarn extract-mitre-attacks` from the root `security_solution` plugin directory, and then `node scripts/i18n_check.js --fix` from Kibana root to regen the i18n files. ## Acceptance Criteria - [x] User can map and use new MITRE techniques in Security Solution - [ ] The user-facing documentation is updated with the new version - [ ] [MITRE ATT&CK® coverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html) page - [ ] elastic/docs-content#4395 ## Test Criteria - [x] Verify that new techniques (see the changelog link above) are available for mapping on the Rule Creation page under "Advanced settings" - [x] Verify that new techniques are available on the MITRE ATT&CK coverage page
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 19, 2025
) ## Summary Addresses: elastic#166152 for `9.3.0` Updates MITRE ATT&CK mappings to [`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/). Last update was to `v17.1` in elastic#231375. To update, I modified https://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v18.1` tag. Then ran `yarn extract-mitre-attacks` from the root `security_solution` plugin directory, and then `node scripts/i18n_check.js --fix` from Kibana root to regen the i18n files. ## Acceptance Criteria - [x] User can map and use new MITRE techniques in Security Solution - [ ] The user-facing documentation is updated with the new version - [ ] [MITRE ATT&CK® coverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html) page - [ ] elastic/docs-content#4395 ## Test Criteria - [x] Verify that new techniques (see the changelog link above) are available for mapping on the Rule Creation page under "Advanced settings" - [x] Verify that new techniques are available on the MITRE ATT&CK coverage page (cherry picked from commit 6b6a30e)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 19, 2025
) ## Summary Addresses: elastic#166152 for `9.3.0` Updates MITRE ATT&CK mappings to [`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/). Last update was to `v17.1` in elastic#231375. To update, I modified https://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v18.1` tag. Then ran `yarn extract-mitre-attacks` from the root `security_solution` plugin directory, and then `node scripts/i18n_check.js --fix` from Kibana root to regen the i18n files. ## Acceptance Criteria - [x] User can map and use new MITRE techniques in Security Solution - [ ] The user-facing documentation is updated with the new version - [ ] [MITRE ATT&CK® coverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html) page - [ ] elastic/docs-content#4395 ## Test Criteria - [x] Verify that new techniques (see the changelog link above) are available for mapping on the Rule Creation page under "Advanced settings" - [x] Verify that new techniques are available on the MITRE ATT&CK coverage page (cherry picked from commit 6b6a30e)
baileycash-elastic
pushed a commit
to baileycash-elastic/kibana
that referenced
this pull request
Dec 19, 2025
) ## Summary Addresses: elastic#166152 for `9.3.0` Updates MITRE ATT&CK mappings to [`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/). Last update was to `v17.1` in elastic#231375. To update, I modified https://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v18.1` tag. Then ran `yarn extract-mitre-attacks` from the root `security_solution` plugin directory, and then `node scripts/i18n_check.js --fix` from Kibana root to regen the i18n files. ## Acceptance Criteria - [x] User can map and use new MITRE techniques in Security Solution - [ ] The user-facing documentation is updated with the new version - [ ] [MITRE ATT&CK® coverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html) page - [ ] elastic/docs-content#4395 ## Test Criteria - [x] Verify that new techniques (see the changelog link above) are available for mapping on the Rule Creation page under "Advanced settings" - [x] Verify that new techniques are available on the MITRE ATT&CK coverage page
dplumlee
added a commit
to dplumlee/kibana
that referenced
this pull request
Dec 22, 2025
) ## Summary Addresses: elastic#166152 for `9.3.0` Updates MITRE ATT&CK mappings to [`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/). Last update was to `v17.1` in elastic#231375. To update, I modified https://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v18.1` tag. Then ran `yarn extract-mitre-attacks` from the root `security_solution` plugin directory, and then `node scripts/i18n_check.js --fix` from Kibana root to regen the i18n files. ## Acceptance Criteria - [x] User can map and use new MITRE techniques in Security Solution - [ ] The user-facing documentation is updated with the new version - [ ] [MITRE ATT&CK® coverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html) page - [ ] elastic/docs-content#4395 ## Test Criteria - [x] Verify that new techniques (see the changelog link above) are available for mapping on the Rule Creation page under "Advanced settings" - [x] Verify that new techniques are available on the MITRE ATT&CK coverage page (cherry picked from commit 6b6a30e) # Conflicts: # x-pack/platform/plugins/private/translations/translations/de-DE.json
dplumlee
added a commit
to dplumlee/kibana
that referenced
this pull request
Dec 22, 2025
) ## Summary Addresses: elastic#166152 for `9.3.0` Updates MITRE ATT&CK mappings to [`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/). Last update was to `v17.1` in elastic#231375. To update, I modified https://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v18.1` tag. Then ran `yarn extract-mitre-attacks` from the root `security_solution` plugin directory, and then `node scripts/i18n_check.js --fix` from Kibana root to regen the i18n files. ## Acceptance Criteria - [x] User can map and use new MITRE techniques in Security Solution - [ ] The user-facing documentation is updated with the new version - [ ] [MITRE ATT&CK® coverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html) page - [ ] elastic/docs-content#4395 ## Test Criteria - [x] Verify that new techniques (see the changelog link above) are available for mapping on the Rule Creation page under "Advanced settings" - [x] Verify that new techniques are available on the MITRE ATT&CK coverage page (cherry picked from commit 6b6a30e) # Conflicts: # x-pack/platform/plugins/private/translations/translations/de-DE.json # x-pack/platform/plugins/private/translations/translations/fr-FR.json # x-pack/platform/plugins/private/translations/translations/zh-CN.json
dplumlee
added a commit
that referenced
this pull request
Dec 22, 2025
…) (#247299) # Backport This will backport the following commits from `main` to `9.1`: - [[Security Solution] Updates kibana MITRE data to `v18.1` (#246770)](#246770) <!--- Backport version: 10.2.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis Plumlee","email":"56367316+dplumlee@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-12-19T16:42:41Z","message":"[Security Solution] Updates kibana MITRE data to `v18.1` (#246770)\n\n## Summary\n\nAddresses: #166152 for `9.3.0`\n\nUpdates MITRE ATT&CK mappings to\n[`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/).\nLast update was to `v17.1` in\nhttps://github.com//pull/231375.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v18.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/4395\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page","sha":"6b6a30ec72ae1737a7afa7bffaf4c4e6310a9249","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","backport:version","Feature:Rule MITRE ATT&CK®","v9.3.0","v9.4.0","v9.2.4","v9.1.10","v8.19.10"],"title":"[Security Solution] Updates kibana MITRE data to `v18.1`","number":246770,"url":"https://github.com/elastic/kibana/pull/246770","mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v18.1` (#246770)\n\n## Summary\n\nAddresses: #166152 for `9.3.0`\n\nUpdates MITRE ATT&CK mappings to\n[`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/).\nLast update was to `v17.1` in\nhttps://github.com//pull/231375.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v18.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/4395\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page","sha":"6b6a30ec72ae1737a7afa7bffaf4c4e6310a9249"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","8.19"],"targetPullRequestStates":[{"branch":"9.3","label":"v9.3.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/247154","number":247154,"state":"OPEN"},{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/246770","number":246770,"mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v18.1` (#246770)\n\n## Summary\n\nAddresses: #166152 for `9.3.0`\n\nUpdates MITRE ATT&CK mappings to\n[`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/).\nLast update was to `v17.1` in\nhttps://github.com//pull/231375.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v18.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/4395\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page","sha":"6b6a30ec72ae1737a7afa7bffaf4c4e6310a9249"}},{"branch":"9.2","label":"v9.2.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/247153","number":247153,"state":"OPEN"},{"branch":"9.1","label":"v9.1.10","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.10","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
dplumlee
added a commit
that referenced
this pull request
Dec 22, 2025
) (#247300) # Backport This will backport the following commits from `main` to `8.19`: - [[Security Solution] Updates kibana MITRE data to `v18.1` (#246770)](#246770) <!--- Backport version: 10.2.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis Plumlee","email":"56367316+dplumlee@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-12-19T16:42:41Z","message":"[Security Solution] Updates kibana MITRE data to `v18.1` (#246770)\n\n## Summary\n\nAddresses: #166152 for `9.3.0`\n\nUpdates MITRE ATT&CK mappings to\n[`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/).\nLast update was to `v17.1` in\nhttps://github.com//pull/231375.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v18.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/4395\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page","sha":"6b6a30ec72ae1737a7afa7bffaf4c4e6310a9249","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","backport:version","Feature:Rule MITRE ATT&CK®","v9.3.0","v9.4.0","v9.2.4","v9.1.10","v8.19.10"],"title":"[Security Solution] Updates kibana MITRE data to `v18.1`","number":246770,"url":"https://github.com/elastic/kibana/pull/246770","mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v18.1` (#246770)\n\n## Summary\n\nAddresses: #166152 for `9.3.0`\n\nUpdates MITRE ATT&CK mappings to\n[`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/).\nLast update was to `v17.1` in\nhttps://github.com//pull/231375.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v18.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/4395\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page","sha":"6b6a30ec72ae1737a7afa7bffaf4c4e6310a9249"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","8.19"],"targetPullRequestStates":[{"branch":"9.3","label":"v9.3.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/247154","number":247154,"state":"OPEN"},{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/246770","number":246770,"mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v18.1` (#246770)\n\n## Summary\n\nAddresses: #166152 for `9.3.0`\n\nUpdates MITRE ATT&CK mappings to\n[`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/).\nLast update was to `v17.1` in\nhttps://github.com//pull/231375.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v18.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/4395\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page","sha":"6b6a30ec72ae1737a7afa7bffaf4c4e6310a9249"}},{"branch":"9.2","label":"v9.2.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/247153","number":247153,"state":"OPEN"},{"branch":"9.1","label":"v9.1.10","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.10","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
kibanamachine
added a commit
that referenced
this pull request
Dec 23, 2025
…) (#247153) # Backport This will backport the following commits from `main` to `9.2`: - [[Security Solution] Updates kibana MITRE data to `v18.1` (#246770)](#246770) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis Plumlee","email":"56367316+dplumlee@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-12-19T16:42:41Z","message":"[Security Solution] Updates kibana MITRE data to `v18.1` (#246770)\n\n## Summary\n\nAddresses: #166152 for `9.3.0`\n\nUpdates MITRE ATT&CK mappings to\n[`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/).\nLast update was to `v17.1` in\nhttps://github.com//pull/231375.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v18.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/4395\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page","sha":"6b6a30ec72ae1737a7afa7bffaf4c4e6310a9249","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","backport:version","Feature:Rule MITRE ATT&CK®","v9.3.0","v9.4.0","v9.2.4","v9.1.10","v8.19.10"],"title":"[Security Solution] Updates kibana MITRE data to `v18.1`","number":246770,"url":"https://github.com/elastic/kibana/pull/246770","mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v18.1` (#246770)\n\n## Summary\n\nAddresses: #166152 for `9.3.0`\n\nUpdates MITRE ATT&CK mappings to\n[`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/).\nLast update was to `v17.1` in\nhttps://github.com//pull/231375.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v18.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/4395\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page","sha":"6b6a30ec72ae1737a7afa7bffaf4c4e6310a9249"}},"sourceBranch":"main","suggestedTargetBranches":["9.3","9.2","9.1","8.19"],"targetPullRequestStates":[{"branch":"9.3","label":"v9.3.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/246770","number":246770,"mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v18.1` (#246770)\n\n## Summary\n\nAddresses: #166152 for `9.3.0`\n\nUpdates MITRE ATT&CK mappings to\n[`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/).\nLast update was to `v17.1` in\nhttps://github.com//pull/231375.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v18.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/4395\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page","sha":"6b6a30ec72ae1737a7afa7bffaf4c4e6310a9249"}},{"branch":"9.2","label":"v9.2.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.10","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.10","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Davis Plumlee <56367316+dplumlee@users.noreply.github.com>
kibanamachine
added a commit
that referenced
this pull request
Dec 23, 2025
…) (#247154) # Backport This will backport the following commits from `main` to `9.3`: - [[Security Solution] Updates kibana MITRE data to `v18.1` (#246770)](#246770) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis Plumlee","email":"56367316+dplumlee@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-12-19T16:42:41Z","message":"[Security Solution] Updates kibana MITRE data to `v18.1` (#246770)\n\n## Summary\n\nAddresses: #166152 for `9.3.0`\n\nUpdates MITRE ATT&CK mappings to\n[`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/).\nLast update was to `v17.1` in\nhttps://github.com//pull/231375.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v18.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/4395\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page","sha":"6b6a30ec72ae1737a7afa7bffaf4c4e6310a9249","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","backport:version","Feature:Rule MITRE ATT&CK®","v9.3.0","v9.4.0","v9.2.4","v9.1.10","v8.19.10"],"title":"[Security Solution] Updates kibana MITRE data to `v18.1`","number":246770,"url":"https://github.com/elastic/kibana/pull/246770","mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v18.1` (#246770)\n\n## Summary\n\nAddresses: #166152 for `9.3.0`\n\nUpdates MITRE ATT&CK mappings to\n[`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/).\nLast update was to `v17.1` in\nhttps://github.com//pull/231375.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v18.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/4395\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page","sha":"6b6a30ec72ae1737a7afa7bffaf4c4e6310a9249"}},"sourceBranch":"main","suggestedTargetBranches":["9.3","9.2","9.1","8.19"],"targetPullRequestStates":[{"branch":"9.3","label":"v9.3.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/246770","number":246770,"mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v18.1` (#246770)\n\n## Summary\n\nAddresses: #166152 for `9.3.0`\n\nUpdates MITRE ATT&CK mappings to\n[`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/).\nLast update was to `v17.1` in\nhttps://github.com//pull/231375.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v18.1` tag.\n\nThen ran `yarn extract-mitre-attacks` from the root `security_solution`\nplugin directory, and then `node scripts/i18n_check.js --fix` from\nKibana root to regen the i18n files.\n\n\n## Acceptance Criteria\n\n- [x] User can map and use new MITRE techniques in Security Solution\n- [ ] The user-facing documentation is updated with the new version\n- [ ] [MITRE ATT&CK®\ncoverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html)\npage\n - [ ] https://github.com/elastic/docs-content/pull/4395\n\n## Test Criteria\n\n- [x] Verify that new techniques (see the changelog link above) are\navailable for mapping on the Rule Creation page under \"Advanced\nsettings\"\n- [x] Verify that new techniques are available on the MITRE ATT&CK\ncoverage page","sha":"6b6a30ec72ae1737a7afa7bffaf4c4e6310a9249"}},{"branch":"9.2","label":"v9.2.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.10","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.10","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Davis Plumlee <56367316+dplumlee@users.noreply.github.com>
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this pull request
Jan 6, 2026
) ## Summary Addresses: elastic#166152 for `9.3.0` Updates MITRE ATT&CK mappings to [`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/). Last update was to `v17.1` in elastic#231375. To update, I modified https://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v18.1` tag. Then ran `yarn extract-mitre-attacks` from the root `security_solution` plugin directory, and then `node scripts/i18n_check.js --fix` from Kibana root to regen the i18n files. ## Acceptance Criteria - [x] User can map and use new MITRE techniques in Security Solution - [ ] The user-facing documentation is updated with the new version - [ ] [MITRE ATT&CK® coverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html) page - [ ] elastic/docs-content#4395 ## Test Criteria - [x] Verify that new techniques (see the changelog link above) are available for mapping on the Rule Creation page under "Advanced settings" - [x] Verify that new techniques are available on the MITRE ATT&CK coverage page
dej611
pushed a commit
to dej611/kibana
that referenced
this pull request
Jan 8, 2026
) ## Summary Addresses: elastic#166152 for `9.3.0` Updates MITRE ATT&CK mappings to [`v18.1`](https://attack.mitre.org/resources/updates/updates-october-2025/). Last update was to `v17.1` in elastic#231375. To update, I modified https://github.com/elastic/kibana/blob/8da457eaa399310954edf4c98cfc0fb540ae48ad/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v18.1` tag. Then ran `yarn extract-mitre-attacks` from the root `security_solution` plugin directory, and then `node scripts/i18n_check.js --fix` from Kibana root to regen the i18n files. ## Acceptance Criteria - [x] User can map and use new MITRE techniques in Security Solution - [ ] The user-facing documentation is updated with the new version - [ ] [MITRE ATT&CK® coverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html) page - [ ] elastic/docs-content#4395 ## Test Criteria - [x] Verify that new techniques (see the changelog link above) are available for mapping on the Rule Creation page under "Advanced settings" - [x] Verify that new techniques are available on the MITRE ATT&CK coverage page
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Addresses: #166152 for
9.2.0Updates MITRE ATT&CK mappings to
v17.1. Last update was tov16.1in #215026.To update, I modified
kibana/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js
Line 22 in 1d54622
to point to the
ATT&CK-v17.1tag.Then ran
yarn extract-mitre-attacksfrom the rootsecurity_solutionplugin directory, and thennode scripts/i18n_check.js --fixfrom Kibana root to regen the i18n files.Note
This PR also adds guards to the test generation script so that it prevents duplicate data being generated and causing tests breaking after running this script. Another step in hopefully making this data generation and related testing entirely automated.
Acceptance Criteria
v17.1docs-content#2518Test Criteria