Restaurant Technology and AI

Restaurant Cybersecurity Basics

Cybersecurity basics for a small restaurant: separate networks, individual logins with MFA, phishing and payment-fraud defenses, and an incident plan.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing6 min read

On this page
  1. Why small restaurants are worth attacking
  2. Separate your networks
  3. Accounts: individual logins and MFA
  4. Phishing and payment fraud
  5. Keep card data off your own systems
  6. Train staff in ten minutes a quarter
  7. Devices, updates and backups
  8. The offboarding checklist
  9. A one-page incident plan
  10. Frequently asked questions
  11. References
Restaurant Technology and AI: Restaurant Cybersecurity BasicsArticle coverRESTAURANT TECHNOLOGY AND AIRestaurantCybersecurity BasicsAva for RestaurantsInsightsRestaurant Technology and AI: Restaurant Cybersecurity BasicsArticle coverRESTAURANT TECHNOLOGY AND AIRestaurantCybersecurity BasicsAva for Restaurants

Key takeaways

  • Separate guest Wi-Fi from the network that runs the POS, kitchen and office.
  • Give everyone their own login and turn on multi-factor authentication, using an app or key over text codes where possible[1].
  • Business email compromise cost US victims close to $2.8 billion in 2024[2]; verify every bank-detail change by phone.
  • Write a one-page incident plan and remove access the day staff leave.

Why small restaurants are worth attacking

Restaurants handle card payments, payroll, supplier invoices and guest data, often on a mix of devices bought over many years and run by busy managers. Most are small: 9 in 10 US restaurants have fewer than 50 employees[3], and 7 in 10 are single-unit operations[4]. That means no security team, shared passwords and a guest Wi-Fi network that sometimes shares a router with the POS.

Criminals know this. Internet crime reported to the FBI's Internet Crime Complaint Center reached $16.6 billion in losses in 2024, and business email compromise, where a criminal impersonates a supplier, a boss or a vendor to redirect payments, accounted for close to $2.8 billion of that from 21,442 complaints[2]. Restaurants pay many suppliers by invoice, which makes them a natural target.

Losses reported to the FBI's IC3 in 2024
Losses reported to the FBI's IC3 in 2024Comparison. All internet crime: 16.6 billion dollars; Business email compromise: 2.8 billion dollars.16.6 billion dollarsAll internet crimeAll internet crime: 16.6 billion dollars2.8 billion dollarsBusiness email compromiseBusiness email compromise: 2.8 billion dollarsLosses reported to the FBI's IC3 in 2024Comparison. All internet crime: 16.6 billion dollars; Business email compromise: 2.8 billion dollars.16.6 billion dollarsAll internet crimeAll internet crime: 16.6 billion dollars2.8 billion dollarsBusiness email compromiseBusiness email compromise: 2.8 billion dollars

Source: Nacha, 2025[2]

Show the data
ItemValue
All internet crime16.6 billion dollars
Business email compromise2.8 billion dollars

The good news is that a handful of basics stop most attacks on a small business. None of them needs an IT department.

Separate your networks

The single most important technical step is keeping guests, staff phones and smart devices off the network that runs payments and the kitchen. If a guest's infected laptop or a cheap camera can see your POS, an attacker can too.

  1. Draw what you have

    List every device: POS terminals, handhelds, kitchen printers and screens, office computer, cameras, music system, thermostats and guest Wi-Fi.

  2. Create separate networks

    At minimum: one for POS and kitchen, one for the office, one for guest Wi-Fi, and one for cameras and smart devices. Most business routers support this; your POS installer or a local IT provider can set it up.

  3. Lock down the router

    Change the default admin password, turn off remote admin unless you need it, and turn on automatic firmware updates.

  4. Rotate guest Wi-Fi passwords

    Change the guest password every few months and never reuse it for any staff network.

  5. Label everything

    Label each network port and cable, so a new device is never plugged into the POS network by mistake.

Never let staff connect personal phones to the POS network, and never give the POS network password to a vendor or contractor without changing it afterward.

Accounts: individual logins and MFA

Shared logins are the most common security gap in restaurants. When everyone uses "manager1" on the POS back office, you cannot tell who did what, and you cannot remove one person's access without changing it for everyone.

  • Give every manager and staff member their own login and PIN on the POS, scheduling, payroll and reservation tools.
  • Turn on multi-factor authentication (MFA) for email, banking, payroll, the POS back office, the reservation admin and delivery-app tablets.
  • Use a password manager for shared business accounts, so passwords are long and unique and can be changed in one place.
  • Keep the owner as the only person who can add admins, and keep a list of every admin account.

Not all MFA is equal. CISA ranks MFA methods from most to least secure: a security key, an authenticator app with number matching, an authenticator app with a one-time code, biometrics, and finally a text or email code, which it says to use only if stronger options are not available for that account[1]. For the owner's email and the bank, a security key or an authenticator app is worth the small setup effort.

Phishing and payment fraud

Most attacks on restaurants start with a message, not with hacking. Train staff to recognize the common patterns.

Common scams aimed at restaurants and how to stop them.
ScamWhat it looks likeThe defense
Supplier bank changeAn email from a "supplier" with new bank details for the next paymentCall the supplier on a number you already have, never one in the email, before changing any payment details
Fake boss requestA text or email from the "owner" asking a manager to buy gift cards or pay an urgent invoiceA standing rule: the owner never asks for gift cards or urgent payments by message
Fake POS or IT supportA caller says they are from your POS company and needs remote access or your loginHang up and call support on the number in your contract
Malicious reservation or catering requestAn email with an attachment or link "with event details"Open attachments only from known senders; ask new clients to paste details in the email
Delivery-app account takeoverA login code arrives that nobody requested, or menu prices changeMFA on delivery-app accounts and an alert to the owner for any bank or menu change
Fake review or listing threatsMessages threatening bad reviews unless you payDo not pay; report to the platform and keep the evidence

Write the bank-change rule down and give it to whoever pays invoices: no change to payment details without a phone call to a known number and a second person's approval. That single rule defeats most business email compromise.

Keep card data off your own systems

The safest card number is one you never see. Use payment terminals that encrypt the card at the point it is tapped or inserted, take phone payments through a secure payment link rather than writing card numbers down, and never store card numbers in reservation notes, spreadsheets or email. If a guest emails a card number for a deposit, delete it, reply asking them to use the payment link, and empty the deleted folder. These habits also make your annual card-security questionnaire much simpler; see PCI compliance for restaurants for how that works.

Train staff in ten minutes a quarter

Long security courses do not work in restaurants. A short talk at line-up, repeated each quarter and given to every new hire, does.

  • Never share your POS PIN or login, even with a manager. Managers have their own.
  • Nobody from the POS company, bank or "head office" will ask for your password. Hang up and tell a manager.
  • Do not plug unknown USB sticks or chargers into POS or office computers.
  • Do not open attachments in catering or reservation emails from senders you do not know; forward them to the manager.
  • If a screen asks you to install something or shows a strange warning, stop and tell a manager.
  • Report mistakes fast. Clicking a bad link is fixable when reported in minutes, and nobody gets in trouble for reporting.

The last point matters most. Staff who fear blame hide mistakes, and hidden mistakes become incidents.

Devices, updates and backups

  • Turn on automatic updates for computers, tablets, phones and routers. Replace devices that no longer receive security updates.
  • Use the POS vendor's supported hardware and let the vendor manage updates for terminals and handhelds.
  • Keep the office computer for office work: no personal browsing, games or downloads.
  • Back up the files that live outside your cloud systems, such as recipes, SOPs, contracts and accounting exports, to a cloud backup and one offline copy.
  • Lock the office and the network cabinet. Physical access is the easiest way in.

Staff turnover makes offboarding part of security. Restaurant employees averaged 25.1 hours a week in September 2026[5], a sign of how many part-time staff a restaurant cycles through. Each departure needs a quick, reliable removal of access.

The offboarding checklist

  1. Deactivate the person's POS login and PIN on their last day.
  2. Remove them from scheduling, payroll admin, reservations and delivery-app accounts.
  3. Change any shared password they knew, including Wi-Fi for staff networks and alarm codes.
  4. Collect keys, key cards and any company devices.
  5. Remove them from group chats used for operations, especially where codes or passwords were ever shared.

A one-page incident plan

  1. Know who to call

    List your POS support number, card processor, bank fraud line, IT helper and insurance broker on one page in the office.

  2. If cards may be compromised

    Call the processor first. Do not wipe devices; investigators may need them.

  3. If an account is taken over

    Reset the password from a clean device, turn on MFA, check for forwarding rules in email and review recent changes.

  4. If money was sent to a fraudster

    Call your bank immediately and ask them to try to recall the payment, then report it to IC3.

  5. Afterward

    Write down what happened and change the rule or setting that let it happen.

Example: a fictional bistro's bookkeeper receives an email from the produce supplier's address with new bank details. Following the rule, she calls the supplier on the number in the vendor file. The supplier knows nothing about it; their email had been compromised. The Example payment goes to the right account, and the bistro warns the supplier.

Frequently asked questions

Should guest Wi-Fi be separate from the POS network?

Yes. Put guests, staff phones and smart devices on separate networks from the POS, kitchen and office.

What is the best multi-factor authentication for a small business?

CISA ranks security keys first, then authenticator apps; text or email codes are the weakest option and best used only when nothing stronger is available[1].

How do restaurants get scammed by email?

Often by fake supplier emails changing bank details, or fake requests from the "owner". Business email compromise caused close to $2.8 billion in reported US losses in 2024[2].

What should I do if I think our POS was hacked?

Call your card processor and POS support immediately, do not wipe the devices, and follow their instructions.

References

  1. Cybersecurity and Infrastructure Security Agency (CISA) (2026). Require Multifactor Authentication (opens in a new tab) ↑

  2. Nacha (2025). FBI's IC3 Finds Almost $8.5 Billion Lost to Business Email Compromise in Last Three Years (opens in a new tab) ↑

  3. National Restaurant Association (2025). National Statistics: Restaurant Industry Facts at a Glance (opens in a new tab) ↑

  4. National Restaurant Association (2025). National Statistics: Restaurant Industry Facts at a Glance (opens in a new tab) ↑

  5. US Bureau of Labor Statistics (2026). Current Employment Statistics: series CES7072200002 (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo