WatchGuard AuthPoint

WatchGuard AuthPoint is being used in all our company departments, for the authentication of all our users when they connect to our network remotely via SSL VPN. We also use Authpoint for the user authentication on our NextCloud installation. We intend to use it in the future for granting access to specific applications via the WatchGuard Access Portal on our Fireboxes.

We can NOT detect password reuse, so we can't enforce any policies to avoid it. Authpoint does add an extra security layer, thus it is reducing the impact of a possible credentials leak.

WatchGuard AuthPoint Total Identity Security (TIS) offers a corporate password manager. We used to have a similar solution from another provider, but having one single product instead of two, does make your life easier!At the time we do not have a need to use the dark web monitoring capabilities, but we expected this to get needed more are times go by and the dark web threats get bigger and bigger!

Things did not use to be that simple at all, when we first used WatchGuard AuthPoint with our SSL VPN connections on the WatchGuard Fireboxes. One would have to setup a radius server on a domain controller and pass all the connection traffic between the Firebox and AuthPoint through an Authentication Gateway on a DC. And then set up at least one more Authentication Gateway to ensure high availability. However since version 12.7 of Fireware this is no longer needed. That was a much expected change that did really make things a lot simpler and did make us very happy!

Most users did like the extra security the mobile token offered, as they are aware of the fact that similar solutions were used by all external partner employees that have visited us. So most of our users recognize that this is a standard way of authentication these days. There were of course a few users that complained about the extra steps needed, but this is really to be expected on any such change. Overall we would consider the reception by our users to be more than positive.

We have not used the Access Portal yet, but plan to do so in the future. So we have no experiences about it so far, but we expect this to be as smooth as the migration to the SSL VPN authentication via WatchGuard AuthPoint and the NextCloud authentication. However the aim here is to make access more secure. we do not expect any reduction the number of involved passwords...

Would only change Authpoint if we ever decided to use firewalls from another company... As long as we have our Fireboxes, Authpoint is the only way to go!

Now that no Radius server is needed for SSL VPN user authentication, if one follows the provided guide, it is easy to make the implementation. No extra training would be needed!

Don't be afraid of the process. Just start following the guide and everything will fall in place!

We just added the company logo to our Authpoint tokes, to be able to easily differentiate them from the other tokens we store on Authpoint mobile.

We have no premium support for Authpoint, as this service as stable as it can be! However we have Gold support (Total Security) for our pair of Fireboxes...

When we last renewed our Authpoint licenses, we had 2 activation codes, an older one and a newer one. We wanted to keep the license count of the newer license and add the older license key to extend the duration of the licenses. Also the older license count was higher than the license count of the newer activation key. So we let the older license expire to be able to reduce the license count and then we entered to 2 activation keys. It turns out that we had entered them in the wrong order and the result was that we activated the user count of the wrong activation key (much lees users than we need) and this got a huge duration period! Support resolved this immediately, reset the activations we had made and gave us instructions on how to properly install the license keys!

Would like to use Auhpoint for 365 as well, but from what we have read in the guide it seems to complex, so this has made us put off our initial thoughts about 365 integrations.

We made no negotiations with the vendor. They were offering the best price in the market, so there was no margin to negotiate about.

Make a good market search before choosing your vendor. There are vendors that are much cheaper than the average and others that have way to high prices...

WatchGuard AuthPoint is being used throughout the whole organization. It has helped us solve the problem of MFA.

Not having to configure more devices locally was beneficial for us. No maintenance costs, much less prone to unavailability.

It was a bit difficult in the beginning for the less tech-savvy colleagues, with a few hiccups and several questions. But with time, everyone got used to it and no more problems arose. Now that we created a beginners guide, new colleagues aren't having a hard time using it for the first time.

We haven't used AuthPoint SSO capabilities yet.

I wouldn't change

It's fairly simple. Authpoint doesn't have many aspects and features that require a deep knowledge from the users.

Fairly simple configuration, with barely any aspect needed to adjust

Nothing relevant

We didn't. Didn't see a need for it

We've never contacted support

None specifically

None I can think of

No