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: v18.1 (changelog)

History of version updates:

• [Security Solution] Updates kibana MITRE data to v18.1 #246770
• [Security Solution] Updates kibana MITRE data to v17.1 #231375
• [Security Solution] Updates kibana MITRE data to v16.1 #215026
• [Security Solution] Updates MITRE ATT&CK framework to v15.1 #183463
• [Security Solution] Updates MITRE ATT&CK framework to v14.1 #174120
• [Security Solution] Updates MITRE ATT&CK framework to v13.1 #166536
• [Security Solution][Detections] Updates MITRE ATT&CK mappings to v12.1 #151931
• [Security Solution][Detections] Update the MITRE ATT&CK model to v11.3 #137122

Acceptance Criteria

• User can map and use new MITRE techniques in Security Solution
• The user-facing documentation is updated with the new version (instructions)
  • MITRE ATT&CK® coverage page (classic/stateful docs)
  • MITRE ATT&CK® coverage page (serverless docs)

Test Criteria

• Verify that new techniques (see the changelog link above) are available for mapping on the Rule Creation page under "Advanced settings"
• Verify that new techniques are available on the MITRE ATT&CK coverage page