[Security Solution] Updates kibana MITRE data to v18.1
#246770
Merged
Conversation
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
dplumlee
added
release_note:enhancement
Team: SecuritySolution
This was referenced Dec 17, 2025
Contributor
|
Pinging @elastic/security-solution (Team: SecuritySolution) |
Contributor
|
Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management) |
Contributor
|
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
Contributor
|
Starting backport for target branches: 8.19, 9.1, 9.2, 9.3 |
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
History
cc @dplumlee |
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)
Contributor
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
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
3 tasks
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
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
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>
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.3.0Updates MITRE ATT&CK mappings to
v18.1. Last update was tov17.1in #231375.To update, I modified
kibana/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js
Line 22 in 8da457e
to point to the
ATT&CK-v18.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.Acceptance Criteria
v18.1docs-content#4395Test Criteria