If there is a teenager in your house, you already know the PlayStation Network has been down. Sony pulled the plug on April 20, and at the time of writing it is still offline. On April 26, Sony confirmed why: an intruder had gotten into the system and accessed personal information tied to roughly 77 million accounts. Names, addresses, email addresses, birth dates, and login details were all potentially exposed, and Sony said it could not rule out that credit card data had been taken too.
Days later, Sony disclosed that its Sony Online Entertainment gaming service had been hit as well, adding millions more accounts to the tally. It is one of the largest data breaches ever reported. And while most small businesses will never hold 77 million records, almost every business holds some customer data. The lessons scale down surprisingly well.
What happened, in plain terms
Sony has said the intrusion took place over several days in mid-April. Once the company realized something was wrong, it shut the network down entirely, brought in outside security firms to investigate, and began rebuilding its systems with added protections. Sony has also been criticized for how long it took to tell customers that their personal information may have been exposed, roughly a week after the network went dark.
Many of the finer details, including exactly how the attackers got in, are still being investigated and debated. We will not guess at them. What is already clear is enough to draw some practical conclusions.
Lesson one: data you do not keep cannot be stolen
The simplest protection is also the most overlooked. Every piece of customer information you store is something you have to protect, and something you have to explain if it leaks.
Take an honest look at what your business collects. Do you need customers' birth dates? Do you need to keep full card numbers on file, or can your payment processor store them for you? Are there old spreadsheets of customer details sitting on someone's desktop from a promotion three years ago? A typical small office has far more stray customer data lying around than anyone realizes.
Before asking "how do we protect this data?", ask "why do we have this data at all?"
Lesson two: encrypt what you must keep
Encryption scrambles information so that it is useless without the key. Sony has said the credit card numbers in its database were encrypted, and that distinction will likely matter a great deal for the people affected. Much of the other personal data, by Sony's own account, was not protected the same way.
For a small business, encryption is more approachable than it sounds:
- Laptops should use full-disk encryption, such as BitLocker on business editions of Windows 7. A lost or stolen laptop then becomes a hardware loss, not a data breach.
- USB drives and backup media that leave the office should be encrypted too.
- Payment data should be handled by a processor that meets the PCI DSS card-industry standards, rather than kept in your own files.
- Passwords for customer accounts on your website should never be stored in plain text.
Lesson three: patching and monitoring are not optional
Whatever the exact entry point turns out to be, large breaches usually involve some combination of unpatched software, weak configuration, and attackers who go unnoticed for too long. None of that is unique to big companies. Small business networks run the same Windows, the same web servers, and the same browser plug-ins.
Keeping servers and computers patched, reviewing firewall settings, and having someone actually watch for unusual activity are the unglamorous basics that stop most attacks, or at least catch them early. A breach discovered in hours is a very different event from one discovered in weeks.
Lesson four: have a plan before you need one
Sony's situation shows how quickly a breach becomes a business problem rather than a technical one. There is downtime, lost revenue, angry customers, press coverage, questions from lawmakers, and the cost of investigators and credit monitoring. Decisions about when to shut systems down and when to tell customers have to be made under enormous pressure.
A small business should think through those questions now, calmly, rather than for the first time in the middle of a crisis:
- Who do we call first if we suspect a breach?
- Who has authority to take systems offline?
- How do we contact affected customers, and what do we tell them?
- What notification rules apply to us? Florida, like most states, has a breach notification law that applies when certain personal information is exposed.
- Do we have clean backups so we can rebuild if we have to?
That plan does not need to be a thick binder. A couple of pages with names, steps, and contact details stored somewhere other than the affected computers can make an enormous difference.
What to do now
- Inventory your customer data. Where is it stored, who can access it, and do you still need it?
- Delete what you do not need, including old exports and spreadsheets.
- Encrypt laptops and portable media that hold customer information.
- Let your payment processor hold card data instead of storing it yourself.
- Get patching under control on every server and computer, including Adobe and Java plug-ins.
- Write a one-page breach plan and make sure the key people know where it is.
- If you had a PlayStation Network account, change that password and any other account where you reused it, and keep an eye on your card statements.
Sony will recover, but the cost of this breach is going to be large, and much of it could have been reduced with basics that apply to businesses of every size. If you would like help taking stock of the customer data your business holds and how well it is protected, our cybersecurity team would be glad to sit down with you. Email info@pinellasit.com or use our contact form.
