![]() ![]() ![]() However this potentially creates a whole heap of admin. I had originally planned to just have an IOT based rule and leave it at that, but part of me doesn't want to whitelist web domains for devices that don't need to have them white listed, so therefore create separate policies. I can see there being more Policy Manager defined rules based on the device etc. I'm used to more traditional firewall devices such as pfsense and Sophos XG It this logic the way of building the rules based on Policy Manager? Up for the deny rule I am going to add a rule for allowing TCP/80 and UDP/3700 as these are the ports that are showing within the sessions and report logs. To expand on this I am then looking at adding a firewall rule within the firewall app, with an explicit deny at the bottom. So the Web Filter is setup to bypass *.sky.com in the pass sites area and the Policy Manager has a rule that applies it to the Sky HD box via a tag at present. I have created a Policy for my SkyHD box, the main reason was the web filter was breaking the OnDemand downloads etc. Based on the Policy Manager being the centre for defining rules etc. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |