Insights

26 Venues, 26 Systems, No IT Team: The Security Crisis Hiding in Plain Sight at Multi-Venue Hospitality Groups

How pub groups, hotel operators, and restaurant chains can fix the venue-by-venue cyber security gap that insurers are starting to notice — without hiring an IT person for every location.

A regional hotel in a 25-venue pub group had been running the same POS terminal for four years. Unpatched. No updates. No one watching.

The venue manager didn’t know it needed updating. Why would they? Their job was running the bar, not managing endpoint security. The group’s head office assumed someone at the venue was handling it. And the POS vendor — well, they send update notifications to whichever email address was on file when the terminal was first installed, back when the previous venue manager still worked there.

Nobody was negligent. Nobody was incompetent. The system just wasn’t built to catch this.

When the group finally ran a security audit, the trigger wasn’t a breach. It was a cyber insurance renewal questionnaire they couldn’t answer. The audit found three more venues in the same position. Different POS vendors. Different patch statuses. Same structural problem.

This isn’t hypothetical. It’s the reality of how most multi-venue hospitality groups operate in Australia: hospitality cyber security is managed venue by venue, or not at all. Not because anyone’s doing anything wrong. Because nobody’s doing anything centrally.

Why do multi-venue groups run like separate IT businesses?

Hospitality groups don’t grow the way other businesses grow.

A tech company opens a new office and extends its existing IT infrastructure. A retailer opens a new store and plugs it into the same ERP and POS platform the other stores use.

A hospitality group acquires a pub. That pub already has a POS system. It already has an internet connection. It already has a relationship with a local IT shop — or more commonly, the venue manager’s nephew who “knows computers.” The group inherits all of it.

Do this five, ten, twenty times and you have a portfolio of venues that look like one business on paper but operate like twenty separate IT environments underneath.

  • A 26-venue Sydney pub group might run four or five different POS platforms.
  • A 15-venue fund-managed hotel portfolio might have ten different internet providers.
  • A 30-venue family pub empire might have patch cycles that range from “last week” to “when the terminal was installed.”

The problem isn’t that any individual venue is badly managed. It’s that nobody manages them as a portfolio. Single-site businesses have one set of security problems. Multi-venue operators don’t have N sets. The complexity is multiplicative. Each venue adds not just its own risk surface, but new combinations of incompatible systems, undocumented configurations, and invisible gaps.

And those gaps are starting to matter.

Gap 1: POS security, venue by venue

Every venue processes card payments. That means every venue has a POS terminal. And in most groups, every venue has a different POS terminal.

  • Some run Square.
  • Some run Toast.
  • Some run Zonal or Micros or a legacy system the vendor stopped supporting three years ago.

Each platform has its own update cycle, its own security patches, its own MFA requirements.

The gap isn’t that these systems are insecure. It’s that nobody has a single dashboard showing which venues are patched, which are compliant, and which are running end-of-life hardware.

POS terminal patching status across venues in a multi-venue hospitality group

This is where the breach data gets sharp. According to VikingCloud’s 2025 State of Hospitality Cyber Report, payment and POS systems are named as the top cyber risk by 72% of hotel IT and security executives. Trustwave SpiderLabs’ 2025 Risk Radar report on the hospitality sector found the same pattern in the wild: POS and property-management systems exploited for chargeback fraud. Not the corporate network. Not the booking system. The terminal where customers tap their cards.

A single unpatched POS terminal at a single venue can compromise cardholder data across the entire group. Once an attacker is inside the terminal, they’re inside the network. And if that network connects back to head office, the blast radius expands to every venue on the same VPN.

This isn’t speculation. It’s the attack pattern behind most hospitality breaches globally: find the weakest POS, pivot laterally, exfiltrate quietly.

The fix isn’t complicated:

  • Standardise the security baseline across all POS endpoints.
  • Centralise patching visibility.
  • Know, without having to call each venue manager, which terminals are current and which aren’t.

Most hospitality groups can’t do this today because they don’t have a single entity responsible for IT across venues.

Gap 2: PCI compliance at scale across every venue

PCI DSS compliance is paperwork-heavy at the best of times. Now multiply it by the number of venues in your portfolio.

And the bar has moved. PCI DSS v4.0.1 has been mandatory since 31 March 2025, including MFA for all access to the cardholder data environment.

An SAQ D (the self-assessment questionnaire most hospitality operators need) requires evidence collection for every location that processes card payments. For a 30-venue group, that’s:

  • 30 sets of firewall configurations.
  • 30 sets of access logs.
  • 30 sets of patching evidence.

Every quarter. Every year.

Most hospitality operators aren’t failing PCI compliance because their security is weak. They’re failing because they can’t produce the documentation for every venue on demand.

The evidence base is largely the same one the ASD Essential 8 checklist maps out, so build it once and reuse it for both.

This gets worse when institutional oversight is involved. A hospitality group owned by a fund or a listed parent company doesn’t just face PCI compliance. It faces investor-grade reporting requirements. A compliance gap at one venue becomes a governance gap at the portfolio level. The kind of thing that shows up in board papers, audit committee meetings, and in the worst case, ASX disclosure obligations.

And for groups with gaming machines, the compliance stack doubles. NSW gaming regulations impose their own security and audit requirements. A venue with 30 poker machines answers to both the PCI Security Standards Council and the state gaming regulator. Two audits. Two sets of consequences for failure.

Gap 3: The regional IT desert

Regional markets are Australia’s largest accommodation segment — 3,583 properties and 118,758 rooms in the Horwath HTL Australia Hotel & Chains 2026 data — yet chain penetration sits at 28% in regional markets against 77% in city centres. That’s pubs in Maitland, hotels in Coffs Harbour, taverns in Nelson Bay. Venues that are hours from the nearest city but still run POS terminals, booking systems, and payment networks that need maintenance.

Quality IT support in regional Australia is scarce. When a POS terminal crashes during Friday dinner service at a regional pub, the venue manager doesn’t call a helpdesk. They become the helpdesk. They spend forty minutes on the phone with the POS vendor, troubleshooting while tables wait and orders stack up.

Every minute a venue manager spends on IT is a minute they’re not managing the guest experience. Over a year, across seven regional venues, this adds up to hundreds of hours of lost operational focus. And it’s happening at the worst possible moments. Peak service, not quiet Tuesday afternoons.

The structural problem is the same one, just geographically amplified: there’s no central IT function. Each regional venue is an island, and the water between them is wide.

Gap 4: Insurance is waking up

Hospitality venues have exactly the risk profile cyber insurers are now scrutinising hardest:

  • Cardholder data.
  • High foot traffic generating PII.
  • Online booking portals.
  • Event ticketing systems.
  • High staff turnover creating identity governance gaps.

Insurers are asking hospitality operators the same questions they’ve been asking retailers for years:

  • Do you have MFA on POS backends?
  • EDR on venue endpoints?
  • A documented patching cadence you can prove?

According to BizCover, Australian small-business cyber insurance uptake is up 85% over three years and 50% year on year. And the losses behind that are getting bigger: the ASD’s Annual Cyber Threat Report 2024–25 puts the average self-reported cybercrime cost at A$80,850 per business, up 50% year on year, and around A$202,700 for large businesses, up 219%. Premiums are following. And the insurers aren’t asking politely anymore. They’re making coverage conditional on answering those questions.

The disconnect is cultural. Most hospitality operators don’t think of themselves as technology businesses. They think of themselves as hospitality businesses, and IT is a cost centre they tolerate. When the insurance renewal lands with a 12-page cyber security questionnaire, the instinct is to fill it out as best they can and hope the broker smooths it over.

In 2020, insurers mostly took the broker’s word for it. It doesn’t work now. Insurers have their own breach data, and hospitality is showing up as a growth sector for claims. The questionnaire isn’t a formality. It’s underwriting.

For some venues, the insurance profile is even sharper. A premium restaurant operating inside the Sydney Opera House has a fundamentally different risk profile from a suburban pub. A breach at an iconic, government-adjacent venue isn’t just a financial event. It’s a reputational one, with media coverage built in. Insurers price that risk accordingly.

Gap 5: High turnover, identity chaos

Hospitality has the highest staff turnover of any Australian sector — around 15.5% a year at industry level, according to Pitcher Partners, and far higher once casual and seasonal venue staff are counted. Every departure should trigger access revocation:

  • POS login.
  • Email.
  • Booking system.
  • Rostering platform.
  • Building access.
  • Maybe even the venue’s shared Dropbox of supplier contacts.

Every new hire needs onboarding across the same systems.

Manual processes don’t scale across ten venues, let alone thirty.

Australia’s own data shows what that costs. The COSBOA/Cyber Wardens 2026 Small Business Cyber Security Pulse Check found hospitality is the slowest sector on the basics: 47% of hospitality businesses use unique passwords, 37% have cloud backups, and only about one in three have MFA on email.

The security risk is obvious: ex-staff with active credentials. The worst case is a disgruntled former employee who still has POS admin access. Rare, but not hypothetical. The more common version is quieter: dormant accounts accumulating across systems, nobody auditing who has access to what, the credential surface growing with every hire and barely shrinking with every departure.

This is a solved problem. Automated identity management via M365 handles onboarding and offboarding at scale. New hires get the right access on day one. Departing staff lose everything on their last day. Microsoft automates the provisioning; conditional access policies enforce it.

But hospitality operators rarely frame hiring and firing as an IT problem. It’s an HR problem, a payroll problem, a roster problem. The credentials just happen.

It’s not technology. It’s structure.

None of these five gaps exist because someone made a bad technology decision.

  • The POS vendor didn’t ship insecure software — the patching cadence just fell through the cracks because nobody owned it centrally.
  • The venue manager didn’t ignore PCI compliance — they just couldn’t produce documentation for a terminal they didn’t know needed documenting.
  • The regional pub didn’t choose to be underserved for IT support — there just isn’t any within a two-hour drive.
  • The operator didn’t fail the insurance questionnaire — the questionnaire asked about things they’d never had to think about before.
  • The HR manager didn’t leave credentials active — there just wasn’t a process that connected a staff departure in the payroll system to an access revocation in the POS system.

These aren’t the result of bad decisions. They’re the result of a structural reality: when every venue runs independently, IT security is fragmented by design. The solution isn’t to buy better software for each venue. It’s to centralise IT management across all of them.

Centralised IT for a multi-venue hospitality group doesn’t mean hiring a CIO and a twenty-person team. It means having one partner who sees the full picture. Every POS terminal, every network, every patch status, every credential. Managed as a single environment with a single security baseline.

One partner. One contract. One escalation path. One fixed monthly price that covers every venue.

How does Planet6 do it?

We run hospitality IT support for Australian groups the same way we run it for 200-employee retailers and national logistics firms: fixed monthly pricing, onshore support, cyber security built into the base service.

For multi-venue hospitality operators, that means:

  • Fixed pricing covers all venues. No per-venue surcharges. No surprise bills when a POS terminal needs replacement. No extra charges because the regional pub had an outage at 8pm on a Saturday. One monthly line item for the entire portfolio.
  • ASD Essential 8 and PCI DSS compliance are part of the service. Not a separate audit project, not an annual scramble, not a consultancy engagement that bills by the hour. Our security baseline (MFA, patching, endpoint detection, access control) is built into the monthly retainer and documented continuously — that is what managed IT means in practice. When your insurer sends that questionnaire, you have the answers ready.
  • Onshore support, same timezone. Our team is in Docklands, Victoria. We work Australian business hours, we speak the same language, and we can put someone on-site at a metro venue same day. For regional venues, we provide remote-first support with the same priority: no metro premium, no regional penalty.
  • Automated identity management across all venues. Staff onboarding and offboarding runs through M365, so credentials are provisioned on day one and revoked on the last day, across every system. No dormant accounts. No ex-staff with POS access. No manual spreadsheets tracking who has which login.
  • Proactive POS endpoint management. We maintain patching cadences, EDR coverage, and vendor liaison for every POS terminal in your portfolio. You get a single dashboard showing the patch status of every venue, updated in real time, without calling a single venue manager.
  • Customer proof. Australian Venue Co., a hospitality operator with venues across the country, runs this model today. The architecture works.

How many IT vendors are managing your venues right now?

Most multi-venue hospitality operators don’t know the answer to that question off the top of their head. It’s usually more than they think:

  • Some venues have a local IT shop.
  • Others have the POS vendor’s support contract.
  • A few have the owner’s friend who set up the WiFi in 2019 and still has the admin password.

Every one of those relationships is a gap between what’s happening at the venue and what the group knows about.

If you’re running five or more venues and you don’t have a single IT partner managing security across all of them, the gaps are already there. The question isn’t whether they exist. It’s whether you find them before an insurer, an auditor, or an attacker does.

Book a 30-minute hospitality IT assessment. We’ll look at your venue portfolio, map the current IT landscape, and show you what centralised management would look like. No obligation. No pitch deck. Just an honest conversation about where you are and where the gaps sit.

Book your assessment →

Hospitality cyber security: frequently asked questions

How do I find out which venues are actually patched right now?

You don’t have to call each venue manager. Centralised patching visibility puts every POS terminal on a single dashboard, updated in real time, so you can see which venues are current, which are compliant, and which are running end-of-life hardware — without a single phone call.

Does centralising IT mean replacing my current POS vendor and the local shops?

Not necessarily. It means one partner manages the security baseline and the relationships, including vendor liaison for every POS terminal, so you get one contract and one escalation path instead of a patchwork of local shops and support contracts. The point is that nothing falls through the gaps between them.

We operate regionally — can you actually support venues hours from a city?

Yes. Regional venues get remote-first support with the same priority as metro sites, with no metro premium and no regional penalty. A Friday-night POS crash at a regional pub gets the same response as one in the city — instead of the venue manager becoming the helpdesk mid-service.

What do I say to my insurer when the cyber questionnaire arrives?

You’ll have the answers ready. MFA, patching, endpoint detection and access control are built into the monthly service and documented continuously, so the questions about MFA on POS backends, EDR on endpoints, and a provable patching cadence are already answered before the questionnaire lands.

What does this cost across all our venues?

One fixed monthly price that covers every venue. No per-venue surcharges, no surprise bills when a terminal needs replacing, no extra charge for a Saturday-night outage at a regional pub. A single monthly line item for the entire portfolio.

Our group has gaming machines — does that change the compliance picture?

It doubles it. A venue with poker machines answers to both the PCI Security Standards Council and the state gaming regulator — two audits, two sets of consequences for failure. Centralised documentation means you can produce the evidence for both on demand, rather than scrambling venue by venue.

For more on how Planet6 builds security into every engagement: see our ASD Essential 8 compliance approach and our fixed-price IT support.