12-11-2019 08:50 AM - edited 02-21-2020 09:45 AM
I'm trying to open web traffic to: upgrade.bitdefender.com on an FMC. I made a change to the access control rules as indicated in the attached pic, but it's had no effect. Is the correct policy to modify?
Thanks!
12-11-2019 09:12 AM
Is this for actual web traffic? Like users trying to browse to that URL? I ask this because the URL object that you have defined is for web browsing sessions. If you want to open your policy for other (Non web-based sessions) to upgrade.bitdefender.com without using an IP/subnet, you will need to utilize the FQDN-based objects that were introduced in version 6.4.0.
I hope this helps!
Thank you for rating helpful posts!
12-11-2019 11:30 AM
So just to make sure we're on the same page...if we're trying to open the traffic via the application rather than a browser then we would use FQDN-based objects to implement it. Is that right?
12-11-2019 12:05 PM
12-14-2019 04:39 PM
You will have to upgrade your FMC and managed sensors/firewalls to 6.4.0.x in order to get support for FQDN objects. In fact, 6.4.0.4 is the current recommended/Gold starred release.
Thank you for rating helpful posts!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide