Cortex XSOAR/XSIAM as way to block users/source IP that generates too many attacks on the NGFW/Prisma Access in a fixed time window

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

General Articles
7 min read
Cyber Elite
No ratings
nikoolayy1_0-1793199257482.png

 

 
Palo Alto Networks Cortex XSOAR (Extended Security Orchestration, Automation and Response) is a security automation and incident response platform that enables organizations to integrate security products, automate repetitive security operations, and coordinate incident investigation and remediation through playbooks.
 

Cortex XSIAM (Extended Security Intelligence and Automation Management) is a cloud-native, AI-driven Security Operations Center (SOC) platform developed by Palo Alto Networks. It combines SIEM, XDR, SOAR, threat intelligence, security analytics, and automated incident response into a unified solution. XSIAM is designed to collect, correlate, and analyze large volumes of security data to detect sophisticated threats, automate investigations, and accelerate incident response—with Cortex XSOAR capabilities built directly into the platform.

 

Content

 

1. Issue description

2. Palo Alto NGFW DUG and DAG groups

3. Cortex XSOAR resolution
4. Cortex XSIAM resolution
5. XSIAM EDL Cloud Service
Summary
 
1. Issue description
 
On the Palo Alto firewalls you can make combination signatures that can detect, log and block a user or source ip  if they do a specific violation couple of times as I have shown in How to Write Palo Alto Networks Custom Vulnerability and Application Signatures with Examples , LIVEcommunity - Rate-Limiting File Uploads with Palo Alto Networks Custom Signatures - LIVEcommunity... and Custom Signatures With ChatGPT and AI Security but what happens when you want to block source ip or user that does for example 5 different violations in 1 minute and maybe to block the offender for 1 hour from doing anything else?
 
Well this can't be done on the Palo Alto NGFW itself but with XSOAR and better yet XSIAM this is possible. XSOAR/XSIAM use a visual form of automation programming called playbooks that removes much of the needed domain knowledge compared to other Automations like Python on Ansible AWX that have shown in other articles Automating the Palo Alto NGFW's Process/Daemon Restarts with Python PEXPECT and Use Ansible AWX to automate the Palo Alto NGFW's management and even Process/Daemon Restarts!
 
 
2. Palo Alto NGFW DUG and DAG groups
 
Palo Alto NGFW has a great feature called dynamic address groups (DAG) and dynamic user groups (DUG) that allows IP addresses or users to be tagged based on many criteria and this tag can expire after time. 
 
 
The dynamic groups are added in Security Policy rules so while the source IP or user is tagged they will be blocked. See Dynamic User Group Auto Remediation configuration as this shows how from the logs the tags can be attached.
 
nikoolayy1_0-1793426825054.png

 

nikoolayy1_1-1793426895672.png

 

 
Tags can be redistributed to other firewalls from a Master firewall as shown in Configure Data Redistribution or from Prisma Access to the on-prem firewalls through the Service connection Identity Redistribution .
 
Another cool option is Policy Object: Quarantine Device Lists that allows GlobalProtect VPN devices to be blocked again based on logs that attach tags.
 
Strata Cloud Manager (SCM) that is the SaaS based cloud service for managing Prisma Access, Prisma AIRS (AI security protection from things like prompt injections and other AI attacks) and Palo Alto NGFW from a central portal that can replace or work together with Panorama with a plugin and it can also be a hub that redistributes the tags to all other NGFW, by using the Cloud Identity Engine (CIA) Configure a Redistribution Profile in Strata Cloud Manager
 
The DUG/DAG feature on it's own can block users/source IP addresses if someone does the same violation and combined with a combination signature that as the time element, it can do it if a user does the same violation couple of times in a minute but still if we want a user/source ip to blocked no matter the violations type just if they do for example 5 violations in minute then we need to feed this tag through REST-API on the firewall from an external system like XSOAR or XSIAM as it is shown in the next points.
 
 
3. Cortex XSOAR resolution
 
Cortex XSOAR on its own can be integrated with syslog or external SIEM or directly to fetch the logs from Panorama or the NGFW with a job Jobs | Cortex XSOAR . The integration is described in Palo Alto Networks Integrations Overview | Cortex XSOAR and  Palo Alto Networks PAN-OS | Cortex XSOAR .
 
After that the built-in playbooks for DUG and DAG can use the NGFW API to tag the source IP and users and then the security policy rules will block - a workflow we will explore in more detail under the XSIAM section in Step 4.
 

Create the scheduled Job

In XSOAR:

  1. Navigate to Jobs.

  2. Select New Job.

  3. Choose a time-triggered job.

  4. Select NGFW - Repeated Violation Detection.

  5. Configure recurrence.

 
You will also need a custom Python automation script to process the logs before triggering the built-in DUG and DAG playbooks—which you can easily generate using an AI tool like ChatGPT.
 
logs = json.loads(demisto.args()["logs"])

now = datetime.now(timezone.utc)
start = now - timedelta(seconds=60)

counts = defaultdict(int)

for log in logs:
    ip = log.get("SourceAddress")
    timestamp = log.get("TimeGenerated")

    if not ip or not timestamp:
        continue

    dt = datetime.fromisoformat(
        timestamp.replace("Z", "+00:00")
    )

    if dt.tzinfo is None:
        dt = dt.replace(tzinfo=timezone.utc)

    if start <= dt <= now:
        counts[ip] += 1

# Identify IPs with more than 5 violations
offenders = [
    {"ip": ip, "count": count}
    for ip, count in counts.items()
    if count > 5
]

# Return results to the XSOAR playbook
demisto.results({
    "Type": 1,
    "ContentsFormat": "json",
    "Contents": offenders,
    "EntryContext": {
        "NGFW.Offenders": offenders
    }
})

 

 
A good example is Playbook of the Week: Automate NGFW Management with Cortex XSOAR  that shows how XSOAR works with the NGFW.
 
XSOAR will need to pull the logs maybe every minute and this is not optimal at all so this is where XSIAM comes into the picture.
 
The same integrations are also available for Prisma Access Cortex XSOAR and Prisma Access Integration - Palo Alto Networks 
 
4. Cortex XSIAM resolution
 
Cortex XSIAM has the same playbooks as Cortex XSOAR plus it is a full SIEM with AI integrations. The Palo Alto NGFW or Panorama can directly send the logs to XSIAM that will then process the logs using a Correlation Rule that uses the XQL language to build the query that will filter the logs, XSIAM has the same options then to add the tags to the users or source IP and send it to Panorama or the NGFW.
 

XQL (Cortex Query Language) is a query language developed by Palo Alto Networks for searching, filtering, aggregating, correlating, and analyzing security data within Cortex XSIAM and Cortex XDR. XQL enables security analysts and engineers to investigate threats, identify suspicious behavior, analyze logs, and build custom security detections.

 
 
  • Palo Alto XSIAM automation window under "Investigation and Response".
 
 
 
playbook.png
 
 
  • How to integrate XSIAM and Palo Alto NGFW.
 
 
playbook5.png
 
 
  • "PAN-OS DAG Configuration" built-in playbook
 
playbook1.png
 
  • "NetSec - Palo Alto Networks DUG - Tag User" built-in playbook
 
 
playbook2.png
 
  • "PAN-OS - Block IP" built-in playbook.
 
playbook3.png
 
 
  • "Cortex Assistant" built-in AI tool.
 
playbook4.png
 
 
The same integrations are also available for Prisma Access Palo Alto Networks integrations | Cortex Documentation Portal 
 
 
5. XSIAM EDL Cloud Service
 

External Dynamic Lists (EDLs) are also a great alternative to what I’ve shown above. XSIAM can generate an EDL that firewalls, Panorama, and Prisma Access can directly ingest. (XSOAR used to offer this feature as well, though it is no longer supported.)

 

 
 
 
Summary
 
Cortex products add tremendous flexibility when integrated with Panorama, Prisma Access, and Palo Alto Networks NGFWs—unlocking advanced cross-correlation and automated enforcement that aren't possible on the NGFW or Prisma Access alone. Furthermore, Cortex XSIAM natively incorporates Cortex XDR (our endpoint protection, detection, and response agent—which I covered in LIVEcommunity - XDR Isolation Exceptions and Exclusions Use Case - LIVEcommunity - 515583).
This allows you to automatically isolate offending users or source IPs directly on the NGFW or Prisma Access based on endpoint telemetry sent by the XDR agent to XSIAM—ensuring that even if a threat or user bypasses local endpoint controls, they immediately hit a wall at the network perimeter.
Rate this article:
  • 118 Views
  • 0 comments
  • 1 Likes
Contributors
Labels
Article Dashboard
Version history
Last Updated:
‎11-17-2026 05:51 AM
Updated by: