Detection rules › Panther

Wiz Issue Alert Passthrough Rule

This is a third-party alert feed, not a detection over modeled telemetry. Another security product raised the finding; this rule forwards or reshapes it into the SIEM. It is searchable for reference but is excluded from the detection-rule browse and the ATT&CK coverage matrix.

Severity: medium
Group by: control.id, issue.id, issue.severity
Log types: Wiz.IssuesWebhook
Reference: https://www.wiz.io/product
Source: github.com/panther-labs/panther-analysis

This rule enriches and contextualizes security alerts generated by Wiz.

Rule body yaml

AnalysisType: rule
RuleID: Wiz.Issue.Alert.Passthrough
Description: This rule enriches and contextualizes security alerts generated by Wiz.
DisplayName: Wiz Issue Alert Passthrough Rule
Runbook: Review the Wiz alert details to determine what malicious behavior was detected, and whether or not it was blocked.
Reference: https://www.wiz.io/product
Enabled: true
Filename: wiz_issue_alert_passthrough.py
Severity: Medium
LogTypes:
  - Wiz.IssuesWebhook
DedupPeriodMinutes: 720
Threshold: 1
Tests:
  - Name: Open Alert
    ExpectedResult: true
    Log:
      {
        "p_event_time": "2025-07-25 13:09:25.306109000",
        "p_log_type": "Wiz.IssuesWebhook",
        "p_parse_time": "2025-10-24 05:04:47.058502203",
        "p_row_id": "eac735a1259bfda5e5fbf9da29a504",
        "p_schema_version": 0,
        "p_source_id": "26c0c4b6-781c-40fa-9bc4-5bd16f8e5dda",
        "p_source_label": "wiz-issue-webhook",
        "p_udm": {},
        "control": {
          "description": "An EC2 instance has an unprotected port that is being probed by a known malicious host. This rule's final severity is assigned dynamically according to the severity assigned by GuardDuty.",
          "id": "cer-awsguardduty-recon-ec2-portprobeunprotectedport",
          "name": "Recon:EC2/PortProbeUnprotectedPort",
          "risks": [],
          "severity": "HIGH"
        },
        "issue": {
          "created": "2025-07-25 13:09:25.306109000",
          "id": "e3188a71-794c-5ee8-b97c-eb794aa5b752",
          "projects": "",
          "severity": "HIGH",
          "status": "OPEN"
        },
        "resource": {
          "cloudPlatform": "AWS",
          "cloudProviderURL": "",
          "id": "",
          "name": "jenkins-aws",
          "region": "us-east-2",
          "status": "",
          "subscriptionId": "111111111111",
          "subscriptionName": "My-Subscription",
          "type": "virtualMachine"
        },
        "trigger": {
          "ruleId": "710a481b-3066-439f-9612-3f103afce604",
          "ruleName": "issue-updates",
          "source": "ISSUE",
          "type": "Open"
        }
      }
  - Name: Low-Severity Open Alert
    ExpectedResult: true
    Log:
      {
        "p_event_time": "2025-07-25 13:09:25.306109000",
        "p_log_type": "Wiz.IssuesWebhook",
        "p_parse_time": "2025-10-24 05:04:47.058502203",
        "p_row_id": "eac735a1259bfda5e5fbf9da29a504",
        "p_schema_version": 0,
        "p_source_id": "26c0c4b6-781c-40fa-9bc4-5bd16f8e5dda",
        "p_source_label": "wiz-issue-webhook",
        "p_udm": {},
        "control": {
          "description": "An EC2 instance has an unprotected port that is being probed by a known malicious host. This rule's final severity is assigned dynamically according to the severity assigned by GuardDuty.",
          "id": "cer-awsguardduty-recon-ec2-portprobeunprotectedport",
          "name": "Recon:EC2/PortProbeUnprotectedPort",
          "risks": [],
          "severity": "HIGH"
        },
        "issue": {
          "created": "2025-07-25 13:09:25.306109000",
          "id": "e3188a71-794c-5ee8-b97c-eb794aa5b752",
          "projects": "",
          "severity": "LOW",
          "status": "OPEN"
        },
        "resource": {
          "cloudPlatform": "AWS",
          "cloudProviderURL": "",
          "id": "",
          "name": "jenkins-aws",
          "region": "us-east-2",
          "status": "",
          "subscriptionId": "111111111111",
          "subscriptionName": "My-Subscription",
          "type": "virtualMachine"
        },
        "trigger": {
          "ruleId": "710a481b-3066-439f-9612-3f103afce604",
          "ruleName": "issue-updates",
          "source": "ISSUE",
          "type": "Open"
        }
      }
  - Name: Resolved Alert
    ExpectedResult: false
    Log:
      {
        "p_event_time": "2025-07-25 13:09:25.306109000",
        "p_log_type": "Wiz.IssuesWebhook",
        "p_parse_time": "2025-10-24 05:04:47.058502203",
        "p_row_id": "eac735a1259bfda5e5fbf9da29a504",
        "p_schema_version": 0,
        "p_source_id": "26c0c4b6-781c-40fa-9bc4-5bd16f8e5dda",
        "p_source_label": "wiz-issue-webhook",
        "p_udm": {},
        "control": {
          "description": "An EC2 instance has an unprotected port that is being probed by a known malicious host. This rule's final severity is assigned dynamically according to the severity assigned by GuardDuty.",
          "id": "cer-awsguardduty-recon-ec2-portprobeunprotectedport",
          "name": "Recon:EC2/PortProbeUnprotectedPort",
          "risks": [],
          "severity": "HIGH"
        },
        "issue": {
          "created": "2025-07-25 13:09:25.306109000",
          "id": "e3188a71-794c-5ee8-b97c-eb794aa5b752",
          "projects": "",
          "severity": "LOW",
          "status": "Resolved"
        },
        "resource": {
          "cloudPlatform": "AWS",
          "cloudProviderURL": "",
          "id": "",
          "name": "jenkins-aws",
          "region": "us-east-2",
          "status": "",
          "subscriptionId": "984186218765",
          "subscriptionName": "My-Subscription",
          "type": "virtualMachine"
        },
        "trigger": {
          "ruleId": "710a481b-3066-439f-9612-3f103afce604",
          "ruleName": "issue-updates",
          "source": "ISSUE",
          "type": "Resolved"
        }
      }

Detection logic

Condition

issue.status eq "OPEN"
issue.severity ne "INFORMATIONAL"

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
`issue.severity`	ne	`INFORMATIONAL`
`issue.status`	eq	`OPEN`

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
`id`	`resource.id`
`type`	`resource.type`
`name`	`resource.name`
`name`	`control.name`

`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)