What is our primary use case?
My main use case for Google Authenticator is for saving my data protection. It can be needed if any hacker or attacker tries to access my email, so they need two-factor authentication. I need to activate this for reducing hacking from my email and for my data privacy.
A specific example of how I use Google Authenticator in my daily work is that because I used to work in cloud technology, I am also using Google Cloud and Google Workspace. I need this activated for authentication, which is primary for my security because a lot of data is collaborating in my Google Workspace. I need to activate this for authentication to reduce and block attackers from hacking my email and my workspace.
The other use is for other apps where I apply authentication to log in with Google. This is helpful to me.
What is most valuable?
In my opinion, the best feature Google Authenticator offers is that it makes your time more secure and your data more secure. The feature is good.
The security features of Google Authenticator have helped me greatly because when you do not activate this, you only have one protection with any Google account requiring OTP. Google Authenticator employs two-factor authentication, making you more secure than with just a single layer. This helps me sync and access GitHub, Microsoft, and any accounts using Google's authentication.
Regarding the features of Google Authenticator, I find it very easy and free, and there is no need for an internet connection when I generate the code. It is simple for me to implement, standard for TOTP, and compatible with many services. Primarily, it can reduce password leak issues significantly.
Google Authenticator has positively impacted my organization by improving security and productivity.
Regarding how security and productivity have improved, my team collaborates in the cloud and needs to spend time working there securely. With the feature in Google Cloud, Google Authenticator makes their lives easier. They do not need to be experts to use it. Many applications can be connected, which is excellent, and the primary security with two layers is very effective.
What needs improvement?
A potential improvement for Google Authenticator that I suggest is to add push notifications in the future. Currently, I think everything is good. Simply adding the feature for push notifications would be beneficial.
For how long have I used the solution?
I have been using Google Authenticator for a long time. I cannot remember exactly, but I started using this for my first email approximately 15 years ago.
What do I think about the stability of the solution?
Google Authenticator is stable.
What do I think about the scalability of the solution?
The scalability of Google Authenticator is adequate. It is an application authentication but related to supportive infrastructures. I think it is great for any platform and condition, quickly generating codes even without an internet connection.
How are customer service and support?
My experience with customer support so far is good.
Which solution did I use previously and why did I switch?
I previously used a different solution, which was Microsoft because it is needed from the application itself, implemented using Microsoft specifically in Azure. However, for most applications, I use Google applications.
What was our ROI?
I see a return on investment because spending costs are non-existent, and it significantly helps improve security with its free features, free downloads, free support, and easy understanding and learning. That is more than good enough.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is that pricing is very free, which is good. The price is still free.
Which other solutions did I evaluate?
Before choosing Google Authenticator, I evaluated other options, specifically Microsoft Azure and Microsoft authentication.
What other advice do I have?
The accuracy and reliability of Google Authenticator's output are solid because after generating the code, it can be implemented directly to the application on the server that uses Google authentication.
Google Authenticator is deployed in my organization using a hybrid cloud setup since it can handle authentication from Google applications.
My advice for others looking into using Google Authenticator is that if you need to improve your security, activating MFA or two-layer authentication will make your life easier and more secure, alleviating worries about hacking or cracking your applications or emails related to using Google Authenticator. I give this product a rating of 9.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
