
Improve Physical SecurityThe physical security of token servers is tantamount, and similarly partners need to stress the importance to token holders of keeping close track of their devices. Depending on the attack, physical access may be the only thing a well-equipped hacker needs at this point.

Consider Turning Off Remote AccessIt may not be a possibility for some systems, but this option is the most secure choice until RSA offers more details about the breach.

Reexamine Passwords and PINsTokens are part of multifactor authentication schemes. Passwords and pins are more important than ever if you choose to keep remote access on while the situation unfolds. Be sure to educate and enforce strong password principles.

Train Help DeskIs your help desk staff giving away key information about customer accounts to social engineering scammers? If you’re not sure, it’s time to retrain.

Lock Down Active DirectoriesRSA is suggesting that organizations implement two-factor authentication to control access to Active Directory and to keep special monitoring tabs on and to stay on the lookout for unusual account behavior.

Explore AlternativesIf you or your customers are unsatisfied with RSA’s response, if customers can’t afford to be without remote access or multifactor authentication, or if your customer was already unhappy with the unwieldiness of tokens, now is the time to look for authentication alternatives.

Monitor Privilege LevelsService providers will especially want to watch their customer’s accounts closely for unusual changes in privilege levels and access rights and potentially may even want to add manual approval for changes in key accounts.

Train Employees On Social EngineeringCustomer and partner employees need to be reminded of why they need to avoid giving away credential information over the phone or email. They should also be instructed to report these requests.

Patch, Patch, PatchEnsure that customers have not only patched their operating systems and key apps, but also their security software.