Last Thursday, in the middle of the busiest shopping stretch of the year, Target confirmed what security reporters had started hinting at the day before: criminals had stolen payment card data from its stores. According to Target, about 40 million credit and debit card accounts may have been affected, belonging to customers who shopped in its U.S. stores between November 27 and December 15.
If you run a boutique in Dunedin, a restaurant in St. Pete, or a surf shop in Madeira Beach, it is tempting to file this under "big-company problem." It is not. Card thieves go after small merchants all the time. They just do not make the national news when they do. Here is what we know so far, and what you can do to protect your own registers.
What we know so far
Target has said the stolen information includes customer names, card numbers, expiration dates, and the three-digit security codes. The theft affected purchases made at the registers in its physical stores; Target has said online shoppers were not affected. The company says it has fixed the problem, is working with law enforcement and an outside forensics firm, and offered shoppers a store discount last weekend by way of apology. If you shopped there during that window, keep a close eye on your card statements.
What has not been made public yet is exactly how the attackers got in. Investigations like this take weeks or months, and early speculation often turns out to be wrong, so we will not guess. What matters for your business is the target itself: the point-of-sale system, where cards are swiped and card data exists, however briefly, in a form criminals can use.
Card thieves go where the cards are swiped. For a small retailer or restaurant, that is a PC or terminal sitting on the counter.
Why small merchants are attractive targets
Big retailers have security teams and still get breached. Small businesses usually have far fewer defenses, and attackers know it. Common weak spots we see in small shops and restaurants:
- The POS computer is also used to check email, browse the web, or play music.
- The POS is on the same network as the office PCs, the security cameras, and the free customer Wi-Fi.
- Remote access software was installed by the POS vendor and left open with a default or shared password.
- The POS runs an old version of Windows and has not been updated in years.
- Nobody is quite sure who is responsible for security: the owner, the POS vendor, or the card processor.
For a small business, a card breach can mean fines from the card brands, forensic investigation costs, higher processing fees, and lost customer trust in a community where word travels fast.
PCI compliance in plain English
If you accept credit cards, you have agreed to follow the Payment Card Industry Data Security Standard, known as PCI DSS. It is a set of security requirements from the card brands. For most small merchants, it means completing an annual self-assessment questionnaire and, if you have internet-connected card systems, passing regular network scans.
The PCI Council released version 3.0 of the standard last month, which takes effect at the start of 2014. Whatever version you are on, the spirit is the same: protect card data, keep your systems secure, and limit who can get to them. Too many small businesses treat the questionnaire as paperwork. Answer it honestly, and it is actually a pretty useful checklist.
Keep the POS on its own network
If you do only one thing after reading this, separate your payment systems from everything else. Your registers and card terminals should sit on their own network segment, isolated from:
- Office computers used for email and web browsing
- Guest or customer Wi-Fi
- Security cameras, music systems, and other gadgets
A properly configured business firewall can do this with separate networks, often called VLANs, and rules that allow the POS to talk only to what it needs, such as your card processor. That way, if an office PC picks up malware from a bad email, it cannot reach your registers.
Patch, lock down, and watch
- Keep the POS updated. Windows updates, POS software updates, and antivirus. If your POS still runs Windows XP, remember that security updates for it end in April 2014. Start talking to your POS vendor about an upgrade now.
- Use it for one job. No email, no web browsing, no Facebook on the register.
- Lock down remote access. If your vendor needs remote access, it should be turned on only when needed, protected by a strong unique password, and logged.
- Change default passwords on the POS, the router, and anything else on that network.
- Give each employee their own login and remove access promptly when people leave.
- Watch for tampering. Inspect card readers and PIN pads for skimmers or anything that looks added on.
Consider moving card data off your network
The less card data your systems touch, the less there is to steal. Talk to your processor about options such as point-to-point encryption, where card data is encrypted inside the card reader before it ever reaches your computer. Chip card (EMV) readers are also worth planning for. They are standard in much of the world, and the major U.S. card brands have announced they plan to shift fraud liability toward merchants who have not adopted chip readers by October 2015.
Your POS security checklist
- Put payment systems on a separate network from office PCs and guest Wi-Fi.
- Make sure the POS is used only for sales.
- Apply updates to Windows, POS software, and antivirus.
- Change all default passwords and review vendor remote access.
- Complete your PCI self-assessment honestly and fix what it turns up.
- Ask your processor about encrypted card readers and chip card support.
- Check card readers for tampering regularly.
The holidays are a rough time to think about this, we know. But January is a great time to fix it. If you would like help separating your payment network or reviewing your POS setup, our cybersecurity team works with small retailers and restaurants throughout Pinellas and Pasco. Reach out at info@pinellasit.com, and happy holidays.
