I had to do a transfer of ownership before and it is pretty painless once you know the procedure.
The Action "Externally Remediated" means the Indicator was remediated by Administrators outside of TDR. Since APT blocker is not allowed to submit it for Sandbox File action, we effectively remove the Indicator from the Dashboard by rescoring it to a 1 without actually performing and real remediation actions on the file. TDR did not act on this file therefore I believe your backup software's crash was purely coincidental. If you find this sequence of events occurs again please put in a support case as you might be dealing with a defect.
So long as Azure MFA supports RADIUS and passes the SSLVPN group (SSLVPN-Users) as Radius attribute 11, it should work with no issue.
WatchGuard's MFA solution (AuthPoint) has a RADIUS server built into it's gateway software. This can be used with the SSLVPN.
You would need to add new HTTP & HTTPS policies From: the desired domain names, with App Control not enabled or with an App Control action which does not include DROP on Web File Transfer.
Make sure that the new policies are above the existing polieis so that they will be evaluated first.
Giving credit where due:
KevCar (https://community.watchguard.com/watchguard-community/profile/KevCar) is the one who suggested deleting the folder. So far, my connection has been flawless for the first time in many months.
WatchGuard doesn't have any program like that (we do offer significant discounts on new firewalls to schools, however.)
My apologies, but I used a online translation tool to read your question. Please feel free to correct me if I have any part of your issue wrong.
You said that you want to test using your Mobile VPN without having to use a Hotspot or similar "other" external connection.
My assumption is that you're using SSLVPN, as this VPN is policy bound to only listen to what is listed in the "WatchGuard SSLVPN" policy.
-Find that policy in your policy list.
-If you see a warning that you're modifying a automatically generated policy, click OK.
-In the from field, add "Any-Trusted" and/or "Any-Optional."
-Save your configuration to the firewall.
This should allow the customer to connect to the SSLVPN from the internal network.
There's no way to rename the action, but you can clone it and name the cloned one whatever you want (then deleting the old one.)
Use this button in the policy in policy manager to do that:https://imgur.com/a/yBuRpeJ
Thanks for writing.
The access portal is a bit complex, so there's not a video quite yet. Any video produced would likely be specific to an integration, as a general example video would be very long, and not touch on any specific points.
I'd suggest starting here, if you haven't already:
(Reverse Proxy for the Access Portal)https://www.watchguard.com/help/docs/help-center/en-US/Content/en-US/Fireware/services/access portal/access_portal_reverse-proxy.html
In the future, please do not post connection (port) and domain info here, as this forum is accessible and search-able via the general Internet. If you need help that requires posting specific information, I'd suggest creating a support case with WatchGuard's support center button (top right of the page) instead. That'll help keep your information safe.
These errors always indicate the proxy was unable to pre-validate the chain using certificates presented by the server and its own root CA bundle. Kind of like a browser would.
The server is misconfigured. It is not sending the intermediate certificate in its response.
1 Sent by server www.matrixgames.com
2 Extra download Go Daddy Secure Certificate Authority - G2
3 In trust store Go Daddy Root Certificate Authority - G2 Self-signed
2 is the responsibility of the server. Both, Firefox and Chrome, have 2 cert in their bundles.
To mitigate, you can append the intermediate certificate to Firebox's CA bundle. Import it as a General Use certificate via FSM / View / Certificates / Import Certificate. Link to the certificate from GoDaddy's certificate repository: https://ssl-ccp.godaddy.com/repository/gdig2.crt.pem
I'll recommend that we add it to the next CA bundle update.