When a security company gets hacked, it makes for irresistible headlines. In mid-March, RSA, the company behind the SecurID tokens that many banks, corporations, and government agencies use for logins, published an open letter to its customers saying it had been the target of an "extremely sophisticated" attack. RSA said the attackers had taken information related to its SecurID two-factor authentication products.
Last week, RSA shared more about how the attack started, and the answer was almost disappointingly ordinary: a couple of emails and an Excel spreadsheet. For a small business owner, that detail is the most important part of the story.
What happened
According to RSA's own account, attackers sent phishing emails to small groups of employees over a couple of days. The emails carried the subject line "2011 Recruitment Plan" and included an Excel file. The messages were apparently caught by the company's spam filtering, but at least one employee pulled one out of the junk folder and opened the attachment.
Hidden inside the spreadsheet was code that exploited a previously unknown flaw in Adobe Flash. Opening the file quietly installed a remote-control program that gave the attackers a foothold inside RSA's network. From there, they worked their way toward more valuable accounts and systems and eventually copied data out.
RSA has not said exactly what was taken, only that it relates to SecurID and could reduce the effectiveness of the system in a broader attack. The company has been advising customers on steps to strengthen their deployments.
Lesson one: phishing still works, even on experts
It is tempting to think phishing only catches the careless. RSA is a security company, full of people who think about attacks for a living, and it still took just one person opening one attachment. The email was timely, plausible, and about something people naturally want to read. That is exactly what makes a good phishing email.
For a small business, the takeaways are practical:
- The spam folder is there for a reason. If something was filtered out, treat it with extra suspicion before fishing it back out.
- Unexpected attachments deserve a pause, even if the subject line looks relevant to your job. When in doubt, check with the sender another way.
- Staff should feel safe asking. An office where people can say "this looks odd, can you check it?" without embarrassment is far better protected than one where they just click to avoid looking foolish.
Lesson two: patching is not just about Windows
The spreadsheet did not exploit Excel on its own. It used a flaw in Flash, which was embedded in the file. That is a reminder that attackers go after whatever software is on the machine, and add-ons like Flash, Adobe Reader, and Java are among their favorite targets because they are everywhere and often out of date.
In this case the flaw was brand new, so patching alone would not have saved RSA on the day. But in the real world, most successful attacks on small businesses use holes that were fixed months ago. Keeping those browser plug-ins and document readers updated closes the door on a huge share of everyday attacks.
Lesson three: two-factor authentication is still worth it
Some commentary has suggested that this breach proves two-factor authentication is broken. That is the wrong conclusion. Two-factor authentication means a login needs something you know (a password) plus something you have (like a token or phone). Even if the stolen information weakens SecurID in some situations, an attacker would still need other pieces, such as a user's password and details about which token belongs to whom, to take advantage of it.
A lock that has been weakened is still better than a door left open. Two factors are still far stronger than a password alone.
For small businesses, the most common attack is not a sophisticated nation-state operation. It is a stolen or guessed password used to log in to email, remote access, or a banking site. Two-factor authentication stops that cold. If your bank offers it for online banking, turn it on. If you have remote access into your office network, it should require more than a password.
Lesson four: defense in depth
The real story of the RSA breach is that one layer failed, then another, then another. The spam filter caught the email, but a person retrieved it. The desktop opened the file, and the unknown flaw was not stopped. Once inside, the attackers were able to move around the network.
Security professionals call the answer "defense in depth": several overlapping layers, so that when one fails, and eventually one will, the next one catches the problem. For a small office that typically means:
- Email filtering that blocks the bulk of junk and malicious attachments
- Up-to-date antivirus on every computer and server
- Prompt patching of Windows, Office, and browser plug-ins
- Staff who do not run as administrators on their own machines
- A firewall that watches traffic going out, not just coming in
- Two-factor authentication on remote access and critical accounts
- Backups that are kept separate from the main network
What to do now
- Remind your staff about suspicious attachments, and especially about retrieving messages from the spam folder.
- Update Flash, Adobe Reader, and Java on every computer, and set them to update automatically where possible.
- If you use SecurID tokens, follow RSA's guidance and talk to your IT provider about the recommended steps.
- Turn on two-factor authentication for online banking and remote access wherever it is available.
- Review who has administrator rights on your computers and remove them where they are not needed.
The RSA breach is a humbling reminder that nobody is too big or too smart to be phished. The good news is that layered, sensible protection works, and it does not have to be complicated. If you would like a second set of eyes on your email filtering, patching, and logins, our cybersecurity team is glad to help. Reach us at info@pinellasit.com or through the contact form.
