--- name: implementing-threat-modeling-with-mitre-attack-d6ec7e5b9111 description: 'Implements threat modeling using the MITRE ATT&CK framework to map adversary TTPs against organizational assets, assess detection coverage gaps, and prioritize defensive investments. Use when SOC teams need to align detection engineering with threat landscape, conduct threat assessments for new environments, or justify security tool procurement. ' domain: cybersecurity subdomain: soc-operations tags: - soc - mitre-attack - threat-modeling - ttp - detection-coverage - attack-navigator - risk-assessment version: '1.0' author: mahipal license: Apache-2.0 nist_ai_rmf: - MEASURE-2.7 - MAP-5.1 - MANAGE-2.4 atlas_techniques: - AML.T0070 - AML.T0066 - AML.T0082 d3fend_techniques: - File Metadata Consistency Validation - Application Protocol Command Analysis - Identifier Analysis - Content Format Conversion - Message Analysis nist_csf: - DE.CM-01 - DE.AE-02 - RS.MA-01 - DE.AE-06 mitre_attack: - T1078 - T1685.002 - T1685.005 - T1566 --- # Implementing Threat Modeling with MITRE ATT&CK ## When to Use Use this skill when: - SOC teams need to assess detection coverage against relevant threat actors and their TTPs - Security leadership requires threat-informed defense prioritization - New environments (cloud migration, OT integration) need detection strategy planning - Purple team exercises require structured adversary emulation based on threat models - Annual risk assessments need ATT&CK-based threat landscape analysis **Do not use** as a one-time exercise — threat models must be continuously updated as adversary TTPs evolve and organizational attack surface changes. ## Prerequisites - MITRE ATT&CK framework knowledge (Enterprise, ICS, Mobile, or Cloud matrices) - ATT&CK Navigator tool (web or local) for layer visualization - Current detection rule inventory mapped to ATT&CK technique IDs - Threat intelligence on adversary groups targeting your sector - Organizational asset inventory with criticality classifications ## Workflow ### Step 1: Identify Relevant Threat Actors Research adversary groups targeting your sector using MITRE ATT&CK Groups: ```python import requests import json # Download ATT&CK STIX data response = requests.get( "https://raw.githubusercontent.com/mitre/cti/master/enterprise-attack/enterprise-attack.json" ) attack_data = response.json() # Extract groups and their techniques groups = {} for obj in attack_data["objects"]: if obj["type"] == "intrusion-set": group_name = obj["name"] aliases = obj.get("aliases", []) description = obj.get("description", "") groups[group_name] = { "aliases": aliases, "description": description[:200], "techniques": [] } # Map techniques to groups via relationships relationships = [obj for obj in attack_data["objects"] if obj["type"] == "relationship"] techniques = {obj["id"]: obj for obj in attack_data["objects"] if obj["type"] == "attack-pattern"} for rel in relationships: if rel["relationship_type"] == "uses": source = rel["source_ref"] target = rel["target_ref"] for group_name, group_data in groups.items(): if source == group_data.get("id") and target in techniques: tech = techniques[target] ext_refs = tech.get("external_references", []) for ref in ext_refs: if ref.get("source_name") == "mitre-attack": group_data["techniques"].append(ref["external_id"]) # Example: Financial sector threat actors financial_actors = ["FIN7", "FIN8", "Carbanak", "APT38", "Lazarus Group"] for actor in financial_actors: if actor in groups: print(f"{actor}: {len(groups[actor]['techniques'])} techniques") print(f" Top techniques: {groups[actor]['techniques'][:10]}") ``` ### Step 2: Build Threat Actor TTP Profile Create ATT&CK Navigator layers for priority threat actors: ```python import json def create_attack_layer(actor_name, techniques, color="#ff6666"): """Generate ATT&CK Navigator JSON layer for a threat actor""" layer = { "name": f"{actor_name} TTP Profile", "versions": { "attack": "15", "navigator": "5.0", "layer": "4.5" }, "domain": "enterprise-attack", "description": f"Techniques associated with {actor_name}", "techniques": [ { "techniqueID": tech_id, "tactic": "", "color": color, "comment": f"Used by {actor_name}", "enabled": True, "score": 1 } for tech_id in techniques ], "gradient": { "colors": ["#ffffff", color], "minValue": 0, "maxValue": 1 } } return layer # Create layers for top threat actors fin7_techniques = ["T1566.001", "T1059.001", "T1053.005", "T1547.001", "T1078", "T1021.001", "T1003", "T1071.001", "T1041"] layer = create_attack_layer("FIN7", fin7_techniques, "#ff6666") with open("fin7_layer.json", "w") as f: json.dump(layer, f, indent=2) ``` ### Step 3: Map Current Detection Coverage Export current detection rules mapped to ATT&CK: ```spl --- Extract ATT&CK technique mappings from Splunk ES correlation searches | rest /services/saved/searches splunk_server=local | where match(title, "^(COR|ESCU|RBA):") | eval techniques = if(isnotnull(action.correlationsearch.annotations), spath(action.correlationsearch.annotations, "mitre_attack"), "unmapped") | stats count by techniques | mvexpand techniques | stats count by techniques | rename techniques AS technique_id, count AS rule_count ``` Create detection coverage layer: ```python def create_coverage_layer(detection_rules): """Generate coverage layer from detection rule inventory""" technique_counts = {} for rule in detection_rules: for tech in rule.get("techniques", []): technique_counts[tech] = technique_counts.get(tech, 0) + 1 layer = { "name": "SOC Detection Coverage", "versions": {"attack": "15", "navigator": "5.0", "layer": "4.5"}, "domain": "enterprise-attack", "techniques": [ { "techniqueID": tech_id, "color": "#31a354" if count >= 2 else "#a1d99b" if count == 1 else "", "score": count, "comment": f"{count} detection rule(s)" } for tech_id, count in technique_counts.items() ], "gradient": { "colors": ["#ffffff", "#a1d99b", "#31a354"], "minValue": 0, "maxValue": 3 } } return layer ``` ### Step 4: Perform Gap Analysis Overlay threat actor TTPs against detection coverage: ```python def gap_analysis(threat_techniques, covered_techniques): """Identify detection gaps for specific threat actor""" gaps = set(threat_techniques) - set(covered_techniques) covered = set(threat_techniques) & set(covered_techniques) print(f"Threat Actor Techniques: {len(threat_techniques)}") print(f"Detected: {len(covered)} ({len(covered)/len(threat_techniques)*100:.0f}%)") print(f"Gaps: {len(gaps)} ({len(gaps)/len(threat_techniques)*100:.0f}%)") # Prioritize gaps by kill chain phase priority_order = { "TA0001": 1, "TA0002": 2, "TA0003": 3, "TA0004": 4, "TA0005": 5, "TA0006": 6, "TA0007": 7, "TA0008": 8, "TA0009": 9, "TA0010": 10, "TA0011": 11, "TA0040": 12 } gap_details = [] for tech_id in gaps: gap_details.append({ "technique": tech_id, "priority": "HIGH" if tech_id.split(".")[0] in ["T1003", "T1021", "T1059"] else "MEDIUM", "recommendation": f"Build detection for {tech_id}" }) return { "total_actor_techniques": len(threat_techniques), "covered": len(covered), "gaps": len(gaps), "coverage_pct": round(len(covered)/len(threat_techniques)*100, 1), "gap_details": sorted(gap_details, key=lambda x: x["priority"]) } # Run analysis result = gap_analysis(fin7_techniques, current_coverage) ``` ### Step 5: Create Prioritized Remediation Plan Build a detection engineering roadmap: ```yaml threat_model_remediation_plan: assessed_date: 2024-03-15 primary_threats: - FIN7 (Financial sector) - APT38 (DPRK financial) - Lazarus Group (Destructive) current_coverage: 64% target_coverage: 80% priority_1_gaps: # 30-day target - technique: T1021.002 name: SMB/Windows Admin Shares data_source: Windows Security Event 5140 effort: Low detection_approach: Monitor admin share access from non-admin workstations - technique: T1003.006 name: DCSync data_source: Windows Security Event 4662 effort: Medium detection_approach: Detect DS-Replication-Get-Changes from non-DC sources priority_2_gaps: # 60-day target - technique: T1055 name: Process Injection data_source: Sysmon EventCode 8, 10 effort: High detection_approach: Monitor cross-process memory access patterns - technique: T1071.001 name: Web Protocols (C2) data_source: Proxy/Firewall logs effort: Medium detection_approach: Detect beaconing patterns in HTTP/S traffic priority_3_gaps: # 90-day target - technique: T1070.004 name: File Deletion data_source: Sysmon EventCode 23 effort: Low detection_approach: Monitor mass file deletion in sensitive directories ``` ### Step 6: Validate with Adversary Emulation Test coverage using MITRE Caldera or Atomic Red Team: ```bash # Using Atomic Red Team to validate coverage for FIN7 techniques # T1566.001 — Spearphishing Attachment Invoke-AtomicTest T1566.001 # T1059.001 — PowerShell Invoke-AtomicTest T1059.001 -TestNumbers 1,2,3 # T1053.005 — Scheduled Task Invoke-AtomicTest T1053.005 # T1547.001 — Registry Run Keys Invoke-AtomicTest T1547.001 # T1003 — Credential Dumping Invoke-AtomicTest T1003 -TestNumbers 1,2 # Verify detections # Check SIEM for corresponding alerts within 15 minutes ``` Document emulation results to validate threat model accuracy. ## Key Concepts | Term | Definition | |------|-----------| | **MITRE ATT&CK** | Knowledge base of adversary tactics, techniques, and procedures based on real-world observations | | **TTP** | Tactics, Techniques, and Procedures — the behavioral patterns of adversary groups | | **ATT&CK Navigator** | Web tool for visualizing ATT&CK matrices as layered heatmaps showing coverage or threat profiles | | **Gap Analysis** | Process of comparing threat actor TTPs against detection coverage to identify blind spots | | **Threat-Informed Defense** | Security strategy prioritizing defenses based on actual adversary behaviors rather than theoretical risks | | **Adversary Emulation** | Controlled simulation of threat actor TTPs to validate detection and response capabilities | ## Tools & Systems - **MITRE ATT&CK Navigator**: Web-based visualization tool for creating and overlaying ATT&CK technique layers - **MITRE Caldera**: Automated adversary emulation platform for testing detection coverage at scale - **Atomic Red Team**: Open-source library of ATT&CK technique tests for security control validation - **CTID ATT&CK Workbench**: MITRE tool for customizing ATT&CK knowledge base with organizational context - **Tidal Cyber**: Commercial platform for threat-informed defense planning using ATT&CK framework ## Common Scenarios - **Annual Threat Assessment**: Map top 5 threat actors to ATT&CK, overlay against detection, produce gap analysis - **Cloud Migration Planning**: Model cloud-specific threats (T1078.004, T1537) and plan detection coverage - **M&A Security Assessment**: Threat model the acquired company's environment against relevant threat actors - **Budget Justification**: Use gap analysis to demonstrate detection blind spots requiring tool investment - **Purple Team Planning**: Select adversary emulation scenarios based on highest-priority gaps from threat model ## Output Format ``` THREAT MODEL ASSESSMENT — Financial Services Division ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Date: 2024-03-15 Threat Actors: FIN7, APT38, Lazarus Group Techniques Total: 87 unique techniques across all actors DETECTION COVERAGE: Covered: 56/87 (64%) Gaps: 31/87 (36%) Tactic Coverage Breakdown: Initial Access: 78% ████████░░ Execution: 82% █████████░ Persistence: 71% ████████░░ Priv Escalation: 65% ███████░░░ Defense Evasion: 52% ██████░░░░ <-- Priority gap Credential Access: 58% ██████░░░░ <-- Priority gap Discovery: 45% █████░░░░░ Lateral Movement: 61% ███████░░░ Collection: 50% ██████░░░░ Exfiltration: 55% ██████░░░░ C2: 67% ███████░░░ TOP PRIORITY GAPS (30-day remediation): 1. T1055 Process Injection — used by all 3 actors, 0 detections 2. T1003.006 DCSync — used by FIN7 and Lazarus, 0 detections 3. T1070.004 File Deletion — evidence destruction, 0 detections INVESTMENT RECOMMENDATION: Closing top 10 gaps requires: 2 detection engineer FTEs, 60 days Expected coverage improvement: 64% -> 76% ``` --- Source attribution: costrict-plugins-repo Original project: https://github.com/costrict-plugins-repo/mukul975-anthropic-cybersecurity-skills-cybersecurity-skills/blob/1b344d155f00bae5cf27d8eba9508e8f5050d904/skills/implementing-threat-modeling-with-mitre-attack/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. Please do not remove or change the license header comment from a contributed file except when necessary. Copyright 2026 mukul975 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: costrict-plugins-repo Original project: https://github.com/costrict-plugins-repo/mukul975-anthropic-cybersecurity-skills-cybersecurity-skills/blob/1b344d155f00bae5cf27d8eba9508e8f5050d904/skills/implementing-threat-modeling-with-mitre-attack/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: Security Engineer Specialties: API Tools: Attack Navigator, Mitre Attack Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: c17eb7792a6b3cc0e8855692d7895e855aa59e2fad7d7dda33af458ec0200e56