CRL revocation traffic identified as ms-update

L1 Bithead

CRL revocation traffic identified as ms-update

Is this an expected behaviour? We where somewhat surprised that the application included this traffic. It includes all SSL CRL traffic (like establishing remote desktop or visiting websites), independent if its related to Windows Update.

L7 Applicator

Re: CRL revocation traffic identified as ms-update

I checked a couple firewall logs on my end, and don't see that same behavior. But most browsers will use OCSP instead if it is present in the certificate.

 

A CRL is just an HTTP GET request (unlike OCSP which is its own protocol on top of HTTP) so it doesn't have its own application in the App-ID database.

 

If it's only CRL requests that are triggering as ms-update, I'm not sure how that could happen outside of an app-override rule. It may help if you specify the PAN-OS version along with the APP-ID version that's installed on your firewall.

L1 Bithead

Re: CRL revocation traffic identified as ms-update

We had a deny policy in place for ms-update for clients - to enforce SCCM distribution. I suspect this had an adverse affect on the clients - maybe affecting root certificate updates. For example, when establishing secure connection using RDP there where a 15-30 second delay. Using other https resources also resulted in similar delays. Immediately after disabling the deny policy this problem went away.

 

Our setup: PANOS 8.1.2, 8070-5032. No application overrides in use.

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 Live Community as a whole!

The Live Community thanks you for your participation!