{
  "hunt": {
    "meta": {
      "tlp": "clear",
      "hunt": {
        "handoff": "keep-as-periodic-hunt",
        "trigger": "intel-report",
        "methodology": "model-assisted",
        "applicability": "campaign-specific",
        "justification": "CISA BOD 26-04 mandates that organizations must run a forensic investigation in parallel with patching for Tier 1 vulnerabilities. Failure to do so leaves an organization blind to intruders who gained access before the patch was applied."
      },
      "name": "BOD 26-04 Critical Vulnerability Triage",
      "type": "investigation",
      "labels": [
        "hunt",
        "attack.t1190",
        "attack.t1059.003",
        "attack.t1059.004",
        "attack.t1021.001",
        "attack.t1074.001",
        "execution",
        "initial access",
        "lateral movement"
      ],
      "related": [
        {
          "hunt": "shadow-it-exposed-service-discovery",
          "reason": "Correct identification of the external attack surface is required to accurately scope BOD 26-04 timelines.",
          "relation": "precedes"
        }
      ],
      "targets": {
        "web": {
          "name": "Web server / proxy logs",
          "category": "siem",
          "telemetry": [
            "network"
          ]
        },
        "hunter": {
          "name": "Hunt agent",
          "agent": true
        },
        "analyst": {
          "name": "Tier-2 analyst",
          "role": "analyst"
        },
        "endpoint": {
          "name": "Endpoint telemetry (hb_ surfaces)",
          "category": "endpoint",
          "telemetry": [
            "endpoint"
          ]
        }
      },
      "analysis": "A detection rule fires on a known shell; this hunt performs forensic triage by cross-referencing vulnerability scan status, internet exposure, and anomalous server-side error patterns to satisfy a specific regulatory mandate.",
      "coverage": [
        {
          "stage": "exposed-vulnerable-applications",
          "steps": [
            "vulnerability-scoping"
          ],
          "status": "covered"
        },
        {
          "stage": "unauthenticated-exploit-bypass",
          "steps": [
            "rare-portal-errors"
          ],
          "status": "covered"
        },
        {
          "stage": "elevated-execution",
          "steps": [
            "service-shell-execution"
          ],
          "status": "covered"
        },
        {
          "stage": "post-exploitation-triage",
          "reason": "Requires volatile memory analysis or network traffic pcaps which are not present in the listed surfaces.",
          "status": "not_visible",
          "blind_spot": "no-volatile-memory-access"
        }
      ],
      "scenario": {
        "stages": [
          {
            "name": "Public Asset Exposure",
            "slug": "exposed-vulnerable-applications",
            "tactic": "initial-access",
            "techniques": [
              "T1190"
            ],
            "observables": [
              "microsoft 365",
              "palo alto",
              "sharepoint",
              "n-central",
              "User-ID Authentication Portal",
              "Captive Portal",
              "CVE-2026-55040",
              "CVE-2026-63520",
              "CVE-2026-0300",
              "CVE-2026-18556",
              "CVE-2026-18577"
            ]
          },
          {
            "name": "Vulnerability Exploitation",
            "slug": "unauthenticated-exploit-bypass",
            "tactic": "initial-access",
            "techniques": [
              "T1190"
            ],
            "observables": [
              "JWT bypass",
              "buffer overflow",
              "specially crafted packets",
              "authentication bypass",
              "account takeover"
            ]
          },
          {
            "name": "System-Level Execution",
            "slug": "elevated-execution",
            "tactic": "execution",
            "techniques": [
              "T1059"
            ],
            "observables": [
              "SharePoint service account",
              "root privileges",
              "arbitrary code execution",
              "unauthenticated RCE"
            ]
          },
          {
            "name": "Post-Exploitation Activity",
            "slug": "post-exploitation-triage",
            "tactic": "lateral-movement",
            "techniques": [
              "T1021",
              "T1083",
              "T1074"
            ],
            "observables": [
              "lateral movement",
              "data staging",
              "volatile data capture",
              "persistence establishment"
            ]
          }
        ],
        "summary": "Adversaries exploit publicly exposed, high-impact vulnerabilities in SharePoint, PAN-OS, and N-central to achieve unauthenticated remote code execution or administrative takeover. Under CISA BOD 26-04, these Tier 1 exploits require rapid forensic triage within 72 hours to detect post-exploitation behaviors such as lateral movement and data staging."
      },
      "severity": "high",
      "rationale": "Focus first on hosts confirmed as internet-facing in hb_exposed_assets. Use the device_uid from hb_vulnerability_finding to retrieve the Network Hostname from hb_devices to correctly populate scope_hosts for the behavioral steps.",
      "guardrails": {
        "claims": "no_unsupported",
        "evidence": "citation_required",
        "telemetry": "untrusted",
        "missing_data": "not_benign"
      },
      "hypothesis": "An attacker has exploited a publicly exposed, KEV-listed application (SharePoint, PAN-OS, or N-central) before remediation, establishing initial access or executing code with high privileges.",
      "parameters": {
        "cve_ids": {
          "from": {
            "ref": "Rapid7 BOD 26-04",
            "kind": "article",
            "observed": "2026-11-04"
          },
          "type": "list[string]",
          "default": [
            "CVE-2026-0300",
            "CVE-2026-18556",
            "CVE-2026-18577",
            "CVE-2026-55040",
            "CVE-2026-63520"
          ],
          "description": "Target KEV-listed vulnerabilities from the CISA catalog."
        },
        "scope_hosts": {
          "type": "list[host]",
          "default": [],
          "description": "Hostnames identified as vulnerable in the scoping step; leave empty to scan the entire estate."
        },
        "shell_names": {
          "type": "list[string]",
          "default": [
            "cmd.exe",
            "powershell.exe",
            "sh",
            "bash",
            "zsh"
          ],
          "description": "Standard shell processes often used for arbitrary code execution."
        },
        "lookback_days": {
          "type": "number",
          "default": "14",
          "description": "Days of history to examine for exploitation evidence."
        },
        "vulnerable_paths": {
          "type": "list[path]",
          "default": [
            "/portal/",
            "/_layouts/15/",
            "/ncentral/"
          ],
          "description": "Sensitive URL paths associated with the vulnerable service portals."
        },
        "vulnerable_parents": {
          "type": "list[string]",
          "default": [
            "w3wp.exe",
            "java",
            "pan_auth",
            "authd",
            "tomcat"
          ],
          "description": "Processes associated with the vulnerable services (SharePoint, PAN-OS, N-central)."
        }
      },
      "provenance": {
        "authors": [
          {
            "org": "huntbase.io",
            "name": "Huntbase hunt generation"
          }
        ],
        "generated": {
          "by": "huntbase-hunt-generation",
          "from": "https://www.rapid7.com/blog/post/it-racing-the-three-day-clock-cisa-bod-26-04",
          "gates": [
            "dry-run",
            "lint"
          ],
          "model": "hb_google/gemini-3-flash-preview"
        }
      },
      "references": [
        {
          "url": "https://www.rapid7.com/blog/post/it-racing-the-three-day-clock-cisa-bod-26-04",
          "name": "Rapid7 \u2014 The Race Against the 3-Day Clock: How Rapid7 Helps Meet BOD 26-04 Compliance"
        }
      ],
      "blind_spots": [
        {
          "id": "no-volatile-memory-access",
          "risk": "A sophisticated buffer overflow (like CVE-2026-0300) can execute code entirely in memory; without volatile data capture, this hunt may return a false negative.",
          "stage": "post-exploitation-triage",
          "question": "Was fileless code injected into memory without spawning a separate process?",
          "requires": "Forensic RAM capture (e.g. Velociraptor)"
        },
        {
          "id": "http-body-inspection",
          "risk": "Surface telemetry sees only metadata; if the exploit doesn't trigger a 403/500 or a child process, it remains invisible.",
          "stage": "unauthenticated-exploit-bypass",
          "question": "Did the HTTP request contain a JWT bypass or exploit payload in the body?",
          "requires": "hb_http_activity with request_body or WAF logs"
        }
      ]
    },
    "name": "BOD 26-04 Critical Vulnerability Triage",
    "description": "This hunt implements the mandatory forensic triage lifecycle established by CISA Binding Operational Directive 26-04. The directive requires that for Tier 1 vulnerabilities (actively exploited and providing total control), organizations must not only patch within 72 hours but also perform a concurrent forensic investigation to detect pre-patch compromise. This hunt scopes the estate to vulnerable assets, identifies anomalous web activity on those portals (specifically 403/500 errors indicating bypass attempts), and monitors for shells spawned by the vulnerable service daemons. An agent synthesizes the evidence to meet the triage reporting requirement."
  },
  "nodes": [
    {
      "id": "hypothesis",
      "type": "hypothesis",
      "label": "Hypothesis",
      "config": {
        "tags": [],
        "coverage": [
          {
            "stage": "exposed-vulnerable-applications",
            "steps": [
              "vulnerability-scoping"
            ],
            "status": "covered"
          },
          {
            "stage": "unauthenticated-exploit-bypass",
            "steps": [
              "rare-portal-errors"
            ],
            "status": "covered"
          },
          {
            "stage": "elevated-execution",
            "steps": [
              "service-shell-execution"
            ],
            "status": "covered"
          },
          {
            "stage": "post-exploitation-triage",
            "reason": "Requires volatile memory analysis or network traffic pcaps which are not present in the listed surfaces.",
            "status": "not_visible",
            "blind_spot": "no-volatile-memory-access"
          }
        ],
        "rationale": "An attacker has exploited a publicly exposed, KEV-listed application (SharePoint, PAN-OS, or N-central) before remediation, establishing initial access or executing code with high privileges.",
        "blind_spots": [
          {
            "id": "no-volatile-memory-access",
            "risk": "A sophisticated buffer overflow (like CVE-2026-0300) can execute code entirely in memory; without volatile data capture, this hunt may return a false negative.",
            "stage": "post-exploitation-triage",
            "question": "Was fileless code injected into memory without spawning a separate process?",
            "requires": "Forensic RAM capture (e.g. Velociraptor)"
          },
          {
            "id": "http-body-inspection",
            "risk": "Surface telemetry sees only metadata; if the exploit doesn't trigger a 403/500 or a child process, it remains invisible.",
            "stage": "unauthenticated-exploit-bypass",
            "question": "Did the HTTP request contain a JWT bypass or exploit payload in the body?",
            "requires": "hb_http_activity with request_body or WAF logs"
          }
        ],
        "scoping_notes": "Focus first on hosts confirmed as internet-facing in hb_exposed_assets. Use the device_uid from hb_vulnerability_finding to retrieve the Network Hostname from hb_devices to correctly populate scope_hosts for the behavioral steps.",
        "beyond_detection": "A detection rule fires on a known shell; this hunt performs forensic triage by cross-referencing vulnerability scan status, internet exposure, and anomalous server-side error patterns to satisfy a specific regulatory mandate."
      }
    },
    {
      "id": "vulnerability-scoping",
      "type": "query",
      "label": "Identify KEV-listed vulnerable assets",
      "config": {
        "dsl": "sqlite",
        "role": "scoping",
        "source": "endpoint",
        "content": "SELECT device_uid, resource_uid, cve_uid, severity, status, first_seen FROM hb_vulnerability_finding WHERE instr(',' || '{{cve_ids}}' || ',', ',' || cve_uid || ',') > 0 AND status != 'suppressed' AND resource_type IN ('device', 'virtual_machine')",
        "surface": "hb_vulnerability_finding",
        "description": "Scope the estate to assets reporting target CVEs. While this surface uses device_uid, the agent will correlate this with hostnames from hb_devices to enable downstream triage on behavioral surfaces.",
        "expected_signal": "A list of device identifiers that are confirmed vulnerable. Silence indicates no known vulnerable assets in current scan results."
      },
      "parents": [
        {
          "id": "hypothesis"
        }
      ],
      "primitive_config": {
        "dsl": "sqlite",
        "role": "scoping",
        "label": "Identify KEV-listed vulnerable assets",
        "reads": [
          "device_uid",
          "resource_uid",
          "cve_uid",
          "severity",
          "status",
          "first_seen"
        ],
        "source": "hb_vulnerability_finding",
        "target": "endpoint",
        "content": "SELECT device_uid, resource_uid, cve_uid, severity, status, first_seen FROM hb_vulnerability_finding WHERE instr(',' || '{{cve_ids}}' || ',', ',' || cve_uid || ',') > 0 AND status != 'suppressed' AND resource_type IN ('device', 'virtual_machine')",
        "silence": "not_evidence_of_absence",
        "expected": "A list of device identifiers that are confirmed vulnerable. Silence indicates no known vulnerable assets in current scan results.",
        "verified": "dry-run",
        "verified_at": "2026-11-18"
      }
    },
    {
      "id": "rare-portal-errors",
      "type": "query",
      "label": "Rare HTTP errors on vulnerable paths",
      "config": {
        "dsl": "sqlite",
        "role": "baseline",
        "source": "web",
        "content": "SELECT device_hostname, url_path, status_code, COUNT(DISTINCT device_hostname) AS hosts, COUNT(*) AS requests FROM hb_http_activity WHERE (status_code = 403 OR status_code = 500) AND instr(',' || '{{vulnerable_paths}}' || ',', ',' || LOWER(url_path) || ',') > 0 AND (('{{scope_hosts}}' = '') OR (instr(',' || '{{scope_hosts}}' || ',', ',' || device_hostname || ',') > 0)) AND time >= datetime('now', '-{{lookback_days}} days') GROUP BY device_hostname, url_path, status_code HAVING requests < 10 ORDER BY requests ASC",
        "surface": "hb_http_activity",
        "description": "Find unusual internal server errors or forbidden responses on the vulnerable portals, which often correlate with bypass attempts or failed exploit payloads.",
        "expected_signal": "Anomalous 403 or 500 status codes on specific portal paths. Silence suggests no obvious failed exploit traffic matching these indicators."
      },
      "parents": [
        {
          "id": "vulnerability-scoping"
        }
      ],
      "primitive_config": {
        "dsl": "sqlite",
        "role": "baseline",
        "label": "Rare HTTP errors on vulnerable paths",
        "reads": [
          "device_hostname",
          "url_path",
          "status_code",
          "time"
        ],
        "source": "hb_http_activity",
        "target": "web",
        "content": "SELECT device_hostname, url_path, status_code, COUNT(DISTINCT device_hostname) AS hosts, COUNT(*) AS requests FROM hb_http_activity WHERE (status_code = 403 OR status_code = 500) AND instr(',' || '{{vulnerable_paths}}' || ',', ',' || LOWER(url_path) || ',') > 0 AND (('{{scope_hosts}}' = '') OR (instr(',' || '{{scope_hosts}}' || ',', ',' || device_hostname || ',') > 0)) AND time >= datetime('now', '-{{lookback_days}} days') GROUP BY device_hostname, url_path, status_code HAVING requests < 10 ORDER BY requests ASC",
        "silence": "not_evidence_of_absence",
        "baseline": {
          "window": "{{lookback_days}}d",
          "compare": "new_this_window"
        },
        "expected": "Anomalous 403 or 500 status codes on specific portal paths. Silence suggests no obvious failed exploit traffic matching these indicators.",
        "verified": "dry-run",
        "prevalence": {
          "by": "device_hostname",
          "key": [
            "url_path",
            "status_code"
          ],
          "rare_below": 10
        },
        "verified_at": "2026-11-18"
      }
    },
    {
      "id": "service-shell-execution",
      "type": "query",
      "label": "Shells spawned by vulnerable services",
      "config": {
        "dsl": "sqlite",
        "role": "detection-candidate",
        "source": "endpoint",
        "content": "SELECT device_hostname, process_name, process_cmd_line, parent_process_name, user_name, time FROM hb_process_activity WHERE (('{{scope_hosts}}' = '') OR (instr(',' || '{{scope_hosts}}' || ',', ',' || device_hostname || ',') > 0)) AND instr(',' || '{{shell_names}}' || ',', ',' || LOWER(process_name) || ',') > 0 AND instr(',' || '{{vulnerable_parents}}' || ',', ',' || LOWER(parent_process_name) || ',') > 0 AND time >= datetime('now', '-{{lookback_days}} days')",
        "surface": "hb_process_activity",
        "description": "Detect arbitrary code execution by identifying shells launched from the vulnerable service parents, including the Palo Alto and N-central daemons.",
        "expected_signal": "A shell process running with service-level or root privileges. This is a high-fidelity indicator of exploitation."
      },
      "parents": [
        {
          "id": "rare-portal-errors"
        }
      ],
      "primitive_config": {
        "dsl": "sqlite",
        "role": "detection-candidate",
        "label": "Shells spawned by vulnerable services",
        "reads": [
          "device_hostname",
          "process_name",
          "process_cmd_line",
          "parent_process_name",
          "user_name",
          "time"
        ],
        "source": "hb_process_activity",
        "target": "endpoint",
        "content": "SELECT device_hostname, process_name, process_cmd_line, parent_process_name, user_name, time FROM hb_process_activity WHERE (('{{scope_hosts}}' = '') OR (instr(',' || '{{scope_hosts}}' || ',', ',' || device_hostname || ',') > 0)) AND instr(',' || '{{shell_names}}' || ',', ',' || LOWER(process_name) || ',') > 0 AND instr(',' || '{{vulnerable_parents}}' || ',', ',' || LOWER(parent_process_name) || ',') > 0 AND time >= datetime('now', '-{{lookback_days}} days')",
        "silence": "not_evidence_of_absence",
        "expected": "A shell process running with service-level or root privileges. This is a high-fidelity indicator of exploitation.",
        "verified": "dry-run",
        "verified_at": "2026-11-18"
      }
    },
    {
      "id": "forensic-triage-agent",
      "type": "analytic",
      "label": "Synthesize triage evidence",
      "config": {
        "cite": "required",
        "tools": [
          "endpoint",
          "web"
        ],
        "context": [
          "vulnerability-scoping",
          "rare-portal-errors",
          "service-shell-execution"
        ],
        "objective": "Determine if any host identified as vulnerable (via device_uid correlation) shows evidence of exploitation in the HTTP or process logs. The verdict must distinguish between failed attempts (403/500 errors) and successful code execution (shells spawned by service parents).",
        "description": "Analyze the vulnerability scoping and behavioral results to reach a compromise verdict per host, fulfilling Phase 5 of the CISA protocol.",
        "max_iterations": 5,
        "expected_signal": "A per-host verdict citing evidence of exploitation.",
        "success_criteria": "A verdict of malicious | suspicious | benign per host, citing specific rows for any compromise evidence found."
      },
      "parents": [
        {
          "id": "service-shell-execution"
        }
      ]
    },
    {
      "id": "triage-decision",
      "type": "checkpoint",
      "label": "Evaluate compromise verdict",
      "config": {
        "fuzzy": true,
        "judge": "hunter",
        "question": "the forensic-triage-agent verdict is malicious or suspicious for at least one host",
        "condition": "the forensic-triage-agent verdict is malicious or suspicious for at least one host",
        "blind_spot": "no-volatile-memory-access",
        "confidence": "high",
        "description": "Route the hunt based on whether evidence of compromise was found during the triage window.",
        "checkpoint_type": "mandatory"
      },
      "parents": [
        {
          "id": "forensic-triage-agent"
        }
      ]
    },
    {
      "id": "remediation-review",
      "type": "task",
      "label": "Remediation and escalation review",
      "config": {
        "assignee": "analyst",
        "description": "Analyze the findings to determine if the vulnerability has been exploited and if full IR escalation is required.",
        "instructions": "Review the agent's cited rows. If exploitation is confirmed, activate the Incident Response plan immediately (Phase 6 of BOD 26-04). If only failed attempts were found, ensure the patching team has prioritized these specific assets for immediate remediation to close the exposure window."
      },
      "parents": [
        {
          "id": "triage-decision",
          "branch": "on_supports"
        },
        {
          "id": "triage-decision",
          "branch": "default"
        },
        {
          "id": "triage-decision",
          "branch": "on_unavailable"
        }
      ]
    },
    {
      "id": "compliance-close-out",
      "type": "task",
      "label": "Compliance close-out",
      "config": {
        "assignee": "analyst",
        "description": "Document the forensic triage results to satisfy BOD 26-04 reporting requirements.",
        "instructions": "Record the hosts examined, the search criteria used (403/500 errors and service-child processes), and the final forensic verdict. This documentation serves as the organization's proof of compliance with the 72-hour triage mandate."
      },
      "parents": [
        {
          "id": "triage-decision",
          "branch": "on_refutes"
        },
        {
          "id": "remediation-review"
        }
      ]
    }
  ]
}