As depicted in the 2019 movie Ford v Ferrari, the sports car race 24 Hours of Le Mans is an endurance race that tests the durability of equipment and the will and stamina of participants. For many corporate IT teams, dealing with the sudden, almost overnight transition to an all remote workforce has been an endurance race with similar tests.
And in the frenzy of needing to rapidly ramp up remote access to an entire organization and the rush to get authenticators into people’s hands to win the initial leg of the race, the obvious fact that there will be downstream impacts to the stability and performance of your authentication system can easily be overlooked. After all, RSA Authentication Manager is a workhorse that often masks smaller upticks without a hitch.
However, as your remote user population explodes, peak authentication rates go through the roof, and associated administrative activities (exacerbated by “newbies” to multifactor authentication) ascend to all-time highs, it is possible for performance slowdowns -- and blinding panic -- to set in.
Your RSA SecurID solution, normally a rock of IT stability, is going sideways... “The RSA is broken”... What is happening?!?!?
Don't worry. Everything is going be alright after making the necessary adjustments.
It is important that you take a systematic approach to reviewing your RSA environment and evaluating key areas for “redlining” conditions that ultimately result in a poor user experience of one sort or another. These key areas include both underlying system resources as well as RSA configuration parameters.
Extensive RSA performance tuning guidance is available through documents posted under the “Optimize & Tune” section of the new RSA Remote Workforce Resource Center.
Over its 30+ year history, RSA SecurID Access has established itself as a proven winner, capable of standing up to the biggest challenges... even while running at high RPMs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.