Techbanq

Hospitality · security

A hotel is a data business that never closes

Every night a hotel holds card numbers, scanned passports and the run of its own building systems, behind a front desk that talks to strangers for a living and a network its guests share. Attackers understand that combination well; this guide explains it in the hotel’s own terms, and where defence actually starts.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

Workstation showing terminal output during a security review

Cybersecurity credentials

  • National Cybersecurity Authority, Saudi Arabia

    NCA registration

    Registered cybersecurity service provider

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The prize

Four things a criminal can sell out of a hotel

A property is not attacked at random. Each of these has a buyer, and knowing which ones your hotel holds — and where — is the first honest security exercise.

  1. 01

    Cards that sit on file for weeks

    A hotel takes a card at booking, holds it through the stay and charges it at checkout — sometimes reading it aloud over the phone in between. That long window, multiplied across every reservation, is why hospitality has always drawn payment-data theft.

  2. 02

    Passports scanned at every check-in

    Identity documents are collected as a legal duty and accumulate quietly — in the PMS, in scanner folders, in email threads. A folder of passport scans is raw material for identity fraud, and it is often protected like an ordinary shared drive.

  3. 03

    Loyalty balances that spend like cash

    Points buy rooms and flights, guests check those accounts rarely, and the passwords are reused from other breached sites. Taken over, an account is drained through bookings that look legitimate — a theft many programmes only hear about from the guest.

  4. 04

    The hotel’s own name and inbox

    A compromised hotel mailbox writes convincing emails to guests, suppliers and banks — a deposit request here, a changed account number there. The attacker is not stealing data at that point; they are spending your credibility.

The soft spots

Where a property is soft, and what each gap exposes

The routes in are mundane. What decides the damage is whether the middle of this picture — how the network is split and who can reach what — is designed or merely accumulated.

A surface diagram: four soft spots — front-desk workstations, guest wifi bleeding into operations, third-party connections, and convincing calls or emails — converge on a control of segmentation and least access, producing an isolated payment path, contained identity data and incidents that stay small.

  • Front-desk workstations

    Open all night, shared across shifts, browsing the web beside the PMS.

  • Guest wifi bleeding into operations

    One flat network where a laptop in room 412 can see the printers, the cameras, sometimes the PMS.

  • Third-party connections

    Booking engines, channel managers, spa and POS vendors — each with credentials, each a door someone else holds a key to.

  • A convincing phone call or email

    The caller claiming to be the OTA, the invoice with a new bank account — aimed at a desk trained to be helpful.

What we do

Segmentation and least access

Guest, operations and payment traffic separated; every person and vendor holding only the access their job needs, under their own name.

  • A payment path attackers cannot browse to

    Card flows isolated from the network guests and office laptops share.

  • Identity data with a short reach

    Passport scans stored in one governed place, not scattered across drives and inboxes.

  • A bad day that stays small

    One compromised machine or vendor account meets a boundary instead of the whole property.

None of this requires exotic technology. It requires the network to be drawn on purpose.

People first

The desk habits that outweigh any security product

Most successful attacks on hotels begin with a person, not a firewall, and the person is usually doing their job well: being helpful to a caller, acting fast on an email marked urgent. The defence is a handful of habits that survive a busy lobby. Card numbers are never written into notes, chats or paper — payment happens in the terminal or the engine’s own page, full stop. A caller claiming to be the bank, the OTA or corporate IT gets a call back on the number the hotel already has, not the one they offer. A supplier’s changed bank account is confirmed by phone with a known contact before a single riyal moves.

Two more habits close most of the remainder. Every member of staff signs in as themselves — a shared front-desk login means no one can ever say who did what, and a leaver’s access quietly outlives them. And screens lock when the desk steps away, because a lobby workstation is the one computer in the building that strangers stand next to all day. These cost training and insistence, not budget, and they blunt the attacks that actually arrive far more often than the exotic ones do.

When it happens

Handling an incident while the lobby stays open

A hotel cannot close to investigate. Readiness means the property can lose a system at 2 a.m. and still check guests in, cut keys and take payment while the problem is contained.

STAGE 01

Decide the authority before the night it is needed

Name in advance who may disconnect a system, whom the night manager calls first, and what they may decide alone. An incident at 2 a.m. runs on the plan that exists, not the one being drafted during it. A night shift that acts in minutes instead of waiting for the morning.

STAGE 02

Keep the guest moving on paper

A printed arrivals list, a manual key procedure and a standalone payment terminal, rehearsed once a year, let the desk run degraded for hours. An outage guests barely notice is a different event from one that fills the lobby. Check-in, keys and payment that survive the loss of a system.

STAGE 03

Contain and keep the evidence

Isolate the affected machine or account rather than wiping it — the instinct to reinstall and move on destroys exactly what investigators, insurers and card processors will ask for. A contained system and an intact record of what happened.

STAGE 04

Tell the truth on schedule

If guest data is involved, obligations to guests, regulators and payment partners come with clocks attached. Prepared contact lists and draft wording turn a legal scramble into a checklist, and guests forgive an honest notice far more readily than a discovered silence. Notifications that happen by plan, not by panic.

Our role

What we secure in a property and what the GM still owns

  1. 01

    An exposure review in the hotel’s language

    We assess the property as this guide reads it — what it holds, which doors are open, which vendor connections exist — and report in terms a GM can act on, ranked by return rather than by fear.

  2. 02

    The network drawn on purpose

    We design and implement the segmentation between guest, operations and payment traffic, and the access model behind it, working with the property’s existing equipment wherever it is capable of the job.

  3. 03

    Readiness the night shift can run

    We build the incident plan around a 24/7 desk — the authority chart, the paper fallbacks, the notification drafts — and rehearse it with the people who will actually be on shift.

The standards of hospitality — how guests are spoken to, what the desk promises, how an apology is made — stay entirely the hotel’s; we make sure a bad night stays a technical event instead of becoming the guest’s story about your property.

Common questions

What buyers ask

We are one small property, not a chain. Would anyone really bother attacking us?+

Yes, because most attacks are not aimed at you in particular. Automated scanning finds an exposed system or a reused password without knowing or caring whose it is, and phishing is sent by the thousand. A small property holds the same categories of value as a large one — cards, identity documents, a trusted name — with a fraction of the defences, which from the attacker’s side is not obscurity but a better ratio. The realistic goal for a small hotel is not to repel a determined expert; it is to stop being the easiest target on the street, which the unglamorous basics largely achieve.

Our payments already run through the booking engine and the bank. What is left to protect?+

The paths around the engine. A compliant payment page protects the transaction inside it — not the card number a caller reads to the desk, the one written in a booking note, or the terminal sitting on a network guests can reach. It also does nothing for the rest of what the hotel holds: passport scans, loyalty accounts, and a mailbox that can be turned against your suppliers and guests. Outsourced payment processing is genuinely valuable; treating it as the whole of security is how the other doors stay open.

Is guest wifi always a risk, or can it be made safe to offer?+

It can be made safe to offer; what makes it dangerous is sharing. The risk is almost never the guest network existing — it is the guest network being the same network the PMS, the cameras, the office machines and the payment terminals sit on, so one curious or compromised device in a guest room can reach the property’s operational heart. Properly segmented, with guest traffic walled off from operations and payments, guest wifi is a service like hot water. The test is simple to commission: from a device on the guest network, can anything operational be seen at all. The answer should be no, and it is worth actually checking rather than assuming.

What can a hotel improve this quarter without buying anything new?+

Four things, all discipline. Give every staff member their own login and remove the shared desk account, then close the accounts of everyone who has left — most properties find at least one. Adopt the call-back rule: any request touching money or access, from any caller or email, is verified on a number the hotel already holds. Find every place passport scans and card numbers are stored outside the systems meant to hold them — scanner folders, inboxes, spreadsheets — and delete or move them. And write the one-page night plan: who the shift calls, what they may switch off, and where the paper check-in procedure lives. None of this needs a purchase order, and together it removes the openings most real incidents use.

See your exposure first

A plain-language exposure review of one property — what it holds, which doors are open, and the three changes with the best return — readable by a GM, not only by IT.

Start the conversation