If you run more than one restaurant, PCI compliance usually shows up as a yearly questionnaire from your payment processor and often a monthly fee if you don’t finish it. It’s easy to treat it as paperwork. The trouble is that the questionnaire asks about things that live in your network closet: how the POS is separated from guest Wi-Fi, who can log in remotely, and whether anyone is watching the firewall. At five, ten or fifty locations, those answers drift unless someone owns them.
This guide explains what PCI DSS actually asks of a restaurant group, which parts are usually handled by your POS and payment vendors, and which parts stay with you.
R3 Services is a managed IT provider, not a PCI assessor (QSA). We help restaurant groups build and run the IT controls PCI asks about. Your acquiring bank or processor decides what validation you need.
What PCI DSS is, in one paragraph
The Payment Card Industry Data Security Standard (PCI DSS) is the security rulebook the card brands require of every business that accepts cards. The current version is PCI DSS 4.0.1. You prove compliance to your acquiring bank or processor, usually with a Self-Assessment Questionnaire (SAQ) once a year, plus quarterly external vulnerability scans for some SAQ types. Larger merchants, or those who’ve had a breach, may need an on-site assessment.
Which questionnaire does a restaurant usually fill out?
It depends on how cards flow through your locations. Your processor tells you which SAQ applies, but here is the usual pattern:
| How you take cards | Typical SAQ | What it means for your network |
|---|---|---|
| Terminals in a listed point-to-point encryption (P2PE) solution | SAQ P2PE | Smallest scope. Card data is encrypted in the terminal, so your network is mostly out of scope. |
| Standalone IP-connected terminals, not tied to other systems | SAQ B-IP | The terminals and the network path they use are in scope. |
| Integrated POS (terminals talk to the POS system) on your network | SAQ C | Your POS network, firewall, remote access and the devices around it are in scope. |
| Integrated POS where locations share a network, or card data is stored | SAQ D | Full PCI DSS applies. This is common for groups with connected locations. |
| Online ordering on your own site | SAQ A or A-EP | Depends on whether the payment page is fully hosted by the processor. If a third party runs the whole checkout, it may be out of your scope. |
Many restaurant groups use more than one method: integrated POS in the dining room, a different setup at the bar, online ordering through a third party. Each one needs to be counted. If your locations are networked together, ask your processor whether SAQ C still fits.
The parts your POS vendor covers, and the parts it doesn’t
Modern cloud POS platforms such as Toast, Square and SpotOn, along with Oracle MICROS, handle a lot of the heavy lifting: encrypted card readers, tokenization and secure payment processing. That is real protection, and it can shrink your scope a lot.
What the POS vendor does not control:
- Your network. Whether the POS shares a network with guest Wi-Fi, the office PC, cameras or the music system.
- Your firewall. Its rules, its firmware and who can change it.
- Remote access. Every vendor, technician and manager who can reach the network from outside.
- Passwords and accounts. Shared logins on the back-office PC, default passwords on network gear, ex-employees who still have access.
- The other devices. The manager’s laptop that checks email and the POS reports, the camera DVR with a default password.
PCI calls the systems that handle card data the cardholder data environment (CDE). Anything connected to it, or able to affect its security, is in scope too. The single biggest lever a restaurant has is keeping that environment small.
The five controls that matter most at a restaurant
1. Segment the network
Put payment devices and the POS on their own network (VLAN), with firewall rules that block traffic from guest Wi-Fi, staff Wi-Fi, cameras, music and the office. Done properly, segmentation is what keeps a compromised guest phone or camera from ever reaching a card terminal. It also shrinks what the questionnaire covers.
At a multi-location group, segmentation has to be identical everywhere. One location set up by a different installer is where the gap usually is. Our restaurant opening IT checklist covers how to build it in from the first day.
2. Lock down remote access
POS vendors, kitchen equipment vendors, your IT team and sometimes owners all need remote access. PCI DSS 4.0 requires multi-factor authentication for remote access into the cardholder data environment. It also expects vendor access to be turned on only when needed and monitored, and it limits shared accounts. In practice: no always-on remote desktop tools and no shared vendor logins. Every connection should be named, logged and time-limited.
3. Manage the firewall like it matters
A firewall that was configured at opening and never touched again is a liability. Keep firmware patched, review rules at least every six months (PCI DSS Req. 1.2.7), remove rules nobody can explain, and keep a current diagram of each location’s network. If a manager can plug a new device into the POS network without anyone knowing, the firewall isn’t doing its job.
4. Kill default and shared passwords
Default passwords on switches, access points, cameras and printers are among the first things attackers try. Shared logins on back-office PCs make it impossible to know who did what. Give every person their own account, turn on MFA where you can, and remove access the day someone leaves. At ten locations with seasonal turnover, that last step only happens if it’s part of a process.
5. Watch, log and keep records
Depending on your SAQ, PCI expects you to log activity on in-scope systems and review it. For a restaurant group, that usually means centralized logging from firewalls and servers, alerts on unusual activity, and someone who looks. Keep your evidence (scan reports, firewall reviews, training records) in one place so the yearly questionnaire is routine, not a scramble.
The gaps we see most often at real locations
From supporting restaurant and hospitality locations across the country, these come up again and again:
- Guest Wi-Fi and the POS on the same network “temporarily” since a busy weekend.
- A location opened in a hurry with a different firewall model and no segmentation.
- An old remote access tool still installed from a vendor who left two years ago.
- The office PC used for email, browsing and POS reports, with a shared password on a sticky note.
- Quarterly scans failing silently because the scan vendor’s emails go to a former manager.
- No one sure which SAQ applies to online ordering.
None of these are exotic. They happen because the people running the restaurants are, reasonably, focused on running restaurants.
A simple annual PCI routine for a restaurant group
- Confirm your SAQ type(s) with each processor, location by location.
- Update the network diagram for every location, including card flow.
- Review firewall rules and remove anything unexplained (every six months).
- Audit remote access: list every vendor and tool, remove what isn’t needed, confirm MFA.
- Audit accounts: remove ex-employees, end shared logins, change defaults.
- Check the quarterly scans passed (if your SAQ requires them), and fix what didn’t.
- Train staff on card skimming, phishing and what to do if a terminal looks tampered with.
- Complete and submit the SAQ with evidence in one folder.
Where R3 fits
R3 Services supports more than 110 restaurant and hospitality locations in 17 states and DC, for groups including bartaco. For restaurant groups we build and run the IT side of PCI: segmented networks with one standard at every location, managed firewalls, controlled remote access with MFA, account cleanup, monitoring and the evidence you need for your questionnaire, as part of our cybersecurity services. A real R3 technician answers the phone 24/7, so the POS going down during Saturday dinner gets a person, not a ticket queue.
We’re not a QSA, and we’ll tell you when you need one. What we do is help keep the answers on your questionnaire true at every location, all year, not just the day you fill it out.
Request a free IT assessment and we’ll review one location’s network against the controls above, or see how we support restaurant groups.
Frequently Asked Questions
Does using Toast or Square make my restaurant PCI compliant?
No. A modern POS reduces your scope and handles card encryption, but you’re still responsible for your network, firewall, remote access and accounts. Most merchants still validate compliance with their processor each year, though some payment providers handle part of that for you.
What is network segmentation, and why does PCI care?
Segmentation means putting payment devices on their own network, separated from guest Wi-Fi, cameras and office computers by firewall rules. It keeps a compromise elsewhere from reaching card systems and shrinks how much of your environment PCI covers.
How often do restaurants have to do PCI compliance?
Most restaurants complete a Self-Assessment Questionnaire once a year. Some SAQ types also require quarterly external vulnerability scans, and PCI DSS requires reviews of in-scope firewall rules at least every six months.
Is R3 Services a PCI assessor?
No. R3 is a managed IT and cybersecurity provider. We build and run the IT controls PCI asks about and help prepare the evidence. Your processor sets your validation requirements, and a Qualified Security Assessor (QSA) performs formal assessments when one is needed.

