BWC Cybersecurity Overlord ✭✭✭
Reactions
Comments
-
This might be what you're looking for. —Michael@BWC
-
@bzperry I'am located in Germany, the distributor pricelist shows price band 1-24, I googled the SKUs and 5-24 showed up. I believe 5-24 is outdated, because if I check the catalog on MySonicWall it shows 1-24 as well. A question probably only SNWL can answer for your geographic location. —Michael@BWC
-
@bzperry an Endpoint is a Computer (Windows, macOS, Linux) which needs to be licensed for using Capture Client. You don't license CC to the Firewall. The license can be attached to a Firewall to enforce CC when behind a SNWL Firewall, but this is not mandatory. There are a couple of SKUs available, I mentioned the price…
-
@bzperry you can see Capture Client as an independent product from the Firewall. Capture ATP (auto mitigation) is done on the Endpoint not on the Firewall if enabled in the CC policy. If you have Capture ATP and DPI-SSL enabled on the Firewall as well, it will be inspected there first, but you don't need to rely on it.…
-
@bzperry the SKU you mentioned is for the price band 5 to 24 licenses (which means a minimum order of 5 licenses), you need one license for each Endpoint, the Firewall does not need a license because it does not run CC. —Michael@BWC
-
@bzperry Capture Client works independently from the Firewall and will be managed through Cloud Security Center (Management Portal). On that matter it's like any other Endpoint security solution. The DPI-SSL component of Capture Client is more of a certificate deployment helper, not relevant if you don't have DPI-SSL at…
-
Hi @Community Manager ja the problem is still ongoing, I provided all information I had. It seems like some authentication glitch specific to my deployment because others I spoke to do not have that kind of issue. —Michael@BWC
-
@supbod you probably did not have enabled the proper flow monitoring. Please check your settings. —Michael@BWC
-
@Siuren no worries, it's simpler than you might think. Just make sure that the NSA 2600 is running on a Firmware that is supported by the Migration tool. Update the new NSa 2700 to 7.0.1-5145, which is officially supported by the Migration Tool convert the Configuration with the Migration Tool Import the Configuration into…
-
Did the newly release 6.5.4.15-117n resolved the issue? —Michael@BWC
-
@STCNtech did you tried to put a mini switch between the non-working interface and the Modem/Router? Sometimes the Interfaces of the TZ are not playing nice with others. —Michael@BWC
-
@SteveGwynne we had this a couple of times, policy based routing (PBR) is the term you're looking for. Maybe this helps as a starter: —Michael@BWC
-
On Gen6 the mentioned settings can be found under Manage → Logs & Reporting → Log Settings → Base Setup, you have to hit the "Import Template" toggle. —Michael@BWC
-
@Mithun_Haridas the Event ID is the value of "m=" in your syslog. —Michael@BWC
-
@jvpangan17 that sounds like a dilemma, not having a current support does not help in that case. Maybe @Community Manager has access to the Release Notes since 6.5.4.8, I have only access to 6.5.4.13 and 6.5.4.15 and there was nothing reboot related mentioned in there. But it might be related to the fixed vulnerabilities…