{
  "base": "http://localhost:22040",
  "models": [
    "vanilla-rag",
    "hybrid-rag",
    "contextual-rag",
    "graph-rag",
    "agentic-rag",
    "n8n-adaptive-rag",
    "lazy-graph-rag"
  ],
  "model_profiles": [
    {
      "model": "vanilla-rag",
      "base_model": "vanilla-rag",
      "flavor": "default",
      "requires_reingest": false,
      "experimental": false
    },
    {
      "model": "hybrid-rag",
      "base_model": "hybrid-rag",
      "flavor": "default",
      "requires_reingest": false,
      "experimental": false
    },
    {
      "model": "contextual-rag",
      "base_model": "contextual-rag",
      "flavor": "default",
      "requires_reingest": false,
      "experimental": false
    },
    {
      "model": "graph-rag",
      "base_model": "graph-rag",
      "flavor": "default",
      "requires_reingest": false,
      "experimental": false
    },
    {
      "model": "agentic-rag",
      "base_model": "agentic-rag",
      "flavor": "default",
      "requires_reingest": false,
      "experimental": false
    },
    {
      "model": "n8n-adaptive-rag",
      "base_model": "n8n-adaptive-rag",
      "flavor": "default",
      "requires_reingest": false,
      "experimental": false
    },
    {
      "model": "lazy-graph-rag",
      "base_model": "lazy-graph-rag",
      "flavor": "default",
      "requires_reingest": false,
      "experimental": true
    }
  ],
  "queries_file": "demo/cyber_threat_intel_queries.yaml",
  "run_id": "live-2026-07-17-cyber_threat_intel",
  "dataset_id": "cyber_threat_intel",
  "canonical_rows_file": "/Users/kaveh/repos/rag-showcase/compare/results/live-2026-07-17-cyber_threat_intel-evidence.jsonl",
  "evaluation_summary_file": "/Users/kaveh/repos/rag-showcase/compare/results/live-2026-07-17-cyber_threat_intel-evaluation.json",
  "queries": [
    {
      "id": "cyber_group_technique_software_chain",
      "query": "Which intrusion groups in this slice share credential-access or discovery techniques, and what software or tools connect them?",
      "expect_winner": "graph-rag",
      "rationale": "Requires graph paths across intrusion groups, tools, malware, and ATT&CK techniques."
    },
    {
      "id": "cyber_credential_access_path",
      "query": "Trace the relationship path from Cleaver, Carbanak, Mimikatz, Windows Credential Editor, and LSASS Memory. Which actors and software converge on credential access?",
      "expect_winner": "graph-rag",
      "rationale": "Requires multi-hop path traversal over intrusion sets, software tools, and techniques."
    },
    {
      "id": "cyber_campaign_overlap",
      "query": "Which campaigns overlap by tooling or technique, especially around PowerShell, Reg, spearphishing, discovery, or exfiltration?",
      "expect_winner": "graph-rag",
      "rationale": "Requires shared-entity graph reasoning across campaigns, groups, tools, and techniques."
    },
    {
      "id": "cyber_mitigation_coverage",
      "query": "Which mitigations cover credential, Active Directory, web-content, or registry-related techniques, and which techniques do they mitigate?",
      "expect_winner": "graph-rag",
      "rationale": "Requires relationship aggregation over mitigation-to-technique paths."
    },
    {
      "id": "cyber_campaign_timeline_context",
      "query": "Compare Frankenstein, Operation CuckooBees, Operation Honeybee, and Night Dragon by timeframe, target context, and the techniques or tools each used.",
      "expect_winner": "graph-rag",
      "rationale": "Requires temporal graph reasoning plus textual evidence."
    },
    {
      "id": "cyber_protocol_and_web_mitigation_path",
      "query": "Connect protocol impersonation, web-based content restrictions, spearphishing links, and command-and-control style techniques. Which groups, campaigns, or software are involved?",
      "expect_winner": "graph-rag",
      "rationale": "Requires graph path reasoning across techniques, mitigations, campaigns, groups, and software."
    }
  ],
  "cells": [
    {
      "query_id": "cyber_group_technique_software_chain",
      "model": "vanilla-rag",
      "base_model": "vanilla-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 7.4,
      "raw": "Based on the provided context, the following intrusion groups share credential-access or discovery techniques through specific software or tools:\n\n**1. Cleaver (G0003) and Carbanak (G0008)**\n*   **Shared Tool:** Both groups use **Mimikatz (S0002)**.\n    *   *Note:* Mimikatz is associated with credential dumping/access.\n*   **Shared Tool:** Both groups use **PsExec (S0029)**.\n    *   *Note:* PsExec is often used for lateral movement and remote execution, which can facilitate discovery and access.\n\n**2. Carbanak (G0008) and OS Credential Dumping (T1003)**\n*   **Shared Technique:** Carbanak uses the technique **OS Credential Dumping (T1003)**.\n    *   *Note:* While T1003 is a technique rather than a group, the context lists \"Carbanak (S0030)\" under the relations for OS Credential Dumping, indicating this group utilizes this credential-access method.\n\n**3. Cleaver (G0003) and Carbanak (G0008) via Shared Techniques**\n*   **Shared Technique:** Both groups utilize techniques related to system discovery and access:\n    *   Cleaver uses **ARP Cache Poisoning (T1557.002)** and **LSASS Memory (T1003.001)**.\n    *   Carbanak uses **Valid Accounts (T1078)** and **Remote Access Tools (T1219)**.\n    *   While they do not share a single specific tool for discovery in the direct relations listed, Cleaver's use of LSASS Memory dumping is a credential-access technique, and Carbanak also dumps credentials via OS Credential Dumping.\n\n**Summary of Connecting Software/Tools:**\n*   **Mimikatz (S0002)** connects **Cleaver** and **Carbanak**.\n*   **PsExec (S0029)** connects **Cleaver** and **Carbanak**.\n\n<details><summary>🔎 Retrieved context (5 sources)</summary>\n\n**1. cyber_threat_intel/003-g0003.md**\n\n> # Cleaver\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: intrusion-set\nATT&CK ID: G0003\nSTIX ID: intrusion-set--8f5e8dc7-739d-4f5e-a8a1-a66e004d7063\n\nDescription:\n[Cleaver](https://attack.mitre.org/groups/G0003) is a threat grou\n\n**2. cyber_threat_intel/008-g0008.md**\n\n> # Carbanak\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: intrusion-set\nATT&CK ID: G0008\nSTIX ID: intrusion-set--55033a4d-3ffe-46b2-99b4-2c1541e9ce1c\n\nDescription:\n[Carbanak](https://attack.mitre.org/groups/G0008) is a cybercrim\n\n**3. cyber_threat_intel/046-t1003.md**\n\n> # OS Credential Dumping\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1003\nSTIX ID: attack-pattern--0a3ead4e-6d47-4ccb-854c-a6a4f9d96b22\n\nDescription:\nAdversaries may attempt to dump credentials to ob\n\n**4. cyber_threat_intel/009-g0009.md**\n\n> # Deep Panda\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: intrusion-set\nATT&CK ID: G0009\nSTIX ID: intrusion-set--a653431d-6a5e-4600-8ad3-609b5af57064\n\nDescription:\n[Deep Panda](https://attack.mitre.org/groups/G0009) is a suspe\n\n**5. cyber_threat_intel/005-g0005.md**\n\n> # APT12\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: intrusion-set\nATT&CK ID: G0005\nSTIX ID: intrusion-set--c47f937f-1022-4f42-8525-e7a4779a14cb\n\nDescription:\n[APT12](https://attack.mitre.org/groups/G0005) is a threat group th\n\n</details>\n\n---\n📊 7.3s · 5 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the provided context, the following intrusion groups share credential-access or discovery techniques through specific software or tools:\n\n**1. Cleaver (G0003) and Carbanak (G0008)**\n*   **Shared Tool:** Both groups use **Mimikatz (S0002)**.\n    *   *Note:* Mimikatz is associated with credential dumping/access.\n*   **Shared Tool:** Both groups use **PsExec (S0029)**.\n    *   *Note:* PsExec is often used for lateral movement and remote execution, which can facilitate discovery and access.\n\n**2. Carbanak (G0008) and OS Credential Dumping (T1003)**\n*   **Shared Technique:** Carbanak uses the technique **OS Credential Dumping (T1003)**.\n    *   *Note:* While T1003 is a technique rather than a group, the context lists \"Carbanak (S0030)\" under the relations for OS Credential Dumping, indicating this group utilizes this credential-access method.\n\n**3. Cleaver (G0003) and Carbanak (G0008) via Shared Techniques**\n*   **Shared Technique:** Both groups utilize techniques related to system discovery and access:\n    *   Cleaver uses **ARP Cache Poisoning (T1557.002)** and **LSASS Memory (T1003.001)**.\n    *   Carbanak uses **Valid Accounts (T1078)** and **Remote Access Tools (T1219)**.\n    *   While they do not share a single specific tool for discovery in the direct relations listed, Cleaver's use of LSASS Memory dumping is a credential-access technique, and Carbanak also dumps credentials via OS Credential Dumping.\n\n**Summary of Connecting Software/Tools:**\n*   **Mimikatz (S0002)** connects **Cleaver** and **Carbanak**.\n*   **PsExec (S0029)** connects **Cleaver** and **Carbanak**.",
      "sources": [
        {
          "title": "cyber_threat_intel/003-g0003.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/008-g0008.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/046-t1003.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/009-g0009.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/005-g0005.md",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 7.3431234620002215,
        "chunks": 5,
        "llm_calls": 2,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_group_technique_software_chain",
      "model": "hybrid-rag",
      "base_model": "hybrid-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 20.3,
      "raw": "Based on the provided context, there are no intrusion groups that share credential-access or discovery techniques through common software or tools.\n\nWhile **APT28** (G0007) is listed as using **NTDS** (T1003.003), which is a credential-access technique under OS Credential Dumping, the context does not list any other intrusion group using NTDS or sharing specific credential-access software with APT28.\n\nSimilarly, while **Deep Panda** (G0009) and **Operation CuckooBees** (C0012) are listed as using discovery techniques (such as Remote System Discovery), they do not share any common software or tools in the provided relations:\n*   **Deep Panda** uses tools like Mivast, Sakula, StreamEx, and techniques like PowerShell and Regsvr32.\n*   **Operation CuckooBees** uses tools like dsquery and techniques like Windows Service and Archive via Utility.\n\nOther groups mentioned in the context (Ember Bear, APT39, Carbanak, MgBot, Revenge RAT, PinchDuke, Poseidon Group, OnionDuke, Mustang Panda, Daggerfly, GALLIUM, FrostyGoop, FIN13, MirrorFace) are linked to credential dumping or Security Account Manager techniques but do not share specific software tools with each other or with the groups using discovery techniques in this slice.\n\n<details><summary>🔎 Retrieved context (5 sources)</summary>\n\n**1. cyber_threat_intel/046-t1003.md** · score 0.023\n\n> # OS Credential Dumping\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1003\nSTIX ID: attack-pattern--0a3ead4e-6d47-4ccb-854c-a6a4f9d96b22\n\nDescription:\nAdversaries may attempt to dump credentials to ob\n\n**2. cyber_threat_intel/048-t1003-002.md** · score 0.017\n\n> # Security Account Manager\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1003.002\nSTIX ID: attack-pattern--1644e709-12d2-41e5-a60f-3470991f5011\n\nDescription:\nAdversaries may attempt to extract credent\n\n**3. cyber_threat_intel/009-g0009.md** · score 0.016\n\n> # Deep Panda\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: intrusion-set\nATT&CK ID: G0009\nSTIX ID: intrusion-set--a653431d-6a5e-4600-8ad3-609b5af57064\n\nDescription:\n[Deep Panda](https://attack.mitre.org/groups/G0009) is a suspe\n\n**4. cyber_threat_intel/019-c0012.md** · score 0.015\n\n> # Operation CuckooBees\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0012\nSTIX ID: campaign--93c23946-49af-41f4-ac03-40f9ffc7419b\n\nDescription:\n[Operation CuckooBees](https://attack.mitre.org/campaigns/C001\n\n**5. cyber_threat_intel/007-g0007.md** · score 0.015\n\n> # APT28\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: intrusion-set\nATT&CK ID: G0007\nSTIX ID: intrusion-set--bef4c620-0787-42a8-a96d-b7eb6e85917c\n\nDescription:\n[APT28](https://attack.mitre.org/groups/G0007) is a threat group th\n\n</details>\n\n---\n📊 20.3s · 5 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the provided context, there are no intrusion groups that share credential-access or discovery techniques through common software or tools.\n\nWhile **APT28** (G0007) is listed as using **NTDS** (T1003.003), which is a credential-access technique under OS Credential Dumping, the context does not list any other intrusion group using NTDS or sharing specific credential-access software with APT28.\n\nSimilarly, while **Deep Panda** (G0009) and **Operation CuckooBees** (C0012) are listed as using discovery techniques (such as Remote System Discovery), they do not share any common software or tools in the provided relations:\n*   **Deep Panda** uses tools like Mivast, Sakula, StreamEx, and techniques like PowerShell and Regsvr32.\n*   **Operation CuckooBees** uses tools like dsquery and techniques like Windows Service and Archive via Utility.\n\nOther groups mentioned in the context (Ember Bear, APT39, Carbanak, MgBot, Revenge RAT, PinchDuke, Poseidon Group, OnionDuke, Mustang Panda, Daggerfly, GALLIUM, FrostyGoop, FIN13, MirrorFace) are linked to credential dumping or Security Account Manager techniques but do not share specific software tools with each other or with the groups using discovery techniques in this slice.",
      "sources": [
        {
          "title": "cyber_threat_intel/046-t1003.md",
          "score": 0.022536736
        },
        {
          "title": "cyber_threat_intel/048-t1003-002.md",
          "score": 0.01741503
        },
        {
          "title": "cyber_threat_intel/009-g0009.md",
          "score": 0.016261153
        },
        {
          "title": "cyber_threat_intel/019-c0012.md",
          "score": 0.01523126
        },
        {
          "title": "cyber_threat_intel/007-g0007.md",
          "score": 0.014838095
        }
      ],
      "metrics": {
        "seconds": 20.317428342998028,
        "chunks": 5,
        "llm_calls": 2,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_group_technique_software_chain",
      "model": "contextual-rag",
      "base_model": "contextual-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 25.4,
      "raw": "Based on the provided context, the following intrusion groups share credential-access or discovery techniques, connected by specific software or tools:\n\n**1. Groups sharing LSASS Memory (T1003.001) via Windows Credential Editor (S0005):**\n*   **Leviathan (G0065)**\n*   **FIN5 (G0053)**\n*   **APT39 (G0087)**\n*   **FIN6 (G0037)**\n*   **GALLIUM (G0093)**\n*   **Threat Group-3390 (G0027)**\n*   **BRONZE BUTLER (G0060)**\n\n**2. Groups sharing OS Credential Dumping (T1003) directly:**\n*   **Ember Bear (G1003)**\n*   **APT39 (G0087)**\n*   **Carbanak (S0030)**\n*   **MgBot (S1146)**\n*   **Revenge RAT (S0379)**\n*   **PinchDuke (S0048)**\n*   **Poseidon Group (G0033)**\n*   **OnionDuke (S0052)**\n*   **Mustang Panda (G0129)**\n\n**3. Groups sharing NTDS (T1003.003) directly:**\n*   **APT28 (G0007)**\n*   **Scattered Spider (G1015)**\n*   **Sandworm Team (G0034)**\n*   **FIN13 (G1016)**\n*   **FIN6 (G0037)**\n*   **Volt Typhoon (G1017)**\n\n**4. Groups sharing NTDS (T1003.003) via CrackMapExec (S0488):**\n*   **APT28 (G0007)**\n*   **Scattered Spider (G1015)**\n*   **Sandworm Team (G0034)**\n*   **FIN13 (G1016)**\n*   **FIN6 (G0037)**\n*   **Volt Typhoon (G1017)**\n\n**5. Groups sharing NTDS (T1003.003) via esentutl (S0404):**\n*   **APT28 (G0007)**\n*   **Scattered Spider (G1015)**\n*   **Sandworm Team (G0034)**\n*   **FIN13 (G1016)**\n*   **FIN6 (G0037)**\n*   **Volt Typhoon (G1017)**\n\n**Note on Deep Panda (G0009):**\nWhile Deep Panda is listed in the context, it does not share credential-access or discovery techniques with the other groups via a common tool in this specific slice. It uses Process Discovery (T1057), Remote System Discovery (T1018), and various other tools (Mivast, StreamEx, Sakula, etc.), but none of these are listed as shared by the other credential-focused groups in the provided text.\n\n<details><summary>🔎 Retrieved context (5 sources)</summary>\n\n**1. cyber_threat_intel/046-t1003.md** · score 0.050\n\n> This section details the MITRE ATT&CK technique T1003 for OS Credential Dumping, describing how adversaries extract login material from system memory or structures to facilitate lateral movement. It further lists specific threat groups that\n\n**2. cyber_threat_intel/049-t1003-003.md** · score 0.033\n\n> This section details the NTDS technique (T1003.003), which involves adversaries accessing or copying the Active Directory domain database to steal credentials and gather information about domain members. It lists specific tools used for thi\n\n**3. cyber_threat_intel/047-t1003-001.md** · score 0.028\n\n> This section details the LSASS Memory technique (T1003.001), a subtechnique of OS Credential Dumping used by adversaries to harvest credentials for lateral movement. It outlines methods such as memory dumping with tools like Procdump and Mi\n\n**4. cyber_threat_intel/032-s0005.md** · score 0.028\n\n> This section details the Windows Credential Editor, a password dumping tool identified by MITRE ATT&CK ID S0005. It outlines the tool's technical capabilities and lists specific threat groups that utilize this software for credential theft.\n\n**5. cyber_threat_intel/009-g0009.md** · score 0.026\n\n> This text provides a detailed profile of the Deep Panda intrusion set, including its aliases, attribution history, and associated MITRE ATT&CK techniques and tools.\n\n# Deep Panda\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: in\n\n</details>\n\n---\n📊 25.4s · 5 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the provided context, the following intrusion groups share credential-access or discovery techniques, connected by specific software or tools:\n\n**1. Groups sharing LSASS Memory (T1003.001) via Windows Credential Editor (S0005):**\n*   **Leviathan (G0065)**\n*   **FIN5 (G0053)**\n*   **APT39 (G0087)**\n*   **FIN6 (G0037)**\n*   **GALLIUM (G0093)**\n*   **Threat Group-3390 (G0027)**\n*   **BRONZE BUTLER (G0060)**\n\n**2. Groups sharing OS Credential Dumping (T1003) directly:**\n*   **Ember Bear (G1003)**\n*   **APT39 (G0087)**\n*   **Carbanak (S0030)**\n*   **MgBot (S1146)**\n*   **Revenge RAT (S0379)**\n*   **PinchDuke (S0048)**\n*   **Poseidon Group (G0033)**\n*   **OnionDuke (S0052)**\n*   **Mustang Panda (G0129)**\n\n**3. Groups sharing NTDS (T1003.003) directly:**\n*   **APT28 (G0007)**\n*   **Scattered Spider (G1015)**\n*   **Sandworm Team (G0034)**\n*   **FIN13 (G1016)**\n*   **FIN6 (G0037)**\n*   **Volt Typhoon (G1017)**\n\n**4. Groups sharing NTDS (T1003.003) via CrackMapExec (S0488):**\n*   **APT28 (G0007)**\n*   **Scattered Spider (G1015)**\n*   **Sandworm Team (G0034)**\n*   **FIN13 (G1016)**\n*   **FIN6 (G0037)**\n*   **Volt Typhoon (G1017)**\n\n**5. Groups sharing NTDS (T1003.003) via esentutl (S0404):**\n*   **APT28 (G0007)**\n*   **Scattered Spider (G1015)**\n*   **Sandworm Team (G0034)**\n*   **FIN13 (G1016)**\n*   **FIN6 (G0037)**\n*   **Volt Typhoon (G1017)**\n\n**Note on Deep Panda (G0009):**\nWhile Deep Panda is listed in the context, it does not share credential-access or discovery techniques with the other groups via a common tool in this specific slice. It uses Process Discovery (T1057), Remote System Discovery (T1018), and various other tools (Mivast, StreamEx, Sakula, etc.), but none of these are listed as shared by the other credential-focused groups in the provided text.",
      "sources": [
        {
          "title": "cyber_threat_intel/046-t1003.md",
          "score": 0.04993039
        },
        {
          "title": "cyber_threat_intel/049-t1003-003.md",
          "score": 0.033487342
        },
        {
          "title": "cyber_threat_intel/047-t1003-001.md",
          "score": 0.028313097
        },
        {
          "title": "cyber_threat_intel/032-s0005.md",
          "score": 0.027746525
        },
        {
          "title": "cyber_threat_intel/009-g0009.md",
          "score": 0.026076756
        }
      ],
      "metrics": {
        "seconds": 25.4051731369982,
        "chunks": 5,
        "llm_calls": 2,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_group_technique_software_chain",
      "model": "graph-rag",
      "base_model": "graph-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 16.7,
      "raw": "Based on the provided knowledge base, several intrusion sets share credential access or discovery techniques through specific software tools. The following analysis details these overlaps:\n\n### Groups Sharing Credential Access Techniques via Mimikatz\n\nTwo primary threat groups are explicitly linked to the use of **Mimikatz** (S0002), a well-known tool for dumping credentials from memory:\n\n*   **Cleaver**: Documented as using both **LSASS Memory** (T1003.001) and **Mimikatz** to extract credentials [1]. The LSASS Memory technique is specifically defined as accessing credential material stored in the process memory of the Local Security Authority Subsystem Service [Knowledge Graph].\n*   **Carbanak**: This cybercriminal group, known for targeting financial institutions, also utilizes **Mimikatz** (S0002) to extract credentials from memory. Additionally, Carbanak is linked to the **OS Credential Dumping** (T1003) technique in general [2], which encompasses various methods for obtaining account login and credential material [3].\n\n### Groups Sharing Credential Access via Other Tools\n\nBeyond Mimikatz, other specific tools link distinct groups:\n\n*   **APT12 and Cleaver**: While not sharing a tool directly in the provided text, both groups are documented as using **LSASS Memory** techniques. Cleaver explicitly uses LSASS Memory (T1003.001) [1]. APT12 is noted for using tools like **RIPTIDE** and **HTRAN**, but the shared tactical approach of targeting LSASS memory is a key overlap in their credential access capabilities described in the broader context of credential dumping methods [Knowledge Graph].\n*   **APT39**: This group uses **pwdump** for credential dumping. While no other group in this slice is explicitly stated to use pwdump, it falls under the **OS Credential Dumping** technique (T1003), which is also used by **Carbanak** [3]. Thus, they share the overarching *technique* of OS Credential Dumping, though via potentially different tools (pwdump vs. Mimikatz/LSASS Memory).\n\n### Groups Sharing Discovery Techniques\n\n*   **Operation Sharpshooter**: This campaign uses **Registry Run Keys / Startup Folder** for persistence, which is a distinct operational technique not directly shared as a discovery method by the other groups listed here. However, it highlights the use of Windows registry manipulation, a common theme in maintaining access after discovery.\n*   **Frankenstein**: Uses **Security Software Discovery (T1518.001)** to identify security tools on victim systems [Knowledge Graph]. No other group in this specific slice is explicitly linked to this discovery technique.\n\n### Summary of Connections\n\n| Technique / Tool | Intrusion Group(s) | Source Context |\n| :--- | :--- | :--- |\n| **Mimikatz (S0002)** | **Cleaver**, **Carbanak** | Both groups use Mimikatz to dump credentials [1], [2]. |\n| **LSASS Memory (T1003.001)** | **Cleaver** | Cleaver uses this specific credential dumping method [1]. |\n| **OS Credential Dumping (T1003)** | **Carbanak**, **APT39** | Carbanak and APT39 both utilize the broader OS Credential Dumping technique, though via different implied tools (Mimikatz/LSASS vs. pwdump) [2], [3]. |\n| **pwdump** | **APT39** | Used by APT39 for credential dumping [Knowledge Graph]. |\n\nIn conclusion, **Cleaver** and **Carbanak** are the most directly connected groups in this slice through their shared use of **Mimikatz** for credential access. **APT39** shares the broader *category* of OS Credential Dumping with Carbanak but uses **pwdump** instead.\n\n<details><summary>🔎 Retrieved context (1 source)</summary>\n\n**1. LightRAG knowledge graph**\n\n> Graph + vector dual retrieval (profile=graph-rag) over the corpus's extracted entities and relations.\n\n</details>\n\n---\n📊 16.7s · 0 chunks · 1 LLM call · 0 cloud",
      "answer": "Based on the provided knowledge base, several intrusion sets share credential access or discovery techniques through specific software tools. The following analysis details these overlaps:\n\n### Groups Sharing Credential Access Techniques via Mimikatz\n\nTwo primary threat groups are explicitly linked to the use of **Mimikatz** (S0002), a well-known tool for dumping credentials from memory:\n\n*   **Cleaver**: Documented as using both **LSASS Memory** (T1003.001) and **Mimikatz** to extract credentials [1]. The LSASS Memory technique is specifically defined as accessing credential material stored in the process memory of the Local Security Authority Subsystem Service [Knowledge Graph].\n*   **Carbanak**: This cybercriminal group, known for targeting financial institutions, also utilizes **Mimikatz** (S0002) to extract credentials from memory. Additionally, Carbanak is linked to the **OS Credential Dumping** (T1003) technique in general [2], which encompasses various methods for obtaining account login and credential material [3].\n\n### Groups Sharing Credential Access via Other Tools\n\nBeyond Mimikatz, other specific tools link distinct groups:\n\n*   **APT12 and Cleaver**: While not sharing a tool directly in the provided text, both groups are documented as using **LSASS Memory** techniques. Cleaver explicitly uses LSASS Memory (T1003.001) [1]. APT12 is noted for using tools like **RIPTIDE** and **HTRAN**, but the shared tactical approach of targeting LSASS memory is a key overlap in their credential access capabilities described in the broader context of credential dumping methods [Knowledge Graph].\n*   **APT39**: This group uses **pwdump** for credential dumping. While no other group in this slice is explicitly stated to use pwdump, it falls under the **OS Credential Dumping** technique (T1003), which is also used by **Carbanak** [3]. Thus, they share the overarching *technique* of OS Credential Dumping, though via potentially different tools (pwdump vs. Mimikatz/LSASS Memory).\n\n### Groups Sharing Discovery Techniques\n\n*   **Operation Sharpshooter**: This campaign uses **Registry Run Keys / Startup Folder** for persistence, which is a distinct operational technique not directly shared as a discovery method by the other groups listed here. However, it highlights the use of Windows registry manipulation, a common theme in maintaining access after discovery.\n*   **Frankenstein**: Uses **Security Software Discovery (T1518.001)** to identify security tools on victim systems [Knowledge Graph]. No other group in this specific slice is explicitly linked to this discovery technique.\n\n### Summary of Connections\n\n| Technique / Tool | Intrusion Group(s) | Source Context |\n| :--- | :--- | :--- |\n| **Mimikatz (S0002)** | **Cleaver**, **Carbanak** | Both groups use Mimikatz to dump credentials [1], [2]. |\n| **LSASS Memory (T1003.001)** | **Cleaver** | Cleaver uses this specific credential dumping method [1]. |\n| **OS Credential Dumping (T1003)** | **Carbanak**, **APT39** | Carbanak and APT39 both utilize the broader OS Credential Dumping technique, though via different implied tools (Mimikatz/LSASS vs. pwdump) [2], [3]. |\n| **pwdump** | **APT39** | Used by APT39 for credential dumping [Knowledge Graph]. |\n\nIn conclusion, **Cleaver** and **Carbanak** are the most directly connected groups in this slice through their shared use of **Mimikatz** for credential access. **APT39** shares the broader *category* of OS Credential Dumping with Carbanak but uses **pwdump** instead.",
      "sources": [
        {
          "title": "LightRAG knowledge graph",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 16.65459038300105,
        "chunks": 0,
        "llm_calls": 1,
        "cloud_calls": 0
      },
      "approach_metadata": {
        "lightrag": {
          "query_profile": "graph-rag"
        }
      }
    },
    {
      "query_id": "cyber_group_technique_software_chain",
      "model": "agentic-rag",
      "base_model": "agentic-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 23.1,
      "raw": "Based on the provided knowledge base, the intrusion groups that share credential-access or discovery techniques are **Carbanak**, **Ember Bear**, **APT39**, **Poseidon Group**, and **Mustang Panda** (for credential access), as well as **Threat Group-1314** and **Ke3chang** (for discovery).\n\nThe specific software and tools connecting them are:\n\n*   **Carbanak**: Uses **Mimikatz** and **gsecdump** to perform OS Credential Dumping (T1003) and access the Security Account Manager (T1003.002).\n*   **Threat Group-1314**: Uses the Windows utility **Net** for System Service Discovery (T1007).\n*   **Ke3chang**: Uses **netstat** and **Ping** for discovery techniques such as System Owner/User Discovery and Network Info Acquisition.\n\nWhile **Ember Bear**, **APT39**, **Poseidon Group**, and **Mustang Panda** are also linked to OS Credential Dumping (T1003), the provided text does not specify unique tools for them, though it notes that tools like Mimikatz or gsecdump are commonly shared among adversaries.\n\n<details><summary>🔎 Retrieved context (1 source)</summary>\n\n**1. 🤖 Agent trace**\n\n> **Step 1.** **Thought:** To answer this question accurately, I need to access the specific document corpus or knowledge graph that contains the \"slice\" of data you are referring to. Since the context of \"this slice\" is not provided in the prompt, I will perform a search for intrusion groups known to share credential-access and discovery techniques, as well as the tools they use, which often appear in threat intelligence reports (like those from Mandiant, CrowdStrike, or Microsoft).\n\nHowever, without the specific source text, I cannot definitively say which groups are in *your* specific slice. I will assume you are referring to a common set of APTs often analyzed together in such contexts (e.g., APT29, APT28, APT41, or similar clusters).\n\nLet's search for information on intrusion groups sharing these techniques and the connecting tools.\n\n**Action:** `search_vectors(intrusion groups share credential-access discovery techniques software tools)`\n\n**Observation:** - cyber_threat_intel/046-t1003.md: # OS Credential Dumping\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1003\nSTIX ID: attack-pattern--0a3ead4e-6d47-4ccb-854c-a6a4f9d96b22\n\nDescription:\nAdversari\n- cyber_threat_intel/036-s0039.md: # Net\n\nSource: MITRE ATT&CK E\n\n**Step 2.** **Action:** `query_graph(Which intrusion groups share credential-access (T1003) or discovery techniques, and what software or tools connect them?)`\n\n**Observation:** Based on the provided knowledge base, several intrusion groups are linked to **OS Credential Dumping** (T1003) or related discovery techniques. The specific connections, including the software or tools involved, are detailed below:\n\n### Groups Linked to OS Credential Dumping (T1003)\n\nThe following g\n\n</details>\n\n---\n📊 23.1s · 0 chunks · 5 LLM calls · 0 cloud",
      "answer": "Based on the provided knowledge base, the intrusion groups that share credential-access or discovery techniques are **Carbanak**, **Ember Bear**, **APT39**, **Poseidon Group**, and **Mustang Panda** (for credential access), as well as **Threat Group-1314** and **Ke3chang** (for discovery).\n\nThe specific software and tools connecting them are:\n\n*   **Carbanak**: Uses **Mimikatz** and **gsecdump** to perform OS Credential Dumping (T1003) and access the Security Account Manager (T1003.002).\n*   **Threat Group-1314**: Uses the Windows utility **Net** for System Service Discovery (T1007).\n*   **Ke3chang**: Uses **netstat** and **Ping** for discovery techniques such as System Owner/User Discovery and Network Info Acquisition.\n\nWhile **Ember Bear**, **APT39**, **Poseidon Group**, and **Mustang Panda** are also linked to OS Credential Dumping (T1003), the provided text does not specify unique tools for them, though it notes that tools like Mimikatz or gsecdump are commonly shared among adversaries.",
      "sources": [
        {
          "title": "🤖 Agent trace",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 23.08579263499996,
        "chunks": 0,
        "llm_calls": 5,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_group_technique_software_chain",
      "model": "n8n-adaptive-rag",
      "base_model": "n8n-adaptive-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 0.8,
      "raw": "Based on the provided knowledge base, the intrusion groups that share credential-access or discovery techniques are **Carbanak**, **Ember Bear**, **APT39**, **Poseidon Group**, and **Mustang Panda** (for credential access), as well as **Threat Group-1314** and **Ke3chang** (for discovery).\n\nThe specific software and tools connecting them are:\n\n*   **Carbanak**: Uses **Mimikatz** and **gsecdump** to perform OS Credential Dumping (T1003) and access the Security Account Manager (T1003.002).\n*   **Threat Group-1314**: Uses the Windows utility **Net** for System Service Discovery (T1007).\n*   **Ke3chang**: Uses **netstat** and **Ping** for discovery techniques such as System Owner/User Discovery and Network Info Acquisition.\n\nWhile **Ember Bear**, **APT39**, **Poseidon Group**, and **Mustang Panda** are also linked to OS Credential Dumping (T1003), the provided text does not specify unique tools for them, though it notes that tools like Mimikatz or gsecdump are commonly shared among adversaries.\n\n<details><summary>🔎 Retrieved context (1 source)</summary>\n\n**1. 🤖 Agent trace**\n\n> **Step 1.** **Thought:** To answer this question accurately, I need to access the specific document corpus or knowledge graph that contains the \"slice\" of data you are referring to. Since the context of \"this slice\" is not provided in the prompt, I will perform a search for intrusion groups known to share credential-access and discovery techniques, as well as the tools they use, which often appear in threat intelligence reports (like those from Mandiant, CrowdStrike, or Microsoft).\n\nHowever, without the specific source text, I cannot definitively say which groups are in *your* specific slice. I will assume you are referring to a common set of APTs often analyzed together in such contexts (e.g., APT29, APT28, APT41, or similar clusters).\n\nLet's search for information on intrusion groups sharing these techniques and the connecting tools.\n\n**Action:** `search_vectors(intrusion groups share credential-access discovery techniques software tools)`\n\n**Observation:** - cyber_threat_intel/046-t1003.md: # OS Credential Dumping\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1003\nSTIX ID: attack-pattern--0a3ead4e-6d47-4ccb-854c-a6a4f9d96b22\n\nDescription:\nAdversari\n- cyber_threat_intel/036-s0039.md: # Net\n\nSource: MITRE ATT&CK E\n\n**Step 2.** **Action:** `query_graph(Which intrusion groups share credential-access (T1003) or discovery techniques, and what software or tools connect them?)`\n\n**Observation:** Based on the provided knowledge base, several intrusion groups are linked to **OS Credential Dumping** (T1003) or related discovery techniques. The specific connections, including the software or tools involved, are detailed below:\n\n### Groups Linked to OS Credential Dumping (T1003)\n\nThe following g\n\n</details>\n\n---\n📊 0.7s · 0 chunks · 6 LLM calls · 0 cloud",
      "answer": "Based on the provided knowledge base, the intrusion groups that share credential-access or discovery techniques are **Carbanak**, **Ember Bear**, **APT39**, **Poseidon Group**, and **Mustang Panda** (for credential access), as well as **Threat Group-1314** and **Ke3chang** (for discovery).\n\nThe specific software and tools connecting them are:\n\n*   **Carbanak**: Uses **Mimikatz** and **gsecdump** to perform OS Credential Dumping (T1003) and access the Security Account Manager (T1003.002).\n*   **Threat Group-1314**: Uses the Windows utility **Net** for System Service Discovery (T1007).\n*   **Ke3chang**: Uses **netstat** and **Ping** for discovery techniques such as System Owner/User Discovery and Network Info Acquisition.\n\nWhile **Ember Bear**, **APT39**, **Poseidon Group**, and **Mustang Panda** are also linked to OS Credential Dumping (T1003), the provided text does not specify unique tools for them, though it notes that tools like Mimikatz or gsecdump are commonly shared among adversaries.",
      "sources": [
        {
          "title": "🤖 Agent trace",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 0.7487533749990689,
        "chunks": 0,
        "llm_calls": 6,
        "cloud_calls": 0
      },
      "approach_metadata": {
        "adaptive": {
          "route": "complex",
          "approach": "agentic-rag"
        }
      }
    },
    {
      "query_id": "cyber_group_technique_software_chain",
      "model": "lazy-graph-rag",
      "base_model": "lazy-graph-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 11.3,
      "raw": "Based on the provided context, the following intrusion groups share credential-access or discovery techniques through specific software or tools:\n\n**1. Groups sharing \"Net\" (S0039) for Discovery techniques:**\nThe **Net** utility is used for various discovery techniques (such as Password Policy Discovery, Domain Groups, System Time Discovery, Domain Account, Local Account, System Service Discovery, Remote System Discovery, Network Share Discovery, and System Network Connections Discovery). The following intrusion groups use Net:\n*   MirrorFace (G1054)\n*   Naikon (G0019)\n*   Magic Hound (G0059)\n*   APT38 (G0082)\n*   Dragonfly (G0035)\n*   Deep Panda (G0009)\n*   Threat Group-3390 (G0027)\n*   C0026 (C0026)\n*   OilRig (G0049)\n*   Threat Group-1314 (G0028)\n*   APT28 (G0007)\n*   APT41 (G0096)\n\n**2. Groups sharing \"Security Account Manager\" (T1003.002) for Credential Access:**\nThe **Security Account Manager** technique involves extracting credential material from the SAM database. The following intrusion groups use this technique:\n*   Daggerfly (G1034)\n*   GALLIUM (G0093)\n*   APT29 (G0016)\n*   FIN13 (G1016)\n*   MirrorFace (G1054)\n\n**3. Groups sharing \"Reg\" (S0075) for Credential Access and Discovery:**\nThe **Reg** utility is used to interact with the Windows Registry, specifically for accessing Credentials in Registry (T1552.002), Query Registry (T1012), and Modify Registry (T1112). The following intrusion groups use Reg:\n*   Rancor (G0075)\n*   OilRig (G0049)\n*   Daggerfly (G1034)\n*   Dragonfly (G0035)\n*   GALLIUM (G0093)\n*   Turla (G0010)\n*   Gamaredon Group (G0047)\n*   Volt Typhoon (G1017)\n\n**Summary of Shared Connections:**\n*   **MirrorFace (G1054)** connects to the group using **Net** and also uses **Security Account Manager**.\n*   **OilRig (G0049)** connects to the group using **Net** and also uses **Reg**.\n*   **Daggerfly (G1034)** connects to the group using **Security Account Manager** and also uses **Reg**.\n*   **Dragonfly (G0035)** connects to the group using **Net** and also uses **Reg**.\n*   **GALLIUM (G0093)** connects to the group using **Security Account Manager** and also uses **Reg**.\n\n<details><summary>🔎 Retrieved context (8 sources)</summary>\n\n**1. cyber_threat_intel/036-s0039.md** · score 69.000\n\n> # Net\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: tool\nATT&CK ID: S0039\nSTIX ID: tool--03342581-f790-4f03-ba41-e82e67392e23\n\nDescription:\nThe [Net](https://attack.mitre.org/software/S0039) utility is a component of the Window\n\n**2. cyber_threat_intel/027-s0011.md** · score 32.000\n\n> # Taidoor\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: malware\nATT&CK ID: S0011\nSTIX ID: malware--b143dfa4-e944-43ff-8429-bfffc308c517\n\nDescription:\n[Taidoor](https://attack.mitre.org/software/S0011) is a remote access trojan \n\n**3. cyber_threat_intel/008-g0008.md** · score 30.500\n\n> # Carbanak\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: intrusion-set\nATT&CK ID: G0008\nSTIX ID: intrusion-set--55033a4d-3ffe-46b2-99b4-2c1541e9ce1c\n\nDescription:\n[Carbanak](https://attack.mitre.org/groups/G0008) is a cybercrim\n\n**4. cyber_threat_intel/009-g0009.md** · score 26.750\n\n> # Deep Panda\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: intrusion-set\nATT&CK ID: G0009\nSTIX ID: intrusion-set--a653431d-6a5e-4600-8ad3-609b5af57064\n\nDescription:\n[Deep Panda](https://attack.mitre.org/groups/G0009) is a suspe\n\n**5. cyber_threat_intel/011-c0001.md** · score 26.000\n\n> # Frankenstein\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0001\nSTIX ID: campaign--26d9ebae-de59-427f-ae9a-349456bae4b1\n\nDescription:\n[Frankenstein](https://attack.mitre.org/campaigns/C0001) was described\n\n**6. cyber_threat_intel/048-t1003-002.md** · score 25.500\n\n> # Security Account Manager\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1003.002\nSTIX ID: attack-pattern--1644e709-12d2-41e5-a60f-3470991f5011\n\nDescription:\nAdversaries may attempt to extract credent\n\n**7. cyber_threat_intel/019-c0012.md** · score 25.000\n\n> # Operation CuckooBees\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0012\nSTIX ID: campaign--93c23946-49af-41f4-ac03-40f9ffc7419b\n\nDescription:\n[Operation CuckooBees](https://attack.mitre.org/campaigns/C001\n\n**8. cyber_threat_intel/039-s0075.md** · score 25.000\n\n> # Reg\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: tool\nATT&CK ID: S0075\nSTIX ID: tool--cde2d700-9ed1-46cf-9bce-07364fe8b24f\n\nDescription:\n[Reg](https://attack.mitre.org/software/S0075) is a Windows utility used to interact wi\n\n</details>\n\n---\n📊 11.3s · 8 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the provided context, the following intrusion groups share credential-access or discovery techniques through specific software or tools:\n\n**1. Groups sharing \"Net\" (S0039) for Discovery techniques:**\nThe **Net** utility is used for various discovery techniques (such as Password Policy Discovery, Domain Groups, System Time Discovery, Domain Account, Local Account, System Service Discovery, Remote System Discovery, Network Share Discovery, and System Network Connections Discovery). The following intrusion groups use Net:\n*   MirrorFace (G1054)\n*   Naikon (G0019)\n*   Magic Hound (G0059)\n*   APT38 (G0082)\n*   Dragonfly (G0035)\n*   Deep Panda (G0009)\n*   Threat Group-3390 (G0027)\n*   C0026 (C0026)\n*   OilRig (G0049)\n*   Threat Group-1314 (G0028)\n*   APT28 (G0007)\n*   APT41 (G0096)\n\n**2. Groups sharing \"Security Account Manager\" (T1003.002) for Credential Access:**\nThe **Security Account Manager** technique involves extracting credential material from the SAM database. The following intrusion groups use this technique:\n*   Daggerfly (G1034)\n*   GALLIUM (G0093)\n*   APT29 (G0016)\n*   FIN13 (G1016)\n*   MirrorFace (G1054)\n\n**3. Groups sharing \"Reg\" (S0075) for Credential Access and Discovery:**\nThe **Reg** utility is used to interact with the Windows Registry, specifically for accessing Credentials in Registry (T1552.002), Query Registry (T1012), and Modify Registry (T1112). The following intrusion groups use Reg:\n*   Rancor (G0075)\n*   OilRig (G0049)\n*   Daggerfly (G1034)\n*   Dragonfly (G0035)\n*   GALLIUM (G0093)\n*   Turla (G0010)\n*   Gamaredon Group (G0047)\n*   Volt Typhoon (G1017)\n\n**Summary of Shared Connections:**\n*   **MirrorFace (G1054)** connects to the group using **Net** and also uses **Security Account Manager**.\n*   **OilRig (G0049)** connects to the group using **Net** and also uses **Reg**.\n*   **Daggerfly (G1034)** connects to the group using **Security Account Manager** and also uses **Reg**.\n*   **Dragonfly (G0035)** connects to the group using **Net** and also uses **Reg**.\n*   **GALLIUM (G0093)** connects to the group using **Security Account Manager** and also uses **Reg**.",
      "sources": [
        {
          "title": "cyber_threat_intel/036-s0039.md",
          "score": 69.0
        },
        {
          "title": "cyber_threat_intel/027-s0011.md",
          "score": 32.0
        },
        {
          "title": "cyber_threat_intel/008-g0008.md",
          "score": 30.5
        },
        {
          "title": "cyber_threat_intel/009-g0009.md",
          "score": 26.75
        },
        {
          "title": "cyber_threat_intel/011-c0001.md",
          "score": 26.0
        },
        {
          "title": "cyber_threat_intel/048-t1003-002.md",
          "score": 25.5
        },
        {
          "title": "cyber_threat_intel/019-c0012.md",
          "score": 25.0
        },
        {
          "title": "cyber_threat_intel/039-s0075.md",
          "score": 25.0
        }
      ],
      "metrics": {
        "seconds": 11.321834379003121,
        "chunks": 8,
        "llm_calls": 2,
        "cloud_calls": 0
      },
      "approach_metadata": {
        "lazy_graph": {
          "experimental": true,
          "cache_hit": false,
          "index_seconds": 0.027987,
          "graph_chunks": 66,
          "graph_concepts": 762,
          "graph_edges": 13949,
          "relevance_tests": 24,
          "relevance_budget": 24,
          "seed_k": 8,
          "max_context_chunks": 8,
          "llm_index_calls": 0,
          "cache_namespace": "RagBase_cyber_threat_intel.concepts-24"
        }
      }
    },
    {
      "query_id": "cyber_credential_access_path",
      "model": "vanilla-rag",
      "base_model": "vanilla-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 10.7,
      "raw": "Based on the provided context, it is not possible to trace a relationship path involving **Cleaver** because there is no mention of \"Cleaver\" in the text.\n\nHowever, regarding the other entities:\n*   **Carbanak** (S0030) uses **OS Credential Dumping** (T1003).\n*   **Mimikatz** (S0002) is a credential dumper that uses techniques such as **Security Account Manager** (T1003.002) and **LSASS Memory** (via the description of LSASS Memory dumping which mentions Mimikatz, though the direct relation in [3] lists other techniques, [4] explicitly states mimikatz can be run on LSASS dumps).\n*   **Windows Credential Editor** is a password dumping tool that uses **LSASS Memory** (T1003.001).\n\nThe actors and software mentioned in the context that converge on credential access (specifically OS Credential Dumping or its sub-techniques like LSASS Memory) include:\n*   **APT39** (uses OS Credential Dumping and Windows Credential Editor)\n*   **FIN5** (uses Windows Credential Editor)\n*   **GALLIUM** (uses Windows Credential Editor and Security Account Manager)\n*   **Threat Group-3390** (uses Windows Credential Editor)\n*   **BRONZE BUTLER** (uses Windows Credential Editor and Mimikatz)\n*   **Ember Bear** (uses OS Credential Dumping)\n*   **MgBot** (uses OS Credential Dumping)\n*   **Revenge RAT** (uses OS Credential Dumping)\n*   **PinchDuke** (uses OS Credential Dumping)\n*   **Poseidon Group** (uses OS Credential Dumping)\n*   **OnionDuke** (uses OS Credential Dumping)\n*   **Mustang Panda** (uses OS Credential Dumping)\n*   **APT32** (uses Mimikatz)\n*   **APT29** (uses Mimikatz and Security Account Manager)\n*   **Earth Lusca** (uses Mimikatz)\n*   **FIN7** (uses Mimikatz)\n*   **DarkHydrus** (uses Mimikatz)\n*   **TA505** (uses Mimikatz)\n*   **Agrius** (uses Mimikatz)\n*   **Operation Wocao** (uses Mimikatz)\n*   **Sandworm Team** (uses Mimikatz)\n*   **APT33** (uses Mimikatz)\n*   **Akira** (uses Mimikatz)\n*   **Daggerfly** (uses Security Account Manager)\n*   **CrackMapExec** (uses Security Account Manager)\n*   **gsecdump** (uses Security Account Manager)\n*   **FrostyGoop Incident** (uses Security Account Manager)\n*   **Koadic** (uses Security Account Manager)\n*   **FIN13** (uses Security Account Manager)\n*   **MirrorFace** (uses Security Account Manager)\n*   **C0017** (uses Security Account Manager)\n*   **pwdump** (uses Security Account Manager)\n\n<details><summary>🔎 Retrieved context (5 sources)</summary>\n\n**1. cyber_threat_intel/032-s0005.md**\n\n> # Windows Credential Editor\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: tool\nATT&CK ID: S0005\nSTIX ID: tool--242f3da3-4425-4d11-8f5c-b842886da966\n\nDescription:\n[Windows Credential Editor](https://attack.mitre.org/software/S00\n\n**2. cyber_threat_intel/046-t1003.md**\n\n> # OS Credential Dumping\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1003\nSTIX ID: attack-pattern--0a3ead4e-6d47-4ccb-854c-a6a4f9d96b22\n\nDescription:\nAdversaries may attempt to dump credentials to ob\n\n**3. cyber_threat_intel/031-s0002.md**\n\n> # Mimikatz\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: tool\nATT&CK ID: S0002\nSTIX ID: tool--afc079f3-c0ea-4096-b75d-3f05338b7f60\n\nDescription:\n[Mimikatz](https://attack.mitre.org/software/S0002) is a credential dumper capable\n\n**4. cyber_threat_intel/047-t1003-001.md**\n\n> # LSASS Memory\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1003.001\nSTIX ID: attack-pattern--65f2d882-3f41-4d48-8a06-29af77ec9f90\n\nDescription:\nAdversaries may attempt to access credential material \n\n**5. cyber_threat_intel/048-t1003-002.md**\n\n> # Security Account Manager\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1003.002\nSTIX ID: attack-pattern--1644e709-12d2-41e5-a60f-3470991f5011\n\nDescription:\nAdversaries may attempt to extract credent\n\n</details>\n\n---\n📊 10.7s · 5 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the provided context, it is not possible to trace a relationship path involving **Cleaver** because there is no mention of \"Cleaver\" in the text.\n\nHowever, regarding the other entities:\n*   **Carbanak** (S0030) uses **OS Credential Dumping** (T1003).\n*   **Mimikatz** (S0002) is a credential dumper that uses techniques such as **Security Account Manager** (T1003.002) and **LSASS Memory** (via the description of LSASS Memory dumping which mentions Mimikatz, though the direct relation in [3] lists other techniques, [4] explicitly states mimikatz can be run on LSASS dumps).\n*   **Windows Credential Editor** is a password dumping tool that uses **LSASS Memory** (T1003.001).\n\nThe actors and software mentioned in the context that converge on credential access (specifically OS Credential Dumping or its sub-techniques like LSASS Memory) include:\n*   **APT39** (uses OS Credential Dumping and Windows Credential Editor)\n*   **FIN5** (uses Windows Credential Editor)\n*   **GALLIUM** (uses Windows Credential Editor and Security Account Manager)\n*   **Threat Group-3390** (uses Windows Credential Editor)\n*   **BRONZE BUTLER** (uses Windows Credential Editor and Mimikatz)\n*   **Ember Bear** (uses OS Credential Dumping)\n*   **MgBot** (uses OS Credential Dumping)\n*   **Revenge RAT** (uses OS Credential Dumping)\n*   **PinchDuke** (uses OS Credential Dumping)\n*   **Poseidon Group** (uses OS Credential Dumping)\n*   **OnionDuke** (uses OS Credential Dumping)\n*   **Mustang Panda** (uses OS Credential Dumping)\n*   **APT32** (uses Mimikatz)\n*   **APT29** (uses Mimikatz and Security Account Manager)\n*   **Earth Lusca** (uses Mimikatz)\n*   **FIN7** (uses Mimikatz)\n*   **DarkHydrus** (uses Mimikatz)\n*   **TA505** (uses Mimikatz)\n*   **Agrius** (uses Mimikatz)\n*   **Operation Wocao** (uses Mimikatz)\n*   **Sandworm Team** (uses Mimikatz)\n*   **APT33** (uses Mimikatz)\n*   **Akira** (uses Mimikatz)\n*   **Daggerfly** (uses Security Account Manager)\n*   **CrackMapExec** (uses Security Account Manager)\n*   **gsecdump** (uses Security Account Manager)\n*   **FrostyGoop Incident** (uses Security Account Manager)\n*   **Koadic** (uses Security Account Manager)\n*   **FIN13** (uses Security Account Manager)\n*   **MirrorFace** (uses Security Account Manager)\n*   **C0017** (uses Security Account Manager)\n*   **pwdump** (uses Security Account Manager)",
      "sources": [
        {
          "title": "cyber_threat_intel/032-s0005.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/046-t1003.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/031-s0002.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/047-t1003-001.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/048-t1003-002.md",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 10.660091629000817,
        "chunks": 5,
        "llm_calls": 2,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_credential_access_path",
      "model": "hybrid-rag",
      "base_model": "hybrid-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 20.7,
      "raw": "Based on the provided context, the following actors and software converge on credential access techniques:\n\n**Actors (Intrusion Sets) Converging on Credential Access:**\n*   **Cleaver (G0003):** Uses LSASS Memory (T1003.001).\n*   **Carbanak (G0008):** Uses Mimikatz (S0002) and PsExec (S0029) (often associated with credential access/lateral movement, though the text explicitly links Carbanak to Mimikatz).\n\n**Software/Tools Converging on Credential Access:**\n*   **Mimikatz (S0002):** Used by Cleaver and Carbanak.\n*   **Windows Credential Editor (S0005):** A password dumping tool that uses LSASS Memory (T1003.001). It is used by Leviathan, FIN5, APT39, FIN6, GALLIUM, Threat Group-3390, and BRONZE BUTLER.\n*   **LSASS Memory (T1003.001):** A technique for OS Credential Dumping. It is used by Cleaver and Windows Credential Editor.\n\n**Convergence Summary:**\n*   **Cleaver** and **Carbanak** both utilize **Mimikatz**.\n*   **Cleaver** utilizes the **LSASS Memory** technique, which is also utilized by **Windows Credential Editor**.\n*   Therefore, **Cleaver**, **Carbanak**, and **Windows Credential Editor** (along with other actors like FIN5, APT39, etc., who use Windows Credential Editor) converge on credential access via **Mimikatz** or the **LSASS Memory** technique.\n\n<details><summary>🔎 Retrieved context (5 sources)</summary>\n\n**1. cyber_threat_intel/003-g0003.md** · score 0.067\n\n> # Cleaver\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: intrusion-set\nATT&CK ID: G0003\nSTIX ID: intrusion-set--8f5e8dc7-739d-4f5e-a8a1-a66e004d7063\n\nDescription:\n[Cleaver](https://attack.mitre.org/groups/G0003) is a threat grou\n\n**2. cyber_threat_intel/008-g0008.md** · score 0.024\n\n> # Carbanak\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: intrusion-set\nATT&CK ID: G0008\nSTIX ID: intrusion-set--55033a4d-3ffe-46b2-99b4-2c1541e9ce1c\n\nDescription:\n[Carbanak](https://attack.mitre.org/groups/G0008) is a cybercrim\n\n**3. cyber_threat_intel/032-s0005.md** · score 0.019\n\n> # Windows Credential Editor\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: tool\nATT&CK ID: S0005\nSTIX ID: tool--242f3da3-4425-4d11-8f5c-b842886da966\n\nDescription:\n[Windows Credential Editor](https://attack.mitre.org/software/S00\n\n**4. cyber_threat_intel/046-t1003.md** · score 0.019\n\n> # OS Credential Dumping\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1003\nSTIX ID: attack-pattern--0a3ead4e-6d47-4ccb-854c-a6a4f9d96b22\n\nDescription:\nAdversaries may attempt to dump credentials to ob\n\n**5. cyber_threat_intel/055-m1018.md** · score 0.016\n\n> # User Account Management\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1018\nSTIX ID: course-of-action--93e7968a-9074-4eac-8ae9-9f5200ec3317\n\nDescription:\nUser Account Management involves implementi\n\n</details>\n\n---\n📊 20.6s · 5 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the provided context, the following actors and software converge on credential access techniques:\n\n**Actors (Intrusion Sets) Converging on Credential Access:**\n*   **Cleaver (G0003):** Uses LSASS Memory (T1003.001).\n*   **Carbanak (G0008):** Uses Mimikatz (S0002) and PsExec (S0029) (often associated with credential access/lateral movement, though the text explicitly links Carbanak to Mimikatz).\n\n**Software/Tools Converging on Credential Access:**\n*   **Mimikatz (S0002):** Used by Cleaver and Carbanak.\n*   **Windows Credential Editor (S0005):** A password dumping tool that uses LSASS Memory (T1003.001). It is used by Leviathan, FIN5, APT39, FIN6, GALLIUM, Threat Group-3390, and BRONZE BUTLER.\n*   **LSASS Memory (T1003.001):** A technique for OS Credential Dumping. It is used by Cleaver and Windows Credential Editor.\n\n**Convergence Summary:**\n*   **Cleaver** and **Carbanak** both utilize **Mimikatz**.\n*   **Cleaver** utilizes the **LSASS Memory** technique, which is also utilized by **Windows Credential Editor**.\n*   Therefore, **Cleaver**, **Carbanak**, and **Windows Credential Editor** (along with other actors like FIN5, APT39, etc., who use Windows Credential Editor) converge on credential access via **Mimikatz** or the **LSASS Memory** technique.",
      "sources": [
        {
          "title": "cyber_threat_intel/003-g0003.md",
          "score": 0.067067936
        },
        {
          "title": "cyber_threat_intel/008-g0008.md",
          "score": 0.02384409
        },
        {
          "title": "cyber_threat_intel/032-s0005.md",
          "score": 0.01936531
        },
        {
          "title": "cyber_threat_intel/046-t1003.md",
          "score": 0.019099804
        },
        {
          "title": "cyber_threat_intel/055-m1018.md",
          "score": 0.016000608
        }
      ],
      "metrics": {
        "seconds": 20.577700843001367,
        "chunks": 5,
        "llm_calls": 2,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_credential_access_path",
      "model": "contextual-rag",
      "base_model": "contextual-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 26.1,
      "raw": "Based on the provided context, the following actors and software converge on credential access via **LSASS Memory** (T1003.001) or tools that utilize it:\n\n**Actors converging on LSASS Memory:**\n*   Cleaver (G0003)\n*   Carbanak (G0008) [Note: While Carbanak is not explicitly listed as using LSASS Memory in the provided text, it uses Mimikatz. However, looking strictly at the \"LSASS Memory\" list in [2], Cleaver is listed. Carbanak is not listed in [2]. Let's re-read carefully.]\n\nLet's trace the specific paths for each entity mentioned in the question:\n\n1.  **Cleaver**:\n    *   Directly uses **LSASS Memory** (T1003.001) [Source: [1], [2]].\n    *   Uses **Mimikatz** (S0002) [Source: [1]].\n\n2.  **Carbanak**:\n    *   Uses **Mimikatz** (S0002) [Source: [5]].\n    *   *Note*: Carbanak is not explicitly listed as using LSASS Memory in the provided text, nor is it listed as using Windows Credential Editor.\n\n3.  **Mimikatz**:\n    *   Used by **Cleaver** (G0003) [Source: [1]].\n    *   Used by **Carbanak** (G0008) [Source: [5]].\n    *   *Note*: The text does not explicitly state that Mimikatz uses LSASS Memory, but it is a known credential access tool. However, based *only* on the provided context, we know Cleaver and Carbanak use it.\n\n4.  **Windows Credential Editor**:\n    *   Uses **LSASS Memory** (T1003.001) [Source: [3]].\n    *   Used by: Leviathan, FIN5, APT39, FIN6, GALLIUM, Threat Group-3390, BRONZE BUTLER.\n    *   *Note*: Cleaver and Carbanak are **not** listed as users of Windows Credential Editor in the provided text.\n\n5.  **LSASS Memory**:\n    *   Used by: Indrik Spider, Operation Wocao, OilRig, **Cleaver**, Leafminer, Threat Group-3390, SILENTTRINITY, APT1, Cutting Edge, Leviathan, FIN8, LaZagne [Source: [2]].\n    *   Used by tool: **Windows Credential Editor** [Source: [3]].\n\n**Convergence on Credential Access:**\n\n*   **Cleaver** converges on credential access via two paths in the text:\n    1.  Directly using **LSASS Memory**.\n    2.  Using **Mimikatz**.\n*   **Carbanak** converges on credential access via:\n    1.  Using **Mimikatz**.\n*   **Windows Credential Editor** is a tool that uses **LSASS Memory** for credential theft, but neither Cleaver nor Carbanak are listed as users of this specific tool in the provided context.\n\nTherefore, the actors and software that converge on credential access (specifically via LSASS Memory or Mimikatz) according to the text are:\n*   **Cleaver** (uses LSASS Memory and Mimikatz)\n*   **Carbanak** (uses Mimikatz)\n*   **Windows Credential Editor** (uses LSASS Memory)\n\nThe specific convergence points are:\n*   **LSASS Memory**: Used by Cleaver and Windows Credential Editor.\n*   **Mimikatz**: Used by Cleaver and Carbanak.\n\n<details><summary>🔎 Retrieved context (5 sources)</summary>\n\n**1. cyber_threat_intel/003-g0003.md** · score 0.093\n\n> This text provides a detailed profile of the Cleaver threat group, including its attribution to Iranian actors and its association with Operation Cleaver. It further lists specific techniques and tools utilized by the group as documented in\n\n**2. cyber_threat_intel/047-t1003-001.md** · score 0.047\n\n> The following list identifies specific threat actors and tools that utilize the LSASS Memory technique for credential harvesting. These entities are linked to the T1003.001 attack pattern as part of their operational methods.\n\n- Indrik Spid\n\n**3. cyber_threat_intel/032-s0005.md** · score 0.039\n\n> This section details the Windows Credential Editor, a password dumping tool identified by MITRE ATT&CK ID S0005. It outlines the tool's technical capabilities and lists specific threat groups that utilize this software for credential theft.\n\n**4. cyber_threat_intel/052-m1015.md** · score 0.037\n\n> This section details specific implementation measures for Active Directory Configuration, including account settings, logon restrictions, and authentication silos, while listing associated mitigation relations for various MITRE ATT&CK techn\n\n**5. cyber_threat_intel/008-g0008.md** · score 0.034\n\n> This section details the Carbanak intrusion set, identified by ATT&CK ID G0008, which is a cybercriminal group known for targeting financial institutions using specific malware and tactics. It lists the technical relations and techniques as\n\n</details>\n\n---\n📊 26.1s · 5 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the provided context, the following actors and software converge on credential access via **LSASS Memory** (T1003.001) or tools that utilize it:\n\n**Actors converging on LSASS Memory:**\n*   Cleaver (G0003)\n*   Carbanak (G0008) [Note: While Carbanak is not explicitly listed as using LSASS Memory in the provided text, it uses Mimikatz. However, looking strictly at the \"LSASS Memory\" list in [2], Cleaver is listed. Carbanak is not listed in [2]. Let's re-read carefully.]\n\nLet's trace the specific paths for each entity mentioned in the question:\n\n1.  **Cleaver**:\n    *   Directly uses **LSASS Memory** (T1003.001) [Source: [1], [2]].\n    *   Uses **Mimikatz** (S0002) [Source: [1]].\n\n2.  **Carbanak**:\n    *   Uses **Mimikatz** (S0002) [Source: [5]].\n    *   *Note*: Carbanak is not explicitly listed as using LSASS Memory in the provided text, nor is it listed as using Windows Credential Editor.\n\n3.  **Mimikatz**:\n    *   Used by **Cleaver** (G0003) [Source: [1]].\n    *   Used by **Carbanak** (G0008) [Source: [5]].\n    *   *Note*: The text does not explicitly state that Mimikatz uses LSASS Memory, but it is a known credential access tool. However, based *only* on the provided context, we know Cleaver and Carbanak use it.\n\n4.  **Windows Credential Editor**:\n    *   Uses **LSASS Memory** (T1003.001) [Source: [3]].\n    *   Used by: Leviathan, FIN5, APT39, FIN6, GALLIUM, Threat Group-3390, BRONZE BUTLER.\n    *   *Note*: Cleaver and Carbanak are **not** listed as users of Windows Credential Editor in the provided text.\n\n5.  **LSASS Memory**:\n    *   Used by: Indrik Spider, Operation Wocao, OilRig, **Cleaver**, Leafminer, Threat Group-3390, SILENTTRINITY, APT1, Cutting Edge, Leviathan, FIN8, LaZagne [Source: [2]].\n    *   Used by tool: **Windows Credential Editor** [Source: [3]].\n\n**Convergence on Credential Access:**\n\n*   **Cleaver** converges on credential access via two paths in the text:\n    1.  Directly using **LSASS Memory**.\n    2.  Using **Mimikatz**.\n*   **Carbanak** converges on credential access via:\n    1.  Using **Mimikatz**.\n*   **Windows Credential Editor** is a tool that uses **LSASS Memory** for credential theft, but neither Cleaver nor Carbanak are listed as users of this specific tool in the provided context.\n\nTherefore, the actors and software that converge on credential access (specifically via LSASS Memory or Mimikatz) according to the text are:\n*   **Cleaver** (uses LSASS Memory and Mimikatz)\n*   **Carbanak** (uses Mimikatz)\n*   **Windows Credential Editor** (uses LSASS Memory)\n\nThe specific convergence points are:\n*   **LSASS Memory**: Used by Cleaver and Windows Credential Editor.\n*   **Mimikatz**: Used by Cleaver and Carbanak.",
      "sources": [
        {
          "title": "cyber_threat_intel/003-g0003.md",
          "score": 0.09274174
        },
        {
          "title": "cyber_threat_intel/047-t1003-001.md",
          "score": 0.04682535
        },
        {
          "title": "cyber_threat_intel/032-s0005.md",
          "score": 0.0387973
        },
        {
          "title": "cyber_threat_intel/052-m1015.md",
          "score": 0.03672482
        },
        {
          "title": "cyber_threat_intel/008-g0008.md",
          "score": 0.033600606
        }
      ],
      "metrics": {
        "seconds": 26.11162842900012,
        "chunks": 5,
        "llm_calls": 2,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_credential_access_path",
      "model": "graph-rag",
      "base_model": "graph-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 20.8,
      "raw": "Based on the provided knowledge graph and document chunks, here is the synthesis of the relationship paths regarding credential access techniques, tools, and actors.\n\n### Convergence on Credential Access\n\nThe threat landscape demonstrates a clear convergence where specific adversaries (actors) utilize specific software (tools) to exploit specific operating system mechanisms (techniques) for credential harvesting. The path flows from **Actors** $\\rightarrow$ **Tools/Software** $\\rightarrow$ **Techniques/Mechanisms** $\\rightarrow$ **Credential Materials**.\n\n#### 1. The Actors (Adversaries)\nTwo primary threat groups are highlighted in the context regarding their involvement in credential dumping operations:\n*   **Cleaver (G0003):** An adversary group attributed to Iranian actors [KG Data] [Doc Chunk 4].\n*   **Carbanak:** A cybercriminal group that has targeted financial institutions since at least 2013 and uses OS Credential Dumping techniques [KG Data] [Doc Chunk 2].\n\n#### 2. The Software (Tools)\nThese actors converge on two primary tools for credential extraction:\n*   **Mimikatz:** A widely used post-exploitation tool capable of extracting plaintext passwords, hashes, PIN codes, and Kerberos tickets from memory. It is described as a \"credential dumper capable of obtaining plaintext Windows account logins and passwords\" [Doc Chunk 3].\n*   **Windows Credential Editor:** A specialized password dumping tool utilized by adversaries to harvest credentials [Doc Chunk 1].\n\n**Relationships between Actors and Tools:**\n*   **Cleaver** employs both **Mimikatz** and the **LSASS Memory** technique [KG Data] [Doc Chunk 4].\n*   **Carbanak** uses **Mimikatz** to extract credentials from memory [KG Data] [Doc Chunk 3]. Note: While Carbanak is listed as using Windows Credential Editor in one KG relationship entry, the document chunks explicitly link Carbanak to OS Credential Dumping and Mimikatz usage. The KG data confirms Carbanak uses Mimikatz (S0002) [KG Data].\n\n#### 3. The Mechanisms (Techniques & Memory)\nThe software tools exploit specific Windows security subsystems:\n*   **LSASS Memory (T1003.001):** This is the primary technique identified. It involves accessing credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS). After a user logs on, LSASS generates and stores various credential materials that can be harvested [Doc Chunk 4].\n    *   **Windows Credential Editor** uses **LSASS Memory** for credential dumping [KG Data] [Doc Chunk 1].\n    *   **Cleaver** employs the **LSASS Memory** technique [KG Data] [Doc Chunk 4].\n*   **Mimikatz's Interaction with Memory:** Mimikatz can be run locally to analyze dumped LSASS process memory to extract logon passwords. It utilizes in-memory techniques to retrieve credential material, such as the Security Account Manager (SAM) database and LSA secrets [KG Data] [Doc Chunk 4].\n    *   Specifically, Mimikatz uses **Security Support Provider (SSP)** DLLs, which are loaded into the LSASS process at system start, granting access to encrypted and plaintext passwords stored in Windows [Doc Chunk 4].\n\n#### 4. The Target (Credential Materials)\nThe ultimate object of this convergence is **Credential Materials**. These include:\n*   Plaintext passwords.\n*   Password hashes.\n*   Smart card PINs.\n*   Kerberos tickets.\n\nThese materials are stored in the LSASS process memory and can be harvested to conduct **Lateral Movement** using alternate authentication material [Doc Chunk 4] [KG Data].\n\n### Summary of Convergence Paths\n\n1.  **Cleaver Path:**\n    *   Cleaver $\\rightarrow$ Uses Mimikatz [KG Data].\n    *   Cleaver $\\rightarrow$ Uses LSASS Memory technique [KG Data].\n    *   Mimikatz $\\rightarrow$ Analyzes/Extracts from LSASS Memory [KG Data] [Doc Chunk 4].\n\n2.  **Carbanak Path:**\n    *   Carbanak $\\rightarrow$ Uses OS Credential Dumping [Doc Chunk 2].\n    *   Carbanak $\\rightarrow$ Uses Mimikatz [KG Data].\n    *   Mimikatz $\\rightarrow$ Extracts from Memory/SAM (Components of LSASS/OS Credential Dumping) [KG Data] [Doc Chunk 5].\n\n3.  **Tool Mechanism Path:**\n    *   Windows Credential Editor $\\rightarrow$ Uses LSASS Memory [KG Data].\n    *   Mimikatz $\\rightarrow$ Uses Security Support Provider (loaded in LSASS) [KG Data] [Doc Chunk 4].\n\n**Conclusion:**\nThe actors **Cleaver** and **Carbanak** converge on the software tools **Mimikatz** and **Windows Credential Editor**. These tools, in turn, exploit the **LSASS Memory** mechanism to harvest **Credential Materials**. This illustrates a common threat pattern where diverse adversaries leverage well-known, powerful open-source or public-domain tools (like Mimikatz) to access sensitive data stored in core Windows security subsystems (LSASS).\n\n### References\n\n- [1] Windows Credential Editor\n- [2] OS Credential Dumping\n- [3] Mimikatz\n- [4] LSASS Memory\n- [5] Security Account Manager\n\n<details><summary>🔎 Retrieved context (1 source)</summary>\n\n**1. LightRAG knowledge graph**\n\n> Graph + vector dual retrieval (profile=graph-rag) over the corpus's extracted entities and relations.\n\n</details>\n\n---\n📊 20.8s · 0 chunks · 1 LLM call · 0 cloud",
      "answer": "Based on the provided knowledge graph and document chunks, here is the synthesis of the relationship paths regarding credential access techniques, tools, and actors.\n\n### Convergence on Credential Access\n\nThe threat landscape demonstrates a clear convergence where specific adversaries (actors) utilize specific software (tools) to exploit specific operating system mechanisms (techniques) for credential harvesting. The path flows from **Actors** $\\rightarrow$ **Tools/Software** $\\rightarrow$ **Techniques/Mechanisms** $\\rightarrow$ **Credential Materials**.\n\n#### 1. The Actors (Adversaries)\nTwo primary threat groups are highlighted in the context regarding their involvement in credential dumping operations:\n*   **Cleaver (G0003):** An adversary group attributed to Iranian actors [KG Data] [Doc Chunk 4].\n*   **Carbanak:** A cybercriminal group that has targeted financial institutions since at least 2013 and uses OS Credential Dumping techniques [KG Data] [Doc Chunk 2].\n\n#### 2. The Software (Tools)\nThese actors converge on two primary tools for credential extraction:\n*   **Mimikatz:** A widely used post-exploitation tool capable of extracting plaintext passwords, hashes, PIN codes, and Kerberos tickets from memory. It is described as a \"credential dumper capable of obtaining plaintext Windows account logins and passwords\" [Doc Chunk 3].\n*   **Windows Credential Editor:** A specialized password dumping tool utilized by adversaries to harvest credentials [Doc Chunk 1].\n\n**Relationships between Actors and Tools:**\n*   **Cleaver** employs both **Mimikatz** and the **LSASS Memory** technique [KG Data] [Doc Chunk 4].\n*   **Carbanak** uses **Mimikatz** to extract credentials from memory [KG Data] [Doc Chunk 3]. Note: While Carbanak is listed as using Windows Credential Editor in one KG relationship entry, the document chunks explicitly link Carbanak to OS Credential Dumping and Mimikatz usage. The KG data confirms Carbanak uses Mimikatz (S0002) [KG Data].\n\n#### 3. The Mechanisms (Techniques & Memory)\nThe software tools exploit specific Windows security subsystems:\n*   **LSASS Memory (T1003.001):** This is the primary technique identified. It involves accessing credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS). After a user logs on, LSASS generates and stores various credential materials that can be harvested [Doc Chunk 4].\n    *   **Windows Credential Editor** uses **LSASS Memory** for credential dumping [KG Data] [Doc Chunk 1].\n    *   **Cleaver** employs the **LSASS Memory** technique [KG Data] [Doc Chunk 4].\n*   **Mimikatz's Interaction with Memory:** Mimikatz can be run locally to analyze dumped LSASS process memory to extract logon passwords. It utilizes in-memory techniques to retrieve credential material, such as the Security Account Manager (SAM) database and LSA secrets [KG Data] [Doc Chunk 4].\n    *   Specifically, Mimikatz uses **Security Support Provider (SSP)** DLLs, which are loaded into the LSASS process at system start, granting access to encrypted and plaintext passwords stored in Windows [Doc Chunk 4].\n\n#### 4. The Target (Credential Materials)\nThe ultimate object of this convergence is **Credential Materials**. These include:\n*   Plaintext passwords.\n*   Password hashes.\n*   Smart card PINs.\n*   Kerberos tickets.\n\nThese materials are stored in the LSASS process memory and can be harvested to conduct **Lateral Movement** using alternate authentication material [Doc Chunk 4] [KG Data].\n\n### Summary of Convergence Paths\n\n1.  **Cleaver Path:**\n    *   Cleaver $\\rightarrow$ Uses Mimikatz [KG Data].\n    *   Cleaver $\\rightarrow$ Uses LSASS Memory technique [KG Data].\n    *   Mimikatz $\\rightarrow$ Analyzes/Extracts from LSASS Memory [KG Data] [Doc Chunk 4].\n\n2.  **Carbanak Path:**\n    *   Carbanak $\\rightarrow$ Uses OS Credential Dumping [Doc Chunk 2].\n    *   Carbanak $\\rightarrow$ Uses Mimikatz [KG Data].\n    *   Mimikatz $\\rightarrow$ Extracts from Memory/SAM (Components of LSASS/OS Credential Dumping) [KG Data] [Doc Chunk 5].\n\n3.  **Tool Mechanism Path:**\n    *   Windows Credential Editor $\\rightarrow$ Uses LSASS Memory [KG Data].\n    *   Mimikatz $\\rightarrow$ Uses Security Support Provider (loaded in LSASS) [KG Data] [Doc Chunk 4].\n\n**Conclusion:**\nThe actors **Cleaver** and **Carbanak** converge on the software tools **Mimikatz** and **Windows Credential Editor**. These tools, in turn, exploit the **LSASS Memory** mechanism to harvest **Credential Materials**. This illustrates a common threat pattern where diverse adversaries leverage well-known, powerful open-source or public-domain tools (like Mimikatz) to access sensitive data stored in core Windows security subsystems (LSASS).\n\n### References\n\n- [1] Windows Credential Editor\n- [2] OS Credential Dumping\n- [3] Mimikatz\n- [4] LSASS Memory\n- [5] Security Account Manager",
      "sources": [
        {
          "title": "LightRAG knowledge graph",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 20.813574300002074,
        "chunks": 0,
        "llm_calls": 1,
        "cloud_calls": 0
      },
      "approach_metadata": {
        "lightrag": {
          "query_profile": "graph-rag"
        }
      }
    },
    {
      "query_id": "cyber_credential_access_path",
      "model": "agentic-rag",
      "base_model": "agentic-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 29.2,
      "raw": "Based on the knowledge graph and document analysis, here is the traced relationship path and convergence of actors and software on credential access:\n\n### Relationship Path Trace\n\nThe core convergence point for all these entities is **LSASS Memory** (Local Security Authority Subsystem Service), which stores credential material in process memory. The relationships are structured as follows:\n\n1.  **Cleaver**\n    *   **Actor:** Iranian-linked threat group.\n    *   **Tool Used:** **Mimikatz**.\n    *   **Target/Technique:** Uses Mimikatz to dump and analyze **LSASS Memory** for credential extraction and lateral movement.\n\n2.  **Carbanak**\n    *   **Actor:** Cybercriminal group targeting financial institutions.\n    *   **Tool Used:** **Mimikatz**.\n    *   **Target/Technique:** Uses Mimikatz to extract credentials from memory (including LSASS) for further access.\n\n3.  **Mimikatz**\n    *   **Software:** A post-exploitation tool.\n    *   **Function:** Extracts plaintext passwords, hashes, and Kerberos tickets from memory.\n    *   **Convergence:** It is the primary software bridge used by both **Cleaver** and **Carbanak** to exploit **LSASS Memory**.\n\n4.  **Windows Credential Editor**\n    *   **Software:** An alternative credential dumping tool.\n    *   **Target/Technique:** Also exploits **LSASS Memory** for password dumping.\n    *   **Convergence:** While it shares the same target (LSASS) as Mimikatz, it is used by a different set of actors (e.g., Leviathan, FIN5, APT39), not Cleaver or Carbanak in this context.\n\n### Actors and Software Converging on Credential Access\n\nThe following actors and software converge on the goal of **credential access** via **LSASS Memory**:\n\n*   **Actors:**\n    *   **Cleaver:** Uses Mimikatz to access LSASS Memory.\n    *   **Carbanak:** Uses Mimikatz to access LSASS Memory.\n    *   **Leviathan, FIN5, APT39, FIN6, GALLIUM, Threat Group-3390, BRONZE BUTLER:** Use Windows Credential Editor to access LSASS Memory.\n\n*   **Software/Tools:**\n    *   **Mimikatz:** The primary tool used by Cleaver and Carbanak (and many other APTs) to dump credentials from LSASS Memory.\n    *   **Windows Credential Editor:** An alternative tool used by other threat groups to achieve the same credential access via LSASS Memory.\n\n*   **Target/Technique:**\n    *   **LSASS Memory:** The common data source exploited by both Mimikatz and Windows Credential Editor to harvest credentials for lateral movement and unauthorized access.\n\nIn summary, **Mimikatz** is the key software converging **Cleaver** and **Carbanak** on **LSASS Memory** for credential access. **Windows Credential Editor** represents a parallel path used by other actors to achieve the same objective via the same target.\n\n<details><summary>🔎 Retrieved context (1 source)</summary>\n\n**1. 🤖 Agent trace**\n\n> **Step 1.** **Action:** `query_graph(Trace the relationship path between Cleaver, Carbanak, Mimikatz, Windows Credential Editor, and LSASS Memory. Identify which actors and software converge on credential access techniques involving these components.)`\n\n**Observation:** Based on the provided knowledge graph and document chunks, the relationships between Cleaver, Carbanak, Mimikatz, Windows Credential Editor, and LSASS Memory can be traced through specific threat actors and their operational tools for credential extraction and lateral movement.\n\n### Convergence of A\n\n</details>\n\n---\n📊 29.2s · 0 chunks · 3 LLM calls · 0 cloud",
      "answer": "Based on the knowledge graph and document analysis, here is the traced relationship path and convergence of actors and software on credential access:\n\n### Relationship Path Trace\n\nThe core convergence point for all these entities is **LSASS Memory** (Local Security Authority Subsystem Service), which stores credential material in process memory. The relationships are structured as follows:\n\n1.  **Cleaver**\n    *   **Actor:** Iranian-linked threat group.\n    *   **Tool Used:** **Mimikatz**.\n    *   **Target/Technique:** Uses Mimikatz to dump and analyze **LSASS Memory** for credential extraction and lateral movement.\n\n2.  **Carbanak**\n    *   **Actor:** Cybercriminal group targeting financial institutions.\n    *   **Tool Used:** **Mimikatz**.\n    *   **Target/Technique:** Uses Mimikatz to extract credentials from memory (including LSASS) for further access.\n\n3.  **Mimikatz**\n    *   **Software:** A post-exploitation tool.\n    *   **Function:** Extracts plaintext passwords, hashes, and Kerberos tickets from memory.\n    *   **Convergence:** It is the primary software bridge used by both **Cleaver** and **Carbanak** to exploit **LSASS Memory**.\n\n4.  **Windows Credential Editor**\n    *   **Software:** An alternative credential dumping tool.\n    *   **Target/Technique:** Also exploits **LSASS Memory** for password dumping.\n    *   **Convergence:** While it shares the same target (LSASS) as Mimikatz, it is used by a different set of actors (e.g., Leviathan, FIN5, APT39), not Cleaver or Carbanak in this context.\n\n### Actors and Software Converging on Credential Access\n\nThe following actors and software converge on the goal of **credential access** via **LSASS Memory**:\n\n*   **Actors:**\n    *   **Cleaver:** Uses Mimikatz to access LSASS Memory.\n    *   **Carbanak:** Uses Mimikatz to access LSASS Memory.\n    *   **Leviathan, FIN5, APT39, FIN6, GALLIUM, Threat Group-3390, BRONZE BUTLER:** Use Windows Credential Editor to access LSASS Memory.\n\n*   **Software/Tools:**\n    *   **Mimikatz:** The primary tool used by Cleaver and Carbanak (and many other APTs) to dump credentials from LSASS Memory.\n    *   **Windows Credential Editor:** An alternative tool used by other threat groups to achieve the same credential access via LSASS Memory.\n\n*   **Target/Technique:**\n    *   **LSASS Memory:** The common data source exploited by both Mimikatz and Windows Credential Editor to harvest credentials for lateral movement and unauthorized access.\n\nIn summary, **Mimikatz** is the key software converging **Cleaver** and **Carbanak** on **LSASS Memory** for credential access. **Windows Credential Editor** represents a parallel path used by other actors to achieve the same objective via the same target.",
      "sources": [
        {
          "title": "🤖 Agent trace",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 29.17854767999961,
        "chunks": 0,
        "llm_calls": 3,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_credential_access_path",
      "model": "n8n-adaptive-rag",
      "base_model": "n8n-adaptive-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 10.7,
      "raw": "Based on the knowledge graph and document analysis, here is the traced relationship path and convergence of actors and software on credential access:\n\n### Relationship Path Trace\n\nThe core convergence point for all these entities is **LSASS Memory** (Local Security Authority Subsystem Service), which stores credential material in process memory. The relationships are structured as follows:\n\n1.  **Cleaver**\n    *   **Actor:** Iranian-linked threat group.\n    *   **Tool Used:** **Mimikatz**.\n    *   **Target/Technique:** Uses Mimikatz to dump and analyze **LSASS Memory** for credential extraction and lateral movement.\n\n2.  **Carbanak**\n    *   **Actor:** Cybercriminal group targeting financial institutions.\n    *   **Tool Used:** **Mimikatz**.\n    *   **Target/Technique:** Uses Mimikatz to extract credentials from memory (including LSASS) for further access.\n\n3.  **Mimikatz**\n    *   **Software:** A post-exploitation tool.\n    *   **Function:** Extracts plaintext passwords, hashes, and Kerberos tickets from memory.\n    *   **Convergence:** It is the primary software bridge used by both **Cleaver** and **Carbanak** to exploit **LSASS Memory**.\n\n4.  **Windows Credential Editor**\n    *   **Software:** An alternative credential dumping tool.\n    *   **Target/Technique:** Also exploits **LSASS Memory** for password dumping.\n    *   **Convergence:** While it shares the same target (LSASS) as Mimikatz, it is used by a different set of actors (e.g., Leviathan, FIN5, APT39), not Cleaver or Carbanak in this context.\n\n### Actors and Software Converging on Credential Access\n\nThe following actors and software converge on the goal of **credential access** via **LSASS Memory**:\n\n*   **Actors:**\n    *   **Cleaver:** Uses Mimikatz to access LSASS Memory.\n    *   **Carbanak:** Uses Mimikatz to access LSASS Memory.\n    *   **Leviathan, FIN5, APT39, FIN6, GALLIUM, Threat Group-3390, BRONZE BUTLER:** Use Windows Credential Editor to access LSASS Memory.\n\n*   **Software/Tools:**\n    *   **Mimikatz:** The primary tool used by Cleaver and Carbanak (and many other APTs) to dump credentials from LSASS Memory.\n    *   **Windows Credential Editor:** An alternative tool used by other threat groups to achieve the same credential access via LSASS Memory.\n\n*   **Target/Technique:**\n    *   **LSASS Memory:** The common data source exploited by both Mimikatz and Windows Credential Editor to harvest credentials for lateral movement and unauthorized access.\n\nIn summary, **Mimikatz** is the key software converging **Cleaver** and **Carbanak** on **LSASS Memory** for credential access. **Windows Credential Editor** represents a parallel path used by other actors to achieve the same objective via the same target.\n\n<details><summary>🔎 Retrieved context (1 source)</summary>\n\n**1. 🤖 Agent trace**\n\n> **Step 1.** **Action:** `query_graph(Trace the relationship path between Cleaver, Carbanak, Mimikatz, Windows Credential Editor, and LSASS Memory. Identify which actors and software converge on credential access techniques involving these components.)`\n\n**Observation:** Based on the provided knowledge graph and document chunks, the relationships between Cleaver, Carbanak, Mimikatz, Windows Credential Editor, and LSASS Memory can be traced through specific threat actors and their operational tools for credential extraction and lateral movement.\n\n### Convergence of A\n\n</details>\n\n---\n📊 10.7s · 0 chunks · 4 LLM calls · 0 cloud",
      "answer": "Based on the knowledge graph and document analysis, here is the traced relationship path and convergence of actors and software on credential access:\n\n### Relationship Path Trace\n\nThe core convergence point for all these entities is **LSASS Memory** (Local Security Authority Subsystem Service), which stores credential material in process memory. The relationships are structured as follows:\n\n1.  **Cleaver**\n    *   **Actor:** Iranian-linked threat group.\n    *   **Tool Used:** **Mimikatz**.\n    *   **Target/Technique:** Uses Mimikatz to dump and analyze **LSASS Memory** for credential extraction and lateral movement.\n\n2.  **Carbanak**\n    *   **Actor:** Cybercriminal group targeting financial institutions.\n    *   **Tool Used:** **Mimikatz**.\n    *   **Target/Technique:** Uses Mimikatz to extract credentials from memory (including LSASS) for further access.\n\n3.  **Mimikatz**\n    *   **Software:** A post-exploitation tool.\n    *   **Function:** Extracts plaintext passwords, hashes, and Kerberos tickets from memory.\n    *   **Convergence:** It is the primary software bridge used by both **Cleaver** and **Carbanak** to exploit **LSASS Memory**.\n\n4.  **Windows Credential Editor**\n    *   **Software:** An alternative credential dumping tool.\n    *   **Target/Technique:** Also exploits **LSASS Memory** for password dumping.\n    *   **Convergence:** While it shares the same target (LSASS) as Mimikatz, it is used by a different set of actors (e.g., Leviathan, FIN5, APT39), not Cleaver or Carbanak in this context.\n\n### Actors and Software Converging on Credential Access\n\nThe following actors and software converge on the goal of **credential access** via **LSASS Memory**:\n\n*   **Actors:**\n    *   **Cleaver:** Uses Mimikatz to access LSASS Memory.\n    *   **Carbanak:** Uses Mimikatz to access LSASS Memory.\n    *   **Leviathan, FIN5, APT39, FIN6, GALLIUM, Threat Group-3390, BRONZE BUTLER:** Use Windows Credential Editor to access LSASS Memory.\n\n*   **Software/Tools:**\n    *   **Mimikatz:** The primary tool used by Cleaver and Carbanak (and many other APTs) to dump credentials from LSASS Memory.\n    *   **Windows Credential Editor:** An alternative tool used by other threat groups to achieve the same credential access via LSASS Memory.\n\n*   **Target/Technique:**\n    *   **LSASS Memory:** The common data source exploited by both Mimikatz and Windows Credential Editor to harvest credentials for lateral movement and unauthorized access.\n\nIn summary, **Mimikatz** is the key software converging **Cleaver** and **Carbanak** on **LSASS Memory** for credential access. **Windows Credential Editor** represents a parallel path used by other actors to achieve the same objective via the same target.",
      "sources": [
        {
          "title": "🤖 Agent trace",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 10.730052129998512,
        "chunks": 0,
        "llm_calls": 4,
        "cloud_calls": 0
      },
      "approach_metadata": {
        "adaptive": {
          "route": "complex",
          "approach": "agentic-rag"
        }
      }
    },
    {
      "query_id": "cyber_credential_access_path",
      "model": "lazy-graph-rag",
      "base_model": "lazy-graph-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 4.8,
      "raw": "Based on the provided context, it is not possible to fully trace the relationship path for all requested entities because the context does not contain information regarding **Cleaver** or **Carbanak**.\n\nHowever, based on the available documents, the following relationships regarding **Mimikatz**, **Windows Credential Editor**, and **LSASS Memory** can be established:\n\n1.  **Skeleton Key** (a module in **Mimikatz**) is used by **APT5**.\n2.  **Windows Credential Editor** is a password dumping tool that uses **LSASS Memory**.\n3.  The following actors use **Windows Credential Editor**:\n    *   Leviathan\n    *   FIN5\n    *   APT39\n    *   FIN6\n    *   GALLIUM\n    *   Threat Group-3390\n    *   BRONZE BUTLER\n\nThe context does not explicitly link Mimikatz, Windows Credential Editor, and LSASS Memory to a single converging actor other than showing that various threat groups use Windows Credential Editor (which accesses LSASS Memory) and that APT5 uses Skeleton Key (part of Mimikatz). There is no information linking Cleaver or Carbanak to these tools in the provided text.\n\n<details><summary>🔎 Retrieved context (8 sources)</summary>\n\n**1. cyber_threat_intel/032-s0005.md** · score 55.000\n\n> # Windows Credential Editor\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: tool\nATT&CK ID: S0005\nSTIX ID: tool--242f3da3-4425-4d11-8f5c-b842886da966\n\nDescription:\n[Windows Credential Editor](https://attack.mitre.org/software/S00\n\n**2. cyber_threat_intel/021-s0001.md** · score 28.000\n\n> # Trojan.Mebromi\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: malware\nATT&CK ID: S0001\nSTIX ID: malware--c5e9cb46-aced-466c-85ea-7db5572ad9ec\n\nDescription:\n[Trojan.Mebromi](https://attack.mitre.org/software/S0001) is BIOS-leve\n\n**3. cyber_threat_intel/033-s0006.md** · score 28.000\n\n> # pwdump\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: tool\nATT&CK ID: S0006\nSTIX ID: tool--9de2308e-7bed-43a3-8e58-f194b3586700\n\nDescription:\n[pwdump](https://attack.mitre.org/software/S0006) is a credential dumper. (Citation:\n\n**4. cyber_threat_intel/034-s0008.md** · score 27.000\n\n> # gsecdump\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: tool\nATT&CK ID: S0008\nSTIX ID: tool--b07c2c47-fefb-4d7c-a69e-6a3296171f54\n\nDescription:\n[gsecdump](https://attack.mitre.org/software/S0008) is a publicly-available creden\n\n**5. cyber_threat_intel/024-s0007.md** · score 25.000\n\n> # Skeleton Key\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: malware\nATT&CK ID: S0007\nSTIX ID: malware--89f63ae4-f229-4a5c-95ad-6f22ed2b5c49\n\nDescription:\n[Skeleton Key](https://attack.mitre.org/software/S0007) is malware used \n\n**6. cyber_threat_intel/002-g0002.md** · score 24.000\n\n> # Moafee\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: intrusion-set\nATT&CK ID: G0002\nSTIX ID: intrusion-set--2e5d3a83-fe00-41a5-9b60-237efc84832f\n\nDescription:\n[Moafee](https://attack.mitre.org/groups/G0002) is a threat group \n\n**7. cyber_threat_intel/005-g0005.md** · score 24.000\n\n> # APT12\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: intrusion-set\nATT&CK ID: G0005\nSTIX ID: intrusion-set--c47f937f-1022-4f42-8525-e7a4779a14cb\n\nDescription:\n[APT12](https://attack.mitre.org/groups/G0005) is a threat group th\n\n**8. cyber_threat_intel/006-g0006.md** · score 24.000\n\n> # APT1\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: intrusion-set\nATT&CK ID: G0006\nSTIX ID: intrusion-set--6a2e693f-24e5-451a-9f88-b36a108e5662\n\nDescription:\n[APT1](https://attack.mitre.org/groups/G0006) is a Chinese threat gr\n\n</details>\n\n---\n📊 4.8s · 8 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the provided context, it is not possible to fully trace the relationship path for all requested entities because the context does not contain information regarding **Cleaver** or **Carbanak**.\n\nHowever, based on the available documents, the following relationships regarding **Mimikatz**, **Windows Credential Editor**, and **LSASS Memory** can be established:\n\n1.  **Skeleton Key** (a module in **Mimikatz**) is used by **APT5**.\n2.  **Windows Credential Editor** is a password dumping tool that uses **LSASS Memory**.\n3.  The following actors use **Windows Credential Editor**:\n    *   Leviathan\n    *   FIN5\n    *   APT39\n    *   FIN6\n    *   GALLIUM\n    *   Threat Group-3390\n    *   BRONZE BUTLER\n\nThe context does not explicitly link Mimikatz, Windows Credential Editor, and LSASS Memory to a single converging actor other than showing that various threat groups use Windows Credential Editor (which accesses LSASS Memory) and that APT5 uses Skeleton Key (part of Mimikatz). There is no information linking Cleaver or Carbanak to these tools in the provided text.",
      "sources": [
        {
          "title": "cyber_threat_intel/032-s0005.md",
          "score": 55.0
        },
        {
          "title": "cyber_threat_intel/021-s0001.md",
          "score": 28.0
        },
        {
          "title": "cyber_threat_intel/033-s0006.md",
          "score": 28.0
        },
        {
          "title": "cyber_threat_intel/034-s0008.md",
          "score": 27.0
        },
        {
          "title": "cyber_threat_intel/024-s0007.md",
          "score": 25.0
        },
        {
          "title": "cyber_threat_intel/002-g0002.md",
          "score": 24.0
        },
        {
          "title": "cyber_threat_intel/005-g0005.md",
          "score": 24.0
        },
        {
          "title": "cyber_threat_intel/006-g0006.md",
          "score": 24.0
        }
      ],
      "metrics": {
        "seconds": 4.819287376998545,
        "chunks": 8,
        "llm_calls": 2,
        "cloud_calls": 0
      },
      "approach_metadata": {
        "lazy_graph": {
          "experimental": true,
          "cache_hit": true,
          "index_seconds": 0.009119,
          "graph_chunks": 66,
          "graph_concepts": 762,
          "graph_edges": 13949,
          "relevance_tests": 24,
          "relevance_budget": 24,
          "seed_k": 8,
          "max_context_chunks": 8,
          "llm_index_calls": 0,
          "cache_namespace": "RagBase_cyber_threat_intel.concepts-24"
        }
      }
    },
    {
      "query_id": "cyber_campaign_overlap",
      "model": "vanilla-rag",
      "base_model": "vanilla-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 11.6,
      "raw": "Based on the context provided, the following campaigns share specific tools or techniques:\n\n**PowerShell and Visual Basic (T1059.005)**\n*   **Frankenstein** uses PowerShell (T1059.001) and Visual Basic (T1059.005).\n*   **Operation Sharpshooter** uses Visual Basic (T1059.005).\n*   **C0011** uses Visual Basic (T1059.005).\n\n**Spearphishing and Malicious Links/Files**\n*   **Frankenstein** uses Spearphishing Attachment (T1566.001) and Malicious File (T1204.002).\n*   **Operation Spalax** uses Spearphishing Link (T1566.002), Malicious Link (T1204.001), and Upload Malware (T1608.001).\n*   **C0011** uses Spearphishing Link (T1566.002), Malicious Link (T1204.001), Malicious File (T1204.002), and Upload Malware (T1608.001).\n*   **Operation Sharpshooter** uses Malicious File (T1204.002) and Upload Malware (T1608.001).\n\n**Discovery Techniques**\n*   **Frankenstein** uses Process Discovery (T1057), System Information Discovery (T1082), and Security Software Discovery (T1518.001).\n*   No other campaigns in the provided context explicitly list these specific discovery techniques.\n\n**Exfiltration**\n*   **Frankenstein** uses Automated Exfiltration (T1020).\n*   No other campaigns in the provided context explicitly list exfiltration techniques.\n\n**Ingress Tool Transfer (T1105)**\n*   **Operation Sharpshooter** uses Ingress Tool Transfer (T1105).\n*   **Frankenstein** uses Ingress Tool Transfer (T1105).\n*   **C0010** uses Ingress Tool Transfer (T1105).\n\n**Upload Malware (T1608.001)**\n*   **Operation Sharpshooter** uses Upload Malware (T1608.001).\n*   **Operation Spalax** uses Upload Malware (T1608.001).\n*   **C0011** uses Upload Malware (T1608.001).\n*   **C0010** uses Upload Malware (T1608.001).\n\n**Malware (T1587.001)**\n*   **Operation Sharpshooter** uses Malware (T1587.001).\n*   **C0010** uses Malware (T1587.001).\n\n**Domains (T1583.001)**\n*   **Operation Spalax** uses Domains (T1583.001).\n*   **C0011** uses Domains (T1583.001).\n*   **C0010** uses Domains (T1583.001).\n\n**Tool (T1588.002)**\n*   **Operation Spalax** uses Tool (T1588.002).\n*   **C0010** uses Tool (T1588.002).\n\n<details><summary>🔎 Retrieved context (5 sources)</summary>\n\n**1. cyber_threat_intel/020-c0013.md**\n\n> # Operation Sharpshooter\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0013\nSTIX ID: campaign--37764c78-2a99-46d1-a7ea-6454b9bf93a0\n\nDescription:\n[Operation Sharpshooter](https://attack.mitre.org/campaigns/\n\n**2. cyber_threat_intel/014-c0005.md**\n\n> # Operation Spalax\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0005\nSTIX ID: campaign--4c840263-bbda-440d-a22b-674679ddebf1\n\nDescription:\n[Operation Spalax](https://attack.mitre.org/campaigns/C0005) was a\n\n**3. cyber_threat_intel/018-c0011.md**\n\n> # C0011\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0011\nSTIX ID: campaign--b4e5a4a9-f3be-4631-ba8f-da6ebb067fac\n\nDescription:\n[C0011](https://attack.mitre.org/campaigns/C0011) was a suspected cyber espio\n\n**4. cyber_threat_intel/011-c0001.md**\n\n> # Frankenstein\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0001\nSTIX ID: campaign--26d9ebae-de59-427f-ae9a-349456bae4b1\n\nDescription:\n[Frankenstein](https://attack.mitre.org/campaigns/C0001) was described\n\n**5. cyber_threat_intel/017-c0010.md**\n\n> # C0010\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0010\nSTIX ID: campaign--ab747e62-1bcb-479f-a26b-1cd39d413d81\n\nDescription:\n[C0010](https://attack.mitre.org/campaigns/C0010) was a cyber espionage campa\n\n</details>\n\n---\n📊 11.6s · 5 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the context provided, the following campaigns share specific tools or techniques:\n\n**PowerShell and Visual Basic (T1059.005)**\n*   **Frankenstein** uses PowerShell (T1059.001) and Visual Basic (T1059.005).\n*   **Operation Sharpshooter** uses Visual Basic (T1059.005).\n*   **C0011** uses Visual Basic (T1059.005).\n\n**Spearphishing and Malicious Links/Files**\n*   **Frankenstein** uses Spearphishing Attachment (T1566.001) and Malicious File (T1204.002).\n*   **Operation Spalax** uses Spearphishing Link (T1566.002), Malicious Link (T1204.001), and Upload Malware (T1608.001).\n*   **C0011** uses Spearphishing Link (T1566.002), Malicious Link (T1204.001), Malicious File (T1204.002), and Upload Malware (T1608.001).\n*   **Operation Sharpshooter** uses Malicious File (T1204.002) and Upload Malware (T1608.001).\n\n**Discovery Techniques**\n*   **Frankenstein** uses Process Discovery (T1057), System Information Discovery (T1082), and Security Software Discovery (T1518.001).\n*   No other campaigns in the provided context explicitly list these specific discovery techniques.\n\n**Exfiltration**\n*   **Frankenstein** uses Automated Exfiltration (T1020).\n*   No other campaigns in the provided context explicitly list exfiltration techniques.\n\n**Ingress Tool Transfer (T1105)**\n*   **Operation Sharpshooter** uses Ingress Tool Transfer (T1105).\n*   **Frankenstein** uses Ingress Tool Transfer (T1105).\n*   **C0010** uses Ingress Tool Transfer (T1105).\n\n**Upload Malware (T1608.001)**\n*   **Operation Sharpshooter** uses Upload Malware (T1608.001).\n*   **Operation Spalax** uses Upload Malware (T1608.001).\n*   **C0011** uses Upload Malware (T1608.001).\n*   **C0010** uses Upload Malware (T1608.001).\n\n**Malware (T1587.001)**\n*   **Operation Sharpshooter** uses Malware (T1587.001).\n*   **C0010** uses Malware (T1587.001).\n\n**Domains (T1583.001)**\n*   **Operation Spalax** uses Domains (T1583.001).\n*   **C0011** uses Domains (T1583.001).\n*   **C0010** uses Domains (T1583.001).\n\n**Tool (T1588.002)**\n*   **Operation Spalax** uses Tool (T1588.002).\n*   **C0010** uses Tool (T1588.002).",
      "sources": [
        {
          "title": "cyber_threat_intel/020-c0013.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/014-c0005.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/018-c0011.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/011-c0001.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/017-c0010.md",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 11.570248171999992,
        "chunks": 5,
        "llm_calls": 2,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_campaign_overlap",
      "model": "hybrid-rag",
      "base_model": "hybrid-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 21.6,
      "raw": "Based on the provided context, the following campaigns share specific tools or techniques:\n\n**PowerShell and Spearphishing Attachment:**\n*   **Frankenstein (C0001)** uses both **PowerShell (T1059.001)** and **Spearphishing Attachment (T1566.001)**.\n\n**Discovery Techniques:**\n*   **Frankenstein (C0001)** uses **Process Discovery (T1057)**, **System Information Discovery (T1082)**, and **Security Software Discovery (T1518.001)**.\n*   **Operation CuckooBees (C0012)** uses **Peripheral Device Discovery (T1120)**, **Remote System Discovery (T1018)**, **File and Directory Discovery (T1083)**, **System Information Discovery (T1082)**, **System Time Discovery (T1124)**, **System Network Configuration Discovery (T1016)**, and **Password Policy Discovery (T1201)**.\n*   **Operation Honeybee (C0006)** uses **File and Directory Discovery (T1083)**.\n\n**Exfiltration:**\n*   **Frankenstein (C0001)** uses **Automated Exfiltration (T1020)**.\n*   **Operation Honeybee (C0006)** uses **Exfiltration Over C2 Channel (T1041)**.\n\n**Reg Tool:**\n*   **Operation Honeybee (C0006)** uses **Reg (S0075)**. No other campaign in the provided context explicitly lists \"Reg\" as a used tool.\n\n**Malicious File / Ingress Tool Transfer:**\n*   **Frankenstein (C0001)** and **Operation Sharpshooter (C0013)** both use **Malicious File (T1204.002)** and **Ingress Tool Transfer (T1105)**.\n\n**Visual Basic:**\n*   **Frankenstein (C0001)** and **Operation Sharpshooter (C0013)** both use **Visual Basic (T1059.005)**.\n\n<details><summary>🔎 Retrieved context (5 sources)</summary>\n\n**1. cyber_threat_intel/011-c0001.md** · score 0.127\n\n> # Frankenstein\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0001\nSTIX ID: campaign--26d9ebae-de59-427f-ae9a-349456bae4b1\n\nDescription:\n[Frankenstein](https://attack.mitre.org/campaigns/C0001) was described\n\n**2. cyber_threat_intel/019-c0012.md** · score 0.127\n\n> # Operation CuckooBees\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0012\nSTIX ID: campaign--93c23946-49af-41f4-ac03-40f9ffc7419b\n\nDescription:\n[Operation CuckooBees](https://attack.mitre.org/campaigns/C001\n\n**3. cyber_threat_intel/020-c0013.md** · score 0.113\n\n> # Operation Sharpshooter\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0013\nSTIX ID: campaign--37764c78-2a99-46d1-a7ea-6454b9bf93a0\n\nDescription:\n[Operation Sharpshooter](https://attack.mitre.org/campaigns/\n\n**4. cyber_threat_intel/044-t1001-003.md** · score 0.101\n\n> # Protocol or Service Impersonation\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1001.003\nSTIX ID: attack-pattern--c325b232-d5bc-4dde-a3ec-71f3db9e8adc\n\nDescription:\nAdversaries may impersonate legit\n\n**5. cyber_threat_intel/015-c0006.md** · score 0.099\n\n> # Operation Honeybee\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0006\nSTIX ID: campaign--4553292d-12c6-4a93-934d-12160370d4e0\n\nDescription:\n[Operation Honeybee](https://attack.mitre.org/campaigns/C0006) w\n\n</details>\n\n---\n📊 21.5s · 5 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the provided context, the following campaigns share specific tools or techniques:\n\n**PowerShell and Spearphishing Attachment:**\n*   **Frankenstein (C0001)** uses both **PowerShell (T1059.001)** and **Spearphishing Attachment (T1566.001)**.\n\n**Discovery Techniques:**\n*   **Frankenstein (C0001)** uses **Process Discovery (T1057)**, **System Information Discovery (T1082)**, and **Security Software Discovery (T1518.001)**.\n*   **Operation CuckooBees (C0012)** uses **Peripheral Device Discovery (T1120)**, **Remote System Discovery (T1018)**, **File and Directory Discovery (T1083)**, **System Information Discovery (T1082)**, **System Time Discovery (T1124)**, **System Network Configuration Discovery (T1016)**, and **Password Policy Discovery (T1201)**.\n*   **Operation Honeybee (C0006)** uses **File and Directory Discovery (T1083)**.\n\n**Exfiltration:**\n*   **Frankenstein (C0001)** uses **Automated Exfiltration (T1020)**.\n*   **Operation Honeybee (C0006)** uses **Exfiltration Over C2 Channel (T1041)**.\n\n**Reg Tool:**\n*   **Operation Honeybee (C0006)** uses **Reg (S0075)**. No other campaign in the provided context explicitly lists \"Reg\" as a used tool.\n\n**Malicious File / Ingress Tool Transfer:**\n*   **Frankenstein (C0001)** and **Operation Sharpshooter (C0013)** both use **Malicious File (T1204.002)** and **Ingress Tool Transfer (T1105)**.\n\n**Visual Basic:**\n*   **Frankenstein (C0001)** and **Operation Sharpshooter (C0013)** both use **Visual Basic (T1059.005)**.",
      "sources": [
        {
          "title": "cyber_threat_intel/011-c0001.md",
          "score": 0.12697153
        },
        {
          "title": "cyber_threat_intel/019-c0012.md",
          "score": 0.1269561
        },
        {
          "title": "cyber_threat_intel/020-c0013.md",
          "score": 0.11320241
        },
        {
          "title": "cyber_threat_intel/044-t1001-003.md",
          "score": 0.10085453
        },
        {
          "title": "cyber_threat_intel/015-c0006.md",
          "score": 0.09894015
        }
      ],
      "metrics": {
        "seconds": 21.548478010001418,
        "chunks": 5,
        "llm_calls": 2,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_campaign_overlap",
      "model": "contextual-rag",
      "base_model": "contextual-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 21.1,
      "raw": "Based on the context provided, the following campaigns overlap by specific tools or techniques:\n\n**PowerShell**\n*   **Frankenstein (C0001)** uses PowerShell (T1059.001).\n\n**Reg / Modify Registry**\n*   **Operation Honeybee (C0006)** uses Reg (S0075) and Modify Registry (T1112).\n*   **Turla (G0010)** uses Modify Registry (T1112).\n\n**Spearphishing**\n*   **Frankenstein (C0001)** uses Spearphishing Attachment (T1566.001).\n*   **Turla (G0010)** is noted for conducting spearphishing campaigns.\n\n**Discovery Techniques**\nMultiple campaigns overlap on various discovery techniques:\n*   **System Information Discovery (T1082):** Used by **Operation CuckooBees (C0012)**, **Frankenstein (C0001)**, and **Turla (G0010)**.\n*   **File and Directory Discovery (T1083):** Used by **Operation Honeybee (C0006)** and **Operation CuckooBees (C0012)**.\n*   **Scheduled Task (T1053.005):** Used by **CostaRicto (C0004)** and **Frankenstein (C0001)**.\n\n**Exfiltration**\n*   **Operation Honeybee (C0006)** uses Exfiltration Over C2 Channel (T1041).\n*   **Frankenstein (C0001)** uses Automated Exfiltration (T1020).\n\n<details><summary>🔎 Retrieved context (5 sources)</summary>\n\n**1. cyber_threat_intel/015-c0006.md** · score 0.194\n\n> This section details the MITRE ATT&CK campaign C0006, known as Operation Honeybee, which targeted humanitarian and inter-Korean affairs organizations across multiple countries from late 2017 to early 2018. It outlines the specific tactics a\n\n**2. cyber_threat_intel/013-c0004.md** · score 0.181\n\n> This section details the CostaRicto cyber espionage campaign, outlining its global targeting of financial institutions and specific geographic focus on South Asia. It further lists the technical tools, malware, and tactics employed by the a\n\n**3. cyber_threat_intel/019-c0012.md** · score 0.169\n\n> This chunk details the specific MITRE ATT&CK techniques and tactics employed by the Operation CuckooBees cyber espionage campaign, as defined in the MITRE ATT&CK Enterprise STIX bundle. It provides the technical mapping of the group's activ\n\n**4. cyber_threat_intel/011-c0001.md** · score 0.159\n\n> This chunk details the \"Frankenstein\" campaign (C0001), a highly-targeted operation from early 2019 where threat actors utilized open-source tools like Empire to execute various tactics and techniques. It provides the specific MITRE ATT&CK \n\n**5. cyber_threat_intel/010-g0010.md** · score 0.155\n\n> This section provides detailed technical information about the Turla threat group, including its attribution to Russia's FSB and specific MITRE ATT&CK techniques it employs. It serves as a comprehensive profile linking the group's identity \n\n</details>\n\n---\n📊 21.1s · 5 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the context provided, the following campaigns overlap by specific tools or techniques:\n\n**PowerShell**\n*   **Frankenstein (C0001)** uses PowerShell (T1059.001).\n\n**Reg / Modify Registry**\n*   **Operation Honeybee (C0006)** uses Reg (S0075) and Modify Registry (T1112).\n*   **Turla (G0010)** uses Modify Registry (T1112).\n\n**Spearphishing**\n*   **Frankenstein (C0001)** uses Spearphishing Attachment (T1566.001).\n*   **Turla (G0010)** is noted for conducting spearphishing campaigns.\n\n**Discovery Techniques**\nMultiple campaigns overlap on various discovery techniques:\n*   **System Information Discovery (T1082):** Used by **Operation CuckooBees (C0012)**, **Frankenstein (C0001)**, and **Turla (G0010)**.\n*   **File and Directory Discovery (T1083):** Used by **Operation Honeybee (C0006)** and **Operation CuckooBees (C0012)**.\n*   **Scheduled Task (T1053.005):** Used by **CostaRicto (C0004)** and **Frankenstein (C0001)**.\n\n**Exfiltration**\n*   **Operation Honeybee (C0006)** uses Exfiltration Over C2 Channel (T1041).\n*   **Frankenstein (C0001)** uses Automated Exfiltration (T1020).",
      "sources": [
        {
          "title": "cyber_threat_intel/015-c0006.md",
          "score": 0.19423749
        },
        {
          "title": "cyber_threat_intel/013-c0004.md",
          "score": 0.18131886
        },
        {
          "title": "cyber_threat_intel/019-c0012.md",
          "score": 0.16868249
        },
        {
          "title": "cyber_threat_intel/011-c0001.md",
          "score": 0.15878503
        },
        {
          "title": "cyber_threat_intel/010-g0010.md",
          "score": 0.1548056
        }
      ],
      "metrics": {
        "seconds": 21.111243634000857,
        "chunks": 5,
        "llm_calls": 2,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_campaign_overlap",
      "model": "graph-rag",
      "base_model": "graph-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 18.6,
      "raw": "Based on the provided Knowledge Graph and Document Chunks, several campaigns exhibit overlaps in tools, techniques, and methodologies. Below is a synthesis of these overlaps categorized by the specific areas you requested.\n\n### Campaigns Overlapping via PowerShell and Scripting\n\nSeveral campaigns utilize **PowerShell** for command execution, automation, or as part of their toolset:\n\n*   **Frankenstein**: Explicitly uses **PowerShell (T1059.001)** for command execution and task automation [4].\n*   **Night Dragon**: Utilizes the **Windows Command Shell**, which is closely related to PowerShell environments in terms of scripting and command-line interaction capabilities, often overlapping in functional use cases [5].\n*   **Operation Spalax**: Uses **Command and Scripting Interpreter (T1059)**, a technique that encompasses PowerShell usage, alongside malware delivery [2].\n\nAdditionally, the general artifact **PowerShell** is noted in the knowledge graph as being used by threat actors like **Deep Panda** and **APT28**, though specific campaign-level documents for these groups were not provided in the chunks, their attribution to these techniques links them via tooling.\n\n### Campaigns Overlapping via Spearphishing (Attachment and Link)\n\n**Spearphishing** is a highly prevalent technique across multiple campaigns, often overlapping between **Attachments** and **Links**:\n\n*   **C0011 (Transparent Tribe)**: Employs both **Spearphishing Attachment (T1566.001)** and **Spearphishing Link (T1566.002)** to target students in India [3].\n*   **Frankenstein**: Uses **Spearphishing Attachment (T1566.001)** to deliver payloads, aligning with the initial access vector of C0011 [4].\n*   **Night Dragon**: Relies on **Spearphishing Link (T1566.002)**, sharing this delivery mechanism with C0011 [5].\n*   **Operation Spalax**: Also utilizes **Spearphishing Link (T1566.002)** alongside generic phishing topics, further linking it to the link-based spearphishing techniques of Night Dragon and C0011 [2].\n\nThe knowledge graph further notes that **APT28** and **APT12** use Spearphishing Attachments, and **Taidoor** is delivered via this method, indicating a broader ecosystem overlap in initial access techniques.\n\n### Campaigns Overlapping via Discovery Techniques\n\nThe technique **Security Software Discovery (T1518.001)** is explicitly linked to specific campaigns:\n\n*   **Frankenstein**: Uses **Security Software Discovery (T1518.001)** to identify security tools on the victim's system [4].\n*   The knowledge graph also identifies **Tasklist** as a tool used for Security Software Discovery, which is a common utility in the Windows environment often employed alongside other discovery commands like `ps` or `systeminfo`.\n\nWhile no other campaign in the provided chunks explicitly lists \"Security Software Discovery (T1518.001),\" **Operation Sharpshooter** uses **Process Injection (T1055)** and **Native API (T1106)**, which are related to evasion and persistence rather than direct discovery, but often occur in parallel during the same operations.\n\n### Campaigns Overlapping via Exfiltration and Ingress Tool Transfer\n\nOverlap exists in the handling of tools and data movement:\n\n*   **Ingress Tool Transfer**:\n    *   **Frankenstein** uses **Ingress Tool Transfer (T1105)** to bring in additional tools [4].\n    *   **Operation Sharpshooter** also utilizes **Ingress Tool Transfer (T1105)**, indicating a shared logistical method for deploying malware or utilities into the target environment [1].\n    *   The knowledge graph links **FunnyDream** and **CostaRicto** to Ingress Tool Transfer, suggesting a broader tactical overlap among these groups.\n\n*   **Exfiltration**:\n    *   **Frankenstein** uses **Automated Exfiltration (T1020)** [4].\n    *   While no other campaign in the chunks explicitly lists \"Automated Exfiltration,\" **Night Dragon** involves collecting data from SCADA systems and financials, implying exfiltration activities, though the specific technique is not labeled as T1020 in the text.\n\n### Summary of Key Overlaps\n\n| Technique/Tool | Campaigns Involved |\n| :--- | :--- |\n| **Spearphishing Link** | C0011, Night Dragon, Operation Spalax |\n| **Spearphishing Attachment** | C0011, Frankenstein |\n| **PowerShell / Command Interpreter** | Frankenstein (Explicit PowerShell), Operation Spalax (Command Interpreter), Night Dragon (Cmd Shell) |\n| **Ingress Tool Transfer** | Frankenstein, Operation Sharpshooter |\n| **Security Software Discovery** | Frankenstein |\n\nThese overlaps suggest that while the campaigns target different sectors (e.g., Energy in Night Dragon, Education in C0011, Nuclear/Defense in Sharpshooter), they share common operational playbooks regarding initial access (spearphishing) and logistical support (ingress tool transfer).\n\n<details><summary>🔎 Retrieved context (1 source)</summary>\n\n**1. LightRAG knowledge graph**\n\n> Graph + vector dual retrieval (profile=graph-rag) over the corpus's extracted entities and relations.\n\n</details>\n\n---\n📊 18.6s · 0 chunks · 1 LLM call · 0 cloud",
      "answer": "Based on the provided Knowledge Graph and Document Chunks, several campaigns exhibit overlaps in tools, techniques, and methodologies. Below is a synthesis of these overlaps categorized by the specific areas you requested.\n\n### Campaigns Overlapping via PowerShell and Scripting\n\nSeveral campaigns utilize **PowerShell** for command execution, automation, or as part of their toolset:\n\n*   **Frankenstein**: Explicitly uses **PowerShell (T1059.001)** for command execution and task automation [4].\n*   **Night Dragon**: Utilizes the **Windows Command Shell**, which is closely related to PowerShell environments in terms of scripting and command-line interaction capabilities, often overlapping in functional use cases [5].\n*   **Operation Spalax**: Uses **Command and Scripting Interpreter (T1059)**, a technique that encompasses PowerShell usage, alongside malware delivery [2].\n\nAdditionally, the general artifact **PowerShell** is noted in the knowledge graph as being used by threat actors like **Deep Panda** and **APT28**, though specific campaign-level documents for these groups were not provided in the chunks, their attribution to these techniques links them via tooling.\n\n### Campaigns Overlapping via Spearphishing (Attachment and Link)\n\n**Spearphishing** is a highly prevalent technique across multiple campaigns, often overlapping between **Attachments** and **Links**:\n\n*   **C0011 (Transparent Tribe)**: Employs both **Spearphishing Attachment (T1566.001)** and **Spearphishing Link (T1566.002)** to target students in India [3].\n*   **Frankenstein**: Uses **Spearphishing Attachment (T1566.001)** to deliver payloads, aligning with the initial access vector of C0011 [4].\n*   **Night Dragon**: Relies on **Spearphishing Link (T1566.002)**, sharing this delivery mechanism with C0011 [5].\n*   **Operation Spalax**: Also utilizes **Spearphishing Link (T1566.002)** alongside generic phishing topics, further linking it to the link-based spearphishing techniques of Night Dragon and C0011 [2].\n\nThe knowledge graph further notes that **APT28** and **APT12** use Spearphishing Attachments, and **Taidoor** is delivered via this method, indicating a broader ecosystem overlap in initial access techniques.\n\n### Campaigns Overlapping via Discovery Techniques\n\nThe technique **Security Software Discovery (T1518.001)** is explicitly linked to specific campaigns:\n\n*   **Frankenstein**: Uses **Security Software Discovery (T1518.001)** to identify security tools on the victim's system [4].\n*   The knowledge graph also identifies **Tasklist** as a tool used for Security Software Discovery, which is a common utility in the Windows environment often employed alongside other discovery commands like `ps` or `systeminfo`.\n\nWhile no other campaign in the provided chunks explicitly lists \"Security Software Discovery (T1518.001),\" **Operation Sharpshooter** uses **Process Injection (T1055)** and **Native API (T1106)**, which are related to evasion and persistence rather than direct discovery, but often occur in parallel during the same operations.\n\n### Campaigns Overlapping via Exfiltration and Ingress Tool Transfer\n\nOverlap exists in the handling of tools and data movement:\n\n*   **Ingress Tool Transfer**:\n    *   **Frankenstein** uses **Ingress Tool Transfer (T1105)** to bring in additional tools [4].\n    *   **Operation Sharpshooter** also utilizes **Ingress Tool Transfer (T1105)**, indicating a shared logistical method for deploying malware or utilities into the target environment [1].\n    *   The knowledge graph links **FunnyDream** and **CostaRicto** to Ingress Tool Transfer, suggesting a broader tactical overlap among these groups.\n\n*   **Exfiltration**:\n    *   **Frankenstein** uses **Automated Exfiltration (T1020)** [4].\n    *   While no other campaign in the chunks explicitly lists \"Automated Exfiltration,\" **Night Dragon** involves collecting data from SCADA systems and financials, implying exfiltration activities, though the specific technique is not labeled as T1020 in the text.\n\n### Summary of Key Overlaps\n\n| Technique/Tool | Campaigns Involved |\n| :--- | :--- |\n| **Spearphishing Link** | C0011, Night Dragon, Operation Spalax |\n| **Spearphishing Attachment** | C0011, Frankenstein |\n| **PowerShell / Command Interpreter** | Frankenstein (Explicit PowerShell), Operation Spalax (Command Interpreter), Night Dragon (Cmd Shell) |\n| **Ingress Tool Transfer** | Frankenstein, Operation Sharpshooter |\n| **Security Software Discovery** | Frankenstein |\n\nThese overlaps suggest that while the campaigns target different sectors (e.g., Energy in Night Dragon, Education in C0011, Nuclear/Defense in Sharpshooter), they share common operational playbooks regarding initial access (spearphishing) and logistical support (ingress tool transfer).",
      "sources": [
        {
          "title": "LightRAG knowledge graph",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 18.628292090998002,
        "chunks": 0,
        "llm_calls": 1,
        "cloud_calls": 0
      },
      "approach_metadata": {
        "lightrag": {
          "query_profile": "graph-rag"
        }
      }
    },
    {
      "query_id": "cyber_campaign_overlap",
      "model": "agentic-rag",
      "base_model": "agentic-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 72.3,
      "raw": "Based on the analysis of the knowledge graph and document corpus, here are the campaigns that overlap by tooling or technique in the specified categories:\n\n### 1. **Frankenstein** and **Operation Honeybee**\n*   **Overlapping Category:** **Registry Manipulation**\n*   **Specific Technique:** `Modify Registry (T1112)`\n    *   **Operation Honeybee** explicitly uses `Reg` to modify Windows Registry entries.\n    *   **Frankenstein** is linked to the `Modify Registry` technique in the knowledge graph relations connecting it to Operation Honeybee, indicating shared tooling/technique usage for persistence or configuration changes.\n\n### 2. **Frankenstein** and **C0011** (Transparent Tribe)\n*   **Overlapping Category:** **Spearphishing**\n*   **Specific Technique:** `Spearphishing Attachment (T1566.001)`\n    *   Both campaigns utilize malicious email attachments as the primary initial access vector to deliver payloads to victims.\n\n### Summary of Overlaps by Category\n\n| Category | Campaigns with Overlap | Shared Technique(s) |\n| :--- | :--- | :--- |\n| **Registry Manipulation** | Frankenstein, Operation Honeybee | Modify Registry (T1112) / Use of `Reg` |\n| **Spearphishing** | Frankenstein, C0011 | Spearphishing Attachment (T1566.001) |\n| **PowerShell** | *No direct overlap found* | Frankenstein uses PowerShell; no other campaign in this specific set is explicitly linked to it in the provided data. |\n| **Discovery** | *No direct overlap found* | Frankenstein uses Security Software Discovery; no other campaign listed shares this specific technique. |\n| **Exfiltration** | *No direct overlap found* | Frankenstein uses Automated Exfiltration; no other campaign listed shares this specific technique. |\n\n**Conclusion:**\nThe primary overlaps are between **Frankenstein** and **Operation Honeybee** (Registry) and between **Frankenstein** and **C0011** (Spearphishing). No campaigns in the provided context share overlapping techniques specifically for PowerShell, Discovery, or Exfiltration beyond Frankenstein's unique usage of these in this dataset.\n\n<details><summary>🔎 Retrieved context (1 source)</summary>\n\n**1. 🤖 Agent trace**\n\n> **Step 1.** **Thought:** To identify which campaigns overlap in their tooling and techniques (specifically regarding PowerShell, Registry manipulation, Spearphishing, Discovery, and Exfiltration), I need to query the knowledge graph for relationships between threat actors/campaigns and these specific TTPs (Tactics, Techniques, and Procedures).\n\nI will start by searching for campaigns associated with these specific techniques to see which ones are linked.\n\n**Action:** `query_graph(Which campaigns use PowerShell, Registry manipulation, Spearphishing, Discovery, or Exfiltration techniques? List the campaigns and their associated techniques.)`\n\n**Observation:** Based on the provided knowledge base, here are the campaigns that utilize PowerShell, Registry manipulation, Spearphishing, Discovery, or Exfiltration techniques:\n\n### **C0011**\nThis suspected cyber espionage campaign conducted by Transparent Tribe utilized several of the specified techniques:\n*   *\n\n**Step 2.** **Action:** `query_graph(Which campaigns share overlapping techniques in PowerShell, Registry manipulation, Spearphishing, Discovery, or Exfiltration? List the specific shared techniques for each pair of overlapping campaigns.)`\n\n**Observation:** Based on the provided context, the following campaigns share overlapping techniques in the specified categories (PowerShell, Registry manipulation, Spearphishing, Discovery, and Exfiltration):\n\n### 1. Frankenstein and Operation Honeybee\nThese two campaigns overlap specifically in **Registry Manipula\n\n**Step 3.** **Action:** `query_graph(Which campaigns share overlapping techniques in PowerShell, Registry manipulation, Spearphishing, Discovery, or Exfiltration? List the specific shared techniques for each pair of campaigns.)`\n\n**Observation:** Based on the provided Knowledge Graph and Document Chunks, the campaigns **Frankenstein** and **Operation Honeybee** are identified as sharing specific malicious techniques, primarily involving Registry manipulation. While other campaigns like **C0011** and **Frankenstein** share Spearphishing techn\n\n</details>\n\n---\n📊 72.3s · 0 chunks · 7 LLM calls · 0 cloud",
      "answer": "Based on the analysis of the knowledge graph and document corpus, here are the campaigns that overlap by tooling or technique in the specified categories:\n\n### 1. **Frankenstein** and **Operation Honeybee**\n*   **Overlapping Category:** **Registry Manipulation**\n*   **Specific Technique:** `Modify Registry (T1112)`\n    *   **Operation Honeybee** explicitly uses `Reg` to modify Windows Registry entries.\n    *   **Frankenstein** is linked to the `Modify Registry` technique in the knowledge graph relations connecting it to Operation Honeybee, indicating shared tooling/technique usage for persistence or configuration changes.\n\n### 2. **Frankenstein** and **C0011** (Transparent Tribe)\n*   **Overlapping Category:** **Spearphishing**\n*   **Specific Technique:** `Spearphishing Attachment (T1566.001)`\n    *   Both campaigns utilize malicious email attachments as the primary initial access vector to deliver payloads to victims.\n\n### Summary of Overlaps by Category\n\n| Category | Campaigns with Overlap | Shared Technique(s) |\n| :--- | :--- | :--- |\n| **Registry Manipulation** | Frankenstein, Operation Honeybee | Modify Registry (T1112) / Use of `Reg` |\n| **Spearphishing** | Frankenstein, C0011 | Spearphishing Attachment (T1566.001) |\n| **PowerShell** | *No direct overlap found* | Frankenstein uses PowerShell; no other campaign in this specific set is explicitly linked to it in the provided data. |\n| **Discovery** | *No direct overlap found* | Frankenstein uses Security Software Discovery; no other campaign listed shares this specific technique. |\n| **Exfiltration** | *No direct overlap found* | Frankenstein uses Automated Exfiltration; no other campaign listed shares this specific technique. |\n\n**Conclusion:**\nThe primary overlaps are between **Frankenstein** and **Operation Honeybee** (Registry) and between **Frankenstein** and **C0011** (Spearphishing). No campaigns in the provided context share overlapping techniques specifically for PowerShell, Discovery, or Exfiltration beyond Frankenstein's unique usage of these in this dataset.",
      "sources": [
        {
          "title": "🤖 Agent trace",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 72.31367657399824,
        "chunks": 0,
        "llm_calls": 7,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_campaign_overlap",
      "model": "n8n-adaptive-rag",
      "base_model": "n8n-adaptive-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 15.1,
      "raw": "Based on the analysis of the knowledge graph and document corpus, here are the campaigns that overlap by tooling or technique in the specified categories:\n\n### 1. **Frankenstein** and **Operation Honeybee**\n*   **Overlapping Category:** **Registry Manipulation**\n*   **Specific Technique:** `Modify Registry (T1112)`\n    *   **Operation Honeybee** explicitly uses `Reg` to modify Windows Registry entries.\n    *   **Frankenstein** is linked to the `Modify Registry` technique in the knowledge graph relations connecting it to Operation Honeybee, indicating shared tooling/technique usage for persistence or configuration changes.\n\n### 2. **Frankenstein** and **C0011** (Transparent Tribe)\n*   **Overlapping Category:** **Spearphishing**\n*   **Specific Technique:** `Spearphishing Attachment (T1566.001)`\n    *   Both campaigns utilize malicious email attachments as the primary initial access vector to deliver payloads to victims.\n\n### Summary of Overlaps by Category\n\n| Category | Campaigns with Overlap | Shared Technique(s) |\n| :--- | :--- | :--- |\n| **Registry Manipulation** | Frankenstein, Operation Honeybee | Modify Registry (T1112) / Use of `Reg` |\n| **Spearphishing** | Frankenstein, C0011 | Spearphishing Attachment (T1566.001) |\n| **PowerShell** | *No direct overlap found* | Frankenstein uses PowerShell; no other campaign in this specific set is explicitly linked to it in the provided data. |\n| **Discovery** | *No direct overlap found* | Frankenstein uses Security Software Discovery; no other campaign listed shares this specific technique. |\n| **Exfiltration** | *No direct overlap found* | Frankenstein uses Automated Exfiltration; no other campaign listed shares this specific technique. |\n\n**Conclusion:**\nThe primary overlaps are between **Frankenstein** and **Operation Honeybee** (Registry) and between **Frankenstein** and **C0011** (Spearphishing). No campaigns in the provided context share overlapping techniques specifically for PowerShell, Discovery, or Exfiltration beyond Frankenstein's unique usage of these in this dataset.\n\n<details><summary>🔎 Retrieved context (1 source)</summary>\n\n**1. 🤖 Agent trace**\n\n> **Step 1.** **Thought:** To identify which campaigns overlap in their tooling and techniques (specifically regarding PowerShell, Registry manipulation, Spearphishing, Discovery, and Exfiltration), I need to query the knowledge graph for relationships between threat actors/campaigns and these specific TTPs (Tactics, Techniques, and Procedures).\n\nI will start by searching for campaigns associated with these specific techniques to see which ones are linked.\n\n**Action:** `query_graph(Which campaigns use PowerShell, Registry manipulation, Spearphishing, Discovery, or Exfiltration techniques? List the campaigns and their associated techniques.)`\n\n**Observation:** Based on the provided knowledge base, here are the campaigns that utilize PowerShell, Registry manipulation, Spearphishing, Discovery, or Exfiltration techniques:\n\n### **C0011**\nThis suspected cyber espionage campaign conducted by Transparent Tribe utilized several of the specified techniques:\n*   *\n\n**Step 2.** **Action:** `query_graph(Which campaigns share overlapping techniques in PowerShell, Registry manipulation, Spearphishing, Discovery, or Exfiltration? List the specific shared techniques for each pair of overlapping campaigns.)`\n\n**Observation:** Based on the provided context, the following campaigns share overlapping techniques in the specified categories (PowerShell, Registry manipulation, Spearphishing, Discovery, and Exfiltration):\n\n### 1. Frankenstein and Operation Honeybee\nThese two campaigns overlap specifically in **Registry Manipula\n\n**Step 3.** **Action:** `query_graph(Which campaigns share overlapping techniques in PowerShell, Registry manipulation, Spearphishing, Discovery, or Exfiltration? List the specific shared techniques for each pair of campaigns.)`\n\n**Observation:** Based on the provided Knowledge Graph and Document Chunks, the campaigns **Frankenstein** and **Operation Honeybee** are identified as sharing specific malicious techniques, primarily involving Registry manipulation. While other campaigns like **C0011** and **Frankenstein** share Spearphishing techn\n\n</details>\n\n---\n📊 15.1s · 0 chunks · 8 LLM calls · 0 cloud",
      "answer": "Based on the analysis of the knowledge graph and document corpus, here are the campaigns that overlap by tooling or technique in the specified categories:\n\n### 1. **Frankenstein** and **Operation Honeybee**\n*   **Overlapping Category:** **Registry Manipulation**\n*   **Specific Technique:** `Modify Registry (T1112)`\n    *   **Operation Honeybee** explicitly uses `Reg` to modify Windows Registry entries.\n    *   **Frankenstein** is linked to the `Modify Registry` technique in the knowledge graph relations connecting it to Operation Honeybee, indicating shared tooling/technique usage for persistence or configuration changes.\n\n### 2. **Frankenstein** and **C0011** (Transparent Tribe)\n*   **Overlapping Category:** **Spearphishing**\n*   **Specific Technique:** `Spearphishing Attachment (T1566.001)`\n    *   Both campaigns utilize malicious email attachments as the primary initial access vector to deliver payloads to victims.\n\n### Summary of Overlaps by Category\n\n| Category | Campaigns with Overlap | Shared Technique(s) |\n| :--- | :--- | :--- |\n| **Registry Manipulation** | Frankenstein, Operation Honeybee | Modify Registry (T1112) / Use of `Reg` |\n| **Spearphishing** | Frankenstein, C0011 | Spearphishing Attachment (T1566.001) |\n| **PowerShell** | *No direct overlap found* | Frankenstein uses PowerShell; no other campaign in this specific set is explicitly linked to it in the provided data. |\n| **Discovery** | *No direct overlap found* | Frankenstein uses Security Software Discovery; no other campaign listed shares this specific technique. |\n| **Exfiltration** | *No direct overlap found* | Frankenstein uses Automated Exfiltration; no other campaign listed shares this specific technique. |\n\n**Conclusion:**\nThe primary overlaps are between **Frankenstein** and **Operation Honeybee** (Registry) and between **Frankenstein** and **C0011** (Spearphishing). No campaigns in the provided context share overlapping techniques specifically for PowerShell, Discovery, or Exfiltration beyond Frankenstein's unique usage of these in this dataset.",
      "sources": [
        {
          "title": "🤖 Agent trace",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 15.072369714998786,
        "chunks": 0,
        "llm_calls": 8,
        "cloud_calls": 0
      },
      "approach_metadata": {
        "adaptive": {
          "route": "complex",
          "approach": "agentic-rag"
        }
      }
    },
    {
      "query_id": "cyber_campaign_overlap",
      "model": "lazy-graph-rag",
      "base_model": "lazy-graph-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 12.4,
      "raw": "Based on the context provided, here are the campaigns that overlap by specific tools or techniques:\n\n**PowerShell**\n*   **Frankenstein** uses PowerShell (T1059.001).\n\n**Reg**\n*   **Operation Honeybee** uses Reg (S0075).\n\n**Spearphishing**\n*   **Frankenstein** uses Spearphishing Attachment (T1566.001).\n*   **C0011** uses Spearphishing Link (T1566.002) and Spearphishing Attachment (T1566.001).\n\n**Discovery Techniques**\nMultiple campaigns overlap on various discovery techniques:\n*   **System Information Discovery (T1082):** Used by **Frankenstein**, **Operation CuckooBees**, and **FunnyDream**.\n*   **Process Discovery (T1057):** Used by **Frankenstein** and **FunnyDream**.\n*   **Remote System Discovery (T1018):** Used by **Operation CuckooBees** and **FunnyDream**.\n*   **File and Directory Discovery (T1083):** Used by **Operation CuckooBees** and **Operation Honeybee**.\n*   **System Network Configuration Discovery (T1016):** Used by **Operation CuckooBees** and **FunnyDream**.\n*   **Security Software Discovery (T1518.001):** Used by **Frankenstein**.\n*   **Password Policy Discovery (T1201):** Used by **Operation CuckooBees**.\n*   **System Time Discovery (T1124):** Used by **Operation CuckooBees**.\n*   **Peripheral Device Discovery (T1120):** Used by **Operation CuckooBees**.\n*   **Network Service Discovery (T1046):** Used by **CostaRicto**.\n\n**Exfiltration / Data Handling**\n*   **Automated Exfiltration (T1020):** Used by **Frankenstein**.\n*   **Exfiltration Over C2 Channel (T1041):** Used by **Operation Honeybee**.\n*   **Archive via Utility (T1560.001):** Used by **Operation CuckooBees** and **FunnyDream**.\n*   **Local Data Staging (T1074.001):** Used by **Operation Honeybee**.\n\n**Other Notable Overlaps**\n*   **Ingress Tool Transfer (T1105):** Used by **Frankenstein**, **FunnyDream**, **CostaRicto**, and **C0010**.\n*   **Scheduled Task (T1053.005):** Used by **Frankenstein** and **CostaRicto**.\n*   **Visual Basic (T1059.005):** Used by **Frankenstein**, **FunnyDream**, and **C0011**.\n*   **Domains (T1583.001):** Used by **CostaRicto**, **Operation Honeybee**, **Operation Spalax**, **C0011**, and **C0010**.\n*   **Tool (T1588.002):** Used by **CostaRicto**, **Operation Spalax**, and **C0010**.\n*   **Malware (T1588.001):** Used by **FunnyDream** and **Operation Spalax**.\n*   **Upload Malware (T1608.001):** Used by **Operation Spalax**, **C0011**, and **C0010**.\n*   **Malicious Link (T1204.001):** Used by **Operation Spalax** and **C0011**.\n\n<details><summary>🔎 Retrieved context (8 sources)</summary>\n\n**1. cyber_threat_intel/011-c0001.md** · score 64.000\n\n> # Frankenstein\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0001\nSTIX ID: campaign--26d9ebae-de59-427f-ae9a-349456bae4b1\n\nDescription:\n[Frankenstein](https://attack.mitre.org/campaigns/C0001) was described\n\n**2. cyber_threat_intel/019-c0012.md** · score 33.500\n\n> # Operation CuckooBees\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0012\nSTIX ID: campaign--93c23946-49af-41f4-ac03-40f9ffc7419b\n\nDescription:\n[Operation CuckooBees](https://attack.mitre.org/campaigns/C001\n\n**3. cyber_threat_intel/016-c0007.md** · score 29.600\n\n> # FunnyDream\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0007\nSTIX ID: campaign--8d2bc130-89fe-466e-a4f9-6bce6129c2b8\n\nDescription:\n[FunnyDream](https://attack.mitre.org/campaigns/C0007) was a suspected C\n\n**4. cyber_threat_intel/013-c0004.md** · score 29.000\n\n> # CostaRicto\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0004\nSTIX ID: campaign--f9cc545e-b0ef-4b92-8884-a3a4427609f6\n\nDescription:\n[CostaRicto](https://attack.mitre.org/campaigns/C0004) was a suspected h\n\n**5. cyber_threat_intel/015-c0006.md** · score 25.750\n\n> # Operation Honeybee\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0006\nSTIX ID: campaign--4553292d-12c6-4a93-934d-12160370d4e0\n\nDescription:\n[Operation Honeybee](https://attack.mitre.org/campaigns/C0006) w\n\n**6. cyber_threat_intel/014-c0005.md** · score 25.500\n\n> # Operation Spalax\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0005\nSTIX ID: campaign--4c840263-bbda-440d-a22b-674679ddebf1\n\nDescription:\n[Operation Spalax](https://attack.mitre.org/campaigns/C0005) was a\n\n**7. cyber_threat_intel/018-c0011.md** · score 25.429\n\n> # C0011\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0011\nSTIX ID: campaign--b4e5a4a9-f3be-4631-ba8f-da6ebb067fac\n\nDescription:\n[C0011](https://attack.mitre.org/campaigns/C0011) was a suspected cyber espio\n\n**8. cyber_threat_intel/017-c0010.md** · score 25.000\n\n> # C0010\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0010\nSTIX ID: campaign--ab747e62-1bcb-479f-a26b-1cd39d413d81\n\nDescription:\n[C0010](https://attack.mitre.org/campaigns/C0010) was a cyber espionage campa\n\n</details>\n\n---\n📊 12.4s · 8 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the context provided, here are the campaigns that overlap by specific tools or techniques:\n\n**PowerShell**\n*   **Frankenstein** uses PowerShell (T1059.001).\n\n**Reg**\n*   **Operation Honeybee** uses Reg (S0075).\n\n**Spearphishing**\n*   **Frankenstein** uses Spearphishing Attachment (T1566.001).\n*   **C0011** uses Spearphishing Link (T1566.002) and Spearphishing Attachment (T1566.001).\n\n**Discovery Techniques**\nMultiple campaigns overlap on various discovery techniques:\n*   **System Information Discovery (T1082):** Used by **Frankenstein**, **Operation CuckooBees**, and **FunnyDream**.\n*   **Process Discovery (T1057):** Used by **Frankenstein** and **FunnyDream**.\n*   **Remote System Discovery (T1018):** Used by **Operation CuckooBees** and **FunnyDream**.\n*   **File and Directory Discovery (T1083):** Used by **Operation CuckooBees** and **Operation Honeybee**.\n*   **System Network Configuration Discovery (T1016):** Used by **Operation CuckooBees** and **FunnyDream**.\n*   **Security Software Discovery (T1518.001):** Used by **Frankenstein**.\n*   **Password Policy Discovery (T1201):** Used by **Operation CuckooBees**.\n*   **System Time Discovery (T1124):** Used by **Operation CuckooBees**.\n*   **Peripheral Device Discovery (T1120):** Used by **Operation CuckooBees**.\n*   **Network Service Discovery (T1046):** Used by **CostaRicto**.\n\n**Exfiltration / Data Handling**\n*   **Automated Exfiltration (T1020):** Used by **Frankenstein**.\n*   **Exfiltration Over C2 Channel (T1041):** Used by **Operation Honeybee**.\n*   **Archive via Utility (T1560.001):** Used by **Operation CuckooBees** and **FunnyDream**.\n*   **Local Data Staging (T1074.001):** Used by **Operation Honeybee**.\n\n**Other Notable Overlaps**\n*   **Ingress Tool Transfer (T1105):** Used by **Frankenstein**, **FunnyDream**, **CostaRicto**, and **C0010**.\n*   **Scheduled Task (T1053.005):** Used by **Frankenstein** and **CostaRicto**.\n*   **Visual Basic (T1059.005):** Used by **Frankenstein**, **FunnyDream**, and **C0011**.\n*   **Domains (T1583.001):** Used by **CostaRicto**, **Operation Honeybee**, **Operation Spalax**, **C0011**, and **C0010**.\n*   **Tool (T1588.002):** Used by **CostaRicto**, **Operation Spalax**, and **C0010**.\n*   **Malware (T1588.001):** Used by **FunnyDream** and **Operation Spalax**.\n*   **Upload Malware (T1608.001):** Used by **Operation Spalax**, **C0011**, and **C0010**.\n*   **Malicious Link (T1204.001):** Used by **Operation Spalax** and **C0011**.",
      "sources": [
        {
          "title": "cyber_threat_intel/011-c0001.md",
          "score": 64.0
        },
        {
          "title": "cyber_threat_intel/019-c0012.md",
          "score": 33.5
        },
        {
          "title": "cyber_threat_intel/016-c0007.md",
          "score": 29.6
        },
        {
          "title": "cyber_threat_intel/013-c0004.md",
          "score": 29.0
        },
        {
          "title": "cyber_threat_intel/015-c0006.md",
          "score": 25.75
        },
        {
          "title": "cyber_threat_intel/014-c0005.md",
          "score": 25.5
        },
        {
          "title": "cyber_threat_intel/018-c0011.md",
          "score": 25.42857142857143
        },
        {
          "title": "cyber_threat_intel/017-c0010.md",
          "score": 25.0
        }
      ],
      "metrics": {
        "seconds": 12.411943130999134,
        "chunks": 8,
        "llm_calls": 2,
        "cloud_calls": 0
      },
      "approach_metadata": {
        "lazy_graph": {
          "experimental": true,
          "cache_hit": true,
          "index_seconds": 0.009579,
          "graph_chunks": 66,
          "graph_concepts": 762,
          "graph_edges": 13949,
          "relevance_tests": 24,
          "relevance_budget": 24,
          "seed_k": 8,
          "max_context_chunks": 8,
          "llm_index_calls": 0,
          "cache_namespace": "RagBase_cyber_threat_intel.concepts-24"
        }
      }
    },
    {
      "query_id": "cyber_mitigation_coverage",
      "model": "vanilla-rag",
      "base_model": "vanilla-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 10.6,
      "raw": "Based on the context provided, here are the mitigations covering credential, Active Directory, web-content, or registry-related techniques and the specific techniques they mitigate:\n\n**1. Active Directory Configuration (M1015)**\n*   **Mitigates:**\n    *   Cached Domain Credentials (T1003.005)\n    *   DCSync (T1003.006)\n    *   Use Alternate Authentication Material (T1550)\n    *   Pass the Ticket (T1550.003)\n    *   Group Policy Preferences (T1552.006)\n    *   Steal or Forge Kerberos Tickets (T1558)\n    *   Cloud Accounts (T1078.004)\n    *   Software Deployment Tools (T1072)\n    *   Unsecured Credentials (T1552)\n    *   SID-History Injection (T1134.005)\n    *   SAML Tokens (T1606.002)\n    *   Steal or Forge Authentication Certificates (T1649)\n\n**2. Application Developer Guidance (M1013)**\n*   **Mitigates:**\n    *   Use Alternate Authentication Material (T1550)\n    *   Code Repositories (T1593.003)\n    *   Valid Accounts (T1078)\n\n**3. Restrict Web-Based Content (M1021)**\n*   **Mitigates:**\n    *   Content Injection (T1659)\n    *   Bidirectional Communication (T1102.002)\n    *   Spearphishing Link (T1566.002)\n    *   Steal Application Access Token (T1528)\n    *   Steal Web Session Cookie (T1539)\n    *   Compiled HTML File (T1218.001)\n    *   Dynamic Resolution (T1568)\n    *   Dead Drop Resolver (T1102.001)\n    *   User Execution (T1204)\n    *   External Remote Services (T1133)\n    *   Drive-by Compromise (T1189)\n    *   Spearphishing via Service (T1566.003)\n\n**4. Restrict Registry Permissions (M1024)**\n*   **Mitigates:**\n    *   Time Providers (T1547.003)\n    *   COR_PROFILER (T1574.012)\n    *   Logon Script (Windows) (T1037.001)\n    *   Network Provider DLL (T1556.008)\n    *   Modify Authentication Process (T1556)\n    *   Disable or Modify System Firewall (T1686)\n    *   Server Software Component (T1505)\n    *   Terminal Services DLL (T1505.005)\n    *   Disable or Modify Windows Event Log (T1685.001)\n    *   Services Registry Permissions Weakness (T1574.011)\n\n<details><summary>🔎 Retrieved context (5 sources)</summary>\n\n**1. cyber_threat_intel/052-m1015.md**\n\n> - Active Directory Configuration -> mitigates -> Cached Domain Credentials (T1003.005)\n- Active Directory Configuration -> mitigates -> DCSync (T1003.006)\n- Active Directory Configuration -> mitigates -> Use Alternate Authentication Materia\n\n**2. cyber_threat_intel/051-m1013.md**\n\n> - Application Developer Guidance -> mitigates -> Use Alternate Authentication Material (T1550)\n- Application Developer Guidance -> mitigates -> Code Repositories (T1593.003)\n- Application Developer Guidance -> mitigates -> Valid Accounts (T\n\n**3. cyber_threat_intel/052-m1015.md**\n\n> # Active Directory Configuration\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1015\nSTIX ID: course-of-action--e3388c78-2a8d-47c2-8422-c1398b324462\n\nDescription:\nImplement robust Active Directory (A\n\n**4. cyber_threat_intel/058-m1021.md**\n\n> # Restrict Web-Based Content\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1021\nSTIX ID: course-of-action--21da4fd4-27ad-4e9c-b93d-0b9b14d02c96\n\nDescription:\nRestricting web-based content involves e\n\n**5. cyber_threat_intel/060-m1024.md**\n\n> # Restrict Registry Permissions\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1024\nSTIX ID: course-of-action--a2c36a5d-4058-475e-8e77-fff75e50d3b9\n\nDescription:\nRestricting registry permissions invo\n\n</details>\n\n---\n📊 10.6s · 5 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the context provided, here are the mitigations covering credential, Active Directory, web-content, or registry-related techniques and the specific techniques they mitigate:\n\n**1. Active Directory Configuration (M1015)**\n*   **Mitigates:**\n    *   Cached Domain Credentials (T1003.005)\n    *   DCSync (T1003.006)\n    *   Use Alternate Authentication Material (T1550)\n    *   Pass the Ticket (T1550.003)\n    *   Group Policy Preferences (T1552.006)\n    *   Steal or Forge Kerberos Tickets (T1558)\n    *   Cloud Accounts (T1078.004)\n    *   Software Deployment Tools (T1072)\n    *   Unsecured Credentials (T1552)\n    *   SID-History Injection (T1134.005)\n    *   SAML Tokens (T1606.002)\n    *   Steal or Forge Authentication Certificates (T1649)\n\n**2. Application Developer Guidance (M1013)**\n*   **Mitigates:**\n    *   Use Alternate Authentication Material (T1550)\n    *   Code Repositories (T1593.003)\n    *   Valid Accounts (T1078)\n\n**3. Restrict Web-Based Content (M1021)**\n*   **Mitigates:**\n    *   Content Injection (T1659)\n    *   Bidirectional Communication (T1102.002)\n    *   Spearphishing Link (T1566.002)\n    *   Steal Application Access Token (T1528)\n    *   Steal Web Session Cookie (T1539)\n    *   Compiled HTML File (T1218.001)\n    *   Dynamic Resolution (T1568)\n    *   Dead Drop Resolver (T1102.001)\n    *   User Execution (T1204)\n    *   External Remote Services (T1133)\n    *   Drive-by Compromise (T1189)\n    *   Spearphishing via Service (T1566.003)\n\n**4. Restrict Registry Permissions (M1024)**\n*   **Mitigates:**\n    *   Time Providers (T1547.003)\n    *   COR_PROFILER (T1574.012)\n    *   Logon Script (Windows) (T1037.001)\n    *   Network Provider DLL (T1556.008)\n    *   Modify Authentication Process (T1556)\n    *   Disable or Modify System Firewall (T1686)\n    *   Server Software Component (T1505)\n    *   Terminal Services DLL (T1505.005)\n    *   Disable or Modify Windows Event Log (T1685.001)\n    *   Services Registry Permissions Weakness (T1574.011)",
      "sources": [
        {
          "title": "cyber_threat_intel/052-m1015.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/051-m1013.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/052-m1015.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/058-m1021.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/060-m1024.md",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 10.607253046000551,
        "chunks": 5,
        "llm_calls": 2,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_mitigation_coverage",
      "model": "hybrid-rag",
      "base_model": "hybrid-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 26.2,
      "raw": "Based on the context provided, here are the mitigations that cover credential, Active Directory, web-content, or registry-related techniques and the specific techniques they mitigate:\n\n**1. Restrict Registry Permissions (M1024)**\n*   **Technique Covered:** Registry-related techniques.\n*   **Mitigates:**\n    *   Time Providers (T1547.003)\n    *   COR_PROFILER (T1574.012)\n    *   Logon Script (Windows) (T1037.001)\n    *   Network Provider DLL (T1556.008)\n    *   Modify Authentication Process (T1556)\n    *   Disable or Modify System Firewall (T1686)\n    *   Server Software Component (T1505)\n    *   Terminal Services DLL (T1505.005)\n    *   Disable or Modify Windows Event Log (T1685.001)\n    *   Services Registry Permissions Weakness (T1574.011)\n\n**2. User Account Management (M1018)**\n*   **Technique Covered:** Credential-related techniques (via password policies and account management).\n*   **Mitigates:**\n    *   Cloud Infrastructure Discovery (T1580)\n    *   Poisoned Pipeline Execution (T1677)\n    *   Domain Accounts (T1078.002)\n    *   Create or Modify System Process (T1543)\n    *   Network Sniffing (T1040)\n    *   Modify Cloud Compute Infrastructure (T1578)\n    *   Software Deployment Tools (T1072)\n\n**3. Active Directory Configuration (M1015)**\n*   **Technique Covered:** Active Directory and credential-related techniques.\n*   **Mitigates:**\n    *   Steal or Forge Kerberos Tickets (T1558)\n    *   Cloud Accounts (T1078.004)\n    *   Software Deployment Tools (T1072)\n    *   Unsecured Credentials (T1552)\n    *   SID-History Injection (T1134.005)\n    *   SAML Tokens (T1606.002)\n    *   Steal or Forge Authentication Certificates (T1649)\n\n**4. Application Developer Guidance (M1013)**\n*   **Technique Covered:** Web-content related techniques (via secure coding practices for SQL Injection and XSS).\n*   **Mitigates:**\n    *   SMS Pumping (T1496.003)\n    *   Plist File Modification (T1647)\n    *   Supply Chain Compromise (T1195)\n    *   Hijack Execution Flow (T1574)\n    *   Hide Artifacts (T1564)\n    *   Exploitation for Credential Access (T1212)\n    *   File/Path Exclusions (T1564.012)\n    *   Application Access Token (T1550.001)\n    *   XPC Services (T1559.003)\n\n**5. Restrict File and Directory Permissions**\n*   **Technique Covered:** Registry-related techniques (specifically Windows Host Firewall registry settings).\n*   **Mitigates:**\n    *   Windows Host Firewall (T1686.003)\n\n<details><summary>🔎 Retrieved context (5 sources)</summary>\n\n**1. cyber_threat_intel/060-m1024.md** · score 0.713\n\n> # Restrict Registry Permissions\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1024\nSTIX ID: course-of-action--a2c36a5d-4058-475e-8e77-fff75e50d3b9\n\nDescription:\nRestricting registry permissions invo\n\n**2. cyber_threat_intel/055-m1018.md** · score 0.711\n\n> # User Account Management\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1018\nSTIX ID: course-of-action--93e7968a-9074-4eac-8ae9-9f5200ec3317\n\nDescription:\nUser Account Management involves implementi\n\n**3. cyber_threat_intel/052-m1015.md** · score 0.507\n\n> # Active Directory Configuration\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1015\nSTIX ID: course-of-action--e3388c78-2a8d-47c2-8422-c1398b324462\n\nDescription:\nImplement robust Active Directory (A\n\n**4. cyber_threat_intel/051-m1013.md** · score 0.408\n\n> # Application Developer Guidance\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1013\nSTIX ID: course-of-action--25dc1ce8-eb55-4333-ae30-a7cb4f5894a1\n\nDescription:\nApplication Developer Guidance focus\n\n**5. cyber_threat_intel/059-m1022.md** · score 0.379\n\n> - Restrict File and Directory Permissions -> mitigates -> Windows Host Firewall (T1686.003)\n\n</details>\n\n---\n📊 26.2s · 5 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the context provided, here are the mitigations that cover credential, Active Directory, web-content, or registry-related techniques and the specific techniques they mitigate:\n\n**1. Restrict Registry Permissions (M1024)**\n*   **Technique Covered:** Registry-related techniques.\n*   **Mitigates:**\n    *   Time Providers (T1547.003)\n    *   COR_PROFILER (T1574.012)\n    *   Logon Script (Windows) (T1037.001)\n    *   Network Provider DLL (T1556.008)\n    *   Modify Authentication Process (T1556)\n    *   Disable or Modify System Firewall (T1686)\n    *   Server Software Component (T1505)\n    *   Terminal Services DLL (T1505.005)\n    *   Disable or Modify Windows Event Log (T1685.001)\n    *   Services Registry Permissions Weakness (T1574.011)\n\n**2. User Account Management (M1018)**\n*   **Technique Covered:** Credential-related techniques (via password policies and account management).\n*   **Mitigates:**\n    *   Cloud Infrastructure Discovery (T1580)\n    *   Poisoned Pipeline Execution (T1677)\n    *   Domain Accounts (T1078.002)\n    *   Create or Modify System Process (T1543)\n    *   Network Sniffing (T1040)\n    *   Modify Cloud Compute Infrastructure (T1578)\n    *   Software Deployment Tools (T1072)\n\n**3. Active Directory Configuration (M1015)**\n*   **Technique Covered:** Active Directory and credential-related techniques.\n*   **Mitigates:**\n    *   Steal or Forge Kerberos Tickets (T1558)\n    *   Cloud Accounts (T1078.004)\n    *   Software Deployment Tools (T1072)\n    *   Unsecured Credentials (T1552)\n    *   SID-History Injection (T1134.005)\n    *   SAML Tokens (T1606.002)\n    *   Steal or Forge Authentication Certificates (T1649)\n\n**4. Application Developer Guidance (M1013)**\n*   **Technique Covered:** Web-content related techniques (via secure coding practices for SQL Injection and XSS).\n*   **Mitigates:**\n    *   SMS Pumping (T1496.003)\n    *   Plist File Modification (T1647)\n    *   Supply Chain Compromise (T1195)\n    *   Hijack Execution Flow (T1574)\n    *   Hide Artifacts (T1564)\n    *   Exploitation for Credential Access (T1212)\n    *   File/Path Exclusions (T1564.012)\n    *   Application Access Token (T1550.001)\n    *   XPC Services (T1559.003)\n\n**5. Restrict File and Directory Permissions**\n*   **Technique Covered:** Registry-related techniques (specifically Windows Host Firewall registry settings).\n*   **Mitigates:**\n    *   Windows Host Firewall (T1686.003)",
      "sources": [
        {
          "title": "cyber_threat_intel/060-m1024.md",
          "score": 0.7128143
        },
        {
          "title": "cyber_threat_intel/055-m1018.md",
          "score": 0.71122557
        },
        {
          "title": "cyber_threat_intel/052-m1015.md",
          "score": 0.50735664
        },
        {
          "title": "cyber_threat_intel/051-m1013.md",
          "score": 0.40788925
        },
        {
          "title": "cyber_threat_intel/059-m1022.md",
          "score": 0.3793088
        }
      ],
      "metrics": {
        "seconds": 26.206217220002145,
        "chunks": 5,
        "llm_calls": 2,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_mitigation_coverage",
      "model": "contextual-rag",
      "base_model": "contextual-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 23.6,
      "raw": "Based on the context provided, the following mitigations cover credential, Active Directory, web-content, or registry-related techniques and the specific techniques they mitigate:\n\n**1. Restrict Registry Permissions (M1024)**\n*   **Techniques Mitigated:**\n    *   Time Providers (T1547.003)\n    *   COR_PROFILER (T1574.012)\n    *   Logon Script (Windows) (T1037.001)\n    *   Network Provider DLL (T1556.008)\n    *   Modify Authentication Process (T1556)\n    *   Disable or Modify System Firewall (T1686)\n    *   Server Software Component (T1505)\n    *   Terminal Services DLL (T1505.005)\n    *   Disable or Modify Windows Event Log (T1685.001)\n    *   Services Registry Permissions Weakness (T1574.011)\n    *   Clear Network Connection History and Configurations (T1070.007)\n    *   Modify Registry (T1112)\n\n**2. User Account Management (M1018)**\n*   **Techniques Mitigated:**\n    *   Cloud Infrastructure Discovery (T1580)\n    *   Poisoned Pipeline Execution (T1677)\n    *   Domain Accounts (T1078.002)\n    *   Create or Modify System Process (T1543)\n    *   Network Sniffing (T1040)\n    *   Modify Cloud Compute Infrastructure (T1578)\n    *   Software Deployment Tools (T1072)\n\n**3. Active Directory Configuration (M1015)**\n*   **Techniques Mitigated:**\n    *   Steal or Forge Kerberos Tickets (T1558)\n    *   Cloud Accounts (T1078.004)\n    *   Software Deployment Tools (T1072)\n    *   Unsecured Credentials (T1552)\n    *   SID-History Injection (T1134.005)\n    *   SAML Tokens (T1606.002)\n    *   Steal or Forge Authentication Certificates (T1649)\n    *   Cached Domain Credentials (T1003.005)\n    *   DCSync (T1003.006)\n    *   Use Alternate Authentication Material (T1550)\n    *   Pass the Ticket (T1550.003)\n    *   Group Policy Preferences (T1552.006)\n\n<details><summary>🔎 Retrieved context (5 sources)</summary>\n\n**1. cyber_threat_intel/060-m1024.md** · score 0.790\n\n> This section details the specific implementation measures and tools for mitigating persistence and privilege escalation techniques by restricting access to sensitive Windows registry keys and hives. It outlines procedures for permission adj\n\n**2. cyber_threat_intel/055-m1018.md** · score 0.739\n\n> This section details specific mitigation measures and implementation tools for User Account Management, outlining how policies like least privilege and MFA reduce the attack surface. It further connects these controls to their ability to mi\n\n**3. cyber_threat_intel/052-m1015.md** · score 0.704\n\n> These relations specify the particular MITRE ATT&CK techniques, such as credential theft and authentication bypasses, that are mitigated by implementing robust Active Directory configurations and group policies. This list details how centra\n\n**4. cyber_threat_intel/060-m1024.md** · score 0.663\n\n> This section lists specific MITRE ATT&CK techniques that are mitigated by restricting registry permissions, including those related to clearing network history and modifying registry entries. These relations demonstrate how limiting access \n\n**5. cyber_threat_intel/052-m1015.md** · score 0.618\n\n> This section details specific implementation measures for Active Directory Configuration, including account settings, logon restrictions, and authentication silos, while listing associated mitigation relations for various MITRE ATT&CK techn\n\n</details>\n\n---\n📊 23.6s · 5 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the context provided, the following mitigations cover credential, Active Directory, web-content, or registry-related techniques and the specific techniques they mitigate:\n\n**1. Restrict Registry Permissions (M1024)**\n*   **Techniques Mitigated:**\n    *   Time Providers (T1547.003)\n    *   COR_PROFILER (T1574.012)\n    *   Logon Script (Windows) (T1037.001)\n    *   Network Provider DLL (T1556.008)\n    *   Modify Authentication Process (T1556)\n    *   Disable or Modify System Firewall (T1686)\n    *   Server Software Component (T1505)\n    *   Terminal Services DLL (T1505.005)\n    *   Disable or Modify Windows Event Log (T1685.001)\n    *   Services Registry Permissions Weakness (T1574.011)\n    *   Clear Network Connection History and Configurations (T1070.007)\n    *   Modify Registry (T1112)\n\n**2. User Account Management (M1018)**\n*   **Techniques Mitigated:**\n    *   Cloud Infrastructure Discovery (T1580)\n    *   Poisoned Pipeline Execution (T1677)\n    *   Domain Accounts (T1078.002)\n    *   Create or Modify System Process (T1543)\n    *   Network Sniffing (T1040)\n    *   Modify Cloud Compute Infrastructure (T1578)\n    *   Software Deployment Tools (T1072)\n\n**3. Active Directory Configuration (M1015)**\n*   **Techniques Mitigated:**\n    *   Steal or Forge Kerberos Tickets (T1558)\n    *   Cloud Accounts (T1078.004)\n    *   Software Deployment Tools (T1072)\n    *   Unsecured Credentials (T1552)\n    *   SID-History Injection (T1134.005)\n    *   SAML Tokens (T1606.002)\n    *   Steal or Forge Authentication Certificates (T1649)\n    *   Cached Domain Credentials (T1003.005)\n    *   DCSync (T1003.006)\n    *   Use Alternate Authentication Material (T1550)\n    *   Pass the Ticket (T1550.003)\n    *   Group Policy Preferences (T1552.006)",
      "sources": [
        {
          "title": "cyber_threat_intel/060-m1024.md",
          "score": 0.78957623
        },
        {
          "title": "cyber_threat_intel/055-m1018.md",
          "score": 0.73899573
        },
        {
          "title": "cyber_threat_intel/052-m1015.md",
          "score": 0.7039824
        },
        {
          "title": "cyber_threat_intel/060-m1024.md",
          "score": 0.6629768
        },
        {
          "title": "cyber_threat_intel/052-m1015.md",
          "score": 0.6177057
        }
      ],
      "metrics": {
        "seconds": 23.571545885999512,
        "chunks": 5,
        "llm_calls": 2,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_mitigation_coverage",
      "model": "graph-rag",
      "base_model": "graph-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 23.9,
      "raw": "Based on the provided knowledge base, several key mitigation strategies address credential access, Active Directory configuration, web content security, and registry permissions. The following is a breakdown of these mitigations and the specific techniques they cover:\n\n### 1. Active Directory Configuration (M1015)\nActive Directory Configuration focuses on implementing robust group policies to secure user accounts, control access, and minimize the attack surface. It addresses various credential and account-related risks within the directory environment.\n\n**Mitigated Techniques:**\n*   **Steal or Forge Kerberos Tickets (T1558)**\n*   **Cloud Accounts (T1078.004)**\n*   **Software Deployment Tools (T1072)**\n*   **Unsecured Credentials (T1552)**: Addresses credentials that are not properly secured.\n*   **SID-History Injection (T1134.005)**\n*   **SAML Tokens (T1606.002)**\n*   **Steal or Forge Authentication Certificates (T1649)**\n*   **Cached Domain Credentials (T1003.005)**: Mitigates risks associated with locally stored domain credentials.\n*   **DCSync (T1003.006)**\n*   **Use Alternate Authentication Material (T1550)**: Covers attacks using alternate auth materials to bypass security.\n*   **Pass the Ticket (T1550.003)**\n*   **Group Policy Preferences (T1552.006)**\n\n### 2. Restrict Web-Based Content (M1021)\nThis mitigation involves enforcing policies and technologies to limit access to potentially malicious websites, unsafe downloads, and unauthorized browser behaviors, such as URL filtering and script blocking.\n\n**Mitigated Techniques:**\n*   **Content Injection (T1659)**\n*   **Bidirectional Communication (T1102.002)**: Limits communication between attackers and compromised systems.\n*   **Spearphishing Link (T1566.002)**\n*   **Steal Application Access Token (T1528)**\n*   **Steal Web Session Cookie (T1539)**\n*   **Compiled HTML File (T1218.001)**\n*   **Dynamic Resolution (T1568)**\n*   **Dead Drop Resolver (T1102.001)**\n*   **User Execution (T1204)**: Helps prevent users from executing malicious code via web sources.\n*   **External Remote Services (T1133)**\n*   **Drive-by Compromise (T1189)**\n*   **Spearphishing via Service (T1566.003)**\n\n### 3. Restrict Registry Permissions (M1024)\nThis mitigation involves configuring access control settings for sensitive registry keys and hives to prevent unauthorized modifications that could lead to persistence, privilege escalation, or defense evasion.\n\n**Mitigated Techniques:**\n*   **Time Providers (T1547.003)**\n*   **COR_PROFILER (T1574.012)**\n*   **Logon Script (Windows) (T1037.001)**\n*   **Network Provider DLL (T1556.008)**\n*   **Modify Authentication Process (T1556)**\n*   **Disable or Modify System Firewall (T1686)**\n*   **Server Software Component (T1505)**\n*   **Terminal Services DLL (T1505.005)**\n*   **Disable or Modify Windows Event Log (T1685.001)**\n*   **Services Registry Permissions Weakness (T1574.011)**\n*   **Clear Network Connection History and Configurations (T1070.007)**\n*   **Modify Registry (T1112)**\n\n### 4. Other Notable Credential-Related Mitigations\n\n#### Encrypt Sensitive Information\nThis technique involves encrypting sensitive data to mitigate the risk of credential dumping.\n*   **Mitigates:**\n    *   **OS Credential Dumping (T1003)**: Adversary attempts to dump credentials from OS caches, memory, or structures.\n\n#### Password Policies (M1027)\nSpecific password policies help secure the Active Directory domain database file.\n*   **Mitigates:**\n    *   **NTDS (T1003.003)**: The technique of accessing or copying the Active Directory domain database to steal credential information.\n\n### Summary of Coverage\n*   **Credential Dumping**: Addressed by **Active Directory Configuration**, **Encrypt Sensitive Information**, and **Password Policies**.\n*   **Active Directory Management/Access**: Addressed primarily by **Active Directory Configuration** through centralized account management and group policies.\n*   **Web-Based Threats**: Addressed by **Restrict Web-Based Content**, which covers phishing, malware delivery, and unauthorized communications.\n*   **Registry-Based Persistence/Evasion**: Addressed by **Restrict Registry Permissions**, covering logon scripts, service modifications, and authentication process changes.\n\n### References\n\n- [1] atlas-21ddd283453b2000d542c7434c7b62abefa10c492e2185f139bb8ada785d73b1.txt\n- [2] atlas-eb871dd9eb1420cca37311885e32eb2978363fc2b333a5945d38cba45c5440f9.txt\n- [3] atlas-0a4567e40d38825c754566a6d1578d0783804d71091fea7391e60cbea751dd03.txt\n- [4] atlas-188fcfe3166728a2bb6ef62aa6baa33528c3527473a65f2281b605d7ea4b3013.txt\n- [5] atlas-3df5a9cb4e34819fb36f61b94a9867e4efea8f756a7300ff378cabaa98aa112b.txt\n\n<details><summary>🔎 Retrieved context (1 source)</summary>\n\n**1. LightRAG knowledge graph**\n\n> Graph + vector dual retrieval (profile=graph-rag) over the corpus's extracted entities and relations.\n\n</details>\n\n---\n📊 23.9s · 0 chunks · 1 LLM call · 0 cloud",
      "answer": "Based on the provided knowledge base, several key mitigation strategies address credential access, Active Directory configuration, web content security, and registry permissions. The following is a breakdown of these mitigations and the specific techniques they cover:\n\n### 1. Active Directory Configuration (M1015)\nActive Directory Configuration focuses on implementing robust group policies to secure user accounts, control access, and minimize the attack surface. It addresses various credential and account-related risks within the directory environment.\n\n**Mitigated Techniques:**\n*   **Steal or Forge Kerberos Tickets (T1558)**\n*   **Cloud Accounts (T1078.004)**\n*   **Software Deployment Tools (T1072)**\n*   **Unsecured Credentials (T1552)**: Addresses credentials that are not properly secured.\n*   **SID-History Injection (T1134.005)**\n*   **SAML Tokens (T1606.002)**\n*   **Steal or Forge Authentication Certificates (T1649)**\n*   **Cached Domain Credentials (T1003.005)**: Mitigates risks associated with locally stored domain credentials.\n*   **DCSync (T1003.006)**\n*   **Use Alternate Authentication Material (T1550)**: Covers attacks using alternate auth materials to bypass security.\n*   **Pass the Ticket (T1550.003)**\n*   **Group Policy Preferences (T1552.006)**\n\n### 2. Restrict Web-Based Content (M1021)\nThis mitigation involves enforcing policies and technologies to limit access to potentially malicious websites, unsafe downloads, and unauthorized browser behaviors, such as URL filtering and script blocking.\n\n**Mitigated Techniques:**\n*   **Content Injection (T1659)**\n*   **Bidirectional Communication (T1102.002)**: Limits communication between attackers and compromised systems.\n*   **Spearphishing Link (T1566.002)**\n*   **Steal Application Access Token (T1528)**\n*   **Steal Web Session Cookie (T1539)**\n*   **Compiled HTML File (T1218.001)**\n*   **Dynamic Resolution (T1568)**\n*   **Dead Drop Resolver (T1102.001)**\n*   **User Execution (T1204)**: Helps prevent users from executing malicious code via web sources.\n*   **External Remote Services (T1133)**\n*   **Drive-by Compromise (T1189)**\n*   **Spearphishing via Service (T1566.003)**\n\n### 3. Restrict Registry Permissions (M1024)\nThis mitigation involves configuring access control settings for sensitive registry keys and hives to prevent unauthorized modifications that could lead to persistence, privilege escalation, or defense evasion.\n\n**Mitigated Techniques:**\n*   **Time Providers (T1547.003)**\n*   **COR_PROFILER (T1574.012)**\n*   **Logon Script (Windows) (T1037.001)**\n*   **Network Provider DLL (T1556.008)**\n*   **Modify Authentication Process (T1556)**\n*   **Disable or Modify System Firewall (T1686)**\n*   **Server Software Component (T1505)**\n*   **Terminal Services DLL (T1505.005)**\n*   **Disable or Modify Windows Event Log (T1685.001)**\n*   **Services Registry Permissions Weakness (T1574.011)**\n*   **Clear Network Connection History and Configurations (T1070.007)**\n*   **Modify Registry (T1112)**\n\n### 4. Other Notable Credential-Related Mitigations\n\n#### Encrypt Sensitive Information\nThis technique involves encrypting sensitive data to mitigate the risk of credential dumping.\n*   **Mitigates:**\n    *   **OS Credential Dumping (T1003)**: Adversary attempts to dump credentials from OS caches, memory, or structures.\n\n#### Password Policies (M1027)\nSpecific password policies help secure the Active Directory domain database file.\n*   **Mitigates:**\n    *   **NTDS (T1003.003)**: The technique of accessing or copying the Active Directory domain database to steal credential information.\n\n### Summary of Coverage\n*   **Credential Dumping**: Addressed by **Active Directory Configuration**, **Encrypt Sensitive Information**, and **Password Policies**.\n*   **Active Directory Management/Access**: Addressed primarily by **Active Directory Configuration** through centralized account management and group policies.\n*   **Web-Based Threats**: Addressed by **Restrict Web-Based Content**, which covers phishing, malware delivery, and unauthorized communications.\n*   **Registry-Based Persistence/Evasion**: Addressed by **Restrict Registry Permissions**, covering logon scripts, service modifications, and authentication process changes.\n\n### References\n\n- [1] atlas-21ddd283453b2000d542c7434c7b62abefa10c492e2185f139bb8ada785d73b1.txt\n- [2] atlas-eb871dd9eb1420cca37311885e32eb2978363fc2b333a5945d38cba45c5440f9.txt\n- [3] atlas-0a4567e40d38825c754566a6d1578d0783804d71091fea7391e60cbea751dd03.txt\n- [4] atlas-188fcfe3166728a2bb6ef62aa6baa33528c3527473a65f2281b605d7ea4b3013.txt\n- [5] atlas-3df5a9cb4e34819fb36f61b94a9867e4efea8f756a7300ff378cabaa98aa112b.txt",
      "sources": [
        {
          "title": "LightRAG knowledge graph",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 23.910304551998706,
        "chunks": 0,
        "llm_calls": 1,
        "cloud_calls": 0
      },
      "approach_metadata": {
        "lightrag": {
          "query_profile": "graph-rag"
        }
      }
    },
    {
      "query_id": "cyber_mitigation_coverage",
      "model": "agentic-rag",
      "base_model": "agentic-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 14.3,
      "raw": "Based on the search results, here are the mitigations that cover credential, Active Directory, web-content, or registry-related techniques and the specific techniques they mitigate:\n\n### 1. Credential-Related Mitigations\n*   **Mitigation:** **Active Directory Configuration** (M1015)\n    *   **Techniques Mitigated:**\n        *   Cached Domain Credentials (T1003.005)\n        *   DCSync (T1003.006)\n*   **Mitigation:** **Restrict Registry Permissions** (M1024)\n    *   **Techniques Mitigated:**\n        *   Clear Network Connection History and Configurations (T1070.007)\n        *   Modify Registry (T1112)\n\n### 2. Active Directory-Related Mitigations\n*   **Mitigation:** **Active Directory Configuration** (M1015)\n    *   **Techniques Mitigated:**\n        *   Cached Domain Credentials (T1003.005)\n        *   DCSync (T1003.006)\n*   **Mitigation:** **User Account Management** (M1018)\n    *   *(Note: While listed in the search results, the specific techniques mitigated by M1018 were not fully detailed in the snippet provided, but it is a key AD-related mitigation.)*\n\n### 3. Web-Content-Related Mitigations\n*   **Mitigation:** **Restrict Web-Based Content** (M1021)\n    *   *(Note: The specific techniques mitigated by M1021 were not fully detailed in the snippet provided, but it is the primary mitigation for web-content techniques.)*\n\n### 4. Registry-Related Mitigations\n*   **Mitigation:** **Restrict Registry Permissions** (M1024)\n    *   **Techniques Mitigated:**\n        *   Clear Network Connection History and Configurations (T1070.007)\n        *   Modify Registry (T1112)\n\n### Summary Table\n\n| Category | Mitigation Name (ID) | Techniques Mitigated |\n| :--- | :--- | :--- |\n| **Credential** | Active Directory Configuration (M1015) | Cached Domain Credentials (T1003.005), DCSync (T1003.006) |\n| **Credential** | Restrict Registry Permissions (M1024) | Clear Network Connection History and Configurations (T1070.007), Modify Registry (T1112) |\n| **Active Directory** | Active Directory Configuration (M1015) | Cached Domain Credentials (T1003.005), DCSync (T1003.006) |\n| **Web-Content** | Restrict Web-Based Content (M1021) | *(Details not fully specified in source snippets)* |\n| **Registry** | Restrict Registry Permissions (M1024) | Clear Network Connection History and Configurations (T1070.007), Modify Registry (T1112) |\n\n*Note: Some mitigations like \"Application Developer Guidance\" (M1013) and \"User Training\" (M1017) were found in the search results but are not primarily categorized under the four specific technical domains requested (Credential, AD, Web-Content, Registry) in the context of direct technique mitigation for those categories.*\n\n<details><summary>🔎 Retrieved context (1 source)</summary>\n\n**1. 🤖 Agent trace**\n\n> **Step 1.** **Thought:** To answer this question accurately, I need to search the document corpus for specific mitigation strategies related to the four categories you mentioned: **Credential**, **Active Directory**, **Web-Content**, and **Registry**.\n\nI will perform separate searches for each category to identify the relevant mitigations and the specific techniques they mitigate.\n\n**Action:** `search_vectors(mitigations for credential access techniques)`\n\n**Observation:** - cyber_threat_intel/046-t1003.md: # OS Credential Dumping\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1003\nSTIX ID: attack-pattern--0a3ead4e-6d47-4ccb-854c-a6a4f9d96b22\n\nDescription:\nAdversari\n- cyber_threat_intel/048-t1003-002.md: # Security Account Manage\n\n**Step 2.** **Action:** `search_vectors(mitigations for Active Directory attacks techniques)`\n\n**Observation:** - cyber_threat_intel/052-m1015.md: - Active Directory Configuration -> mitigates -> Cached Domain Credentials (T1003.005)\n- Active Directory Configuration -> mitigates -> DCSync (T1003.006)\n- Active Directory Configuration -> mitigates\n- cyber_threat_intel/052-m1015.md: # Active Directory Configurat\n\n**Step 3.** **Action:** `search_vectors(mitigations for web content delivery or exploitation techniques)`\n\n**Observation:** - cyber_threat_intel/058-m1021.md: # Restrict Web-Based Content\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1021\nSTIX ID: course-of-action--21da4fd4-27ad-4e9c-b93d-0b9b14d02c96\n\nDescription:\n\n- cyber_threat_intel/051-m1013.md: # Application Developer Guida\n\n**Step 4.** **Action:** `search_vectors(mitigations for registry modification or access techniques)`\n\n**Observation:** - cyber_threat_intel/060-m1024.md: # Restrict Registry Permissions\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1024\nSTIX ID: course-of-action--a2c36a5d-4058-475e-8e77-fff75e50d3b9\n\nDescriptio\n- cyber_threat_intel/048-t1003-002.md: # Security Account Manage\n\n</details>\n\n---\n📊 14.3s · 0 chunks · 6 LLM calls · 0 cloud",
      "answer": "Based on the search results, here are the mitigations that cover credential, Active Directory, web-content, or registry-related techniques and the specific techniques they mitigate:\n\n### 1. Credential-Related Mitigations\n*   **Mitigation:** **Active Directory Configuration** (M1015)\n    *   **Techniques Mitigated:**\n        *   Cached Domain Credentials (T1003.005)\n        *   DCSync (T1003.006)\n*   **Mitigation:** **Restrict Registry Permissions** (M1024)\n    *   **Techniques Mitigated:**\n        *   Clear Network Connection History and Configurations (T1070.007)\n        *   Modify Registry (T1112)\n\n### 2. Active Directory-Related Mitigations\n*   **Mitigation:** **Active Directory Configuration** (M1015)\n    *   **Techniques Mitigated:**\n        *   Cached Domain Credentials (T1003.005)\n        *   DCSync (T1003.006)\n*   **Mitigation:** **User Account Management** (M1018)\n    *   *(Note: While listed in the search results, the specific techniques mitigated by M1018 were not fully detailed in the snippet provided, but it is a key AD-related mitigation.)*\n\n### 3. Web-Content-Related Mitigations\n*   **Mitigation:** **Restrict Web-Based Content** (M1021)\n    *   *(Note: The specific techniques mitigated by M1021 were not fully detailed in the snippet provided, but it is the primary mitigation for web-content techniques.)*\n\n### 4. Registry-Related Mitigations\n*   **Mitigation:** **Restrict Registry Permissions** (M1024)\n    *   **Techniques Mitigated:**\n        *   Clear Network Connection History and Configurations (T1070.007)\n        *   Modify Registry (T1112)\n\n### Summary Table\n\n| Category | Mitigation Name (ID) | Techniques Mitigated |\n| :--- | :--- | :--- |\n| **Credential** | Active Directory Configuration (M1015) | Cached Domain Credentials (T1003.005), DCSync (T1003.006) |\n| **Credential** | Restrict Registry Permissions (M1024) | Clear Network Connection History and Configurations (T1070.007), Modify Registry (T1112) |\n| **Active Directory** | Active Directory Configuration (M1015) | Cached Domain Credentials (T1003.005), DCSync (T1003.006) |\n| **Web-Content** | Restrict Web-Based Content (M1021) | *(Details not fully specified in source snippets)* |\n| **Registry** | Restrict Registry Permissions (M1024) | Clear Network Connection History and Configurations (T1070.007), Modify Registry (T1112) |\n\n*Note: Some mitigations like \"Application Developer Guidance\" (M1013) and \"User Training\" (M1017) were found in the search results but are not primarily categorized under the four specific technical domains requested (Credential, AD, Web-Content, Registry) in the context of direct technique mitigation for those categories.*",
      "sources": [
        {
          "title": "🤖 Agent trace",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 14.268070255999191,
        "chunks": 0,
        "llm_calls": 6,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_mitigation_coverage",
      "model": "n8n-adaptive-rag",
      "base_model": "n8n-adaptive-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 1.3,
      "raw": "Based on the search results, here are the mitigations that cover credential, Active Directory, web-content, or registry-related techniques and the specific techniques they mitigate:\n\n### 1. Credential-Related Mitigations\n*   **Mitigation:** **Active Directory Configuration** (M1015)\n    *   **Techniques Mitigated:**\n        *   Cached Domain Credentials (T1003.005)\n        *   DCSync (T1003.006)\n*   **Mitigation:** **Restrict Registry Permissions** (M1024)\n    *   **Techniques Mitigated:**\n        *   Clear Network Connection History and Configurations (T1070.007)\n        *   Modify Registry (T1112)\n\n### 2. Active Directory-Related Mitigations\n*   **Mitigation:** **Active Directory Configuration** (M1015)\n    *   **Techniques Mitigated:**\n        *   Cached Domain Credentials (T1003.005)\n        *   DCSync (T1003.006)\n*   **Mitigation:** **User Account Management** (M1018)\n    *   *(Note: While listed in the search results, the specific techniques mitigated by M1018 were not fully detailed in the snippet provided, but it is a key AD-related mitigation.)*\n\n### 3. Web-Content-Related Mitigations\n*   **Mitigation:** **Restrict Web-Based Content** (M1021)\n    *   *(Note: The specific techniques mitigated by M1021 were not fully detailed in the snippet provided, but it is the primary mitigation for web-content techniques.)*\n\n### 4. Registry-Related Mitigations\n*   **Mitigation:** **Restrict Registry Permissions** (M1024)\n    *   **Techniques Mitigated:**\n        *   Clear Network Connection History and Configurations (T1070.007)\n        *   Modify Registry (T1112)\n\n### Summary Table\n\n| Category | Mitigation Name (ID) | Techniques Mitigated |\n| :--- | :--- | :--- |\n| **Credential** | Active Directory Configuration (M1015) | Cached Domain Credentials (T1003.005), DCSync (T1003.006) |\n| **Credential** | Restrict Registry Permissions (M1024) | Clear Network Connection History and Configurations (T1070.007), Modify Registry (T1112) |\n| **Active Directory** | Active Directory Configuration (M1015) | Cached Domain Credentials (T1003.005), DCSync (T1003.006) |\n| **Web-Content** | Restrict Web-Based Content (M1021) | *(Details not fully specified in source snippets)* |\n| **Registry** | Restrict Registry Permissions (M1024) | Clear Network Connection History and Configurations (T1070.007), Modify Registry (T1112) |\n\n*Note: Some mitigations like \"Application Developer Guidance\" (M1013) and \"User Training\" (M1017) were found in the search results but are not primarily categorized under the four specific technical domains requested (Credential, AD, Web-Content, Registry) in the context of direct technique mitigation for those categories.*\n\n<details><summary>🔎 Retrieved context (1 source)</summary>\n\n**1. 🤖 Agent trace**\n\n> **Step 1.** **Thought:** To answer this question accurately, I need to search the document corpus for specific mitigation strategies related to the four categories you mentioned: **Credential**, **Active Directory**, **Web-Content**, and **Registry**.\n\nI will perform separate searches for each category to identify the relevant mitigations and the specific techniques they mitigate.\n\n**Action:** `search_vectors(mitigations for credential access techniques)`\n\n**Observation:** - cyber_threat_intel/046-t1003.md: # OS Credential Dumping\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1003\nSTIX ID: attack-pattern--0a3ead4e-6d47-4ccb-854c-a6a4f9d96b22\n\nDescription:\nAdversari\n- cyber_threat_intel/048-t1003-002.md: # Security Account Manage\n\n**Step 2.** **Action:** `search_vectors(mitigations for Active Directory attacks techniques)`\n\n**Observation:** - cyber_threat_intel/052-m1015.md: - Active Directory Configuration -> mitigates -> Cached Domain Credentials (T1003.005)\n- Active Directory Configuration -> mitigates -> DCSync (T1003.006)\n- Active Directory Configuration -> mitigates\n- cyber_threat_intel/052-m1015.md: # Active Directory Configurat\n\n**Step 3.** **Action:** `search_vectors(mitigations for web content delivery or exploitation techniques)`\n\n**Observation:** - cyber_threat_intel/058-m1021.md: # Restrict Web-Based Content\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1021\nSTIX ID: course-of-action--21da4fd4-27ad-4e9c-b93d-0b9b14d02c96\n\nDescription:\n\n- cyber_threat_intel/051-m1013.md: # Application Developer Guida\n\n**Step 4.** **Action:** `search_vectors(mitigations for registry modification or access techniques)`\n\n**Observation:** - cyber_threat_intel/060-m1024.md: # Restrict Registry Permissions\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1024\nSTIX ID: course-of-action--a2c36a5d-4058-475e-8e77-fff75e50d3b9\n\nDescriptio\n- cyber_threat_intel/048-t1003-002.md: # Security Account Manage\n\n</details>\n\n---\n📊 1.3s · 0 chunks · 7 LLM calls · 0 cloud",
      "answer": "Based on the search results, here are the mitigations that cover credential, Active Directory, web-content, or registry-related techniques and the specific techniques they mitigate:\n\n### 1. Credential-Related Mitigations\n*   **Mitigation:** **Active Directory Configuration** (M1015)\n    *   **Techniques Mitigated:**\n        *   Cached Domain Credentials (T1003.005)\n        *   DCSync (T1003.006)\n*   **Mitigation:** **Restrict Registry Permissions** (M1024)\n    *   **Techniques Mitigated:**\n        *   Clear Network Connection History and Configurations (T1070.007)\n        *   Modify Registry (T1112)\n\n### 2. Active Directory-Related Mitigations\n*   **Mitigation:** **Active Directory Configuration** (M1015)\n    *   **Techniques Mitigated:**\n        *   Cached Domain Credentials (T1003.005)\n        *   DCSync (T1003.006)\n*   **Mitigation:** **User Account Management** (M1018)\n    *   *(Note: While listed in the search results, the specific techniques mitigated by M1018 were not fully detailed in the snippet provided, but it is a key AD-related mitigation.)*\n\n### 3. Web-Content-Related Mitigations\n*   **Mitigation:** **Restrict Web-Based Content** (M1021)\n    *   *(Note: The specific techniques mitigated by M1021 were not fully detailed in the snippet provided, but it is the primary mitigation for web-content techniques.)*\n\n### 4. Registry-Related Mitigations\n*   **Mitigation:** **Restrict Registry Permissions** (M1024)\n    *   **Techniques Mitigated:**\n        *   Clear Network Connection History and Configurations (T1070.007)\n        *   Modify Registry (T1112)\n\n### Summary Table\n\n| Category | Mitigation Name (ID) | Techniques Mitigated |\n| :--- | :--- | :--- |\n| **Credential** | Active Directory Configuration (M1015) | Cached Domain Credentials (T1003.005), DCSync (T1003.006) |\n| **Credential** | Restrict Registry Permissions (M1024) | Clear Network Connection History and Configurations (T1070.007), Modify Registry (T1112) |\n| **Active Directory** | Active Directory Configuration (M1015) | Cached Domain Credentials (T1003.005), DCSync (T1003.006) |\n| **Web-Content** | Restrict Web-Based Content (M1021) | *(Details not fully specified in source snippets)* |\n| **Registry** | Restrict Registry Permissions (M1024) | Clear Network Connection History and Configurations (T1070.007), Modify Registry (T1112) |\n\n*Note: Some mitigations like \"Application Developer Guidance\" (M1013) and \"User Training\" (M1017) were found in the search results but are not primarily categorized under the four specific technical domains requested (Credential, AD, Web-Content, Registry) in the context of direct technique mitigation for those categories.*",
      "sources": [
        {
          "title": "🤖 Agent trace",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 1.2735825009986002,
        "chunks": 0,
        "llm_calls": 7,
        "cloud_calls": 0
      },
      "approach_metadata": {
        "adaptive": {
          "route": "complex",
          "approach": "agentic-rag"
        }
      }
    },
    {
      "query_id": "cyber_mitigation_coverage",
      "model": "lazy-graph-rag",
      "base_model": "lazy-graph-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 4.8,
      "raw": "Based on the context provided, the following mitigations cover credential, Active Directory, or registry-related techniques:\n\n**1. Password Policies (M1027)**\n*   **Mitigates:** NTDS (T1003.003) - Accessing or copying the Active Directory domain database.\n*   **Mitigates:** LSA Secrets (T1003.004) - Accessing Local Security Authority secrets stored in the registry.\n\n**2. Privileged Account Management (M1026)**\n*   **Mitigates:** LSA Secrets (T1003.004) - Accessing Local Security Authority secrets stored in the registry.\n\n**3. Encrypt Sensitive Information (M1041)**\n*   **Mitigates:** OS Credential Dumping (T1003) - The general technique of dumping credentials from OS caches, memory, or structures.\n\n<details><summary>🔎 Retrieved context (8 sources)</summary>\n\n**1. cyber_threat_intel/049-t1003-003.md** · score 76.000\n\n> # NTDS\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1003.003\nSTIX ID: attack-pattern--edf91964-b26e-4b4a-9600-ccacd7d7df24\n\nDescription:\nAdversaries may attempt to access or create a copy of the Acti\n\n**2. cyber_threat_intel/048-t1003-002.md** · score 29.375\n\n> # Security Account Manager\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1003.002\nSTIX ID: attack-pattern--1644e709-12d2-41e5-a60f-3470991f5011\n\nDescription:\nAdversaries may attempt to extract credent\n\n**3. cyber_threat_intel/050-t1003-004.md** · score 28.000\n\n> # LSA Secrets\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1003.004\nSTIX ID: attack-pattern--1ecfdab8-7d59-4c98-95d4-dc41970f57fc\n\nDescription:\nAdversaries with SYSTEM access to a host may attempt to\n\n**4. cyber_threat_intel/046-t1003.md** · score 25.000\n\n> # OS Credential Dumping\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1003\nSTIX ID: attack-pattern--0a3ead4e-6d47-4ccb-854c-a6a4f9d96b22\n\nDescription:\nAdversaries may attempt to dump credentials to ob\n\n**5. cyber_threat_intel/027-s0011.md** · score 21.000\n\n> # Taidoor\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: malware\nATT&CK ID: S0011\nSTIX ID: malware--b143dfa4-e944-43ff-8429-bfffc308c517\n\nDescription:\n[Taidoor](https://attack.mitre.org/software/S0011) is a remote access trojan \n\n**6. cyber_threat_intel/029-s0013.md** · score 21.000\n\n> # PlugX\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: malware\nATT&CK ID: S0013\nSTIX ID: malware--64fa0de0-6240-41f4-8638-f4ca7ed528fd\n\nDescription:\n[PlugX](https://attack.mitre.org/software/S0013) is a remote access tool (RAT) \n\n**7. cyber_threat_intel/032-s0005.md** · score 19.000\n\n> # Windows Credential Editor\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: tool\nATT&CK ID: S0005\nSTIX ID: tool--242f3da3-4425-4d11-8f5c-b842886da966\n\nDescription:\n[Windows Credential Editor](https://attack.mitre.org/software/S00\n\n**8. cyber_threat_intel/043-t1001-002.md** · score 19.000\n\n> # Steganography\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1001.002\nSTIX ID: attack-pattern--eec23884-3fa1-4d8a-ac50-6f104d51e235\n\nDescription:\nAdversaries may use steganographic techniques to hide\n\n</details>\n\n---\n📊 4.8s · 8 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the context provided, the following mitigations cover credential, Active Directory, or registry-related techniques:\n\n**1. Password Policies (M1027)**\n*   **Mitigates:** NTDS (T1003.003) - Accessing or copying the Active Directory domain database.\n*   **Mitigates:** LSA Secrets (T1003.004) - Accessing Local Security Authority secrets stored in the registry.\n\n**2. Privileged Account Management (M1026)**\n*   **Mitigates:** LSA Secrets (T1003.004) - Accessing Local Security Authority secrets stored in the registry.\n\n**3. Encrypt Sensitive Information (M1041)**\n*   **Mitigates:** OS Credential Dumping (T1003) - The general technique of dumping credentials from OS caches, memory, or structures.",
      "sources": [
        {
          "title": "cyber_threat_intel/049-t1003-003.md",
          "score": 76.0
        },
        {
          "title": "cyber_threat_intel/048-t1003-002.md",
          "score": 29.375
        },
        {
          "title": "cyber_threat_intel/050-t1003-004.md",
          "score": 28.0
        },
        {
          "title": "cyber_threat_intel/046-t1003.md",
          "score": 25.0
        },
        {
          "title": "cyber_threat_intel/027-s0011.md",
          "score": 21.0
        },
        {
          "title": "cyber_threat_intel/029-s0013.md",
          "score": 21.0
        },
        {
          "title": "cyber_threat_intel/032-s0005.md",
          "score": 19.0
        },
        {
          "title": "cyber_threat_intel/043-t1001-002.md",
          "score": 19.0
        }
      ],
      "metrics": {
        "seconds": 4.809887044000789,
        "chunks": 8,
        "llm_calls": 2,
        "cloud_calls": 0
      },
      "approach_metadata": {
        "lazy_graph": {
          "experimental": true,
          "cache_hit": true,
          "index_seconds": 0.011485,
          "graph_chunks": 66,
          "graph_concepts": 762,
          "graph_edges": 13949,
          "relevance_tests": 24,
          "relevance_budget": 24,
          "seed_k": 8,
          "max_context_chunks": 8,
          "llm_index_calls": 0,
          "cache_namespace": "RagBase_cyber_threat_intel.concepts-24"
        }
      }
    },
    {
      "query_id": "cyber_campaign_timeline_context",
      "model": "vanilla-rag",
      "base_model": "vanilla-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 8.4,
      "raw": "Based on the provided context, here is the comparison of the four campaigns:\n\n**1. Timeframe**\n*   **Frankenstein:** Early 2019.\n*   **Operation CuckooBees:** At least 2019 through May 2022 (ongoing as of that date).\n*   **Operation Honeybee:** Late 2017 through early 2018.\n*   **Night Dragon:** The specific timeframe is not mentioned in the context, only that it was a campaign involving unidentified threat actors.\n\n**2. Target Context**\n*   **Frankenstein:** Highly-targeted; no specific industry or geographic targets are listed, though it relied on open-source tools.\n*   **Operation CuckooBees:** Technology and manufacturing companies in East Asia, Western Europe, and North America. The goal was the theft of proprietary information, R&D documents, source code, and blueprints.\n*   **Operation Honeybee:** Humanitarian aid and inter-Korean affairs organizations. Initially targeted South Korea, expanding to Vietnam, Singapore, Japan, Indonesia, Argentina, and Canada.\n*   **Night Dragon:** Oil, energy, and petrochemical companies, along with individuals and executives in Kazakhstan, Taiwan, Greece, and the United States. The goal was searching for information related to oil and gas field production systems, financials, and collecting data from SCADA systems.\n\n**3. Techniques or Tools Used**\n*   **Frankenstein:** Relied primarily on open-source tools, including Empire. Techniques included Process Discovery, System Information Discovery, Command Obfuscation, Automated Exfiltration, Scheduled Task, Malicious File, Spearphishing Attachment, Ingress Tool Transfer, PowerShell, Security Software Discovery, and Visual Basic.\n*   **Operation CuckooBees:** Used techniques such as Peripheral Device Discovery, dsquery, Remote System Discovery, Windows Service, Archive via Utility, External Remote Services, File and Directory Discovery, System Information Discovery, System Time Discovery, Domain Accounts, System Network Configuration Discovery, and Password Policy Discovery.\n*   **Operation Honeybee:** Used Email Accounts, SYSCON, File and Directory Discovery, Native API, File Deletion, Local Data Staging, Domains, Encrypted/Encoded File, Code Signing, Exfiltration Over C2 Channel, Reg, and Modify Registry.\n*   **Night Dragon:** Used Domain Accounts, gsecdump, Upload Malware, Malware, ASPXSpy, zwShell, Spearphishing Link, Malicious Link, External Remote Services, Data from Local System, Windows Command Shell, and Software Packing.\n\n<details><summary>🔎 Retrieved context (5 sources)</summary>\n\n**1. cyber_threat_intel/019-c0012.md**\n\n> # Operation CuckooBees\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0012\nSTIX ID: campaign--93c23946-49af-41f4-ac03-40f9ffc7419b\n\nDescription:\n[Operation CuckooBees](https://attack.mitre.org/campaigns/C001\n\n**2. cyber_threat_intel/012-c0002.md**\n\n> # Night Dragon\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0002\nSTIX ID: campaign--ae407e32-87e0-4d92-8705-3ae25d504d8a\n\nDescription:\n[Night Dragon](https://attack.mitre.org/campaigns/C0002) was a cyber e\n\n**3. cyber_threat_intel/015-c0006.md**\n\n> # Operation Honeybee\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0006\nSTIX ID: campaign--4553292d-12c6-4a93-934d-12160370d4e0\n\nDescription:\n[Operation Honeybee](https://attack.mitre.org/campaigns/C0006) w\n\n**4. cyber_threat_intel/011-c0001.md**\n\n> # Frankenstein\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0001\nSTIX ID: campaign--26d9ebae-de59-427f-ae9a-349456bae4b1\n\nDescription:\n[Frankenstein](https://attack.mitre.org/campaigns/C0001) was described\n\n**5. cyber_threat_intel/020-c0013.md**\n\n> # Operation Sharpshooter\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0013\nSTIX ID: campaign--37764c78-2a99-46d1-a7ea-6454b9bf93a0\n\nDescription:\n[Operation Sharpshooter](https://attack.mitre.org/campaigns/\n\n</details>\n\n---\n📊 8.3s · 5 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the provided context, here is the comparison of the four campaigns:\n\n**1. Timeframe**\n*   **Frankenstein:** Early 2019.\n*   **Operation CuckooBees:** At least 2019 through May 2022 (ongoing as of that date).\n*   **Operation Honeybee:** Late 2017 through early 2018.\n*   **Night Dragon:** The specific timeframe is not mentioned in the context, only that it was a campaign involving unidentified threat actors.\n\n**2. Target Context**\n*   **Frankenstein:** Highly-targeted; no specific industry or geographic targets are listed, though it relied on open-source tools.\n*   **Operation CuckooBees:** Technology and manufacturing companies in East Asia, Western Europe, and North America. The goal was the theft of proprietary information, R&D documents, source code, and blueprints.\n*   **Operation Honeybee:** Humanitarian aid and inter-Korean affairs organizations. Initially targeted South Korea, expanding to Vietnam, Singapore, Japan, Indonesia, Argentina, and Canada.\n*   **Night Dragon:** Oil, energy, and petrochemical companies, along with individuals and executives in Kazakhstan, Taiwan, Greece, and the United States. The goal was searching for information related to oil and gas field production systems, financials, and collecting data from SCADA systems.\n\n**3. Techniques or Tools Used**\n*   **Frankenstein:** Relied primarily on open-source tools, including Empire. Techniques included Process Discovery, System Information Discovery, Command Obfuscation, Automated Exfiltration, Scheduled Task, Malicious File, Spearphishing Attachment, Ingress Tool Transfer, PowerShell, Security Software Discovery, and Visual Basic.\n*   **Operation CuckooBees:** Used techniques such as Peripheral Device Discovery, dsquery, Remote System Discovery, Windows Service, Archive via Utility, External Remote Services, File and Directory Discovery, System Information Discovery, System Time Discovery, Domain Accounts, System Network Configuration Discovery, and Password Policy Discovery.\n*   **Operation Honeybee:** Used Email Accounts, SYSCON, File and Directory Discovery, Native API, File Deletion, Local Data Staging, Domains, Encrypted/Encoded File, Code Signing, Exfiltration Over C2 Channel, Reg, and Modify Registry.\n*   **Night Dragon:** Used Domain Accounts, gsecdump, Upload Malware, Malware, ASPXSpy, zwShell, Spearphishing Link, Malicious Link, External Remote Services, Data from Local System, Windows Command Shell, and Software Packing.",
      "sources": [
        {
          "title": "cyber_threat_intel/019-c0012.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/012-c0002.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/015-c0006.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/011-c0001.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/020-c0013.md",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 8.341710254000645,
        "chunks": 5,
        "llm_calls": 2,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_campaign_timeline_context",
      "model": "hybrid-rag",
      "base_model": "hybrid-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 25.5,
      "raw": "Based on the provided context, I can only compare **Frankenstein**, **Operation CuckooBees**, and **Night Dragon**. The context does not contain any information regarding **Operation Honeybee**; therefore, it is insufficient to include it in the comparison.\n\nHere is the comparison of the three available campaigns:\n\n### 1. Timeframe\n*   **Frankenstein:** Early 2019.\n*   **Operation CuckooBees:** Since at least 2019 (ongoing as of May 2022).\n*   **Night Dragon:** The specific timeframe is not mentioned in the context, only that it was a past campaign.\n\n### 2. Target Context\n*   **Frankenstein:** Highly-targeted campaign; no specific industry or geographic targets are listed in the description.\n*   **Operation CuckooBees:** Technology and manufacturing companies in East Asia, Western Europe, and North America. The goal was the theft of proprietary information, R&D documents, source code, and blueprints.\n*   **Night Dragon:** Oil, energy, and petrochemical companies, along with individuals and executives in Kazakhstan, Taiwan, Greece, and the United States. The goal was searching for information related to oil and gas field production systems, financials, and data from SCADA systems.\n\n### 3. Techniques or Tools Used\n*   **Frankenstein:**\n    *   **Tools:** Empire (S0363).\n    *   **Techniques:** Process Discovery (T1057), System Information Discovery (T1082), Command Obfuscation (T1027.010), Automated Exfiltration (T1020), Scheduled Task (T1053.005), Malicious File (T1204.002), Spearphishing Attachment (T1566.001), Ingress Tool Transfer (T1105), PowerShell (T1059.001), Security Software Discovery (T1518.001), Visual Basic (T1059.005).\n*   **Operation CuckooBees:**\n    *   **Tools:** dsquery (S0105).\n    *   **Techniques:** Peripheral Device Discovery (T1120), Remote System Discovery (T1018), Windows Service (T1543.003), Archive via Utility (T1560.001), External Remote Services (T1133), File and Directory Discovery (T1083), System Information Discovery (T1082), System Time Discovery (T1124), Domain Accounts (T1078.002), System Network Configuration Discovery (T1016), Password Policy Discovery (T1201).\n*   **Night Dragon:**\n    *   **Tools:** gsecdump (S0008), ASPXSpy (S0073), zwShell (S0350).\n    *   **Techniques:** Domain Accounts (T1078.002), Upload Malware (T1608.001), Malware (T1588.001), Spearphishing Link (T1566.002), Malicious Link (T1204.001), External Remote Services (T1133), Data from Local System (T1005), Windows Command Shell (T1059.003), Software Packing (T1027.002).\n\n<details><summary>🔎 Retrieved context (5 sources)</summary>\n\n**1. cyber_threat_intel/011-c0001.md** · score 0.155\n\n> # Frankenstein\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0001\nSTIX ID: campaign--26d9ebae-de59-427f-ae9a-349456bae4b1\n\nDescription:\n[Frankenstein](https://attack.mitre.org/campaigns/C0001) was described\n\n**2. cyber_threat_intel/019-c0012.md** · score 0.106\n\n> # Operation CuckooBees\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0012\nSTIX ID: campaign--93c23946-49af-41f4-ac03-40f9ffc7419b\n\nDescription:\n[Operation CuckooBees](https://attack.mitre.org/campaigns/C001\n\n**3. cyber_threat_intel/056-m1019.md** · score 0.075\n\n> # Threat Intelligence Program\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1019\nSTIX ID: course-of-action--874c0166-e407-45c2-a1d9-e4e3a6570fd8\n\nDescription:\nA Threat Intelligence Program enables o\n\n**4. cyber_threat_intel/012-c0002.md** · score 0.056\n\n> # Night Dragon\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0002\nSTIX ID: campaign--ae407e32-87e0-4d92-8705-3ae25d504d8a\n\nDescription:\n[Night Dragon](https://attack.mitre.org/campaigns/C0002) was a cyber e\n\n**5. cyber_threat_intel/054-m1017.md** · score 0.051\n\n> # User Training\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1017\nSTIX ID: course-of-action--2a4f6c11-a4a7-4cb9-b0ef-6ae1bb3a718a\n\nDescription:\nUser Training involves educating employees and contra\n\n</details>\n\n---\n📊 25.5s · 5 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the provided context, I can only compare **Frankenstein**, **Operation CuckooBees**, and **Night Dragon**. The context does not contain any information regarding **Operation Honeybee**; therefore, it is insufficient to include it in the comparison.\n\nHere is the comparison of the three available campaigns:\n\n### 1. Timeframe\n*   **Frankenstein:** Early 2019.\n*   **Operation CuckooBees:** Since at least 2019 (ongoing as of May 2022).\n*   **Night Dragon:** The specific timeframe is not mentioned in the context, only that it was a past campaign.\n\n### 2. Target Context\n*   **Frankenstein:** Highly-targeted campaign; no specific industry or geographic targets are listed in the description.\n*   **Operation CuckooBees:** Technology and manufacturing companies in East Asia, Western Europe, and North America. The goal was the theft of proprietary information, R&D documents, source code, and blueprints.\n*   **Night Dragon:** Oil, energy, and petrochemical companies, along with individuals and executives in Kazakhstan, Taiwan, Greece, and the United States. The goal was searching for information related to oil and gas field production systems, financials, and data from SCADA systems.\n\n### 3. Techniques or Tools Used\n*   **Frankenstein:**\n    *   **Tools:** Empire (S0363).\n    *   **Techniques:** Process Discovery (T1057), System Information Discovery (T1082), Command Obfuscation (T1027.010), Automated Exfiltration (T1020), Scheduled Task (T1053.005), Malicious File (T1204.002), Spearphishing Attachment (T1566.001), Ingress Tool Transfer (T1105), PowerShell (T1059.001), Security Software Discovery (T1518.001), Visual Basic (T1059.005).\n*   **Operation CuckooBees:**\n    *   **Tools:** dsquery (S0105).\n    *   **Techniques:** Peripheral Device Discovery (T1120), Remote System Discovery (T1018), Windows Service (T1543.003), Archive via Utility (T1560.001), External Remote Services (T1133), File and Directory Discovery (T1083), System Information Discovery (T1082), System Time Discovery (T1124), Domain Accounts (T1078.002), System Network Configuration Discovery (T1016), Password Policy Discovery (T1201).\n*   **Night Dragon:**\n    *   **Tools:** gsecdump (S0008), ASPXSpy (S0073), zwShell (S0350).\n    *   **Techniques:** Domain Accounts (T1078.002), Upload Malware (T1608.001), Malware (T1588.001), Spearphishing Link (T1566.002), Malicious Link (T1204.001), External Remote Services (T1133), Data from Local System (T1005), Windows Command Shell (T1059.003), Software Packing (T1027.002).",
      "sources": [
        {
          "title": "cyber_threat_intel/011-c0001.md",
          "score": 0.15501662
        },
        {
          "title": "cyber_threat_intel/019-c0012.md",
          "score": 0.10567952
        },
        {
          "title": "cyber_threat_intel/056-m1019.md",
          "score": 0.074627385
        },
        {
          "title": "cyber_threat_intel/012-c0002.md",
          "score": 0.055912506
        },
        {
          "title": "cyber_threat_intel/054-m1017.md",
          "score": 0.050514206
        }
      ],
      "metrics": {
        "seconds": 25.464424137000606,
        "chunks": 5,
        "llm_calls": 2,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_campaign_timeline_context",
      "model": "contextual-rag",
      "base_model": "contextual-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 28.4,
      "raw": "Based on the provided context, here is the comparison of the four campaigns:\n\n**1. Timeframe**\n*   **Frankenstein:** Early 2019.\n*   **Operation CuckooBees:** Since at least 2019 (ongoing as of May 2022).\n*   **Night Dragon:** The text does not specify a timeframe.\n*   **Operation Honeybee:** Late 2017 through early 2018.\n\n**2. Target Context**\n*   **Frankenstein:** Described generally as a \"highly-targeted operation\" by moderately sophisticated actors; specific target sectors or regions are not listed in the description.\n*   **Operation CuckooBees:** Technology and manufacturing companies in East Asia, Western Europe, and North America. The goal was the theft of proprietary information, R&D documents, source code, and blueprints.\n*   **Night Dragon:** Oil, energy, and petrochemical companies, along with individuals and executives in Kazakhstan, Taiwan, Greece, and the United States. Actors searched for information related to oil and gas field production systems, financials, and SCADA system data.\n*   **Operation Honeybee:** Humanitarian aid and inter-Korean affairs organizations across South Korea, Vietnam, Singapore, Japan, Indonesia, Argentina, and Canada.\n\n**3. Techniques or Tools Used**\n*   **Frankenstein:**\n    *   *Tools:* Empire (S0363).\n    *   *Techniques:* Process Discovery (T1057), System Information Discovery (T1082), Command Obfuscation (T1027.010), Automated Exfiltration (T1020), Scheduled Task (T1053.005), Malicious File (T1204.002), Spearphishing Attachment (T1566.001), Ingress Tool Transfer (T1105), PowerShell (T1059.001), Security Software Discovery (T1518.001), Visual Basic (T1059.005).\n*   **Operation CuckooBees:**\n    *   *Tools:* dsquery (S0105).\n    *   *Techniques:* Peripheral Device Discovery (T1120), Remote System Discovery (T1018), Windows Service (T1543.003), Archive via Utility (T1560.001), External Remote Services (T1133), File and Directory Discovery (T1083), System Information Discovery (T1082), System Time Discovery (T1124), Domain Accounts (T1078.002), System Network Configuration Discovery (T1016), Password Policy Discovery (T1201).\n*   **Night Dragon:**\n    *   *Tools:* gsecdump (S0008), ASPXSpy (S0073), zwShell (S0350), Malware (T1588.001).\n    *   *Techniques:* Domain Accounts (T1078.002), Upload Malware (T1608.001), Spearphishing Link (T1566.002), Malicious Link (T1204.001), External Remote Services (T1133), Data from Local System (T1005), Windows Command Shell (T1059.003), Software Packing (T1027.002).\n*   **Operation Honeybee:**\n    *   *Tools:* SYSCON (S0464), Reg (S0075).\n    *   *Techniques:* Email Accounts (T1585.002), File and Directory Discovery (T1083), Native API (T1106), File Deletion (T1070.004), Local Data Staging (T1074.001), Domains (T1583.001), Encrypted/Encoded File (T1027.013), Code Signing (T1553.002), Exfiltration Over C2 Channel (T1041), Modify Registry (T1112).\n\n<details><summary>🔎 Retrieved context (5 sources)</summary>\n\n**1. cyber_threat_intel/011-c0001.md** · score 0.161\n\n> This chunk details the \"Frankenstein\" campaign (C0001), a highly-targeted operation from early 2019 where threat actors utilized open-source tools like Empire to execute various tactics and techniques. It provides the specific MITRE ATT&CK \n\n**2. cyber_threat_intel/019-c0012.md** · score 0.114\n\n> This chunk details the specific MITRE ATT&CK techniques and tactics employed by the Operation CuckooBees cyber espionage campaign, as defined in the MITRE ATT&CK Enterprise STIX bundle. It provides the technical mapping of the group's activ\n\n**3. cyber_threat_intel/056-m1019.md** · score 0.092\n\n> This section details the MITRE ATT&CK mitigation strategy M1019 for establishing a Threat Intelligence Program, outlining specific implementation measures and associated tools. It further defines the program's capability to mitigate various\n\n**4. cyber_threat_intel/012-c0002.md** · score 0.077\n\n> This text provides a detailed overview of the Night Dragon cyber espionage campaign, including its target sectors, geographic scope, and suspected origin. It further lists the specific techniques, tools, and malware utilized by the threat a\n\n**5. cyber_threat_intel/015-c0006.md** · score 0.068\n\n> This section details the MITRE ATT&CK campaign C0006, known as Operation Honeybee, which targeted humanitarian and inter-Korean affairs organizations across multiple countries from late 2017 to early 2018. It outlines the specific tactics a\n\n</details>\n\n---\n📊 28.3s · 5 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the provided context, here is the comparison of the four campaigns:\n\n**1. Timeframe**\n*   **Frankenstein:** Early 2019.\n*   **Operation CuckooBees:** Since at least 2019 (ongoing as of May 2022).\n*   **Night Dragon:** The text does not specify a timeframe.\n*   **Operation Honeybee:** Late 2017 through early 2018.\n\n**2. Target Context**\n*   **Frankenstein:** Described generally as a \"highly-targeted operation\" by moderately sophisticated actors; specific target sectors or regions are not listed in the description.\n*   **Operation CuckooBees:** Technology and manufacturing companies in East Asia, Western Europe, and North America. The goal was the theft of proprietary information, R&D documents, source code, and blueprints.\n*   **Night Dragon:** Oil, energy, and petrochemical companies, along with individuals and executives in Kazakhstan, Taiwan, Greece, and the United States. Actors searched for information related to oil and gas field production systems, financials, and SCADA system data.\n*   **Operation Honeybee:** Humanitarian aid and inter-Korean affairs organizations across South Korea, Vietnam, Singapore, Japan, Indonesia, Argentina, and Canada.\n\n**3. Techniques or Tools Used**\n*   **Frankenstein:**\n    *   *Tools:* Empire (S0363).\n    *   *Techniques:* Process Discovery (T1057), System Information Discovery (T1082), Command Obfuscation (T1027.010), Automated Exfiltration (T1020), Scheduled Task (T1053.005), Malicious File (T1204.002), Spearphishing Attachment (T1566.001), Ingress Tool Transfer (T1105), PowerShell (T1059.001), Security Software Discovery (T1518.001), Visual Basic (T1059.005).\n*   **Operation CuckooBees:**\n    *   *Tools:* dsquery (S0105).\n    *   *Techniques:* Peripheral Device Discovery (T1120), Remote System Discovery (T1018), Windows Service (T1543.003), Archive via Utility (T1560.001), External Remote Services (T1133), File and Directory Discovery (T1083), System Information Discovery (T1082), System Time Discovery (T1124), Domain Accounts (T1078.002), System Network Configuration Discovery (T1016), Password Policy Discovery (T1201).\n*   **Night Dragon:**\n    *   *Tools:* gsecdump (S0008), ASPXSpy (S0073), zwShell (S0350), Malware (T1588.001).\n    *   *Techniques:* Domain Accounts (T1078.002), Upload Malware (T1608.001), Spearphishing Link (T1566.002), Malicious Link (T1204.001), External Remote Services (T1133), Data from Local System (T1005), Windows Command Shell (T1059.003), Software Packing (T1027.002).\n*   **Operation Honeybee:**\n    *   *Tools:* SYSCON (S0464), Reg (S0075).\n    *   *Techniques:* Email Accounts (T1585.002), File and Directory Discovery (T1083), Native API (T1106), File Deletion (T1070.004), Local Data Staging (T1074.001), Domains (T1583.001), Encrypted/Encoded File (T1027.013), Code Signing (T1553.002), Exfiltration Over C2 Channel (T1041), Modify Registry (T1112).",
      "sources": [
        {
          "title": "cyber_threat_intel/011-c0001.md",
          "score": 0.16054352
        },
        {
          "title": "cyber_threat_intel/019-c0012.md",
          "score": 0.11407785
        },
        {
          "title": "cyber_threat_intel/056-m1019.md",
          "score": 0.092305824
        },
        {
          "title": "cyber_threat_intel/012-c0002.md",
          "score": 0.07747084
        },
        {
          "title": "cyber_threat_intel/015-c0006.md",
          "score": 0.0682627
        }
      ],
      "metrics": {
        "seconds": 28.345717804000742,
        "chunks": 5,
        "llm_calls": 2,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_campaign_timeline_context",
      "model": "graph-rag",
      "base_model": "graph-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 25.8,
      "raw": "Based on the provided context, here is a comparison of the four cyber espionage campaigns: Frankenstein, Operation CuckooBees, Operation Honeybee, and Night Dragon.\n\n### 1. Frankenstein\n\n**Timeframe**\nFrankenstein was conducted in **early 2019** [Reference 4].\n\n**Target Context**\nThe provided text does not specify the geographic regions or specific industries targeted by Frankenstein, other than describing it as a \"highly-targeted campaign\" conducted by moderately sophisticated and highly resourceful threat actors [Reference 4].\n\n**Techniques and Tools**\nFrankenstein is characterized by its heavy reliance on **open-source tools**, piecing together unrelated components (hence the name). Key techniques and tools include:\n*   **Empire**: An open-source tool used for conducting malicious activities [Reference 4].\n*   **Command Execution**: Utilized **PowerShell** and **Visual Basic** [Reference 4].\n*   **Discovery**: Employed System Information Discovery, Process Discovery, and Security Software Discovery [Reference 4].\n*   **Persistence and Delivery**: Used **Spearphishing Attachments**, **Malicious Files**, **Scheduled Tasks**, and **Ingress Tool Transfer** to bring tools into the environment [Reference 4].\n*   **Exfiltration and Obfuscation**: Utilized **Automated Exfiltration** and **Command Obfuscation** to hide intent and transfer data [Reference 4].\n\n### 2. Operation CuckooBees\n\n**Timeframe**\nThis campaign has been ongoing since **at least 2019**, with notes indicating it was still active as of May 2022 [Reference 1].\n\n**Target Context**\nOperation CuckooBees targeted technology and manufacturing companies located in **East Asia, Western Europe, and North America** [Reference 1]. The primary goal was the theft of proprietary information, research and development documents, source code, and blueprints for various technologies [Reference 1]. It is affiliated with actors from **Winnti Group**, **APT41**, and **BARIUM** [Reference 1].\n\n**Techniques and Tools**\nThe campaign employs a wide array of reconnaissance and persistence techniques:\n*   **Discovery**: Used System Information Discovery, System Time Discovery, Remote System Discovery, File and Directory Discovery, Peripheral Device Discovery, and System Network Configuration Discovery [Reference 1].\n*   **Credential Access**: Utilized **Domain Accounts**, **Password Policy Discovery**, and **dsquery** (to query Active Directory objects) [Reference 1].\n*   **Persistence**: Used **Windows Service** for persistence or privilege escalation [Reference 1].\n*   **Lateral Movement and Exfiltration**: Used **External Remote Services** for lateral movement and data exfiltration, and **Archive via Utility** to compress/encrypt stolen data [Reference 1].\n\n### 3. Operation Honeybee\n\n**Timeframe**\nThe campaign targeted organizations from at least **late 2017 through early 2018** [Reference 3].\n\n**Target Context**\nOperation Honeybee initially targeted humanitarian aid and inter-Korean affairs organizations in **South Korea**. It later expanded to include **Vietnam, Singapore, Japan, Indonesia, Argentina, and Canada** [Reference 3]. Researchers assessed the threat actors were likely Korean speakers based on metadata in lure documents and executables [Reference 3].\n\n**Techniques and Tools**\nThe campaign focused on espionage and data handling:\n*   **Tool Usage**: Utilized **SYSCON** and **Reg** (a Windows utility to interact with/extract from the Windows Registry) [Reference 3].\n*   **Registry Interaction**: Used **Modify Registry** techniques [Reference 3].\n*   **Data Handling**: Employed **Local Data Staging**, **File Deletion**, **Encrypted/Encoded Files**, and **Code Signing** [Reference 3].\n*   **Discovery**: Used **File and Directory Discovery** [Reference 3].\n*   **Exfiltration**: Utilized **Exfiltration Over C2 Channel** and established **Email Accounts** for operations [Reference 3].\n*   **Infrastructure**: Used **Domains** for operational infrastructure [Reference 3].\n\n### 4. Night Dragon\n\n**Timeframe**\nThe specific timeframe is not explicitly stated in the text, but it is described as a cyber espionage campaign that targeted specific industries (Reference 2). Other sources in the context link it to threat groups active around similar eras to CuckooBees or Honeybee, but no specific start/end dates are provided in the Night Dragon description itself.\n\n**Target Context**\nNight Dragon targeted **oil, energy, and petrochemical companies**, along with individuals and executives in **Kazakhstan, Taiwan, Greece, and the United States** [Reference 2]. The actors searched for information related to oil and gas field production systems, financials, and collected data from **SCADA systems** [Reference 2]. Security researchers assessed the campaign involved a threat group based in **China** [Reference 2].\n\n**Techniques and Tools**\nNight Dragon employed specific malware and credential dumping tools:\n*   **Tools**: Used **gsecdump** (for credential dumping), **ASPxSpy** (malware/tool), and **zwShell** [Reference 2].\n*   **Delivery**: Delivered malicious content via **Spearphishing Links** and **Malicious Links** [Reference 2].\n*   **Execution and Manipulation**: Used **Windows Command Shell**, **Software Packing**, and **Upload Malware** techniques [Reference 2].\n*   **Access and Data Collection**: Leveraged **Domain Accounts**, collected data from the **Local System**, and used **External Remote Services** for access [Reference 2].\n\n### Summary Comparison\n\n| Feature | Frankenstein | Operation CuckooBees | Operation Honeybee | Night Dragon |\n| :--- | :--- | :--- | :--- | :--- |\n| **Timeframe** | Early 2019 | Since at least 2019 (active May 2022) | Late 2017 – Early 2018 | Not explicitly stated |\n| **Primary Targets** | Highly-targeted (specifics not listed) | Tech/Manufacturing in East Asia, Western Europe, North America | Humanitarian/Aid organizations in SK, Vietnam, Singapore, Japan, Indonesia, Argentina, Canada | Oil/Energy/Petrochemical in Kazakhstan, Taiwan, Greece, US |\n| **Affiliated Groups** | Unidentified (resourceful actors) | Winnti Group, APT41, BARIUM | Unidentified (likely Korean speakers) | Unidentified (assessed as group based in China) |\n| **Key Tools/Techniques** | Empire, PowerShell, Visual Basic, Spearphishing Attachments | dsquery, Windows Service, Password Policy Discovery, Archive via Utility | Reg, SYSCON, Modify Registry, Exfiltration Over C2 Channel | gsecdump, ASPxSpy, zwShell, Software Packing, SCADA data collection |\n\n<details><summary>🔎 Retrieved context (1 source)</summary>\n\n**1. LightRAG knowledge graph**\n\n> Graph + vector dual retrieval (profile=graph-rag) over the corpus's extracted entities and relations.\n\n</details>\n\n---\n📊 25.8s · 0 chunks · 1 LLM call · 0 cloud",
      "answer": "Based on the provided context, here is a comparison of the four cyber espionage campaigns: Frankenstein, Operation CuckooBees, Operation Honeybee, and Night Dragon.\n\n### 1. Frankenstein\n\n**Timeframe**\nFrankenstein was conducted in **early 2019** [Reference 4].\n\n**Target Context**\nThe provided text does not specify the geographic regions or specific industries targeted by Frankenstein, other than describing it as a \"highly-targeted campaign\" conducted by moderately sophisticated and highly resourceful threat actors [Reference 4].\n\n**Techniques and Tools**\nFrankenstein is characterized by its heavy reliance on **open-source tools**, piecing together unrelated components (hence the name). Key techniques and tools include:\n*   **Empire**: An open-source tool used for conducting malicious activities [Reference 4].\n*   **Command Execution**: Utilized **PowerShell** and **Visual Basic** [Reference 4].\n*   **Discovery**: Employed System Information Discovery, Process Discovery, and Security Software Discovery [Reference 4].\n*   **Persistence and Delivery**: Used **Spearphishing Attachments**, **Malicious Files**, **Scheduled Tasks**, and **Ingress Tool Transfer** to bring tools into the environment [Reference 4].\n*   **Exfiltration and Obfuscation**: Utilized **Automated Exfiltration** and **Command Obfuscation** to hide intent and transfer data [Reference 4].\n\n### 2. Operation CuckooBees\n\n**Timeframe**\nThis campaign has been ongoing since **at least 2019**, with notes indicating it was still active as of May 2022 [Reference 1].\n\n**Target Context**\nOperation CuckooBees targeted technology and manufacturing companies located in **East Asia, Western Europe, and North America** [Reference 1]. The primary goal was the theft of proprietary information, research and development documents, source code, and blueprints for various technologies [Reference 1]. It is affiliated with actors from **Winnti Group**, **APT41**, and **BARIUM** [Reference 1].\n\n**Techniques and Tools**\nThe campaign employs a wide array of reconnaissance and persistence techniques:\n*   **Discovery**: Used System Information Discovery, System Time Discovery, Remote System Discovery, File and Directory Discovery, Peripheral Device Discovery, and System Network Configuration Discovery [Reference 1].\n*   **Credential Access**: Utilized **Domain Accounts**, **Password Policy Discovery**, and **dsquery** (to query Active Directory objects) [Reference 1].\n*   **Persistence**: Used **Windows Service** for persistence or privilege escalation [Reference 1].\n*   **Lateral Movement and Exfiltration**: Used **External Remote Services** for lateral movement and data exfiltration, and **Archive via Utility** to compress/encrypt stolen data [Reference 1].\n\n### 3. Operation Honeybee\n\n**Timeframe**\nThe campaign targeted organizations from at least **late 2017 through early 2018** [Reference 3].\n\n**Target Context**\nOperation Honeybee initially targeted humanitarian aid and inter-Korean affairs organizations in **South Korea**. It later expanded to include **Vietnam, Singapore, Japan, Indonesia, Argentina, and Canada** [Reference 3]. Researchers assessed the threat actors were likely Korean speakers based on metadata in lure documents and executables [Reference 3].\n\n**Techniques and Tools**\nThe campaign focused on espionage and data handling:\n*   **Tool Usage**: Utilized **SYSCON** and **Reg** (a Windows utility to interact with/extract from the Windows Registry) [Reference 3].\n*   **Registry Interaction**: Used **Modify Registry** techniques [Reference 3].\n*   **Data Handling**: Employed **Local Data Staging**, **File Deletion**, **Encrypted/Encoded Files**, and **Code Signing** [Reference 3].\n*   **Discovery**: Used **File and Directory Discovery** [Reference 3].\n*   **Exfiltration**: Utilized **Exfiltration Over C2 Channel** and established **Email Accounts** for operations [Reference 3].\n*   **Infrastructure**: Used **Domains** for operational infrastructure [Reference 3].\n\n### 4. Night Dragon\n\n**Timeframe**\nThe specific timeframe is not explicitly stated in the text, but it is described as a cyber espionage campaign that targeted specific industries (Reference 2). Other sources in the context link it to threat groups active around similar eras to CuckooBees or Honeybee, but no specific start/end dates are provided in the Night Dragon description itself.\n\n**Target Context**\nNight Dragon targeted **oil, energy, and petrochemical companies**, along with individuals and executives in **Kazakhstan, Taiwan, Greece, and the United States** [Reference 2]. The actors searched for information related to oil and gas field production systems, financials, and collected data from **SCADA systems** [Reference 2]. Security researchers assessed the campaign involved a threat group based in **China** [Reference 2].\n\n**Techniques and Tools**\nNight Dragon employed specific malware and credential dumping tools:\n*   **Tools**: Used **gsecdump** (for credential dumping), **ASPxSpy** (malware/tool), and **zwShell** [Reference 2].\n*   **Delivery**: Delivered malicious content via **Spearphishing Links** and **Malicious Links** [Reference 2].\n*   **Execution and Manipulation**: Used **Windows Command Shell**, **Software Packing**, and **Upload Malware** techniques [Reference 2].\n*   **Access and Data Collection**: Leveraged **Domain Accounts**, collected data from the **Local System**, and used **External Remote Services** for access [Reference 2].\n\n### Summary Comparison\n\n| Feature | Frankenstein | Operation CuckooBees | Operation Honeybee | Night Dragon |\n| :--- | :--- | :--- | :--- | :--- |\n| **Timeframe** | Early 2019 | Since at least 2019 (active May 2022) | Late 2017 – Early 2018 | Not explicitly stated |\n| **Primary Targets** | Highly-targeted (specifics not listed) | Tech/Manufacturing in East Asia, Western Europe, North America | Humanitarian/Aid organizations in SK, Vietnam, Singapore, Japan, Indonesia, Argentina, Canada | Oil/Energy/Petrochemical in Kazakhstan, Taiwan, Greece, US |\n| **Affiliated Groups** | Unidentified (resourceful actors) | Winnti Group, APT41, BARIUM | Unidentified (likely Korean speakers) | Unidentified (assessed as group based in China) |\n| **Key Tools/Techniques** | Empire, PowerShell, Visual Basic, Spearphishing Attachments | dsquery, Windows Service, Password Policy Discovery, Archive via Utility | Reg, SYSCON, Modify Registry, Exfiltration Over C2 Channel | gsecdump, ASPxSpy, zwShell, Software Packing, SCADA data collection |",
      "sources": [
        {
          "title": "LightRAG knowledge graph",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 25.784245636001287,
        "chunks": 0,
        "llm_calls": 1,
        "cloud_calls": 0
      },
      "approach_metadata": {
        "lightrag": {
          "query_profile": "graph-rag"
        }
      }
    },
    {
      "query_id": "cyber_campaign_timeline_context",
      "model": "agentic-rag",
      "base_model": "agentic-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 87.7,
      "raw": "Based on the gathered intelligence, here is a comparison of the Frankenstein, Operation CuckooBees, Operation Honeybee, and Night Dragon campaigns across timeframe, target context, and techniques/tools.\n\n### 1. Timeframe\n\n*   **Night Dragon:** The exact start and end dates are not specified in the available records, but it is identified as a historical cyber espionage campaign (ATT&CK ID: C0002).\n*   **Operation Honeybee:** Late 2017 through early 2018.\n*   **Frankenstein:** Early 2019.\n*   **Operation CuckooBees:** Active since at least 2019 and ongoing as of May 2022.\n\n### 2. Target Context\n\n*   **Night Dragon:**\n    *   **Industry:** Oil, energy, and petrochemical companies.\n    *   **Geography:** Kazakhstan, Taiwan, Greece, and the United States.\n    *   **Goal:** Steal financial data and oil/gas field production system information.\n    *   **Attribution:** Assessed to be a threat group based in China.\n\n*   **Operation Honeybee:**\n    *   **Industry/Context:** Humanitarian aid and inter-Korean affairs organizations.\n    *   **Geography:** Initially South Korea, later expanding to Vietnam, Singapore, Japan, Indonesia, Argentina, and Canada.\n    *   **Attribution:** Likely Korean speakers (based on metadata in lure documents).\n\n*   **Frankenstein:**\n    *   **Context:** Highly-targeted campaign against victims capable of facilitating complex cyber operations.\n    *   **Geography:** Not explicitly detailed in the provided snippets, but involved spearphishing to deliver payloads.\n    *   **Attribution:** Moderately sophisticated and highly resourceful actors who pieced together unrelated open-source tools.\n\n*   **Operation CuckooBees:**\n    *   **Industry/Context:** Technology and manufacturing companies.\n    *   **Geography:** East Asia, Western Europe, and North America.\n    *   **Goal:** Steal proprietary information, R&D documents, source code, and blueprints.\n    *   **Attribution:** Affiliated with Winnti Group, APT41, and BARIUM.\n\n### 3. Techniques and Tools\n\n| Feature | Night Dragon | Operation Honeybee | Frankenstein | Operation CuckooBees |\n| :--- | :--- | :--- | :--- | :--- |\n| **Primary Tools** | • **gsecdump**: Retrieve SAM file, password hashes, LSA secrets.<br>• **zwShell**: System interactions.<br>• **ASPXSpy**: Malware. | • **Reg (S0075)**<br>• **SYSCON (S0464)** | • **Empire (S0363)**: Primary open-source tool used for malicious activities. | • **dsquery (S0105)**: Query Active Directory objects. |\n| **Initial Access** | • Spearphishing Link (T1566.002)<br>• Malicious Link (T1204.001) | • Not explicitly detailed in snippets, but involved lure documents and executables. | • Spearphishing Attachment (T1566.001)<br>• Malicious File (T1204.002) | • Not explicitly detailed in snippets. |\n| **Execution** | • Windows Command Shell (T1059.003) | • Native API (T1106) | • PowerShell (T1059.001)<br>• Visual Basic (T1059.005)<br>• Scheduled Task (T1053.005) | • Not explicitly detailed in snippets. |\n| **Discovery** | • Data from Local System (T1005) | • File and Directory Discovery (T1083) | • Process Discovery (T1057)<br>• System Information Discovery (T1082)<br>• Security Software Discovery (T1518.001) | • Peripheral Device Discovery (T1120)<br>• Remote System Discovery (T1018)<br>• File and Directory Discovery (T1083)<br>• System Information Discovery (T1082)<br>• System Time Discovery (T1124)<br>• System Network Configuration Discovery (T1016)<br>• Password Policy Discovery (T1201) |\n| **Defense Evasion** | • Software Packing (T1027.002) | • Encrypted/Encoded File (T1027.013)<br>• Code Signing (T1553.002)<br>• File Deletion (T1070.004) | • Command Obfuscation (T1027.010) | • Not explicitly detailed in snippets. |\n| **Persistence** | • Domain Accounts (T1078.002) | • Modify Registry (T1112) | • Scheduled Task (T1053.005) | • Windows Service (T1543.003)<br>• Domain Accounts (T1078.002) |\n| **Lateral Movement** | • External Remote Services (T1133) | • Not explicitly detailed in snippets. | • Ingress Tool Transfer (T1105) | • Domain Accounts (T1078.002)<br>• External Remote Services (T1133) |\n| **Exfiltration** | • Upload Malware (T1608.001) | • Exfiltration Over C2 Channel (T1041)<br>• Local Data Staging (T1074.001) | • Automated Exfiltration (T1020) | • Archive via Utility (T1560.001) |\n\n### Summary of Differences\n\n*   **Timeframe:** Night Dragon is the earliest historical campaign (dates unspecified), followed by Operation Honeybee (2017-2018). Frankenstein and Operation CuckooBees are more recent, starting in 2019, with CuckooBees being long-running.\n*   **Targets:** Night Dragon focused on the energy sector; Honeybee on humanitarian/inter-Korean affairs; CuckooBees on tech/manufacturing R&D; and Frankenstein on highly targeted victims for complex operations.\n*   **Tools & Techniques:** \n    *   **Frankenstein** is distinct for its heavy reliance on open-source tools like **Empire** and a \"Frankenstein\" approach of piecing together unrelated components.\n    *   **Night Dragon** used specific credential dumping tools like **gsecdump** and malware like **ASPXSpy**.\n    *   **Operation Honeybee** utilized tools like **Reg** and **SYSCON**, focusing on registry modifications and code signing.\n    *   **Operation CuckooBees** employed **dsquery** for Active Directory reconnaissance and focused heavily on discovery techniques to gather R&D data.\n\n<details><summary>🔎 Retrieved context (1 source)</summary>\n\n**1. 🤖 Agent trace**\n\n> **Step 1.** **Action:** `search_vectors(Frankenstein malware operation details timeframe target techniques)`\n\n**Observation:** - cyber_threat_intel/011-c0001.md: # Frankenstein\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0001\nSTIX ID: campaign--26d9ebae-de59-427f-ae9a-349456bae4b1\n\nDescription:\n[Frankenstein](https://attack.\n- cyber_threat_intel/020-c0013.md: # Operation Sharpshooter\n\nSou\n\n**Step 2.** **Action:** `search_vectors(Operation CuckooBees malware campaign details timeframe target techniques)`\n\n**Observation:** - cyber_threat_intel/019-c0012.md: # Operation CuckooBees\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0012\nSTIX ID: campaign--93c23946-49af-41f4-ac03-40f9ffc7419b\n\nDescription:\n[Operation CuckooBees]\n- cyber_threat_intel/020-c0013.md: # Operation Sharpshooter\n\nSou\n\n**Step 3.** **Action:** `search_vectors(Operation Honeybee malware campaign details timeframe target techniques)`\n\n**Observation:** - cyber_threat_intel/015-c0006.md: # Operation Honeybee\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0006\nSTIX ID: campaign--4553292d-12c6-4a93-934d-12160370d4e0\n\nDescription:\n[Operation Honeybee](htt\n- cyber_threat_intel/019-c0012.md: # Operation CuckooBees\n\nSourc\n\n**Step 4.** **Action:** `search_vectors(Night Dragon cyber espionage operation details timeframe target techniques)`\n\n**Observation:** - cyber_threat_intel/012-c0002.md: # Night Dragon\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0002\nSTIX ID: campaign--ae407e32-87e0-4d92-8705-3ae25d504d8a\n\nDescription:\n[Night Dragon](https://attack.\n- cyber_threat_intel/020-c0013.md: # Operation Sharpshooter\n\nSou\n\n**Step 5.** **Thought:** I need to gather detailed information about each of these four campaigns. Let me search for specific details on each one.\n\n**Action:** `search_vectors(Frankenstein campaign C0001 timeframe target context techniques tools)`\n\n**Observation:** - cyber_threat_intel/011-c0001.md: # Frankenstein\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0001\nSTIX ID: campaign--26d9ebae-de59-427f-ae9a-349456bae4b1\n\nDescription:\n[Frankenstein](https://attack.\n- cyber_threat_intel/017-c0010.md: # C0010\n\nSource: MITRE ATT&CK\n\n**Step 6.** **Action:** `search_vectors(Operation CuckooBees campaign C0012 timeframe target context techniques tools)`\n\n**Observation:** - cyber_threat_intel/019-c0012.md: # Operation CuckooBees\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0012\nSTIX ID: campaign--93c23946-49af-41f4-ac03-40f9ffc7419b\n\nDescription:\n[Operation CuckooBees]\n- cyber_threat_intel/015-c0006.md: # Operation Honeybee\n\nSource:\n\n**Step 7.** **Action:** `search_vectors(Operation Honeybee campaign C0006 timeframe target context techniques tools)`\n\n**Observation:** - cyber_threat_intel/015-c0006.md: # Operation Honeybee\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0006\nSTIX ID: campaign--4553292d-12c6-4a93-934d-12160370d4e0\n\nDescription:\n[Operation Honeybee](htt\n- cyber_threat_intel/019-c0012.md: # Operation CuckooBees\n\nSourc\n\n**Step 8.** **Action:** `search_vectors(Night Dragon campaign C0002 timeframe target context techniques tools)`\n\n**Observation:** - cyber_threat_intel/012-c0002.md: # Night Dragon\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0002\nSTIX ID: campaign--ae407e32-87e0-4d92-8705-3ae25d504d8a\n\nDescription:\n[Night Dragon](https://attack.\n- cyber_threat_intel/034-s0008.md: # gsecdump\n\nSource: MITRE ATT\n\n**Step 9.** **Thought:** I need to get the detailed descriptions for each of these four campaigns. Let me search for more specific information about each one. I'll use the knowledge graph to get comprehensive details on timeframe, target context, and techniques/tools for each campaign.\n\n**Action:** `query_graph(What are the timeframe, target context, and techniques or tools used in the Frankenstein campaign (C0001)?)`\n\n**Observation:** ### Timeframe\nThe Frankenstein campaign (C0001) took place in **early 2019** [1].\n\n### Target Context\nFrankenstein was a **highly-targeted campaign** conducted by threat actors described as moderately sophisticated and highly resourceful [1][6]. While the specific geographic targets are not explicit\n\n**Step 10.** **Action:** `query_graph(What are the timeframe, target context, and techniques or tools used in Operation CuckooBees (C0012)?)`\n\n**Observation:** ### Timeframe\nOperation CuckooBees is a cyber espionage campaign that has been active **since at least 2019**. As of May 2022, the campaign was still ongoing.\n\n### Target Context\nThe campaign specifically targeted technology and manufacturing companies located in the following regions:\n*   East Asia\n\n**Step 11.** **Action:** `query_graph(What are the timeframe, target context, and techniques or tools used in Operation Honeybee (C0006)?)`\n\n**Observation:** Based on the provided knowledge base, here are the details regarding **Operation Honeybee (C0006)**:\n\n### Timeframe\nOperation Honeybee was a cyber campaign that targeted organizations from **late 2017 through early 2018**.\n\n### Target Context and Geographic Expansion\nThe campaign initially focused o\n\n**Step 12.** **Action:** `query_graph(What are the timeframe, target context, and techniques or tools used in Night Dragon (C0002)?)`\n\n**Observation:** Based on the provided knowledge base, here is the information regarding the **Night Dragon** campaign (ATT&CK ID: C0002):\n\n### Target Context\nThe Night Dragon campaign was a cyber espionage operation that primarily targeted oil, energy, and petrochemical companies. It also specifically targeted indi\n\n</details>\n\n---\n📊 87.7s · 0 chunks · 16 LLM calls · 0 cloud",
      "answer": "Based on the gathered intelligence, here is a comparison of the Frankenstein, Operation CuckooBees, Operation Honeybee, and Night Dragon campaigns across timeframe, target context, and techniques/tools.\n\n### 1. Timeframe\n\n*   **Night Dragon:** The exact start and end dates are not specified in the available records, but it is identified as a historical cyber espionage campaign (ATT&CK ID: C0002).\n*   **Operation Honeybee:** Late 2017 through early 2018.\n*   **Frankenstein:** Early 2019.\n*   **Operation CuckooBees:** Active since at least 2019 and ongoing as of May 2022.\n\n### 2. Target Context\n\n*   **Night Dragon:**\n    *   **Industry:** Oil, energy, and petrochemical companies.\n    *   **Geography:** Kazakhstan, Taiwan, Greece, and the United States.\n    *   **Goal:** Steal financial data and oil/gas field production system information.\n    *   **Attribution:** Assessed to be a threat group based in China.\n\n*   **Operation Honeybee:**\n    *   **Industry/Context:** Humanitarian aid and inter-Korean affairs organizations.\n    *   **Geography:** Initially South Korea, later expanding to Vietnam, Singapore, Japan, Indonesia, Argentina, and Canada.\n    *   **Attribution:** Likely Korean speakers (based on metadata in lure documents).\n\n*   **Frankenstein:**\n    *   **Context:** Highly-targeted campaign against victims capable of facilitating complex cyber operations.\n    *   **Geography:** Not explicitly detailed in the provided snippets, but involved spearphishing to deliver payloads.\n    *   **Attribution:** Moderately sophisticated and highly resourceful actors who pieced together unrelated open-source tools.\n\n*   **Operation CuckooBees:**\n    *   **Industry/Context:** Technology and manufacturing companies.\n    *   **Geography:** East Asia, Western Europe, and North America.\n    *   **Goal:** Steal proprietary information, R&D documents, source code, and blueprints.\n    *   **Attribution:** Affiliated with Winnti Group, APT41, and BARIUM.\n\n### 3. Techniques and Tools\n\n| Feature | Night Dragon | Operation Honeybee | Frankenstein | Operation CuckooBees |\n| :--- | :--- | :--- | :--- | :--- |\n| **Primary Tools** | • **gsecdump**: Retrieve SAM file, password hashes, LSA secrets.<br>• **zwShell**: System interactions.<br>• **ASPXSpy**: Malware. | • **Reg (S0075)**<br>• **SYSCON (S0464)** | • **Empire (S0363)**: Primary open-source tool used for malicious activities. | • **dsquery (S0105)**: Query Active Directory objects. |\n| **Initial Access** | • Spearphishing Link (T1566.002)<br>• Malicious Link (T1204.001) | • Not explicitly detailed in snippets, but involved lure documents and executables. | • Spearphishing Attachment (T1566.001)<br>• Malicious File (T1204.002) | • Not explicitly detailed in snippets. |\n| **Execution** | • Windows Command Shell (T1059.003) | • Native API (T1106) | • PowerShell (T1059.001)<br>• Visual Basic (T1059.005)<br>• Scheduled Task (T1053.005) | • Not explicitly detailed in snippets. |\n| **Discovery** | • Data from Local System (T1005) | • File and Directory Discovery (T1083) | • Process Discovery (T1057)<br>• System Information Discovery (T1082)<br>• Security Software Discovery (T1518.001) | • Peripheral Device Discovery (T1120)<br>• Remote System Discovery (T1018)<br>• File and Directory Discovery (T1083)<br>• System Information Discovery (T1082)<br>• System Time Discovery (T1124)<br>• System Network Configuration Discovery (T1016)<br>• Password Policy Discovery (T1201) |\n| **Defense Evasion** | • Software Packing (T1027.002) | • Encrypted/Encoded File (T1027.013)<br>• Code Signing (T1553.002)<br>• File Deletion (T1070.004) | • Command Obfuscation (T1027.010) | • Not explicitly detailed in snippets. |\n| **Persistence** | • Domain Accounts (T1078.002) | • Modify Registry (T1112) | • Scheduled Task (T1053.005) | • Windows Service (T1543.003)<br>• Domain Accounts (T1078.002) |\n| **Lateral Movement** | • External Remote Services (T1133) | • Not explicitly detailed in snippets. | • Ingress Tool Transfer (T1105) | • Domain Accounts (T1078.002)<br>• External Remote Services (T1133) |\n| **Exfiltration** | • Upload Malware (T1608.001) | • Exfiltration Over C2 Channel (T1041)<br>• Local Data Staging (T1074.001) | • Automated Exfiltration (T1020) | • Archive via Utility (T1560.001) |\n\n### Summary of Differences\n\n*   **Timeframe:** Night Dragon is the earliest historical campaign (dates unspecified), followed by Operation Honeybee (2017-2018). Frankenstein and Operation CuckooBees are more recent, starting in 2019, with CuckooBees being long-running.\n*   **Targets:** Night Dragon focused on the energy sector; Honeybee on humanitarian/inter-Korean affairs; CuckooBees on tech/manufacturing R&D; and Frankenstein on highly targeted victims for complex operations.\n*   **Tools & Techniques:** \n    *   **Frankenstein** is distinct for its heavy reliance on open-source tools like **Empire** and a \"Frankenstein\" approach of piecing together unrelated components.\n    *   **Night Dragon** used specific credential dumping tools like **gsecdump** and malware like **ASPXSpy**.\n    *   **Operation Honeybee** utilized tools like **Reg** and **SYSCON**, focusing on registry modifications and code signing.\n    *   **Operation CuckooBees** employed **dsquery** for Active Directory reconnaissance and focused heavily on discovery techniques to gather R&D data.",
      "sources": [
        {
          "title": "🤖 Agent trace",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 87.68383678899772,
        "chunks": 0,
        "llm_calls": 16,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_campaign_timeline_context",
      "model": "n8n-adaptive-rag",
      "base_model": "n8n-adaptive-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 37.8,
      "raw": "Based on the gathered intelligence, here is a comparison of the Frankenstein, Operation CuckooBees, Operation Honeybee, and Night Dragon campaigns across timeframe, target context, and techniques/tools.\n\n### 1. Timeframe\n\n*   **Night Dragon:** The exact start and end dates are not specified in the available records, but it is identified as a historical cyber espionage campaign (ATT&CK ID: C0002).\n*   **Operation Honeybee:** Late 2017 through early 2018.\n*   **Frankenstein:** Early 2019.\n*   **Operation CuckooBees:** Active since at least 2019 and ongoing as of May 2022.\n\n### 2. Target Context\n\n*   **Night Dragon:**\n    *   **Industry:** Oil, energy, and petrochemical companies.\n    *   **Geography:** Kazakhstan, Taiwan, Greece, and the United States.\n    *   **Goal:** Steal financial data and oil/gas field production system information.\n    *   **Attribution:** Assessed to be a threat group based in China.\n\n*   **Operation Honeybee:**\n    *   **Industry/Context:** Humanitarian aid and inter-Korean affairs organizations.\n    *   **Geography:** Initially South Korea, later expanding to Vietnam, Singapore, Japan, Indonesia, Argentina, and Canada.\n    *   **Attribution:** Likely Korean speakers (based on metadata in lure documents).\n\n*   **Frankenstein:**\n    *   **Context:** Highly-targeted campaign against victims capable of facilitating complex cyber operations.\n    *   **Geography:** Not explicitly detailed in the provided snippets, but involved spearphishing to deliver payloads.\n    *   **Attribution:** Moderately sophisticated and highly resourceful actors who pieced together unrelated open-source tools.\n\n*   **Operation CuckooBees:**\n    *   **Industry/Context:** Technology and manufacturing companies.\n    *   **Geography:** East Asia, Western Europe, and North America.\n    *   **Goal:** Steal proprietary information, R&D documents, source code, and blueprints.\n    *   **Attribution:** Affiliated with Winnti Group, APT41, and BARIUM.\n\n### 3. Techniques and Tools\n\n| Feature | Night Dragon | Operation Honeybee | Frankenstein | Operation CuckooBees |\n| :--- | :--- | :--- | :--- | :--- |\n| **Primary Tools** | • **gsecdump**: Retrieve SAM file, password hashes, LSA secrets.<br>• **zwShell**: System interactions.<br>• **ASPXSpy**: Malware. | • **Reg (S0075)**<br>• **SYSCON (S0464)** | • **Empire (S0363)**: Primary open-source tool used for malicious activities. | • **dsquery (S0105)**: Query Active Directory objects. |\n| **Initial Access** | • Spearphishing Link (T1566.002)<br>• Malicious Link (T1204.001) | • Not explicitly detailed in snippets, but involved lure documents and executables. | • Spearphishing Attachment (T1566.001)<br>• Malicious File (T1204.002) | • Not explicitly detailed in snippets. |\n| **Execution** | • Windows Command Shell (T1059.003) | • Native API (T1106) | • PowerShell (T1059.001)<br>• Visual Basic (T1059.005)<br>• Scheduled Task (T1053.005) | • Not explicitly detailed in snippets. |\n| **Discovery** | • Data from Local System (T1005) | • File and Directory Discovery (T1083) | • Process Discovery (T1057)<br>• System Information Discovery (T1082)<br>• Security Software Discovery (T1518.001) | • Peripheral Device Discovery (T1120)<br>• Remote System Discovery (T1018)<br>• File and Directory Discovery (T1083)<br>• System Information Discovery (T1082)<br>• System Time Discovery (T1124)<br>• System Network Configuration Discovery (T1016)<br>• Password Policy Discovery (T1201) |\n| **Defense Evasion** | • Software Packing (T1027.002) | • Encrypted/Encoded File (T1027.013)<br>• Code Signing (T1553.002)<br>• File Deletion (T1070.004) | • Command Obfuscation (T1027.010) | • Not explicitly detailed in snippets. |\n| **Persistence** | • Domain Accounts (T1078.002) | • Modify Registry (T1112) | • Scheduled Task (T1053.005) | • Windows Service (T1543.003)<br>• Domain Accounts (T1078.002) |\n| **Lateral Movement** | • External Remote Services (T1133) | • Not explicitly detailed in snippets. | • Ingress Tool Transfer (T1105) | • Domain Accounts (T1078.002)<br>• External Remote Services (T1133) |\n| **Exfiltration** | • Upload Malware (T1608.001) | • Exfiltration Over C2 Channel (T1041)<br>• Local Data Staging (T1074.001) | • Automated Exfiltration (T1020) | • Archive via Utility (T1560.001) |\n\n### Summary of Differences\n\n*   **Timeframe:** Night Dragon is the earliest historical campaign (dates unspecified), followed by Operation Honeybee (2017-2018). Frankenstein and Operation CuckooBees are more recent, starting in 2019, with CuckooBees being long-running.\n*   **Targets:** Night Dragon focused on the energy sector; Honeybee on humanitarian/inter-Korean affairs; CuckooBees on tech/manufacturing R&D; and Frankenstein on highly targeted victims for complex operations.\n*   **Tools & Techniques:** \n    *   **Frankenstein** is distinct for its heavy reliance on open-source tools like **Empire** and a \"Frankenstein\" approach of piecing together unrelated components.\n    *   **Night Dragon** used specific credential dumping tools like **gsecdump** and malware like **ASPXSpy**.\n    *   **Operation Honeybee** utilized tools like **Reg** and **SYSCON**, focusing on registry modifications and code signing.\n    *   **Operation CuckooBees** employed **dsquery** for Active Directory reconnaissance and focused heavily on discovery techniques to gather R&D data.\n\n<details><summary>🔎 Retrieved context (1 source)</summary>\n\n**1. 🤖 Agent trace**\n\n> **Step 1.** **Action:** `search_vectors(Frankenstein malware operation details timeframe target techniques)`\n\n**Observation:** - cyber_threat_intel/011-c0001.md: # Frankenstein\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0001\nSTIX ID: campaign--26d9ebae-de59-427f-ae9a-349456bae4b1\n\nDescription:\n[Frankenstein](https://attack.\n- cyber_threat_intel/020-c0013.md: # Operation Sharpshooter\n\nSou\n\n**Step 2.** **Action:** `search_vectors(Operation CuckooBees malware campaign details timeframe target techniques)`\n\n**Observation:** - cyber_threat_intel/019-c0012.md: # Operation CuckooBees\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0012\nSTIX ID: campaign--93c23946-49af-41f4-ac03-40f9ffc7419b\n\nDescription:\n[Operation CuckooBees]\n- cyber_threat_intel/020-c0013.md: # Operation Sharpshooter\n\nSou\n\n**Step 3.** **Action:** `search_vectors(Operation Honeybee malware campaign details timeframe target techniques)`\n\n**Observation:** - cyber_threat_intel/015-c0006.md: # Operation Honeybee\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0006\nSTIX ID: campaign--4553292d-12c6-4a93-934d-12160370d4e0\n\nDescription:\n[Operation Honeybee](htt\n- cyber_threat_intel/019-c0012.md: # Operation CuckooBees\n\nSourc\n\n**Step 4.** **Action:** `search_vectors(Night Dragon cyber espionage operation details timeframe target techniques)`\n\n**Observation:** - cyber_threat_intel/012-c0002.md: # Night Dragon\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0002\nSTIX ID: campaign--ae407e32-87e0-4d92-8705-3ae25d504d8a\n\nDescription:\n[Night Dragon](https://attack.\n- cyber_threat_intel/020-c0013.md: # Operation Sharpshooter\n\nSou\n\n**Step 5.** **Thought:** I need to gather detailed information about each of these four campaigns. Let me search for specific details on each one.\n\n**Action:** `search_vectors(Frankenstein campaign C0001 timeframe target context techniques tools)`\n\n**Observation:** - cyber_threat_intel/011-c0001.md: # Frankenstein\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0001\nSTIX ID: campaign--26d9ebae-de59-427f-ae9a-349456bae4b1\n\nDescription:\n[Frankenstein](https://attack.\n- cyber_threat_intel/017-c0010.md: # C0010\n\nSource: MITRE ATT&CK\n\n**Step 6.** **Action:** `search_vectors(Operation CuckooBees campaign C0012 timeframe target context techniques tools)`\n\n**Observation:** - cyber_threat_intel/019-c0012.md: # Operation CuckooBees\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0012\nSTIX ID: campaign--93c23946-49af-41f4-ac03-40f9ffc7419b\n\nDescription:\n[Operation CuckooBees]\n- cyber_threat_intel/015-c0006.md: # Operation Honeybee\n\nSource:\n\n**Step 7.** **Action:** `search_vectors(Operation Honeybee campaign C0006 timeframe target context techniques tools)`\n\n**Observation:** - cyber_threat_intel/015-c0006.md: # Operation Honeybee\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0006\nSTIX ID: campaign--4553292d-12c6-4a93-934d-12160370d4e0\n\nDescription:\n[Operation Honeybee](htt\n- cyber_threat_intel/019-c0012.md: # Operation CuckooBees\n\nSourc\n\n**Step 8.** **Action:** `search_vectors(Night Dragon campaign C0002 timeframe target context techniques tools)`\n\n**Observation:** - cyber_threat_intel/012-c0002.md: # Night Dragon\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0002\nSTIX ID: campaign--ae407e32-87e0-4d92-8705-3ae25d504d8a\n\nDescription:\n[Night Dragon](https://attack.\n- cyber_threat_intel/034-s0008.md: # gsecdump\n\nSource: MITRE ATT\n\n**Step 9.** **Thought:** I need to get the detailed descriptions for each of these four campaigns. Let me search for more specific information about each one. I'll use the knowledge graph to get comprehensive details on timeframe, target context, and techniques/tools for each campaign.\n\n**Action:** `query_graph(What are the timeframe, target context, and techniques or tools used in the Frankenstein campaign (C0001)?)`\n\n**Observation:** ### Timeframe\nThe Frankenstein campaign (C0001) took place in **early 2019** [1].\n\n### Target Context\nFrankenstein was a **highly-targeted campaign** conducted by threat actors described as moderately sophisticated and highly resourceful [1][6]. While the specific geographic targets are not explicit\n\n**Step 10.** **Action:** `query_graph(What are the timeframe, target context, and techniques or tools used in Operation CuckooBees (C0012)?)`\n\n**Observation:** ### Timeframe\nOperation CuckooBees is a cyber espionage campaign that has been active **since at least 2019**. As of May 2022, the campaign was still ongoing.\n\n### Target Context\nThe campaign specifically targeted technology and manufacturing companies located in the following regions:\n*   East Asia\n\n**Step 11.** **Action:** `query_graph(What are the timeframe, target context, and techniques or tools used in Operation Honeybee (C0006)?)`\n\n**Observation:** Based on the provided knowledge base, here are the details regarding **Operation Honeybee (C0006)**:\n\n### Timeframe\nOperation Honeybee was a cyber campaign that targeted organizations from **late 2017 through early 2018**.\n\n### Target Context and Geographic Expansion\nThe campaign initially focused o\n\n**Step 12.** **Action:** `query_graph(What are the timeframe, target context, and techniques or tools used in Night Dragon (C0002)?)`\n\n**Observation:** Based on the provided knowledge base, here is the information regarding the **Night Dragon** campaign (ATT&CK ID: C0002):\n\n### Target Context\nThe Night Dragon campaign was a cyber espionage operation that primarily targeted oil, energy, and petrochemical companies. It also specifically targeted indi\n\n</details>\n\n---\n📊 37.8s · 0 chunks · 17 LLM calls · 0 cloud",
      "answer": "Based on the gathered intelligence, here is a comparison of the Frankenstein, Operation CuckooBees, Operation Honeybee, and Night Dragon campaigns across timeframe, target context, and techniques/tools.\n\n### 1. Timeframe\n\n*   **Night Dragon:** The exact start and end dates are not specified in the available records, but it is identified as a historical cyber espionage campaign (ATT&CK ID: C0002).\n*   **Operation Honeybee:** Late 2017 through early 2018.\n*   **Frankenstein:** Early 2019.\n*   **Operation CuckooBees:** Active since at least 2019 and ongoing as of May 2022.\n\n### 2. Target Context\n\n*   **Night Dragon:**\n    *   **Industry:** Oil, energy, and petrochemical companies.\n    *   **Geography:** Kazakhstan, Taiwan, Greece, and the United States.\n    *   **Goal:** Steal financial data and oil/gas field production system information.\n    *   **Attribution:** Assessed to be a threat group based in China.\n\n*   **Operation Honeybee:**\n    *   **Industry/Context:** Humanitarian aid and inter-Korean affairs organizations.\n    *   **Geography:** Initially South Korea, later expanding to Vietnam, Singapore, Japan, Indonesia, Argentina, and Canada.\n    *   **Attribution:** Likely Korean speakers (based on metadata in lure documents).\n\n*   **Frankenstein:**\n    *   **Context:** Highly-targeted campaign against victims capable of facilitating complex cyber operations.\n    *   **Geography:** Not explicitly detailed in the provided snippets, but involved spearphishing to deliver payloads.\n    *   **Attribution:** Moderately sophisticated and highly resourceful actors who pieced together unrelated open-source tools.\n\n*   **Operation CuckooBees:**\n    *   **Industry/Context:** Technology and manufacturing companies.\n    *   **Geography:** East Asia, Western Europe, and North America.\n    *   **Goal:** Steal proprietary information, R&D documents, source code, and blueprints.\n    *   **Attribution:** Affiliated with Winnti Group, APT41, and BARIUM.\n\n### 3. Techniques and Tools\n\n| Feature | Night Dragon | Operation Honeybee | Frankenstein | Operation CuckooBees |\n| :--- | :--- | :--- | :--- | :--- |\n| **Primary Tools** | • **gsecdump**: Retrieve SAM file, password hashes, LSA secrets.<br>• **zwShell**: System interactions.<br>• **ASPXSpy**: Malware. | • **Reg (S0075)**<br>• **SYSCON (S0464)** | • **Empire (S0363)**: Primary open-source tool used for malicious activities. | • **dsquery (S0105)**: Query Active Directory objects. |\n| **Initial Access** | • Spearphishing Link (T1566.002)<br>• Malicious Link (T1204.001) | • Not explicitly detailed in snippets, but involved lure documents and executables. | • Spearphishing Attachment (T1566.001)<br>• Malicious File (T1204.002) | • Not explicitly detailed in snippets. |\n| **Execution** | • Windows Command Shell (T1059.003) | • Native API (T1106) | • PowerShell (T1059.001)<br>• Visual Basic (T1059.005)<br>• Scheduled Task (T1053.005) | • Not explicitly detailed in snippets. |\n| **Discovery** | • Data from Local System (T1005) | • File and Directory Discovery (T1083) | • Process Discovery (T1057)<br>• System Information Discovery (T1082)<br>• Security Software Discovery (T1518.001) | • Peripheral Device Discovery (T1120)<br>• Remote System Discovery (T1018)<br>• File and Directory Discovery (T1083)<br>• System Information Discovery (T1082)<br>• System Time Discovery (T1124)<br>• System Network Configuration Discovery (T1016)<br>• Password Policy Discovery (T1201) |\n| **Defense Evasion** | • Software Packing (T1027.002) | • Encrypted/Encoded File (T1027.013)<br>• Code Signing (T1553.002)<br>• File Deletion (T1070.004) | • Command Obfuscation (T1027.010) | • Not explicitly detailed in snippets. |\n| **Persistence** | • Domain Accounts (T1078.002) | • Modify Registry (T1112) | • Scheduled Task (T1053.005) | • Windows Service (T1543.003)<br>• Domain Accounts (T1078.002) |\n| **Lateral Movement** | • External Remote Services (T1133) | • Not explicitly detailed in snippets. | • Ingress Tool Transfer (T1105) | • Domain Accounts (T1078.002)<br>• External Remote Services (T1133) |\n| **Exfiltration** | • Upload Malware (T1608.001) | • Exfiltration Over C2 Channel (T1041)<br>• Local Data Staging (T1074.001) | • Automated Exfiltration (T1020) | • Archive via Utility (T1560.001) |\n\n### Summary of Differences\n\n*   **Timeframe:** Night Dragon is the earliest historical campaign (dates unspecified), followed by Operation Honeybee (2017-2018). Frankenstein and Operation CuckooBees are more recent, starting in 2019, with CuckooBees being long-running.\n*   **Targets:** Night Dragon focused on the energy sector; Honeybee on humanitarian/inter-Korean affairs; CuckooBees on tech/manufacturing R&D; and Frankenstein on highly targeted victims for complex operations.\n*   **Tools & Techniques:** \n    *   **Frankenstein** is distinct for its heavy reliance on open-source tools like **Empire** and a \"Frankenstein\" approach of piecing together unrelated components.\n    *   **Night Dragon** used specific credential dumping tools like **gsecdump** and malware like **ASPXSpy**.\n    *   **Operation Honeybee** utilized tools like **Reg** and **SYSCON**, focusing on registry modifications and code signing.\n    *   **Operation CuckooBees** employed **dsquery** for Active Directory reconnaissance and focused heavily on discovery techniques to gather R&D data.",
      "sources": [
        {
          "title": "🤖 Agent trace",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 37.75906209999812,
        "chunks": 0,
        "llm_calls": 17,
        "cloud_calls": 0
      },
      "approach_metadata": {
        "adaptive": {
          "route": "complex",
          "approach": "agentic-rag"
        }
      }
    },
    {
      "query_id": "cyber_campaign_timeline_context",
      "model": "lazy-graph-rag",
      "base_model": "lazy-graph-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 9.9,
      "raw": "Based on the provided context, here is the comparison of the four campaigns:\n\n**1. Timeframe**\n*   **Frankenstein:** Early 2019.\n*   **Operation CuckooBees:** Since at least 2019; ongoing as of May 2022.\n*   **Operation Honeybee:** Late 2017 through early 2018.\n*   **Night Dragon:** The context does not specify a timeframe for this campaign.\n\n**2. Target Context**\n*   **Frankenstein:** The context does not specify the specific targets, only that it was a \"highly-targeted campaign.\"\n*   **Operation CuckooBees:** Technology and manufacturing companies in East Asia, Western Europe, and North America.\n*   **Operation Honeybee:** Humanitarian aid and inter-Korean affairs organizations (initially South Korea, later expanding to Vietnam, Singapore, Japan, Indonesia, Argentina, and Canada).\n*   **Night Dragon:** Oil, energy, and petrochemical companies, along with individuals and executives in Kazakhstan, Taiwan, Greece, and the United States.\n\n**3. Techniques or Tools Used**\n*   **Frankenstein:**\n    *   **Tools:** Empire (S0363), PowerShell (T1059.001), Visual Basic (T1059.005).\n    *   **Techniques:** Process Discovery, System Information Discovery, Command Obfuscation, Automated Exfiltration, Scheduled Task, Malicious File, Spearphishing Attachment, Ingress Tool Transfer, Security Software Discovery.\n*   **Operation CuckooBees:**\n    *   **Tools:** dsquery (S0105).\n    *   **Techniques:** Peripheral Device Discovery, Remote System Discovery, Windows Service, Archive via Utility, External Remote Services, File and Directory Discovery, System Information Discovery, System Time Discovery, Domain Accounts, System Network Configuration Discovery, Password Policy Discovery.\n*   **Operation Honeybee:**\n    *   **Tools:** SYSCON (S0464), Reg (S0075).\n    *   **Techniques:** Email Accounts, File and Directory Discovery, Native API, File Deletion, Local Data Staging, Domains, Encrypted/Encoded File, Code Signing, Exfiltration Over C2 Channel, Modify Registry.\n*   **Night Dragon:**\n    *   **Tools:** gsecdump (S0008), ASPXSpy (S0073), zwShell (S0350).\n    *   **Techniques:** Domain Accounts, Upload Malware, Malware, Spearphishing Link, Malicious Link, External Remote Services, Data from Local System, Windows Command Shell, Software Packing.\n\n<details><summary>🔎 Retrieved context (8 sources)</summary>\n\n**1. cyber_threat_intel/012-c0002.md** · score 54.000\n\n> # Night Dragon\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0002\nSTIX ID: campaign--ae407e32-87e0-4d92-8705-3ae25d504d8a\n\nDescription:\n[Night Dragon](https://attack.mitre.org/campaigns/C0002) was a cyber e\n\n**2. cyber_threat_intel/019-c0012.md** · score 25.500\n\n> # Operation CuckooBees\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0012\nSTIX ID: campaign--93c23946-49af-41f4-ac03-40f9ffc7419b\n\nDescription:\n[Operation CuckooBees](https://attack.mitre.org/campaigns/C001\n\n**3. cyber_threat_intel/015-c0006.md** · score 25.000\n\n> # Operation Honeybee\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0006\nSTIX ID: campaign--4553292d-12c6-4a93-934d-12160370d4e0\n\nDescription:\n[Operation Honeybee](https://attack.mitre.org/campaigns/C0006) w\n\n**4. cyber_threat_intel/014-c0005.md** · score 22.600\n\n> # Operation Spalax\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0005\nSTIX ID: campaign--4c840263-bbda-440d-a22b-674679ddebf1\n\nDescription:\n[Operation Spalax](https://attack.mitre.org/campaigns/C0005) was a\n\n**5. cyber_threat_intel/020-c0013.md** · score 19.500\n\n> # Operation Sharpshooter\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0013\nSTIX ID: campaign--37764c78-2a99-46d1-a7ea-6454b9bf93a0\n\nDescription:\n[Operation Sharpshooter](https://attack.mitre.org/campaigns/\n\n**6. cyber_threat_intel/011-c0001.md** · score 16.750\n\n> # Frankenstein\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0001\nSTIX ID: campaign--26d9ebae-de59-427f-ae9a-349456bae4b1\n\nDescription:\n[Frankenstein](https://attack.mitre.org/campaigns/C0001) was described\n\n**7. cyber_threat_intel/043-t1001-002.md** · score 16.000\n\n> # Steganography\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1001.002\nSTIX ID: attack-pattern--eec23884-3fa1-4d8a-ac50-6f104d51e235\n\nDescription:\nAdversaries may use steganographic techniques to hide\n\n**8. cyber_threat_intel/017-c0010.md** · score 15.000\n\n> # C0010\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0010\nSTIX ID: campaign--ab747e62-1bcb-479f-a26b-1cd39d413d81\n\nDescription:\n[C0010](https://attack.mitre.org/campaigns/C0010) was a cyber espionage campa\n\n</details>\n\n---\n📊 9.9s · 8 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the provided context, here is the comparison of the four campaigns:\n\n**1. Timeframe**\n*   **Frankenstein:** Early 2019.\n*   **Operation CuckooBees:** Since at least 2019; ongoing as of May 2022.\n*   **Operation Honeybee:** Late 2017 through early 2018.\n*   **Night Dragon:** The context does not specify a timeframe for this campaign.\n\n**2. Target Context**\n*   **Frankenstein:** The context does not specify the specific targets, only that it was a \"highly-targeted campaign.\"\n*   **Operation CuckooBees:** Technology and manufacturing companies in East Asia, Western Europe, and North America.\n*   **Operation Honeybee:** Humanitarian aid and inter-Korean affairs organizations (initially South Korea, later expanding to Vietnam, Singapore, Japan, Indonesia, Argentina, and Canada).\n*   **Night Dragon:** Oil, energy, and petrochemical companies, along with individuals and executives in Kazakhstan, Taiwan, Greece, and the United States.\n\n**3. Techniques or Tools Used**\n*   **Frankenstein:**\n    *   **Tools:** Empire (S0363), PowerShell (T1059.001), Visual Basic (T1059.005).\n    *   **Techniques:** Process Discovery, System Information Discovery, Command Obfuscation, Automated Exfiltration, Scheduled Task, Malicious File, Spearphishing Attachment, Ingress Tool Transfer, Security Software Discovery.\n*   **Operation CuckooBees:**\n    *   **Tools:** dsquery (S0105).\n    *   **Techniques:** Peripheral Device Discovery, Remote System Discovery, Windows Service, Archive via Utility, External Remote Services, File and Directory Discovery, System Information Discovery, System Time Discovery, Domain Accounts, System Network Configuration Discovery, Password Policy Discovery.\n*   **Operation Honeybee:**\n    *   **Tools:** SYSCON (S0464), Reg (S0075).\n    *   **Techniques:** Email Accounts, File and Directory Discovery, Native API, File Deletion, Local Data Staging, Domains, Encrypted/Encoded File, Code Signing, Exfiltration Over C2 Channel, Modify Registry.\n*   **Night Dragon:**\n    *   **Tools:** gsecdump (S0008), ASPXSpy (S0073), zwShell (S0350).\n    *   **Techniques:** Domain Accounts, Upload Malware, Malware, Spearphishing Link, Malicious Link, External Remote Services, Data from Local System, Windows Command Shell, Software Packing.",
      "sources": [
        {
          "title": "cyber_threat_intel/012-c0002.md",
          "score": 54.0
        },
        {
          "title": "cyber_threat_intel/019-c0012.md",
          "score": 25.5
        },
        {
          "title": "cyber_threat_intel/015-c0006.md",
          "score": 25.0
        },
        {
          "title": "cyber_threat_intel/014-c0005.md",
          "score": 22.6
        },
        {
          "title": "cyber_threat_intel/020-c0013.md",
          "score": 19.5
        },
        {
          "title": "cyber_threat_intel/011-c0001.md",
          "score": 16.75
        },
        {
          "title": "cyber_threat_intel/043-t1001-002.md",
          "score": 16.0
        },
        {
          "title": "cyber_threat_intel/017-c0010.md",
          "score": 15.0
        }
      ],
      "metrics": {
        "seconds": 9.92508442200051,
        "chunks": 8,
        "llm_calls": 2,
        "cloud_calls": 0
      },
      "approach_metadata": {
        "lazy_graph": {
          "experimental": true,
          "cache_hit": true,
          "index_seconds": 0.009863,
          "graph_chunks": 66,
          "graph_concepts": 762,
          "graph_edges": 13949,
          "relevance_tests": 24,
          "relevance_budget": 24,
          "seed_k": 8,
          "max_context_chunks": 8,
          "llm_index_calls": 0,
          "cache_namespace": "RagBase_cyber_threat_intel.concepts-24"
        }
      }
    },
    {
      "query_id": "cyber_protocol_and_web_mitigation_path",
      "model": "vanilla-rag",
      "base_model": "vanilla-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 4.8,
      "raw": "Based on the context provided, the following groups, campaigns, and software are involved:\n\n**Groups:**\n*   **Lazarus Group (G0032)**\n*   **Mustang Panda (G0129)**\n*   **Higaisa (G0126)**\n*   **Transparent Tribe (G0134)**\n\n**Campaigns:**\n*   **C0011** (attributed to Transparent Tribe)\n*   **Operation Spalax**\n\n**Software/Tools:**\n*   **FRAMESTING (S1120)**\n*   **StarProxy (S1227)**\n*   **PUBLOAD (S1228)**\n*   **Cobalt Strike (S0154)**\n*   **BADCALL (S0245)**\n*   **KeyBoy (S0387)**\n*   **TAINTEDSCRIBE (S0586)**\n*   **Bankshot (S0239)**\n\n<details><summary>🔎 Retrieved context (5 sources)</summary>\n\n**1. cyber_threat_intel/058-m1021.md**\n\n> # Restrict Web-Based Content\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1021\nSTIX ID: course-of-action--21da4fd4-27ad-4e9c-b93d-0b9b14d02c96\n\nDescription:\nRestricting web-based content involves e\n\n**2. cyber_threat_intel/044-t1001-003.md**\n\n> # Protocol or Service Impersonation\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1001.003\nSTIX ID: attack-pattern--c325b232-d5bc-4dde-a3ec-71f3db9e8adc\n\nDescription:\nAdversaries may impersonate legit\n\n**3. cyber_threat_intel/018-c0011.md**\n\n> # C0011\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0011\nSTIX ID: campaign--b4e5a4a9-f3be-4631-ba8f-da6ebb067fac\n\nDescription:\n[C0011](https://attack.mitre.org/campaigns/C0011) was a suspected cyber espio\n\n**4. cyber_threat_intel/014-c0005.md**\n\n> # Operation Spalax\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0005\nSTIX ID: campaign--4c840263-bbda-440d-a22b-674679ddebf1\n\nDescription:\n[Operation Spalax](https://attack.mitre.org/campaigns/C0005) was a\n\n**5. cyber_threat_intel/017-c0010.md**\n\n> # C0010\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0010\nSTIX ID: campaign--ab747e62-1bcb-479f-a26b-1cd39d413d81\n\nDescription:\n[C0010](https://attack.mitre.org/campaigns/C0010) was a cyber espionage campa\n\n</details>\n\n---\n📊 4.7s · 5 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the context provided, the following groups, campaigns, and software are involved:\n\n**Groups:**\n*   **Lazarus Group (G0032)**\n*   **Mustang Panda (G0129)**\n*   **Higaisa (G0126)**\n*   **Transparent Tribe (G0134)**\n\n**Campaigns:**\n*   **C0011** (attributed to Transparent Tribe)\n*   **Operation Spalax**\n\n**Software/Tools:**\n*   **FRAMESTING (S1120)**\n*   **StarProxy (S1227)**\n*   **PUBLOAD (S1228)**\n*   **Cobalt Strike (S0154)**\n*   **BADCALL (S0245)**\n*   **KeyBoy (S0387)**\n*   **TAINTEDSCRIBE (S0586)**\n*   **Bankshot (S0239)**",
      "sources": [
        {
          "title": "cyber_threat_intel/058-m1021.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/044-t1001-003.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/018-c0011.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/014-c0005.md",
          "score": null
        },
        {
          "title": "cyber_threat_intel/017-c0010.md",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 4.741495460999431,
        "chunks": 5,
        "llm_calls": 2,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_protocol_and_web_mitigation_path",
      "model": "hybrid-rag",
      "base_model": "hybrid-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 22.1,
      "raw": "Based on the context provided, the following groups, campaigns, and software are involved:\n\n**Groups:**\n*   Lazarus Group (G0032)\n*   Gamaredon Group (G0047)\n*   Mustang Panda (G0129)\n*   Higaisa (G0126)\n\n**Software/Tools:**\n*   Cobalt Strike (S0154)\n*   KeyBoy (S0387)\n*   Okrum (S0439)\n*   SystemBC (S9001)\n*   StrelaStealer (S1183)\n*   Ninja (S1100)\n*   TrailBlazer (S0682)\n\n**Campaigns:**\n*   Operation Wocao (C0014)\n\n**Techniques/Mitigations involved in the connections:**\n*   **Protocol or Service Impersonation (T1001.003):** Used by Lazarus Group, Mustang Panda, Higaisa, Cobalt Strike, KeyBoy, Okrum, SystemBC, StrelaStealer, Ninja, TrailBlazer, and others to disguise command and control activity.\n*   **Data Obfuscation (T1001):** The parent technique of Protocol or Service Impersonation, used by Gamaredon Group, Okrum, SystemBC, SLOTHFULMEDIA, Ninja, TrailBlazer, and Operation Wocao.\n*   **Spearphishing Link (T1566.002):** Mitigated by Restrict Web-Based Content (M1021).\n*   **Restrict Web-Based Content (M1021):** A mitigation that restricts web-based content and mitigates Spearphishing Link (T1566.002) among other techniques.\n\n<details><summary>🔎 Retrieved context (5 sources)</summary>\n\n**1. cyber_threat_intel/044-t1001-003.md** · score 0.219\n\n> # Protocol or Service Impersonation\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1001.003\nSTIX ID: attack-pattern--c325b232-d5bc-4dde-a3ec-71f3db9e8adc\n\nDescription:\nAdversaries may impersonate legit\n\n**2. cyber_threat_intel/041-t1001.md** · score 0.081\n\n> # Data Obfuscation\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1001\nSTIX ID: attack-pattern--ad255bfe-a9e6-4b52-a258-8d3462abe842\n\nDescription:\nAdversaries may obfuscate command and control traffic \n\n**3. cyber_threat_intel/058-m1021.md** · score 0.042\n\n> # Restrict Web-Based Content\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1021\nSTIX ID: course-of-action--21da4fd4-27ad-4e9c-b93d-0b9b14d02c96\n\nDescription:\nRestricting web-based content involves e\n\n**4. cyber_threat_intel/051-m1013.md** · score 0.032\n\n> # Application Developer Guidance\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1013\nSTIX ID: course-of-action--25dc1ce8-eb55-4333-ae30-a7cb4f5894a1\n\nDescription:\nApplication Developer Guidance focus\n\n**5. cyber_threat_intel/053-m1016.md** · score 0.029\n\n> # Vulnerability Scanning\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1016\nSTIX ID: course-of-action--15437c6d-b998-4a36-be41-4ace3d54d266\n\nDescription:\nVulnerability scanning involves the automate\n\n</details>\n\n---\n📊 22.1s · 5 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the context provided, the following groups, campaigns, and software are involved:\n\n**Groups:**\n*   Lazarus Group (G0032)\n*   Gamaredon Group (G0047)\n*   Mustang Panda (G0129)\n*   Higaisa (G0126)\n\n**Software/Tools:**\n*   Cobalt Strike (S0154)\n*   KeyBoy (S0387)\n*   Okrum (S0439)\n*   SystemBC (S9001)\n*   StrelaStealer (S1183)\n*   Ninja (S1100)\n*   TrailBlazer (S0682)\n\n**Campaigns:**\n*   Operation Wocao (C0014)\n\n**Techniques/Mitigations involved in the connections:**\n*   **Protocol or Service Impersonation (T1001.003):** Used by Lazarus Group, Mustang Panda, Higaisa, Cobalt Strike, KeyBoy, Okrum, SystemBC, StrelaStealer, Ninja, TrailBlazer, and others to disguise command and control activity.\n*   **Data Obfuscation (T1001):** The parent technique of Protocol or Service Impersonation, used by Gamaredon Group, Okrum, SystemBC, SLOTHFULMEDIA, Ninja, TrailBlazer, and Operation Wocao.\n*   **Spearphishing Link (T1566.002):** Mitigated by Restrict Web-Based Content (M1021).\n*   **Restrict Web-Based Content (M1021):** A mitigation that restricts web-based content and mitigates Spearphishing Link (T1566.002) among other techniques.",
      "sources": [
        {
          "title": "cyber_threat_intel/044-t1001-003.md",
          "score": 0.21854897
        },
        {
          "title": "cyber_threat_intel/041-t1001.md",
          "score": 0.08096605
        },
        {
          "title": "cyber_threat_intel/058-m1021.md",
          "score": 0.042398058
        },
        {
          "title": "cyber_threat_intel/051-m1013.md",
          "score": 0.03222111
        },
        {
          "title": "cyber_threat_intel/053-m1016.md",
          "score": 0.029110333
        }
      ],
      "metrics": {
        "seconds": 22.0534749690014,
        "chunks": 5,
        "llm_calls": 2,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_protocol_and_web_mitigation_path",
      "model": "contextual-rag",
      "base_model": "contextual-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 20.6,
      "raw": "Based on the context provided, the following groups, campaigns, and software are involved:\n\n**Groups:**\n*   Lazarus Group (G0032)\n*   Gamaredon Group (G0047)\n*   Mustang Panda (G0129)\n*   Higaisa (G0126)\n\n**Campaigns:**\n*   Operation Wocao (C0014)\n\n**Software/Tools:**\n*   Cobalt Strike (S0154)\n*   FRAMESTING (S1120)\n*   StarProxy (S1227)\n*   PUBLOAD (S1228)\n*   BADCALL (S0245)\n*   KeyBoy (S0387)\n*   TAINTEDSCRIBE (S0586)\n*   Bankshot (S0239)\n*   StrelaStealer (S1183)\n*   Okrum (S0439)\n*   SystemBC (S9001)\n*   SLOTHFULMEDIA (S0533)\n*   Ninja (S1100)\n*   TrailBlazer (S0682)\n\n<details><summary>🔎 Retrieved context (5 sources)</summary>\n\n**1. cyber_threat_intel/044-t1001-003.md** · score 0.294\n\n> This section details the MITRE ATT&CK technique T1001.003, which describes how adversaries impersonate legitimate protocols or web services to disguise command and control traffic. It includes specific descriptions of methods like fake SSL/\n\n**2. cyber_threat_intel/041-t1001.md** · score 0.082\n\n> This section details the \"Data Obfuscation\" technique (T1001), describing how adversaries hide command and control traffic to evade detection. It lists specific malware groups that utilize this method, its sub-techniques, and associated det\n\n**3. cyber_threat_intel/058-m1021.md** · score 0.049\n\n> This section details the mitigation strategy M1021 for restricting web-based content, outlining specific implementation measures such as proxy filtering and DNS controls. It further lists the associated ATT&CK techniques that this course of\n\n**4. cyber_threat_intel/052-m1015.md** · score 0.039\n\n> This section details specific implementation measures for Active Directory Configuration, including account settings, logon restrictions, and authentication silos, while listing associated mitigation relations for various MITRE ATT&CK techn\n\n**5. cyber_threat_intel/053-m1016.md** · score 0.038\n\n> This section details the mitigation strategy M1016 for identifying and remediating security weaknesses across various environments, including endpoints, cloud infrastructure, and web applications. It outlines specific implementation measure\n\n</details>\n\n---\n📊 20.6s · 5 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the context provided, the following groups, campaigns, and software are involved:\n\n**Groups:**\n*   Lazarus Group (G0032)\n*   Gamaredon Group (G0047)\n*   Mustang Panda (G0129)\n*   Higaisa (G0126)\n\n**Campaigns:**\n*   Operation Wocao (C0014)\n\n**Software/Tools:**\n*   Cobalt Strike (S0154)\n*   FRAMESTING (S1120)\n*   StarProxy (S1227)\n*   PUBLOAD (S1228)\n*   BADCALL (S0245)\n*   KeyBoy (S0387)\n*   TAINTEDSCRIBE (S0586)\n*   Bankshot (S0239)\n*   StrelaStealer (S1183)\n*   Okrum (S0439)\n*   SystemBC (S9001)\n*   SLOTHFULMEDIA (S0533)\n*   Ninja (S1100)\n*   TrailBlazer (S0682)",
      "sources": [
        {
          "title": "cyber_threat_intel/044-t1001-003.md",
          "score": 0.29438436
        },
        {
          "title": "cyber_threat_intel/041-t1001.md",
          "score": 0.0817859
        },
        {
          "title": "cyber_threat_intel/058-m1021.md",
          "score": 0.048927207
        },
        {
          "title": "cyber_threat_intel/052-m1015.md",
          "score": 0.039276365
        },
        {
          "title": "cyber_threat_intel/053-m1016.md",
          "score": 0.038127616
        }
      ],
      "metrics": {
        "seconds": 20.56668209200143,
        "chunks": 5,
        "llm_calls": 2,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_protocol_and_web_mitigation_path",
      "model": "graph-rag",
      "base_model": "graph-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 21.4,
      "raw": "Based on the provided knowledge base, the relationship between **Protocol Or Service Impersonation**, **Restrict Web-Based Content**, **Spearphishing Link (T1566.002)**, and **Command-and-Control (C2)** techniques is defined by how certain threat actors exploit impersonation to establish C2 channels, while content restrictions serve as a primary mitigation strategy against the initial delivery vectors like spearphishing links.\n\n### Involvement of Groups, Campaigns, and Software in Protocol Impersonation for C2\n\nAdversaries utilize **Protocol Or Service Impersonation** (ATT&CK ID: T1001.003) to disguise command-and-control activity by making it blend in with legitimate network traffic or trusted services. This is achieved by manipulating HTTP headers, URI endpoints, SSL certificates, and transmitted data, or by impersonating fake SSL/TLS handshakes **(Reference 2)**.\n\nThe following specific entities are identified as using Protocol Or Service Impersonation for command-and-control or malicious payload loading:\n\n**Software/Tools:**\n*   **FRAMESTING**: Uses this technique for command-and-control communications.\n*   **PUBLOAD**: Uses it to load additional payloads.\n*   **Cobalt Strike**: Can be leveraged to perform Protocol Or Service Impersonation for adversary simulation and penetration testing.\n*   **BADCALL**, **KeyBoy**, **StarProxy**, **TAINTEDSCRIBE**, and **Bankshot**: All employ Protocol Or Service Impersonation for malicious activities or cyber espionage **(Reference 2)**.\n\n**Adversary Groups:**\n*   **Lazarus Group** (G0032)\n*   **Mustang Panda** (G0129)\n*   **Higaisa** (G0126)\n*   *(Note: Knowledge graph data also links \"RIPTIDE\" to Web Protocols for communication, which is related but distinct from the explicit Protocol Or Service Impersonation label in the text)* **(Reference 2)**.\n\n### The Role of Spearphishing Links and Restricting Web-Based Content\n\n**Spearphishing Link (T1566.002)** is a primary delivery mechanism used to deceive users into clicking malicious links, which often leads to malware execution or the establishment of an initial foothold **(Reference 1)**. **Restrict Web-Based Content** is explicitly cited as a mitigation measure that helps reduce the risk associated with Spearphishing Link attacks by limiting access to potentially malicious websites and unsafe downloads **(Reference 1)**.\n\nSeveral specific campaigns are linked to the use of Spearphishing Links, which serve as the entry point for subsequent activities (which may include C2 establishment):\n\n**Campaigns using Spearphishing Link:**\n*   **Night Dragon**: A cyber espionage campaign targeting oil, energy, and petrochemical companies. It used Spearphishing Links to deliver malware **(Reference 5)**.\n*   **C0011**: A suspected cyber espionage campaign by Transparent Tribe targeting students in India. It used Spearphishing Links to trick victims into clicking malicious links **(Reference 3)**.\n*   **Operation Spalax**: Targeted Colombian government and private companies. It distributed malware using generic phishing topics and utilized Spearphishing Links **(Reference 4)**.\n\n### Synthesis of Techniques\n\nThe connection between these elements is operational:\n1.  **Delivery**: Campaigns like **Night Dragon**, **C0011**, and **Operation Spalax** use **Spearphishing Link (T1566.002)** to deliver malware to victims **(References 3, 4, 5)**.\n2.  **Mitigation**: **Restrict Web-Based Content** is the recommended course-of-action to mitigate the risk of these spearphishing links being accessed or executed **(Reference 1)**.\n3.  **Persistence/C2**: Once inside a network, threat actors like those using **FRAMESTING**, **PUBLOAD**, or tools associated with **Lazarus Group** and **Mustang Panda** may employ **Protocol Or Service Impersonation** to disguise their command-and-control traffic **(Reference 2)**. Restricting web-based content also helps mitigate the risk of bidirectional communication between an attacker and a compromised system, thereby disrupting these C2 channels **(Reference 1)**.\n\n### References\n\n- [1] atlas-eb871dd9eb1420cca37311885e32eb2978363fc2b333a5945d38cba45c5440f9.txt\n- [2] atlas-f2da0aef56b5422b239b95fa0066ac9bc6ccf463850053a1e71120a8928e5598.txt\n- [3] atlas-5b1ba58640d8b400d03f20ce2d92bbf590e3b7410d6c53c523af0a192bcc4a94.txt\n- [4] atlas-91783cd00b9647215aa929de59676d68b7b5c2c0f974c0f09e1bc5a3f2c22732.txt\n- [5] atlas-7a646c98dadd818c19e47a06dbea67bc142d3e30bccab75568b7c46362feab53.txt\n\n<details><summary>🔎 Retrieved context (1 source)</summary>\n\n**1. LightRAG knowledge graph**\n\n> Graph + vector dual retrieval (profile=graph-rag) over the corpus's extracted entities and relations.\n\n</details>\n\n---\n📊 21.3s · 0 chunks · 1 LLM call · 0 cloud",
      "answer": "Based on the provided knowledge base, the relationship between **Protocol Or Service Impersonation**, **Restrict Web-Based Content**, **Spearphishing Link (T1566.002)**, and **Command-and-Control (C2)** techniques is defined by how certain threat actors exploit impersonation to establish C2 channels, while content restrictions serve as a primary mitigation strategy against the initial delivery vectors like spearphishing links.\n\n### Involvement of Groups, Campaigns, and Software in Protocol Impersonation for C2\n\nAdversaries utilize **Protocol Or Service Impersonation** (ATT&CK ID: T1001.003) to disguise command-and-control activity by making it blend in with legitimate network traffic or trusted services. This is achieved by manipulating HTTP headers, URI endpoints, SSL certificates, and transmitted data, or by impersonating fake SSL/TLS handshakes **(Reference 2)**.\n\nThe following specific entities are identified as using Protocol Or Service Impersonation for command-and-control or malicious payload loading:\n\n**Software/Tools:**\n*   **FRAMESTING**: Uses this technique for command-and-control communications.\n*   **PUBLOAD**: Uses it to load additional payloads.\n*   **Cobalt Strike**: Can be leveraged to perform Protocol Or Service Impersonation for adversary simulation and penetration testing.\n*   **BADCALL**, **KeyBoy**, **StarProxy**, **TAINTEDSCRIBE**, and **Bankshot**: All employ Protocol Or Service Impersonation for malicious activities or cyber espionage **(Reference 2)**.\n\n**Adversary Groups:**\n*   **Lazarus Group** (G0032)\n*   **Mustang Panda** (G0129)\n*   **Higaisa** (G0126)\n*   *(Note: Knowledge graph data also links \"RIPTIDE\" to Web Protocols for communication, which is related but distinct from the explicit Protocol Or Service Impersonation label in the text)* **(Reference 2)**.\n\n### The Role of Spearphishing Links and Restricting Web-Based Content\n\n**Spearphishing Link (T1566.002)** is a primary delivery mechanism used to deceive users into clicking malicious links, which often leads to malware execution or the establishment of an initial foothold **(Reference 1)**. **Restrict Web-Based Content** is explicitly cited as a mitigation measure that helps reduce the risk associated with Spearphishing Link attacks by limiting access to potentially malicious websites and unsafe downloads **(Reference 1)**.\n\nSeveral specific campaigns are linked to the use of Spearphishing Links, which serve as the entry point for subsequent activities (which may include C2 establishment):\n\n**Campaigns using Spearphishing Link:**\n*   **Night Dragon**: A cyber espionage campaign targeting oil, energy, and petrochemical companies. It used Spearphishing Links to deliver malware **(Reference 5)**.\n*   **C0011**: A suspected cyber espionage campaign by Transparent Tribe targeting students in India. It used Spearphishing Links to trick victims into clicking malicious links **(Reference 3)**.\n*   **Operation Spalax**: Targeted Colombian government and private companies. It distributed malware using generic phishing topics and utilized Spearphishing Links **(Reference 4)**.\n\n### Synthesis of Techniques\n\nThe connection between these elements is operational:\n1.  **Delivery**: Campaigns like **Night Dragon**, **C0011**, and **Operation Spalax** use **Spearphishing Link (T1566.002)** to deliver malware to victims **(References 3, 4, 5)**.\n2.  **Mitigation**: **Restrict Web-Based Content** is the recommended course-of-action to mitigate the risk of these spearphishing links being accessed or executed **(Reference 1)**.\n3.  **Persistence/C2**: Once inside a network, threat actors like those using **FRAMESTING**, **PUBLOAD**, or tools associated with **Lazarus Group** and **Mustang Panda** may employ **Protocol Or Service Impersonation** to disguise their command-and-control traffic **(Reference 2)**. Restricting web-based content also helps mitigate the risk of bidirectional communication between an attacker and a compromised system, thereby disrupting these C2 channels **(Reference 1)**.\n\n### References\n\n- [1] atlas-eb871dd9eb1420cca37311885e32eb2978363fc2b333a5945d38cba45c5440f9.txt\n- [2] atlas-f2da0aef56b5422b239b95fa0066ac9bc6ccf463850053a1e71120a8928e5598.txt\n- [3] atlas-5b1ba58640d8b400d03f20ce2d92bbf590e3b7410d6c53c523af0a192bcc4a94.txt\n- [4] atlas-91783cd00b9647215aa929de59676d68b7b5c2c0f974c0f09e1bc5a3f2c22732.txt\n- [5] atlas-7a646c98dadd818c19e47a06dbea67bc142d3e30bccab75568b7c46362feab53.txt",
      "sources": [
        {
          "title": "LightRAG knowledge graph",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 21.342192550997424,
        "chunks": 0,
        "llm_calls": 1,
        "cloud_calls": 0
      },
      "approach_metadata": {
        "lightrag": {
          "query_profile": "graph-rag"
        }
      }
    },
    {
      "query_id": "cyber_protocol_and_web_mitigation_path",
      "model": "agentic-rag",
      "base_model": "agentic-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 24.6,
      "raw": "Based on the provided context, the following groups, campaigns, and software are involved in using **Protocol or Service Impersonation** (often for Command-and-Control or spearphishing purposes):\n\n### Groups (Adversaries)\n*   **Lazarus Group**\n*   **Mustang Panda**\n*   **Higaisa**\n*   **TAINTEDSCRIBE**\n\n### Campaigns\n*   **Operation Spalax** (C0005)\n\n### Software / Tools / Malware\n*   **FRAMESTING**\n*   **StarProxy**\n*   **PUBLOAD**\n*   **BADCALL**\n*   **KeyBoy**\n*   **Bankshot**\n*   **Cobalt Strike** (noted as a legitimate security tool that can be leveraged by adversaries for this technique)\n\nThese entities utilize Protocol or Service Impersonation to disguise Command-and-Control traffic, often mimicking legitimate services like Gmail, Google Drive, or Yahoo Messenger to evade detection.\n\n<details><summary>🔎 Retrieved context (1 source)</summary>\n\n**1. 🤖 Agent trace**\n\n> **Step 1.** **Action:** `search_vectors(protocol impersonation web-based content restrictions spearphishing links command-and-control style techniques threat groups campaigns)`\n\n**Observation:** - cyber_threat_intel/058-m1021.md: # Restrict Web-Based Content\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1021\nSTIX ID: course-of-action--21da4fd4-27ad-4e9c-b93d-0b9b14d02c96\n\nDescription:\n\n- cyber_threat_intel/044-t1001-003.md: # Protocol or Service Imp\n\n**Step 2.** **Action:** `query_graph(threat actors using protocol impersonation and web-based content restrictions for spearphishing and C2)`\n\n**Observation:** Based on the provided context, here is a synthesis of how threat actors utilize Protocol or Service Impersonation in conjunction with the mitigating controls of Restricting Web-Based Content, particularly regarding Spearphishing and Command and Control (C2) activities.\n\n### Protocol or Service Imper\n\n</details>\n\n---\n📊 24.5s · 0 chunks · 4 LLM calls · 0 cloud",
      "answer": "Based on the provided context, the following groups, campaigns, and software are involved in using **Protocol or Service Impersonation** (often for Command-and-Control or spearphishing purposes):\n\n### Groups (Adversaries)\n*   **Lazarus Group**\n*   **Mustang Panda**\n*   **Higaisa**\n*   **TAINTEDSCRIBE**\n\n### Campaigns\n*   **Operation Spalax** (C0005)\n\n### Software / Tools / Malware\n*   **FRAMESTING**\n*   **StarProxy**\n*   **PUBLOAD**\n*   **BADCALL**\n*   **KeyBoy**\n*   **Bankshot**\n*   **Cobalt Strike** (noted as a legitimate security tool that can be leveraged by adversaries for this technique)\n\nThese entities utilize Protocol or Service Impersonation to disguise Command-and-Control traffic, often mimicking legitimate services like Gmail, Google Drive, or Yahoo Messenger to evade detection.",
      "sources": [
        {
          "title": "🤖 Agent trace",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 24.537661760998162,
        "chunks": 0,
        "llm_calls": 4,
        "cloud_calls": 0
      }
    },
    {
      "query_id": "cyber_protocol_and_web_mitigation_path",
      "model": "n8n-adaptive-rag",
      "base_model": "n8n-adaptive-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 0.7,
      "raw": "Based on the provided context, the following groups, campaigns, and software are involved in using **Protocol or Service Impersonation** (often for Command-and-Control or spearphishing purposes):\n\n### Groups (Adversaries)\n*   **Lazarus Group**\n*   **Mustang Panda**\n*   **Higaisa**\n*   **TAINTEDSCRIBE**\n\n### Campaigns\n*   **Operation Spalax** (C0005)\n\n### Software / Tools / Malware\n*   **FRAMESTING**\n*   **StarProxy**\n*   **PUBLOAD**\n*   **BADCALL**\n*   **KeyBoy**\n*   **Bankshot**\n*   **Cobalt Strike** (noted as a legitimate security tool that can be leveraged by adversaries for this technique)\n\nThese entities utilize Protocol or Service Impersonation to disguise Command-and-Control traffic, often mimicking legitimate services like Gmail, Google Drive, or Yahoo Messenger to evade detection.\n\n<details><summary>🔎 Retrieved context (1 source)</summary>\n\n**1. 🤖 Agent trace**\n\n> **Step 1.** **Action:** `search_vectors(protocol impersonation web-based content restrictions spearphishing links command-and-control style techniques threat groups campaigns)`\n\n**Observation:** - cyber_threat_intel/058-m1021.md: # Restrict Web-Based Content\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1021\nSTIX ID: course-of-action--21da4fd4-27ad-4e9c-b93d-0b9b14d02c96\n\nDescription:\n\n- cyber_threat_intel/044-t1001-003.md: # Protocol or Service Imp\n\n**Step 2.** **Action:** `query_graph(threat actors using protocol impersonation and web-based content restrictions for spearphishing and C2)`\n\n**Observation:** Based on the provided context, here is a synthesis of how threat actors utilize Protocol or Service Impersonation in conjunction with the mitigating controls of Restricting Web-Based Content, particularly regarding Spearphishing and Command and Control (C2) activities.\n\n### Protocol or Service Imper\n\n</details>\n\n---\n📊 0.7s · 0 chunks · 5 LLM calls · 0 cloud",
      "answer": "Based on the provided context, the following groups, campaigns, and software are involved in using **Protocol or Service Impersonation** (often for Command-and-Control or spearphishing purposes):\n\n### Groups (Adversaries)\n*   **Lazarus Group**\n*   **Mustang Panda**\n*   **Higaisa**\n*   **TAINTEDSCRIBE**\n\n### Campaigns\n*   **Operation Spalax** (C0005)\n\n### Software / Tools / Malware\n*   **FRAMESTING**\n*   **StarProxy**\n*   **PUBLOAD**\n*   **BADCALL**\n*   **KeyBoy**\n*   **Bankshot**\n*   **Cobalt Strike** (noted as a legitimate security tool that can be leveraged by adversaries for this technique)\n\nThese entities utilize Protocol or Service Impersonation to disguise Command-and-Control traffic, often mimicking legitimate services like Gmail, Google Drive, or Yahoo Messenger to evade detection.",
      "sources": [
        {
          "title": "🤖 Agent trace",
          "score": null
        }
      ],
      "metrics": {
        "seconds": 0.7373630419970141,
        "chunks": 0,
        "llm_calls": 5,
        "cloud_calls": 0
      },
      "approach_metadata": {
        "adaptive": {
          "route": "complex",
          "approach": "agentic-rag"
        }
      }
    },
    {
      "query_id": "cyber_protocol_and_web_mitigation_path",
      "model": "lazy-graph-rag",
      "base_model": "lazy-graph-rag",
      "flavor": "default",
      "requires_reingest": false,
      "ok": true,
      "latency_s": 5.4,
      "raw": "Based on the context provided, the following groups, campaigns, and software are involved:\n\n**Groups:**\n*   **Lazarus Group (G0032)**\n*   **Mustang Panda (G0129)**\n*   **Higaisa (G0126)**\n*   **Transparent Tribe (G0134)**\n\n**Campaigns:**\n*   **C0011**\n\n**Software/Tools:**\n*   **FRAMESTING (S1120)**\n*   **StarProxy (S1227)**\n*   **PUBLOAD (S1228)**\n*   **Cobalt Strike (S0154)**\n*   **BADCALL (S0245)**\n*   **KeyBoy (S0387)**\n*   **TAINTEDSCRIBE (S0586)**\n*   **Bankshot (S0239)**\n\n<details><summary>🔎 Retrieved context (8 sources)</summary>\n\n**1. cyber_threat_intel/058-m1021.md** · score 53.000\n\n> # Restrict Web-Based Content\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1021\nSTIX ID: course-of-action--21da4fd4-27ad-4e9c-b93d-0b9b14d02c96\n\nDescription:\nRestricting web-based content involves e\n\n**2. cyber_threat_intel/044-t1001-003.md** · score 21.500\n\n> # Protocol or Service Impersonation\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1001.003\nSTIX ID: attack-pattern--c325b232-d5bc-4dde-a3ec-71f3db9e8adc\n\nDescription:\nAdversaries may impersonate legit\n\n**3. cyber_threat_intel/055-m1018.md** · score 21.000\n\n> # User Account Management\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1018\nSTIX ID: course-of-action--93e7968a-9074-4eac-8ae9-9f5200ec3317\n\nDescription:\nUser Account Management involves implementi\n\n**4. cyber_threat_intel/059-m1022.md** · score 18.000\n\n> # Restrict File and Directory Permissions\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: course-of-action\nATT&CK ID: M1022\nSTIX ID: course-of-action--987988f0-cf86-4680-a875-2f6456ab2448\n\nDescription:\nRestricting file and direct\n\n**5. cyber_threat_intel/018-c0011.md** · score 17.429\n\n> # C0011\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: campaign\nATT&CK ID: C0011\nSTIX ID: campaign--b4e5a4a9-f3be-4631-ba8f-da6ebb067fac\n\nDescription:\n[C0011](https://attack.mitre.org/campaigns/C0011) was a suspected cyber espio\n\n**6. cyber_threat_intel/008-g0008.md** · score 17.000\n\n> # Carbanak\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: intrusion-set\nATT&CK ID: G0008\nSTIX ID: intrusion-set--55033a4d-3ffe-46b2-99b4-2c1541e9ce1c\n\nDescription:\n[Carbanak](https://attack.mitre.org/groups/G0008) is a cybercrim\n\n**7. cyber_threat_intel/036-s0039.md** · score 17.000\n\n> # Net\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: tool\nATT&CK ID: S0039\nSTIX ID: tool--03342581-f790-4f03-ba41-e82e67392e23\n\nDescription:\nThe [Net](https://attack.mitre.org/software/S0039) utility is a component of the Window\n\n**8. cyber_threat_intel/041-t1001.md** · score 16.750\n\n> # Data Obfuscation\n\nSource: MITRE ATT&CK Enterprise STIX bundle\n\nObject type: attack-pattern\nATT&CK ID: T1001\nSTIX ID: attack-pattern--ad255bfe-a9e6-4b52-a258-8d3462abe842\n\nDescription:\nAdversaries may obfuscate command and control traffic \n\n</details>\n\n---\n📊 5.4s · 8 chunks · 2 LLM calls · 0 cloud",
      "answer": "Based on the context provided, the following groups, campaigns, and software are involved:\n\n**Groups:**\n*   **Lazarus Group (G0032)**\n*   **Mustang Panda (G0129)**\n*   **Higaisa (G0126)**\n*   **Transparent Tribe (G0134)**\n\n**Campaigns:**\n*   **C0011**\n\n**Software/Tools:**\n*   **FRAMESTING (S1120)**\n*   **StarProxy (S1227)**\n*   **PUBLOAD (S1228)**\n*   **Cobalt Strike (S0154)**\n*   **BADCALL (S0245)**\n*   **KeyBoy (S0387)**\n*   **TAINTEDSCRIBE (S0586)**\n*   **Bankshot (S0239)**",
      "sources": [
        {
          "title": "cyber_threat_intel/058-m1021.md",
          "score": 53.0
        },
        {
          "title": "cyber_threat_intel/044-t1001-003.md",
          "score": 21.5
        },
        {
          "title": "cyber_threat_intel/055-m1018.md",
          "score": 21.0
        },
        {
          "title": "cyber_threat_intel/059-m1022.md",
          "score": 18.0
        },
        {
          "title": "cyber_threat_intel/018-c0011.md",
          "score": 17.42857142857143
        },
        {
          "title": "cyber_threat_intel/008-g0008.md",
          "score": 17.0
        },
        {
          "title": "cyber_threat_intel/036-s0039.md",
          "score": 17.0
        },
        {
          "title": "cyber_threat_intel/041-t1001.md",
          "score": 16.75
        }
      ],
      "metrics": {
        "seconds": 5.375922835999518,
        "chunks": 8,
        "llm_calls": 2,
        "cloud_calls": 0
      },
      "approach_metadata": {
        "lazy_graph": {
          "experimental": true,
          "cache_hit": true,
          "index_seconds": 0.008324,
          "graph_chunks": 66,
          "graph_concepts": 762,
          "graph_edges": 13949,
          "relevance_tests": 24,
          "relevance_budget": 24,
          "seed_k": 8,
          "max_context_chunks": 8,
          "llm_index_calls": 0,
          "cache_namespace": "RagBase_cyber_threat_intel.concepts-24"
        }
      }
    }
  ],
  "ingestion": {
    "id": "cb1e73a7-5d4d-4946-be2e-ab1f52d2f4b4",
    "job_id": "cb1e73a7-5d4d-4946-be2e-ab1f52d2f4b4",
    "profile": "cyber_threat_intel",
    "revision": "bfc79c213d77cf5e",
    "content_digest": "47460fe8a60b1314",
    "mode": "atlas-job"
  },
  "runtime": {
    "project": "rag-showcase",
    "base_port": 22000,
    "provider_sources": {
      "llm": "ollama-localhost",
      "comfyui": "disabled"
    },
    "rag_showcase": {
      "commit": "5acdcd336b4f3fb18d1ab6e436e59e4751a55274",
      "dirty": true,
      "tree": "2b7f44d6cce05e258d6e7b576e03bb4689a2af9d",
      "patch_sha256": "99f76ed56aeb7125223815bd8a7521103cc58a7d7f90214634602e2f55e3ce27",
      "patch_capture": "retrospective-known-scope",
      "patch_basis": "sha256 of canonical known-dirty-scope manifest",
      "known_dirty_scope": [
        "README.md",
        "compare/",
        "docs/",
        "infra (submodule pointer)",
        "scripts/",
        "tests/"
      ]
    },
    "atlas": {
      "commit": "c744467e3c81d635f0d556fedca369cfca659e64",
      "dirty": false,
      "tree": "de6d67526e527d394fb4442f67ce21b294287fcd",
      "patch_sha256": "3609b28c0c5a318c567b989afb4c72264a6af9d9a8e22b77182cc01eca02e661",
      "patch_capture": "exact"
    },
    "judge_panel": {
      "endpoint": "http://localhost:11434/v1/chat/completions",
      "models": [
        "qwen3.6:latest",
        "gemma4:31b"
      ],
      "thinking": false
    },
    "runtime_files": {
      "model_inventory": {
        "path": "infra/volumes/litellm/consumer-models.yaml",
        "sha256": "da5024f2b962dc9d1e99e5cb29c47d7e393682568cc99fa9ac1c62ba0a18264e",
        "entries": [
          "agentic-rag",
          "agentic-rag-deeper",
          "contextual-rag",
          "contextual-rag-high-recall",
          "graph-rag",
          "graph-rag-fast",
          "graph-rag-rerank",
          "graph-rag-wide",
          "hybrid-rag",
          "hybrid-rag-fast",
          "hybrid-rag-high-recall",
          "lazy-graph-rag",
          "lazy-graph-rag-balanced",
          "lazy-graph-rag-fast",
          "lazy-graph-rag-wide",
          "n8n-adaptive-rag",
          "n8n-adaptive-rag-default",
          "vanilla-rag",
          "vanilla-rag-wide"
        ]
      },
      "lightrag_query_profiles": {
        "path": "infra/volumes/backend/lightrag-query-profiles.json",
        "sha256": "eab5a36f8666a58abe56f94426c43165e2b203f4ab042f4d82f529befb3921a4",
        "entries": [
          "graph-rag",
          "graph-rag-fast",
          "graph-rag-rerank",
          "graph-rag-wide"
        ]
      }
    }
  }
}
