Detection rules › Panther

Panther rules: socradar

RuleSeverity
SOCRadar Alert Passthroughinformational

SOCRadar Alert Passthrough

#

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.

Status
Experimental
Severity
informational
Group by
alarm_id
Log types
SOCRadar.Incidents
Tags
SOCRadar, Threat Intelligence, Brand Protection, Dark Web, Credential Intelligence, Attack Surface
Reference
socradar.io
Source
github.com/panther-labs/panther-analysis

Surfaces all open SOCRadar security incidents as Panther alerts. Severity is mapped dynamically from SOCRadar's alarm_risk_level (CRITICAL/HIGH/MEDIUM/LOW/INFO). SOCRadar performs the underlying threat detection; this rule ensures every open incident is visible in Panther for triage and response.

Detection logic

def rule(event):
    return event.get("status") != "CLOSED"


def title(event):
    main_type = event.deep_get("alarm_type_details", "alarm_main_type", default="Unknown")
    sub_type = event.deep_get("alarm_type_details", "alarm_sub_type", default="")
    risk = event.get("alarm_risk_level", "UNKNOWN")
    return f"SOCRadar {risk} [{main_type} - {sub_type}]"


def severity(event):
    return event.get("alarm_risk_level", "DEFAULT").upper()


def dedup(event):
    return str(event.get("alarm_id", ""))


def alert_context(event):
    context = {
        "alarm_id": event.get("alarm_id"),
        "alarm_asset": event.get("alarm_asset"),
        "alarm_text": event.get("alarm_text"),
        "main_type": event.deep_get("alarm_type_details", "alarm_main_type"),
        "sub_type": event.deep_get("alarm_type_details", "alarm_sub_type"),
        "status": event.get("status"),
        "mitigation": event.deep_get("alarm_type_details", "alarm_default_mitigation_plan"),
    }

    content = event.get("content") or {}
    for field in (
        "content_link",
        "phishing_domain",
        "phishing_domain_url",
        "compromised_emails",
        "compromised_ips",
        "compromised_domains",
        "malware_family",
        "computer_name",
        "username",
        "source",
        "content_preview",
    ):
        if content.get(field):
            context[field] = content[field]

    return context

Rule specification

AnalysisType: rule
Filename: socradar_alert_passthrough.py
RuleID: "SOCRadar.Alert.Passthrough"
DisplayName: "SOCRadar Alert Passthrough"
Enabled: true
Status: Experimental
LogTypes:
  - SOCRadar.Incidents
Tags:
  - SOCRadar
  - Threat Intelligence
  - Brand Protection
  - Dark Web
  - Credential Intelligence
  - Attack Surface
DedupPeriodMinutes: 60
Severity: Info
Description: >
  Surfaces all open SOCRadar security incidents as Panther alerts. Severity is mapped
  dynamically from SOCRadar's alarm_risk_level (CRITICAL/HIGH/MEDIUM/LOW/INFO).
  SOCRadar performs the underlying threat detection; this rule ensures every open
  incident is visible in Panther for triage and response.
Runbook: |
  1. Review the full alert context including alarm_id, alarm_type_details.alarm_main_type, alarm_type_details.alarm_sub_type, and all content fields (phishing_domain, compromised_emails, malware_family, content_link) to understand the nature and scope of the SOCRadar incident.
  2. Check whether any extracted indicators (p_any_ip_addresses, p_any_domain_names, p_any_emails, p_any_usernames) appear in other log sources or security alerts in the 24 hours before and after this alert to determine if the threat has already reached internal systems.
  3. Search for other SOCRadar incidents with the same alarm_type_details.alarm_main_type or alarm_asset in the past 30 days to identify whether this is an isolated finding or part of a recurring or escalating threat pattern.
Reference: https://socradar.io/incident-response/
SummaryAttributes:
  - alarm_id
  - alarm_risk_level
  - alarm_asset
  - status
  - p_any_ip_addresses
  - p_any_domain_names
  - p_any_emails
  - p_any_usernames

Stages and Predicates

Fires on SOCRadar.Incidents events when the condition below holds.

Condition

  • status is not CLOSED

Indicators

These rows show field, operator, and value matches.

FieldKindValuesSearch
statusne
  • CLOSED
field:"status" kind:ne value:"CLOSED"

Output fields

Fields the rule emits when it matches, drawn from the rule's alert_context.

FieldSource
alarm_id
alarm_asset
alarm_text
main_typealarm_type_details.alarm_main_type
sub_typealarm_type_details.alarm_sub_type
status
mitigationalarm_type_details.alarm_default_mitigation_plan
alarm_risk_level

Response runbook

1. Review the full alert context including alarm_id, alarm_type_details.alarm_main_type, alarm_type_details.alarm_sub_type, and all content fields (phishing_domain, compromised_emails, malware_family, content_link) to understand the nature and scope of the SOCRadar incident.

2. Check whether any extracted indicators (p_any_ip_addresses, p_any_domain_names, p_any_emails, p_any_usernames) appear in other log sources or security alerts in the 24 hours before and after this alert to determine if the threat has already reached internal systems.

3. Search for other SOCRadar incidents with the same alarm_type_details.alarm_main_type or alarm_asset in the past 30 days to identify whether this is an isolated finding or part of a recurring or escalating threat pattern.

Worked example

A sample event from the rule's unit tests that triggers a match.

Sample Test Event
{
  "alarm_asset": "TESTSOCRadar",
  "alarm_assignees": [],
  "alarm_id": 93001001,
  "alarm_risk_level": "CRITICAL",
  "alarm_text": "Detected stolen credentials from infected system. Employee credentials found in stealer logs.",
  "alarm_type_details": {
    "alarm_default_mitigation_plan": "Force password reset. Isolate infected systems. Enable MFA.",
    "alarm_default_risk_level": "CRITICAL",
    "alarm_detection_and_analysis": "",
    "alarm_main_type": "Credential Intelligence",
    "alarm_post_incident_analysis": "",
    "alarm_sub_type": "Stealer Logs"
  },
  "approved_by": "Auto Approve",
  "content": {
    "compromised_emails": "alice.jones@testcompany.com",
    "computer_name": "DESKTOP-HR-042",
    "malware_family": "Vidar Stealer",
    "source": "Underground Forum - XSS.is",
    "username": "alice.jones"
  },
  "date": "2026-03-19 09:00:00",
  "is_approved": true,
  "notification_id": 8810001,
  "status": "OPEN",
  "tags": [
    "credentials",
    "stealer",
    "vidar"
  ]
}