App-ID updates break existing rules

[msullivan]

Howdy,

How do most of you manage situations where App-ID updates break functioning rules?  This just happened to me: I have Lync 2010 and the internal clients need to connect to the edge server.  I had a rule in place that allowed ms-lync, ssl, and stun.  That worked fine until last weeks update (396), at which point ssl was now identified as "ms-lync-online".  So the rule started blocking traffic to external clients who shared a resource.  The fix was to observe internal client traffic to the Lync edge server to see that traffic was now denied, then add the application to the list of allowed traffic.

So that is one instance, I bet others out there have found issues too.  What are people doing to protect functioning policies from breaking after app-id updates?

Thanks,

Mike

[msullivan]

+1

[ericgearhart]

If they broke out App-ID updates from threat updates that would be nice too. I'd like to not be missing threat updates that have come out just because I'm holding off on updating my App-ID version... right now the two are intertwined. I'd rather see them split apart.

[mbutt]

Hi Mike,

You can always go to the release notes before upgrading. That will have the modified decoders and the latest added or changed applications.

Thank you

Numan

[kalebw]

This is about the best option and best description of the circumstances