Upwind Vulnerability Detection Passthrough

Status: Experimental
Severity: medium
Group by: id, severity
Log types: Upwind.Detections
Tags: Upwind, Passthrough, Vulnerability, Initial Access, Exploit Public-Facing Application
Reference: https://docs.upwind.io/restapi/v1/get-threat-detection
Source: github.com/panther-labs/panther-analysis

Re-raises Upwind vulnerability detections in Panther. Covers exploitable CVEs identified in runtime containers, VMs, and serverless environments, prioritized by active exposure.

MITRE ATT&CK coverage

Tactic	Techniques
Initial Access	`T1190` Exploit Public-Facing Application

Rule body yaml

AnalysisType: rule
RuleID: Upwind.Detection.Vulnerability.Passthrough
DisplayName: Upwind Vulnerability Detection Passthrough
Description: >
  Re-raises Upwind vulnerability detections in Panther. Covers exploitable CVEs identified
  in runtime containers, VMs, and serverless environments, prioritized by active exposure.
Runbook: |
  1. Check whether resource.internet_exposure.ingress.active_communication is true and review resource.risk_categories to assess the blast radius of the vulnerability on resource.name in resource.cloud_account_id
  2. Query Upwind.Detections for all vulnerability detections on the same resource.name in the past 90 days to evaluate patch cadence and determine if this finding is recurring
  3. Search for runtime or network threat detections against the same resource.name or resource.cloud_account_id in the past 30 days to determine whether the vulnerability has already been exploited
Reference: https://docs.upwind.io/restapi/v1/get-threat-detection
Enabled: true
Filename: upwind_vulnerability_detection_passthrough.py
Severity: Medium
Status: Experimental
LogTypes:
  - Upwind.Detections
DedupPeriodMinutes: 1440
Threshold: 1
Reports:
  MITRE ATT&CK:
    - TA0001:T1190  # Initial Access: Exploit Public-Facing Application
Tags:
  - Upwind
  - Passthrough
  - Vulnerability
  - Initial Access
  - Exploit Public-Facing Application
Tests:
  - Name: Critical Vulnerability Detection
    ExpectedResult: true
    Log:
      {
        "p_event_time": "2026-03-18T14:00:00Z",
        "p_log_type": "Upwind.Detections",
        "p_row_id": "bb2233cc4455bb2233cc4455bb2233cc",
        "p_schema_version": 0,
        "category": "Vulnerability",
        "description": "Critical CVE-2024-1234 detected in a runtime container image.",
        "first_seen_time": "2026-03-18T13:50:00Z",
        "id": "det-vuln-001",
        "last_seen_time": "2026-03-18T14:00:00Z",
        "occurrence_count": 1,
        "severity": "CRITICAL",
        "status": "open",
        "title": "Critical Vulnerability in Runtime Container",
        "type": "vulnerability",
        "upwind_console_link": "https://console.upwind.io/detections/det-vuln-001",
        "resource": {
          "cloud_account_id": "123456789012",
          "cloud_account_name": "prod-aws",
          "cloud_provider": "AWS",
          "cluster_id": "cluster-abc123",
          "name": "frontend-pod",
          "namespace": "production",
          "region": "us-east-1",
          "type": "Pod",
          "upwind_asset_id": "asset-vuln-001",
          "risk_categories": ["internet_facing", "critical_workload"],
          "internet_exposure": {
            "ingress": {
              "active_communication": true
            }
          }
        },
        "mitre_attacks": [
          {
            "tactic_id": "TA0001",
            "tactic_name": "Initial Access",
            "technique_id": "T1190",
            "technique_name": "Exploit Public-Facing Application"
          }
        ],
        "triggers": [
          {
            "policy_id": "pol-vuln-001",
            "policy_name": "Critical Runtime CVE Policy",
            "events": []
          }
        ]
      }
  - Name: Non-Vulnerability Category - Not Matched
    ExpectedResult: false
    Log:
      {
        "p_event_time": "2026-03-18T14:00:00Z",
        "p_log_type": "Upwind.Detections",
        "p_row_id": "cc3344dd5566cc3344dd5566cc3344dd",
        "p_schema_version": 0,
        "category": "API Threat",
        "description": "Broken auth on API.",
        "first_seen_time": "2026-03-18T13:50:00Z",
        "id": "det-api-003",
        "last_seen_time": "2026-03-18T14:00:00Z",
        "occurrence_count": 2,
        "severity": "HIGH",
        "status": "open",
        "title": "Broken Authentication",
        "type": "api_threat",
        "resource": {
          "cloud_account_id": "123456789012",
          "name": "api-service",
          "region": "us-east-1",
          "type": "Service"
        },
        "mitre_attacks": [],
        "triggers": []
      }
  - Name: Vulnerability Category with Unknown Severity - Suppressed
    ExpectedResult: false
    Log:
      {
        "p_event_time": "2026-03-18T14:00:00Z",
        "p_log_type": "Upwind.Detections",
        "p_row_id": "dd4455ee6677dd4455ee6677dd4455ee",
        "p_schema_version": 0,
        "category": "Vulnerabilities",
        "description": "Low-priority informational CVE detected.",
        "first_seen_time": "2026-03-18T13:50:00Z",
        "id": "det-vuln-002",
        "last_seen_time": "2026-03-18T14:00:00Z",
        "occurrence_count": 1,
        "severity": "INFO",
        "status": "open",
        "title": "Low-Priority CVE Detected",
        "type": "vulnerability",
        "resource": {
          "cloud_account_id": "123456789012",
          "name": "batch-job-pod",
          "region": "us-west-2",
          "type": "Pod"
        },
        "mitre_attacks": [],
        "triggers": []
      }

Detection logic

Condition

category contains "vulnerab"
category not contains "api"

This rule also runs imperative logic the parser cannot express as a filter; the conditions above are the structured part it could extract.

Exclusions

Top-level NOT(...) conjuncts: predicates this rule actively suppresses.

Field	Kind	Excluded values
`category`	contains	`api`

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

Field	Kind	Values
`category`	contains	`vulnerab`

Output fields

Fields the rule emits when it matches. Chronicle authors list these in the outcome block; they appear on the detection and $risk_score drives alerting. Sentinel / Defender XDR rules build them up through project / summarize / extend stages. Sentinel maps these into alert fields via entityMappings and customDetails; Defender XDR custom detections surface them as alert fields directly.

Field	Source
`detection_id`	`id`
`category`
`type`
`status`
`occurrence_count`
`title`

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)