After the Expedia Supplier Breach: An Integration Access Checklist for Hotel Tech Vendors

After the Expedia Supplier Breach: An Integration Access Checklist for Hotel Tech Vendors

Published on:

Published on:

Reading time:

Reading time:

8

8

min read

min read

Table of contents:

TL;DR

  • Expedia confirmed on 12 November 2026 that attackers reached it through a compromised third-party data platform provider; n0n's claim of about 830 million loyalty records remains unconfirmed.

  • Wiz found attackers used a data vendor's credentials to assume customer roles that were mostly no longer in use but still trusted the vendor.

  • Hotel tech vendors hold the same kind of standing access to PMS, channel and guest data, so access that outlives a contract is a risk and a sales objection.

  • Audit the access you hold, add a dated revocation step to offboarding, list your sub-processors, and put it all in your security pack.

On 12 November 2026 Expedia Group confirmed to Skift that attackers reached its systems through a compromised third-party data platform provider, in a supply chain attack that also hit other companies. The confirmation followed claims by a new extortion group called n0n that it had taken Expedia data. Expedia says its platforms remain safe for travellers and partners, and its investigation is ongoing.

This is not a post about Expedia's security. It is about the position every hotel tech vendor is in: you are a third party holding trusted access to someone else's data. A PMS integration, a channel manager connection, a guest messaging tool reading reservations, a revenue system pulling history. Each one is a door your customer opened for you. The question hotel buyers will ask next is simple: who closes it, and when?

Integration access offboarding is the set of steps that removes a vendor's credentials, roles and data paths when an integration, a property or a whole contract ends, so that access does not outlive the relationship.

What is confirmed and what is only claimed

Keep the facts straight before you mention this story to a single prospect. Fear selling on an unfinished investigation will cost you trust with IT buyers who read the same news.

Item

Status

Source

Attack came through a third-party data platform provider

Confirmed by Expedia

Skift, 12 November

Supplier's name

Not named by Expedia

Morning Overview, 15 November

About 830 million loyalty records from 35 programmes, 58 million traveller profiles, 333 million account records

Claimed by n0n, not confirmed by Expedia

Forbes and Security Affairs

500,000 guest records with accommodation details

Claimed by n0n

Security Affairs

Route was a stolen Qubole vendor key

Reported by Forbes citing Wiz and Sentra; not confirmed by Expedia

Forbes, 13 November

Forbes reported the alleged haul includes more than 830 million loyalty programme records, 58 million traveller profiles and over 333 million consumer account and credential records. Security Affairs adds a claimed 500,000 guest records containing accommodation details, which is the line hotel operators will notice. Morning Overview is careful to point out that neither Expedia nor the researchers have publicly tied the Qubole campaign to Expedia, and that until Expedia publishes findings the 830 million figure remains an extortion group's claim.

The lesson that applies to hotel tech: access nobody switched off

The useful part for vendors is the separate research from Wiz. In a 9 November write-up, Wiz said that between 14 and 26 October 2026 a threat actor used credentials from an AWS account associated with Qubole, a cloud data platform, to assume roles that customers had created to trust Qubole. Inside those environments it collected secrets and downloaded data from storage buckets, in some cases whole buckets.

The striking detail is why it worked. Wiz wrote that most of the roles the attacker assumed were not otherwise in use, and in a majority of affected environments the attacker's requests were the only activity from the vendor account that month. The trust policies were still in place, so the requests succeeded. Wiz told The Register that many organisations left trust policies active even after deprecating the platform.

Translate that into hotels. A hotel group drops a guest messaging tool, but the API key in the PMS stays live. A property leaves a management company, but the old revenue system still pulls its reservation feed. A pilot ends, but the sandbox credentials point at production data. None of this is exotic. It is what happens when nobody owns the last step of a contract.

The checklist: what hotel tech vendors should be able to say yes to

Use this as an internal audit first and a sales asset second. Every item you can tick is a sentence for your security pack. Every item you cannot tick is a risk a prospect's IT director will eventually find.

Part 1: Access you hold today

  • ☐ We keep a live register of every hotel, group and integration where we hold credentials, tokens or roles.

  • ☐ Each entry names the scope we hold (read reservations, write rates, read guest profiles) and the date it was last used.

  • ☐ We use short-lived tokens or scoped keys rather than shared, long-lived master credentials wherever the partner system allows it.

  • ☐ We can tell a customer, within one working day, exactly which of their systems we can reach.

Wiz's advice to software providers is blunt: the principals your customers trust are effectively credentials to every customer environment at once. It recommends assuming customer roles from workload identities with short-lived credentials, restricting where those identities can be used and publishing your network ranges so customers can pin their trust policies. Hotel tech is rarely built on cross-account cloud roles, but the principle holds for PMS API keys and OAuth grants.

Part 2: Offboarding when a contract or property ends

  • ☐ Our termination process includes a written step that revokes our own access, not just the hotel's user logins.

  • ☐ We send the customer a dated confirmation that access has been removed and what data we hold or have deleted.

  • ☐ When a single property leaves a group contract, we remove access for that property without waiting for the group renewal.

  • ☐ Pilots and trials have an end date in the system, and access expires automatically if nobody extends it.

This is the part almost no hotel tech vendor puts in a proposal, and it is the part the Qubole research points at. Churn is uncomfortable, so teams avoid designing for it. Yet a clean exit is exactly what a cautious buyer wants to see before they let you in. Our post on hotel data privacy myths vendors repeat covers why deletion and retention promises need to match what your systems actually do.

Part 3: Your own suppliers

  • ☐ We list every sub-processor that touches hotel or guest data, including analytics, data warehouse and AI providers.

  • ☐ We review that list at least once a year and remove tools we no longer use, along with their access.

  • ☐ We can show a hotel the list on request without a week of internal digging.

Expedia's incident, as confirmed, came through a supplier of Expedia, not through Expedia's own product. Your hotel customers sit at the end of the same chain. If your data warehouse vendor is compromised, your customer's guest data is part of the blast radius, and the hotel's contract is with you.

Part 4: What you can prove

  • ☐ We log access to customer data and can produce those logs for a given hotel and date range.

  • ☐ We have an incident notice template and a named person who sends it.

  • ☐ Our answers to the standard questionnaire on access, offboarding and sub-processors are written once, approved and reused.

Logging matters more than it sounds. Wiz noted that in several affected environments, missing logs meant responders could not see which objects the attacker read. A vendor that can say exactly what was and was not touched has a far easier conversation after any incident.

How to use this in sales without fear selling

Three rules keep this on the right side of credibility.

  1. Do not name Expedia, Qubole or any other company in outbound. Say that supply chain access is in the news and that you have documented how you handle it.

  2. Lead with your offboarding process, not your security certificate. Most vendors can say they encrypt data; few can show a dated access removal confirmation.

  3. Put the checklist in your security pack and send it before the IT review, not after.

If you already prepare for group deals with our security questionnaire readiness guide, add a section called access lifecycle that covers onboarding, review and removal. If you are weighing a formal attestation, the trade-offs are in should hotel software get SOC 2 now. A clean offboarding story will not replace an audit, but it answers the question buyers ask this month.

There is a positioning angle too. Integrations are a reason hotels buy, as we argue in why integrations sell hotel software. The same integrations are now a reason IT directors slow deals down. The vendor who treats integration access as something with a beginning and an end turns a security objection into evidence of maturity. That belongs in the trust layer of your go to market system, covered in the pillar on hotel tech GTM strategy.

What to do this week

  • Run Part 1 of the checklist against your top 20 accounts and count any access you hold that has not been used in 90 days.

  • Add an access removal step and a confirmation email to your churn and cancellation workflow.

  • Brief sales and customer success on the confirmed facts above so nobody repeats the unverified numbers as fact.

  • Write one paragraph on access lifecycle for your security pack and website trust page.

If you want a second pair of eyes on where trust questions are stalling your deals, from first call to IT review, book a free GTM leak audit and we will map it with you.

Frequently Asked Questions

What did Expedia confirm about the November 2026 cyberattack?

Are the 830 million record figures confirmed?

What is integration access offboarding?

Why does the Qubole research matter to hotel tech vendors?

How should a hotel tech vendor mention this in sales?

FREE RESOURCES

Free GTM resources for hotel tech vendors

The Hotel Deal Kit, the Hotel Software Pricing Index, the 12-point leak audit and the complete GTM guide, all in one place.

See the resources

Where is your revenue actually leaking?

Twelve questions, about twenty minutes, on your own funnel. The same audit I run on day one of an engagement. No call required.

Get the free leak audit

Unlock Hotelier Demand

Stop Guessing What Hoteliers Want.

I Know What They Really Need.

Let’s engineer your hotel tech into the backbone of every hotelier’s workflow.

Make It Hotelier-Ready

Let’s transform your software into a revenue magnet in 90 days.

Unlock Hotelier Demand

Stop Guessing What Hoteliers Want.

I Know What They Really Need.

Let’s engineer your hotel tech into the backbone of every hotelier’s workflow.

Make It Hotelier-Ready

Let’s transform your software into a revenue magnet in 90 days.