-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Security Solution] Update MITRE ATT&CK mappings to the next version #166152
Comments
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
Pinging @elastic/security-solution (Team: SecuritySolution) |
we have validated this ticket and found the expected checkpoint are working correctly on 8.10.3 and below are observations.
Screen-Shoot |
#171680 ticket for |
**Resolves: #171680 ## Summary Addresses: #166152 for `8.14.0` and #171680 [Flaky test runner result (internal)](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5147) Updates MITRE ATT&CK mappings to `v14.1`. Last update was to `v13.1` in #166536. To update, I modified https://github.com/elastic/kibana/blob/b0c6cc9777d220b3823ab9b1bbe08c5056f7016e/x-pack/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v14.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 - Ticket [here](elastic/security-docs#4550) - [ ] [MITRE ATT&CK® coverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html) page ## 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 ### For maintainers - [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: Kibana Machine <[email protected]>
## Summary Addresses: #166152 for `8.15.0` [Flaky test runner result (internal)](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5996) Updates MITRE ATT&CK mappings to `v15.1`. Last update was to `v14.1` in #174120. To update, I modified https://github.com/elastic/kibana/blob/44e38acd71a7a64fb0df08f01ff9abfada1fec1c/x-pack/plugins/security_solution/scripts/extract_tactics_techniques_mitre.js#L22 to point to the `ATT&CK-v15.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 (elastic/security-docs#5222) - [ ] [MITRE ATT&CK® coverage](https://www.elastic.co/guide/en/security/master/rules-coverage.html) page ## 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 ### For maintainers - [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: Kibana Machine <[email protected]>
Updating the docs 📚The MITRE ATT&CK® version that our current detection rules support is referenced in both classic/stateful and serverless docs. Whenever Elastic changes the supported version of MITRE ATT&CK, we also need to update this information in the docs:
Currently there are separate source files for the classic/stateful docs and serverless docs, so you’ll need to update this info in two different files:
The version number and URL are located within the note at the top of the page. In most cases, you can open a single PR to update both classic & serverless docs. The Security Docs team will automatically be added as a reviewer for the PR, and they can take care of any additional labeling, final approval, merging, and backporting. |
Related to: elastic/detection-rules#3100
Summary
This is a recurring ticket. We take it into work every release cycle. We don't close it, instead, we update its description.
Next version to update to:
TBD
Last version updated to:
v15.1
(changelog)History of version updates:
v15.1
#183463v14.1
#174120v13.1
#166536Acceptance Criteria
Test Criteria
The text was updated successfully, but these errors were encountered: