Skip to content

Conversation

dplumlee
Copy link
Contributor

Summary

Related to: elastic/kibana#215026

Updates MITRE related documentation to currently used version 16.1

@dplumlee dplumlee self-assigned this Apr 28, 2025
Copy link
Contributor

@nastasha-solomon nastasha-solomon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good - thanks for making these changes! Also recommend merging this closer to the GA date for 9.0.1.

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 <[email protected]>
Co-authored-by: Elastic Machine <[email protected]>
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 <[email protected]>
Co-authored-by: Elastic Machine <[email protected]>
(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 <[email protected]>
Co-authored-by: Elastic Machine <[email protected]>
(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 <[email protected]>
Co-authored-by: Elastic Machine <[email protected]>
(cherry picked from commit 203cfc6)
@dplumlee dplumlee enabled auto-merge (squash) May 6, 2025 15:16
@dplumlee dplumlee merged commit 9cc3a7a into main May 6, 2025
3 of 5 checks passed
@dplumlee dplumlee deleted the mitre-16.1-update branch May 6, 2025 15:18
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 <[email protected]>
Co-authored-by: Elastic Machine <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants