06-16-2020 02:24 AM
Hi All,
We have a customer who has upgraded to 9.0 and they get shadow rule warnings since the upgrade.
All the shadowing rules are more generic with any/any for source and destination, but with source user restrictions.
The shadowed rules have more specific source/destination values.
Traffic is hitting the shadowed rules.
The same rules weren't triggering any warnings under 8.1
Has anyone experienced a similar issue?
Thanks,
Andrea
06-16-2020 07:00 AM
Hello,
Yes, I have the same thing with upgrade in 9.0.8 (from 8.1.x) but I haven't created a case yet
(For example: src.user ignored)
06-30-2020 06:41 AM
It appears to be a bug, a fix is targeted for 9.0.11 and 9.1.5
07-01-2020 08:28 AM
Do you have a reference for this being noted for 9.0.11? Been doing some digging and not finding anything calling this out.
Thanks!
03-09-2021 04:58 AM
Do we have the bug ID provided by Palo Alto TAC for this issue? Ta.
03-09-2021 06:07 AM
PAN-137663 | Fixed a cosmetic issue where misleading App-ID and rule shadowing warnings populated after a commit. |
Fixed in 9.0.11 hopefully this is the one.
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!
