http://www.darkreading.com/security-monitoring/167901086/security/security-management/229400558/securid-breach-warning-signs-in-the-audit-logs.html By Kelly Jackson Higgins Darkreading March 29, 2011 Most security experts caution RSA SecurID customers not to panic about the breach the security company revealed last week. But that doesn't mean they shouldn't plan for the worst-case scenario: The SANS Internet Storm Center has come up with a list of things to watch out for in audit logs -- just in case the bad guys got the keys to the kingdom, stole your token "seed" values, and were able to then acquire logins and PIN numbers for a full-blown breach of your two-factor authentication system. SANS ISC handler Daniel Wesemann spelled out the specific audit log entries that could show up in your RSA ACE server for SecurID if there's trouble. But even if an attacker had grabbed seeds from an organization's SecurID tokens, he would still have to figure out the userID and PIN to log in, Wesemann said, so this is one of the worst-case scenarios. His post comes on the heels of fellow ISC handler Rob VandenBrink's, who explained in a post yesterday on the ISC SANS site just how bad it could be. "Long story short, no matter how bad RSA's breach might or might not have been, System Administrators have it in their power to implement truly effective mitigations," VandenBrink wrote. Here are some entries you hopefully won't find in your audit logs in the ACE server. But if you do, take heed: [...] ___________________________________________________________ Tegatai Managed Colocation: Four Provider Blended Tier-1 Bandwidth, Fortinet Universal Threat Management, Natural Disaster Avoidance, Always-On Power Delivery Network, Cisco Switches, SAS 70 Type II Datacenter. Find peace of mind, Defend your Critical Infrastructure. http://www.tegataiphoenix.com/Received on Wed Mar 30 2011 - 00:20:46 PDT
This archive was generated by hypermail 2.2.0 : Wed Mar 30 2011 - 00:28:34 PDT