- Get Started
- News & Events
- Collaboration
- Education Services
- Technologies
- Next-Generation Firewall
- GlobalProtect
- Threat Prevention Services
- Endpoint Protection
- SSL Decryption
- 5G
- IoT Security
- Prisma SD-WAN
Network Security
- Prisma Access
- Prisma SaaS
- Prisma Cloud
- CN-Series
- VM-Series:
- Alibaba
- AWS
- GCP
- Azure
Cloud Security
- Cortex XDR
- Cortex XSOAR
- Cortex Data Lake
Security Operations
- Resources
- COVID-19 Response Center
- LIVEcommunity
- ›
- Collaboration
- ›
- Tools
- ›
- MineMeld
- ›
- MineMeld Discussions
- ›
- How to Use DAGPusher / DAG
How to Use DAGPusher / DAG
Changes to the LIVEcommunity experience are coming soon... Here's what you need to know.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Printer Friendly Page
- Mark as New
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report This Content
I cannot find any documentation on these prototypes. How does MM know what devices to push to? It seems to me we would need to clone stdlib.nonpersistentDagPusher or stdlib.dagPusher and enter some configuration.
I also don't understand the difference between persistent and nonpersistent. Since the output doesn't live on MM, I would hope that MM would be able to add and remove registered IPs from all configured devices or firewalls. Is this the difference between the two?
Solved! Go to Solution.
- Mark as New
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report This Content
Hi @andrew.stanton,
the devices are added via the WebUI after you commit the config with the dag pusher node:
persistent and nonpersistent are related to the persistence of the IP on the PAN-OS device. nonpersistent IP are better for blacklists as they do not survive reboots.
- Mark as New
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report This Content
Hi @andrew.stanton,
the reboot I mentioned was the PAN-OS reboot. When you push IPs via DAG API to a PAN-OS device you can decide if the IP should survive reboot (persistent) or not (non-persistent). Default is persistent.
This is specified via a flag in the API call. The MineMeld output node called persistentDagPusher push IPs marked for persistency. The output node nonpersistentDagPusher instead mark them as non persistent.
Show your appreciation!
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
