Comments
-
I am also lucky as 1/3 sites has a firewall 'big' enough to support Next-Gen AV. I'm going to have to review the latest WG 2019 internet security report as I thought they had said that their new next gen AV was catching a majority of the threats... I also may consider re-directing all internet traffic from my other two…
-
Gregg, I hope thats a key consideration that is pointed out by WatchGuard resellers for potential customers!
-
Thanks for the correction John! I've edited my initial post with the correction
-
I wouldn't compare it to Cylance. TDR is an add-on product, not an AV/Endpoint Protection Solution. If a client already has WatchGuard in place with the appropriate subscription, deploy it (nothing to loose). If you have a client that wants to deploy an additional layer of ransomware or endpoint protection, then look at…
-
Thanks for that recommendation John, I'll check it out!
-
@ Stewy, Yes. That would be very helpful.
-
@ John, Yes.
-
So I've also noticed host "noisy" TDR is. I think my biggest issue is have to manually "resolve" the indicators (7+). I think it may make more sense to NOT resolve the indicators, rather the incidents.
-
You will need to update any applicable inbound rules/NAT with your new ISP's IP's. You will also need to load those additional IP's under secondary networks under the respective interface.
-
I also dont mind the sys tray icon (I think its a good think). I have yet to see a notification...
-
No. It's not designed to be an AV solution.
-
If you are seeing the Authentication attempts in Duo using RADIUS, that's a pretty good sign!
-
be sure you are adding a comma between your actual password and your yubikey OTP. Also, did you add your Yubikey as a Hardware Token or WebAuthn/2UF? I'm pretty sure it has to be added as a Hardware token which will require you to confirm the Yubikey (if you didn't already).
-
Here is a guide: https://www.watchguard.com/docs/tech/watchguard-duo-integration-guide.pdf
-
You will also have to setup a Duo Authentication Gateway and modify your Firewall settings by adding an LDAP server. Users will then login with their password, a comma, then tap the Yubikey.
-
You can do it. We are. You just have to add the hardware token to the users Duo Account.
-
You can add a secondary Gateway.IP for each BOVPN
-
Thanks for that Mark! That's that issue!
-
I've been seeing random NAT'ing issues since 12.4 (beta) I believe.
-
I've already added it to my change window for tomorrow :)
-
Make that 12.4 (Build B292447), NOT Update 1. It also works in Chrome on another computer...
-
12.4 U1 It works on same computer different browser.
-
Looks like I can blame this issue on Chrome...
-
It doesn't defeat the the purpose of a firecluster, rather it moves the single point of failure 'upstream' to another device. Having a firecluster mitigates the risk of a firewall dropping dead/failing.
-
Keep in mind your ISP hardware can typically only hand-off to a single device.
-
Case submitted
-
@Ricardo_Arroyo, I already whitelisted and submitted to our MSP/ConnectWise vendor. I'll also submit a support case shortly.
-
As long as both are BOVPN's, you should (as I am, not with AWS, but with external organizations). Your central hub will need to act as the endpoint between each tunnel.
-
So BGP is handling the routing, not the BOVPN. Your BOVPN choices are IPSec or TLS. Are you meaning your BOVPN with BGP is a BOVPN Virtual Interface?
-
BO = Branch Office....