It appears as though all of the sudden ms-upate traffic is being picked up as either session-end reason threat or n/a and updates are failing on my MS servers. Regardless of the server they all seem to be hitting the unidentified default rule at the bottom.
Solved! Go to Solution.
do you have a decryption profile that would identify that traffic and if so, do you have the "block untrusted issuers" check mark box populated - even if no decrypt?
Just curious, as it looks like MS may have a cert or destination that is not on the PA's, but I have yet to deterimine exactly the issue
I do have a decryption profile but not applied to all. I can insert on the server IPs and see what is going on. Where would I locate the "block untrusted issuers" check box
under objects/decryption/decryption profile/ then in that decryption profile - for the profile itself,
Under SSL Decryption/SSL Forward proxy:
under server certificate verification -check the box that says block sessions with untrusted issuers
Under the No Decryption tab:
check the box for block sessions with untrusted issuers.
Note that this will break traffic if issuers are untrusted or expired, so be careful on what you apply this Decryption policy to if you have never had this applied and are running production traffic through this.
Thanks all for your help and suggestions.I ended up creating a custom app and subsequent security policy to allow MS updates to run. I did open a case with TAC.
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 Live Community as a whole!
The Live Community thanks you for your participation!