Repository navigation
Map 8.x Security prebuilt rule pages to their 9.x rule pages - #3369
Open
nastasha-solomon wants to merge 1 commit into
Open
nastasha-solomon wants to merge 1 commit into
nastasha-solomon wants to merge 1 commit into
Conversation
990 rule pages linked from the 8.19 prebuilt rule reference had no entry in v3-mapping.json, so their "latest documentation" banner linked to /docs. 137 existing rule entries pointed to 9.x pages that now return 404 because the rule was renamed, moved, or deprecated. - Add 949 entries for rules whose title matches a live 9.x rule page. - Add 41 entries for rules not yet published in 9.x, pointing to the prebuilt rules reference. - Fix 92 stale entries to point to the rule's current 9.x page, matched by title or by rule_id through detection-rules history. - Point 45 entries for deprecated rules to the prebuilt rules reference. Every target was checked against www.elastic.co and returns 200. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
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. |
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Relates to https://github.com/elastic/docs-content-internal/issues/750. Follow-up to #3368.
The "latest documentation" banner on most 8.x Elastic Security prebuilt rule pages links to
/docsor to a 9.x page that returns a 404. This PR updates the/en/security/*/rule entries inv3-mapping.jsonso each rule page links to its 9.x page in the Prebuilt detection rules reference.Changes
After this change, every page linked from the 8.19 prebuilt rule reference has an entry. No security rule entry points to a page that doesn't exist.
How the entries were generated
detection-rulesmainbecause they currently differ (see the note below).rule_idthroughdetection-ruleshistory to the rule's current file, which is live.Verification
/en/security/*/block stays sorted.UrlToV3on sample pages gives the expected link. Combined with the fallback in Point 8.x prebuilt rule pages to the 9.x prebuilt rules reference #3368, the issue's own example,prebuilt-rule-8-19-14-potential-sap-netweaver-exploitation.html, links to/docs/reference/security/prebuilt-rules/rules/cross-platform/execution_sap_netweaver_webshell_exec.Note: these entries will drift
The live 9.x prebuilt rules reference is built from
detection-rulescommit230925f(2026-10-08). That's why rules added since then aren't live. Some rules have also moved since that commit. For example, A scheduled task was created became a building block rule on 2026-10-20. When the 9.x reference catches up, a few of these entries will need updating again, and the 41 hub entries can then point to their rule pages.🤖 Generated with Claude Code