Internal traffic is hitting in the isp firewall

[Javith_Ali]

Palo alto is perimeter to customer which is connected to isp firewall.

Internal subnet traffics which are not allowed in isp/ untrust interface are hitted in isp firewall.
Routing is proper. ARP is proper in isp interface( only next hop arp is there)

Implicit deny policy blocking the interzone traffic trust to untrust.

We don't have any clue how our internal private ip address communication is going to ISP firewall.

There is no allowed security policyfor reported internal ip's and routing is proper.

[TranceforLife]

Do you have logs showing the same? Do you know if the course of the traffic is the client(s) ip addresses or actually firewall itself?

[Javith_Ali]

Thanks for reply.

there is no logs showing for the same(means internal to Untrust).

However i can see the logs for the same reported IP's from trust to DMZ subnet (it is taking the actual route configured in VR).

we are getting the report from ISP on Weekly basis. ISP is sharing the different IP's (on weekly basis) but same source subnet (trust) and destination subnet (DMZ).

These IP's are not configured in firewall. client IP's only. Please suggest

[Javith_Ali]

we have tried to configure the pcaps filter from trust to untrust subnet   (which should not be allowed and routing also not there).

But we can filter using ingress interface only. There is no option for egress in pcaps.

So we dont want to configure above filter for reported subnets as this will capture whole legitimate traffics  going to DMZ as well.

[TranceforLife]

Ok. Do you have log enable on the policies so you can confirm if that traffic is actually traversing the firewall and not taking the "alternative" route? Logs will be generated as soon as the traffic is passing the firewall. Logs will not be generated if the traffic is not passing the firewall or for the traffic generated by firewall itself.