Updates MITRE docs to currently used version v16.1
#6797
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
|
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
nastasha-solomon
approved these changes
Apr 28, 2025
|
Would recommend merging this closer to the GA date for 8.18.1. |
nastasha-solomon
added
v8.18.0
v8.18.1
Team: Detections/Response
7 tasks
dplumlee
added a commit
to elastic/kibana
that referenced
this pull request
Apr 28, 2025
## Summary Addresses: #166152 for `8.18.1` and #203370 Updates MITRE ATT&CK mappings to `v16.1`. Last update was to `v15.1` in #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>
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)
mergify bot
pushed a commit
that referenced
this pull request
May 6, 2025
Co-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com> (cherry picked from commit 2a0bcd9)
nastasha-solomon
added a commit
that referenced
this pull request
May 6, 2025
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>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Related to: elastic/kibana#215026
Updates MITRE related documentation to currently used version
16.1