[Security Solution] Updates kibana MITRE data to v16.1#215026
Merged
dplumlee merged 9 commits intoelastic:mainfrom Apr 28, 2025
Merged
[Security Solution] Updates kibana MITRE data to v16.1#215026dplumlee merged 9 commits intoelastic:mainfrom
v16.1#215026dplumlee merged 9 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) |
maximpn
approved these changes
Apr 3, 2025
Contributor
maximpn
left a comment
There was a problem hiding this comment.
@dplumlee Thanks for updating MIRE data to the latest version 🙏
New techniques and sub-techniques were added and Protocol Impersonation (T1001.003) has been renamed to Protocol or Service Impersonation (T1001.003). Nothing was removed making this upgrade safe.
I doubled checked rule management functionality works locally with this functionality and haven't found any issues.
Contributor
|
@elasticmachine merge upstream |
Contributor
|
Starting backport for target branches: 8.18, 8.19, 9.0 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Apr 28, 2025
) ## Summary Addresses: elastic#166152 for `8.18.1` and elastic#203370 Updates MITRE ATT&CK mappings to `v16.1`. Last update was to `v15.1` in elastic#183463. To update, I modified https://github.com/elastic/kibana/blob/df55627b2d695b8721928cb453db31e2b5cb73a4/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v16.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/security-docs#6797 - [ ] elastic/docs-content#1292 ## Test Criteria This PR also updates our cypress tests which run with real MITRE data generated by the same `extract_tactics_techniques_mitre` script. Our tests would often break when the data was updated to a new version because the UI elements being tested would cover each other leading to flakiness or outright test failure. In order to ensure a more streamline update process the tests should no longer break because of this flakiness and only when there's a more serious issue. - [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: Maxim Palenov <maxim.palenov@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit 203cfc6)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Apr 28, 2025
) ## Summary Addresses: elastic#166152 for `8.18.1` and elastic#203370 Updates MITRE ATT&CK mappings to `v16.1`. Last update was to `v15.1` in elastic#183463. To update, I modified https://github.com/elastic/kibana/blob/df55627b2d695b8721928cb453db31e2b5cb73a4/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v16.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/security-docs#6797 - [ ] elastic/docs-content#1292 ## Test Criteria This PR also updates our cypress tests which run with real MITRE data generated by the same `extract_tactics_techniques_mitre` script. Our tests would often break when the data was updated to a new version because the UI elements being tested would cover each other leading to flakiness or outright test failure. In order to ensure a more streamline update process the tests should no longer break because of this flakiness and only when there's a more serious issue. - [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: Maxim Palenov <maxim.palenov@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit 203cfc6)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Apr 28, 2025
) ## Summary Addresses: elastic#166152 for `8.18.1` and elastic#203370 Updates MITRE ATT&CK mappings to `v16.1`. Last update was to `v15.1` in elastic#183463. To update, I modified https://github.com/elastic/kibana/blob/df55627b2d695b8721928cb453db31e2b5cb73a4/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v16.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/security-docs#6797 - [ ] elastic/docs-content#1292 ## Test Criteria This PR also updates our cypress tests which run with real MITRE data generated by the same `extract_tactics_techniques_mitre` script. Our tests would often break when the data was updated to a new version because the UI elements being tested would cover each other leading to flakiness or outright test failure. In order to ensure a more streamline update process the tests should no longer break because of this flakiness and only when there's a more serious issue. - [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: Maxim Palenov <maxim.palenov@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit 203cfc6)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Apr 28, 2025
…) (#219448) # Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Updates kibana MITRE data to `v16.1` (#215026)](#215026) <!--- 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-04-28T18:51:36Z","message":"[Security Solution] Updates kibana MITRE data to `v16.1` (#215026)\n\n## Summary\n\nAddresses: #166152 for `8.18.1`\nand https://github.com/elastic/kibana/issues/203370\n\nUpdates MITRE ATT&CK mappings to `v16.1`. Last update was to `v15.1` in\nhttps://github.com//pull/183463.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/df55627b2d695b8721928cb453db31e2b5cb73a4/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v16.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## 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/security-docs/pull/6797\n - [ ] https://github.com/elastic/docs-content/pull/1292\n\n## Test Criteria\n\nThis PR also updates our cypress tests which run with real MITRE data\ngenerated by the same `extract_tactics_techniques_mitre` script. Our\ntests would often break when the data was updated to a new version\nbecause the UI elements being tested would cover each other leading to\nflakiness or outright test failure. In order to ensure a more streamline\nupdate process the tests should no longer break because of this\nflakiness and only when there's a more serious issue.\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: Maxim Palenov <maxim.palenov@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"203cfc67ea5be4afdbb969a8ead2f45acd94a702","branchLabelMapping":{"^v9.1.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.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security Solution] Updates kibana MITRE data to `v16.1`","number":215026,"url":"https://github.com/elastic/kibana/pull/215026","mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v16.1` (#215026)\n\n## Summary\n\nAddresses: #166152 for `8.18.1`\nand https://github.com/elastic/kibana/issues/203370\n\nUpdates MITRE ATT&CK mappings to `v16.1`. Last update was to `v15.1` in\nhttps://github.com//pull/183463.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/df55627b2d695b8721928cb453db31e2b5cb73a4/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v16.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## 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/security-docs/pull/6797\n - [ ] https://github.com/elastic/docs-content/pull/1292\n\n## Test Criteria\n\nThis PR also updates our cypress tests which run with real MITRE data\ngenerated by the same `extract_tactics_techniques_mitre` script. Our\ntests would often break when the data was updated to a new version\nbecause the UI elements being tested would cover each other leading to\nflakiness or outright test failure. In order to ensure a more streamline\nupdate process the tests should no longer break because of this\nflakiness and only when there's a more serious issue.\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: Maxim Palenov <maxim.palenov@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"203cfc67ea5be4afdbb969a8ead2f45acd94a702"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215026","number":215026,"mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v16.1` (#215026)\n\n## Summary\n\nAddresses: #166152 for `8.18.1`\nand https://github.com/elastic/kibana/issues/203370\n\nUpdates MITRE ATT&CK mappings to `v16.1`. Last update was to `v15.1` in\nhttps://github.com//pull/183463.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/df55627b2d695b8721928cb453db31e2b5cb73a4/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v16.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## 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/security-docs/pull/6797\n - [ ] https://github.com/elastic/docs-content/pull/1292\n\n## Test Criteria\n\nThis PR also updates our cypress tests which run with real MITRE data\ngenerated by the same `extract_tactics_techniques_mitre` script. Our\ntests would often break when the data was updated to a new version\nbecause the UI elements being tested would cover each other leading to\nflakiness or outright test failure. In order to ensure a more streamline\nupdate process the tests should no longer break because of this\nflakiness and only when there's a more serious issue.\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: Maxim Palenov <maxim.palenov@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"203cfc67ea5be4afdbb969a8ead2f45acd94a702"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Davis Plumlee <56367316+dplumlee@users.noreply.github.com> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
kibanamachine
added a commit
that referenced
this pull request
Apr 28, 2025
) (#219447) # Backport This will backport the following commits from `main` to `8.19`: - [[Security Solution] Updates kibana MITRE data to `v16.1` (#215026)](#215026) <!--- 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-04-28T18:51:36Z","message":"[Security Solution] Updates kibana MITRE data to `v16.1` (#215026)\n\n## Summary\n\nAddresses: #166152 for `8.18.1`\nand https://github.com/elastic/kibana/issues/203370\n\nUpdates MITRE ATT&CK mappings to `v16.1`. Last update was to `v15.1` in\nhttps://github.com//pull/183463.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/df55627b2d695b8721928cb453db31e2b5cb73a4/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v16.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## 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/security-docs/pull/6797\n - [ ] https://github.com/elastic/docs-content/pull/1292\n\n## Test Criteria\n\nThis PR also updates our cypress tests which run with real MITRE data\ngenerated by the same `extract_tactics_techniques_mitre` script. Our\ntests would often break when the data was updated to a new version\nbecause the UI elements being tested would cover each other leading to\nflakiness or outright test failure. In order to ensure a more streamline\nupdate process the tests should no longer break because of this\nflakiness and only when there's a more serious issue.\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: Maxim Palenov <maxim.palenov@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"203cfc67ea5be4afdbb969a8ead2f45acd94a702","branchLabelMapping":{"^v9.1.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.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security Solution] Updates kibana MITRE data to `v16.1`","number":215026,"url":"https://github.com/elastic/kibana/pull/215026","mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v16.1` (#215026)\n\n## Summary\n\nAddresses: #166152 for `8.18.1`\nand https://github.com/elastic/kibana/issues/203370\n\nUpdates MITRE ATT&CK mappings to `v16.1`. Last update was to `v15.1` in\nhttps://github.com//pull/183463.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/df55627b2d695b8721928cb453db31e2b5cb73a4/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v16.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## 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/security-docs/pull/6797\n - [ ] https://github.com/elastic/docs-content/pull/1292\n\n## Test Criteria\n\nThis PR also updates our cypress tests which run with real MITRE data\ngenerated by the same `extract_tactics_techniques_mitre` script. Our\ntests would often break when the data was updated to a new version\nbecause the UI elements being tested would cover each other leading to\nflakiness or outright test failure. In order to ensure a more streamline\nupdate process the tests should no longer break because of this\nflakiness and only when there's a more serious issue.\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: Maxim Palenov <maxim.palenov@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"203cfc67ea5be4afdbb969a8ead2f45acd94a702"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215026","number":215026,"mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v16.1` (#215026)\n\n## Summary\n\nAddresses: #166152 for `8.18.1`\nand https://github.com/elastic/kibana/issues/203370\n\nUpdates MITRE ATT&CK mappings to `v16.1`. Last update was to `v15.1` in\nhttps://github.com//pull/183463.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/df55627b2d695b8721928cb453db31e2b5cb73a4/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v16.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## 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/security-docs/pull/6797\n - [ ] https://github.com/elastic/docs-content/pull/1292\n\n## Test Criteria\n\nThis PR also updates our cypress tests which run with real MITRE data\ngenerated by the same `extract_tactics_techniques_mitre` script. Our\ntests would often break when the data was updated to a new version\nbecause the UI elements being tested would cover each other leading to\nflakiness or outright test failure. In order to ensure a more streamline\nupdate process the tests should no longer break because of this\nflakiness and only when there's a more serious issue.\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: Maxim Palenov <maxim.palenov@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"203cfc67ea5be4afdbb969a8ead2f45acd94a702"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Davis Plumlee <56367316+dplumlee@users.noreply.github.com> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
kibanamachine
added a commit
that referenced
this pull request
Apr 28, 2025
) (#219446) # Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Updates kibana MITRE data to `v16.1` (#215026)](#215026) <!--- 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-04-28T18:51:36Z","message":"[Security Solution] Updates kibana MITRE data to `v16.1` (#215026)\n\n## Summary\n\nAddresses: #166152 for `8.18.1`\nand https://github.com/elastic/kibana/issues/203370\n\nUpdates MITRE ATT&CK mappings to `v16.1`. Last update was to `v15.1` in\nhttps://github.com//pull/183463.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/df55627b2d695b8721928cb453db31e2b5cb73a4/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v16.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## 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/security-docs/pull/6797\n - [ ] https://github.com/elastic/docs-content/pull/1292\n\n## Test Criteria\n\nThis PR also updates our cypress tests which run with real MITRE data\ngenerated by the same `extract_tactics_techniques_mitre` script. Our\ntests would often break when the data was updated to a new version\nbecause the UI elements being tested would cover each other leading to\nflakiness or outright test failure. In order to ensure a more streamline\nupdate process the tests should no longer break because of this\nflakiness and only when there's a more serious issue.\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: Maxim Palenov <maxim.palenov@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"203cfc67ea5be4afdbb969a8ead2f45acd94a702","branchLabelMapping":{"^v9.1.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.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security Solution] Updates kibana MITRE data to `v16.1`","number":215026,"url":"https://github.com/elastic/kibana/pull/215026","mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v16.1` (#215026)\n\n## Summary\n\nAddresses: #166152 for `8.18.1`\nand https://github.com/elastic/kibana/issues/203370\n\nUpdates MITRE ATT&CK mappings to `v16.1`. Last update was to `v15.1` in\nhttps://github.com//pull/183463.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/df55627b2d695b8721928cb453db31e2b5cb73a4/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v16.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## 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/security-docs/pull/6797\n - [ ] https://github.com/elastic/docs-content/pull/1292\n\n## Test Criteria\n\nThis PR also updates our cypress tests which run with real MITRE data\ngenerated by the same `extract_tactics_techniques_mitre` script. Our\ntests would often break when the data was updated to a new version\nbecause the UI elements being tested would cover each other leading to\nflakiness or outright test failure. In order to ensure a more streamline\nupdate process the tests should no longer break because of this\nflakiness and only when there's a more serious issue.\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: Maxim Palenov <maxim.palenov@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"203cfc67ea5be4afdbb969a8ead2f45acd94a702"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215026","number":215026,"mergeCommit":{"message":"[Security Solution] Updates kibana MITRE data to `v16.1` (#215026)\n\n## Summary\n\nAddresses: #166152 for `8.18.1`\nand https://github.com/elastic/kibana/issues/203370\n\nUpdates MITRE ATT&CK mappings to `v16.1`. Last update was to `v15.1` in\nhttps://github.com//pull/183463.\n\nTo update, I modified \n\n\nhttps://github.com/elastic/kibana/blob/df55627b2d695b8721928cb453db31e2b5cb73a4/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22\n\nto point to the `ATT&CK-v16.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## 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/security-docs/pull/6797\n - [ ] https://github.com/elastic/docs-content/pull/1292\n\n## Test Criteria\n\nThis PR also updates our cypress tests which run with real MITRE data\ngenerated by the same `extract_tactics_techniques_mitre` script. Our\ntests would often break when the data was updated to a new version\nbecause the UI elements being tested would cover each other leading to\nflakiness or outright test failure. In order to ensure a more streamline\nupdate process the tests should no longer break because of this\nflakiness and only when there's a more serious issue.\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: Maxim Palenov <maxim.palenov@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"203cfc67ea5be4afdbb969a8ead2f45acd94a702"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Davis Plumlee <56367316+dplumlee@users.noreply.github.com> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
dplumlee
added a commit
to elastic/docs-content
that referenced
this pull request
May 6, 2025
## Summary Related to: elastic/kibana#215026 Updates MITRE related documentation to currently used version `16.1` Co-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>
akowalska622
pushed a commit
to akowalska622/kibana
that referenced
this pull request
May 29, 2025
) ## Summary Addresses: elastic#166152 for `8.18.1` and elastic#203370 Updates MITRE ATT&CK mappings to `v16.1`. Last update was to `v15.1` in elastic#183463. To update, I modified https://github.com/elastic/kibana/blob/df55627b2d695b8721928cb453db31e2b5cb73a4/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v16.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/security-docs#6797 - [ ] elastic/docs-content#1292 ## Test Criteria This PR also updates our cypress tests which run with real MITRE data generated by the same `extract_tactics_techniques_mitre` script. Our tests would often break when the data was updated to a new version because the UI elements being tested would cover each other leading to flakiness or outright test failure. In order to ensure a more streamline update process the tests should no longer break because of this flakiness and only when there's a more serious issue. - [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: Maxim Palenov <maxim.palenov@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
6 tasks
dplumlee
added a commit
that referenced
this pull request
Sep 2, 2025
## Summary Addresses: #166152 for `9.2.0` Updates MITRE ATT&CK mappings to `v17.1`. Last update was to `v16.1` in #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
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
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>
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
8.18.1and #203370Updates MITRE ATT&CK mappings to
v16.1. Last update was tov15.1in #183463.To update, I modified
kibana/x-pack/solutions/security/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js
Line 22 in df55627
to point to the
ATT&CK-v16.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
v16.1security-docs#6797v16.1docs-content#1292Test Criteria
This PR also updates our cypress tests which run with real MITRE data generated by the same
extract_tactics_techniques_mitrescript. Our tests would often break when the data was updated to a new version because the UI elements being tested would cover each other leading to flakiness or outright test failure. In order to ensure a more streamline update process the tests should no longer break because of this flakiness and only when there's a more serious issue.