SAF-T1004: reconcile SAF tactic, strengthen example, add diagram, verify refs#216
Open
fkautz wants to merge 1 commit into
Open
SAF-T1004: reconcile SAF tactic, strengthen example, add diagram, verify refs#216fkautz wants to merge 1 commit into
fkautz wants to merge 1 commit into
Conversation
…ify refs Address the SAF-T1004 review (scored 85.8, merge-with-minor-revisions): - Tactic/taxonomy: the Overview declared ATT&CK tactics (Credential Access + Collection) while the framework index files SAF-T1004 under Initial Access. Set the Overview SAF tactic back to Initial Access (ATK-TA0001) to match the index, and moved the Credential Access / Collection framing into the MITRE ATT&CK Mapping section where T1557's tactics belong. - Example Scenario: expanded from a single registry record to the actual name collision (legitimate vs. attacker record) with the resolution step, mapped to Attack-Flow stages 2-4 and to the detection selections. - Added a discovery-hijack flow diagram (DNS + ARP/DHCP + registry) and gave attack-flow stage 6 a stated pivot mechanism. - Verified the odr.exe Microsoft Learn reference (real: "Windows on-device agent registry" CLI with odr mcp add/list/remove), plus the Server Cards roadmap and JRC DNSSEC citations, by content. - Fixed the non-resolving detection-rule references URL (SAF-MCP -> secure-agentic-framework) in both the shipped file and the synced README copy. - Softened "dangerous"; normalized Version-History author casing. Detection rule unchanged (still 12/12, all selections exercised). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Frederick F. Kautz IV <fkautz@alumni.cmu.edu>
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.
Summary
Addresses the SAF-T1004 (Server Impersonation / Name-Collision) review (scored 85.8, merge-with-minor-revisions). Detection rule unchanged (still 12/12).
odr.exeMicrosoft Learn reference is real ("Windows on-device agent registry" CLI withodr mcp add/list/remove), plus the Server Cards roadmap, JRC DNSSEC report, and Internet Society DNSSEC maps (2021 snapshot) by content.referencesURL (SAF-MCP->secure-agentic-framework); gave attack-flow stage 6 a stated pivot mechanism; softened "dangerous"; normalized author-name casing.Test
🤖 Generated with Claude Code