Fix broken reference links in Microsoft 365 Defender hunting queries#14705
Open
d4rk-pri0r wants to merge 1 commit into
Open
Fix broken reference links in Microsoft 365 Defender hunting queries#14705d4rk-pri0r wants to merge 1 commit into
d4rk-pri0r wants to merge 1 commit into
Conversation
Seventeen hunting queries carry dead reference links: - 14 'Original Sigma Rule' links point at rules/apt/... paths in github.com/Neo23x0/sigma that no longer exist - the repo is now SigmaHQ/sigma and the rules moved (mostly under rules-emerging-threats/). Retarget each link to the rule's current path; the schtasks rule rename was confirmed by matching the rule's id GUID (92626ddd-662c-49e3-ac59-f6535f12d189). - One blog reference moved from mergene.medium.com to posts.bluraven.io (same article slug; old URL redirects to the author's homepage). - One docs.microsoft.com attack-surface-reduction link 404s; the page now lives at learn.microsoft.com/en-us/defender-endpoint/. - One self-repo link points at Detections/AuditLogs/ StsRefreshTokenModification.yaml, which moved to the Cloud Identity Threat Protection Essentials solution. Link-integrity only; no query logic changed. Touched files carry no version field.
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.
Change(s):
Hunting Queries/Microsoft 365 Defender/:Original Sigma Rulelinks point atrules/apt/...paths ingithub.com/Neo23x0/sigmathat no longer exist: the repository is nowSigmaHQ/sigmaand the rules were moved (mostly underrules-emerging-threats/) and renamed with logsource prefixes. Each link now targets the rule's current path, verified to exist on SigmaHQ/sigmamaster. Thescheduled task creationretarget was additionally confirmed by the rule's unchangedidGUID (92626ddd-662c-49e3-ac59-f6535f12d189).Execution/detect-anomalous-process-trees.yaml) — the article moved frommergene.medium.comtoposts.bluraven.io(same slug; verified live).Protection events/ExploitGuardAsrDescriptions.yaml) — thedocs.microsoft.com/.../enable-attack-surface-reductionpage 404s; now points at its current home,learn.microsoft.com/en-us/defender-endpoint/enable-attack-surface-reduction(verified live).Defense evasion/UpdateStsRefreshToken[Solorigate].yaml) —Detections/AuditLogs/StsRefreshTokenModification.yamlno longer exists; the query moved toSolutions/Cloud Identity Threat Protection Essentials/Hunting Queries/(verified onmaster).Reason for Change(s):
externaldata()data source was also left alone — replacing a query's live data feed is a functional change, not a link repair.Version Updated:
versionfield (legacy hunting queries); no query logic or schema fields changed.Testing Completed:
master); no new spelling issues introduced.Checked that the validations are passing and have addressed any issues that are present: