Hundreds of organizations have replaced RSA with SecureAuth. Should you? To help you decide, we’ve put together a quick checklist of the top 5 reasons these customers chose to migrate.
Reason 1: 60% lower TCO
The top reason why organizations are making the switch to SecureAuth is total cost of ownership: SecureAuth’s TCO is nearly 60 percent lower than RSA’s.
Many factors contribute to this savings. If you have RSA, you already know about the high administrative and management burden it imposes; all the HA and backup hardware and software you have to buy and maintain; the expensive professional services you need to engage; and the extensive effort required to learn RSA’s proprietary architecture and constantly create and test custom code. We’ll see how SecureAuth reduces many of these costs in the sections below. For the moment, let’s just consider one major cost: tokens.
How much are RSA’s tokens costing you, year in and year out? The expense of buying the actual tokens is just the start. There are also the exorbitant shipping costs, the effort required to distribute and manage them, the cost of end-user training, and all the time your help desk spends supporting them. There’s also the productivity hit as users are forced to step through two-factor authentication multiple times every day (and, we might add, all the time they spend complaining about how much they hate, hate, hate the tokens).
By migrating to SecureAuth, you can eliminate tokens, either immediately or by phasing them out on your schedule. And SecureAuth’s pricing is simple and transparent — there are no hidden costs or additional services you need to tack on past the initial deployment and support costs, which are bundled into our per-user monthly subscription pricing.
Semiconductor producer Marvell deployed SecureAuth adaptive authentication and single sign-on (SSO) for all its 7,200 employees in less than four months — and at a 50 percent cost savings over RSA tokens.
Reason 2: The most modern security
Although RSA was considered a leader in security back when client-server architecture was the norm, things are quite different now. Organizations are eager to embrace cloud and mobile technologies, BYOD brings new devices to the network every day, and the volume of data that must be protected is exploding. Many organizations have found that RSA’s antiquated platform no longer meets their needs.
The future of security is adaptive authentication. But RSA only recently published an adaptive authentication roadmap that SecureAuth achieved two plus years ago. SecureAuth offers advanced adaptive authentication that goes far beyond passwords and tokens by layering together multiple pre-authentication risk checks, such as device recognition, threat intelligence, IP reputation, geo-location, behavioral biometrics, to determine identities with confidence. Moreover, while RSA considers its job done at initial authentication, SecureAuth’s continuous authentication silently checks typing sequences and mouse movements against a stored profile of a given user and device to stop attackers using hijacked credentials or stolen devices.
Just how much better is our security? SecureAuth can guarantee in writing to their customers that no malicious activity will occur from compromised credentials.
Reason 3: A seamless user experience
RSA users have long complained about the multiple daily disruptions for a multi-factor authentication step, carrying around a FOB, and waiting on hold for help desk support.
SecureAuth’s adaptive authentication delivers not only uncompromising security, but also the very best user experience. By layering together multiple technologies, SecureAuth requires multi-factor authentication (or denies an authentication attempt outright) only when the risk is sufficiently high. This streamlines the user experience for the vast majority of cases, while blocking attackers. Plus, SecureAuth’s context-rich push notifications require only a tap of one button to approve an authentication request.
SecureAuth also enables single sign-on and passwordless authentication — both of which improve security while delighting users. There’s even an integrated user self-service function that enables users to enroll their devices, reset their own passwords, unlock their accounts, and more.
“Usually when IT implements an organizational-wide change, you hear grumbling, but employees were glad to finally be rid of their tokens and were pleasantly surprised how easy the SecureAuth IdP solution authenticated and granted access to the Marvell VPN. I’m confident with the high level of security, control, and scalability with SecureAuth IdP. I am also pleased with the best-in-class service and support we’ve received from the SecureAuth team. – Todd Holloway, Senior Manager of Information Security, Marvell
Reason 4: Easier administration and application integration
RSA relies on a proprietary architecture that’s difficult and expensive to integrate with. Many customers also find the RSA administration UI to be virtually unusable, which means they have to laboriously code every workflow. These issues not only drive up costs, but limit agility and innovation.
SecureAuth, on the other hand, offers standards-based support for nearly any device, identity type, VPN, identity store, MFA method, and application, and enables you to utilize RESTful APIs. As a result, it fits in easily with existing investments and drives down implementation and maintenance costs. For example, customers report they have been able to slash the time required to roll out new applications from 6 months with three full time employees using RSA to less than a week with just one resource with SecureAuth. Moreover, support for modern standards such as OAuth and OpenID enables us to easily support your mobile initiatives.
One integration merits special attention. SecureAuth provides native integration to SIEMs, which dramatically increases visibility into authentication attempts. This is critical because 63% of confirmed data breaches involved the use of weak, default, or stolen credentials, according to Verizon’s 2016 Data Breach Investigations Report. Integrating SecureAuth with your SIEM enables correlation of a broad range of security and event data, so your SOC staff can quickly identify anomalies and take action in time to prevent a breach or business disruption. That stands in harsh contrast to the 3–4 weeks migrated customers say it used to take to determine whether a credential was compromised with RSA. Quick dashboard views show login activity, failures, blocked requests, request types, realm utilization, and more, so your security team always has a pulse on access requests.
“[SecureAuth] worked with not only our main Citrix-based application, but all other types of different applications, from VPN to web reserve proxy to cloud-based SaaS apps. It was a home run in every category. – Matt Johnson, Manager, Server Engineering, Houston Methodist
Reason 5: A focus on customer success, not services revenue
Of course, with any software solution, it’s not just about the product; it’s about the support. If you’re like many former RSA customers who have migrated to SecureAuth, you often spend days or weeks trying to locate an RSA resource who has the expertise to answer your questions, and getting them on a call can be nearly impossible. And an RSA upgrade might cost more in services than the original software.
At SecureAuth, our goal is not sell services to our customers; rather, it is to ensure a successful go-live and stay live. Because we sell time-based subscriptions, we have to continually win your business every year. It simply is not in our best interest to sell a solution and walk away. In fact, our customers are fully operational in hours or days, instead of months or years.