From 597ef64720702cc2147103714c16e99d12e1aed2 Mon Sep 17 00:00:00 2001
From: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>
Date: Tue, 16 Sep 2025 16:06:44 -0400
Subject: [PATCH] First draft (#7061)

(cherry picked from commit 059a2b2a31a6946630dd1f03a2c919b80ef7f653)
---
 docs/detections/rules-coverage.asciidoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/detections/rules-coverage.asciidoc b/docs/detections/rules-coverage.asciidoc
index 735d94f475..0b55803c3a 100644
--- a/docs/detections/rules-coverage.asciidoc
+++ b/docs/detections/rules-coverage.asciidoc
@@ -14,7 +14,7 @@ To access the **MITRE ATT&CK® coverage** page, find **Detection rules (SIEM)**
 
 [NOTE]
 ====
-This page only includes the detection rules you currently have installed, and only rules that are mapped to MITRE ATT&CK®. The coverage page maps detections to the following https://attack.mitre.org/resources/updates/updates-april-2024[MITRE ATT&CK® version] used by {elastic-sec}: `v16.1`. Elastic prebuilt rules that aren't installed and custom rules that are either unmapped or mapped to a deprecated tactic or technique will not appear on the coverage map.
+This page only includes the detection rules you currently have installed, and only rules that are mapped to MITRE ATT&CK®. The coverage page maps detections to the following https://attack.mitre.org/resources/updates/updates-april-2024[MITRE ATT&CK® version] used by {elastic-sec}: `v17.1`. Elastic prebuilt rules that aren't installed and custom rules that are either unmapped or mapped to a deprecated tactic or technique will not appear on the coverage map.
 
 You can map custom rules to tactics in **Advanced settings** when creating or editing a rule.
 ====