The Home Depot Breach: What Retailers and Restaurants Should Take From It

From the archive: this article was written in 2014 and reflects the technology and threats of that time. For current advice, see our latest articles or ask us directly.

It is starting to feel like a pattern. Last December it was Target. Over the summer came a string of smaller announcements from restaurant chains and retailers. And this month, Home Depot confirmed that its payment systems had been breached, with malware on its registers collecting card data from customers who shopped in its U.S. and Canadian stores.

The numbers are big. Home Depot has said about 56 million payment cards may have been affected, and that the malware was in its systems for months, reportedly since April. If you shopped there this spring or summer, watch your statements. But if you run a store, a restaurant, or any business that swipes cards, the more important question is what this means for you.

What happened

The details are still coming out, but the broad strokes match what we saw with Target. Attackers got into the company's network, reached the point-of-sale systems — the registers and card terminals — and installed custom malware on them. That malware grabbed card information from the register's memory at the moment a card was swiped, before it could be encrypted, and quietly sent it out.

Because the malware was new and built for this job, standard antivirus reportedly did not catch it. The breach came to light when banks noticed a pattern of fraud on cards that had been used at Home Depot, and security reporters began asking questions.

We covered the mechanics in our post on the Target breach and point-of-sale security. The short version: a register is a computer, and it can be infected like any other computer.

"But I am not Home Depot"

This is the most common response we hear, and it is understandable. Why would anyone bother with a single boutique in Dunedin or a family restaurant in New Port Richey?

The answer is that attackers go after small businesses precisely because they are easier. The federal government issued a warning this summer about malware called "Backoff" that was found on point-of-sale systems at a large number of businesses, many of them small. A common route in was remote access software — the tools a POS vendor or IT person uses to log in and help — protected by weak or default passwords. Attackers scan the internet for those doors, try common passwords, and walk in.

For a small business, a breach does not make national headlines. It shows up as a call from your card processor, fines, forensic investigation costs, and customers who stop trusting you.

EMV chip cards are coming

Most of the world moved to chip cards years ago. The United States is finally following. The major card brands have set October 2015 as the date the "liability shift" takes effect for most merchants. After that date, if a counterfeit card is used at your register and you are not able to accept chip cards, you may be responsible for the fraud losses instead of the bank.

Chip cards help because each transaction creates a unique code that cannot simply be copied and reused, unlike the data on a magnetic stripe. That makes stolen card data much less valuable for making counterfeit cards.

Chip readers do not solve everything — card data can still be stolen, and online fraud is a separate problem — but they are a real improvement. If you are replacing your terminals or POS system in the next year, make sure the new equipment is EMV-capable. Ask your processor about options that encrypt card data right at the terminal, too.

Separate your networks

In many small businesses, everything shares one network: the registers, the office computer where someone checks email, the security cameras, and the free customer Wi-Fi. That means malware picked up on one device can reach all the others.

Your card systems should be on their own network segment, walled off from everything else. Guest Wi-Fi should never touch the network your registers use. A properly configured business firewall can do this without much expense, and it is one of the most effective steps you can take.

Patch and lock down the registers

Many POS systems run on versions of Windows, and a surprising number still run Windows XP, which lost support in April. Keep registers updated, or talk to your vendor about a supported version. Beyond that:

  • Use registers only for sales. No web browsing, no email, no games during slow shifts.
  • Lock down remote access. Change default passwords, use strong unique ones, turn on two-step verification where possible, and disable remote access when it is not needed.
  • Know who has access. Vendors and former employees should not have lingering logins.
  • Watch outgoing traffic. Registers should only talk to your processor and a few known services.

What to do now

  1. Ask your POS vendor what operating system your registers run and when it was last updated.
  2. Find out how your vendor connects remotely, and make sure the passwords are strong and not shared.
  3. Put card systems on a separate network from office computers and guest Wi-Fi.
  4. Plan and budget for EMV-capable terminals ahead of October 2015.
  5. Ask your processor about point-to-point encryption.
  6. Complete your PCI self-assessment honestly and fix what it turns up.

Home Depot will survive this. A small shop hit by the same kind of attack may have a much harder time. The good news is that the measures that would have stopped most of these attacks are not exotic or expensive. If you would like help separating your networks, securing vendor remote access, or planning for chip cards, our cybersecurity team works with retailers and restaurants across Pinellas and Pasco. Get in touch at info@pinellasit.com.

Need help with this?

Talk to a local IT team that has supported businesses across Pinellas & Pasco County since 2010.

Get a Free Consultation Free Security Assessment