Dynamic IP lists Known malicious Panorama Security rule not populating

cancel
Showing results for 
Search instead for 
Did you mean: 

Dynamic IP lists Known malicious Panorama Security rule not populating

L4 Transporter

I'm running into a problem where the "known malicious IP addresses" dynamic list isn't populating in panorama when to trying to add a security policy based on it, but is populating when I go to the local firewall and try to find it under the destination address.  Has anyone ever run into this issue before?

1 ACCEPTED SOLUTION

Accepted Solutions

L3 Networker

I found a solution to this.  Apparently on Panorama, you have to reference by the source name not the EDL name.  For 'Palo Alto Networks - Known malicious IP addresses' use 'panw-known-ip-list'

 

For 'Palo Alto Networks -High risk IP addresses' use 'panw-highrisk-ip-list'.

 

 

View solution in original post

10 REPLIES 10

L7 Applicator

I have not, but if you think of it, it makes sense - most likely an optimization - Panorama doesn't need the list of IP's since it doesn't enforce Security Policies (traffic doesn't go through Panorama).

L3 Networker

Whats the URL for this list as provided by Palo Alto?

Hello,

Are you referring to the Predefined list"

 

https://live.paloaltonetworks.com/t5/Featured-Articles/PAN-OS-8-0-IP-Block-List-Feeds/ta-p/129616

 

If yes, then its a hidden URL I believe.

 

Regards,

The lists ship with a Dynamic Updates package.

I'm researching to find out exactly which one.

Yes I am.  I've even tried to manually copy and paste it into panorama for the destination address--like a custom EDL would show up, but panorama still doesn't recognize it.

The list ships with the Antivirus package. Make sure you deploy the Antivirus package to Panorama so that it has knowledge of the lists.

L3 Networker

I found a solution to this.  Apparently on Panorama, you have to reference by the source name not the EDL name.  For 'Palo Alto Networks - Known malicious IP addresses' use 'panw-known-ip-list'

 

For 'Palo Alto Networks -High risk IP addresses' use 'panw-highrisk-ip-list'.

 

 

Thanks Brandon, commenting on my own post:

 

I have not, but if you think of it, it makes sense - most likely an optimization - Panorama doesn't need the list of IP's since it doesn't enforce Security Policies (traffic doesn't go through Panorama).

 

The reason why that may be wrong is that you should be able to define EDL exceptions in Panorama.

I know this is kinda old but the solution worked for me.  So Thanks! 🙂

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!