03-14-2019 10:33 AM
I've got our PA setup to block file types that are risky. But, I've found a problem with Symantec LiveUpdate pulling down the update files it needs. It uses a couple odd file types that aren't in the list as types that I can allow for a profile. Is there a way to add custom file extensions that I can use to match against, or is there another way to go about only allowing the specific file types that Symantec uses? I was looking for an app-id that I could match against for Symantec or LiveUpdate, but there doesn't appear there is an ID for that, so any ideas are appreciated.
03-14-2019 11:21 AM - edited 03-14-2019 11:22 AM
Do you see traffic blocked?
If Palo does not identify those files what do you see in logs?
Check URL filtering log to identify where Symantec downloads updates.
Most likely liveupdate.symantecliveupdate.com and liveupdate.symantec.com
Create custom URL category (with liveupdate.symantecliveupdate.com and liveupdate.symantec.com in it).
Create Security Policy that allows download of any file from this custom URL category for test.
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!
