Skip to main content
Industry security guideReviewed

Hospitality cyber security: follow a guest's details from the booking to the refund

For owners, managers and technical leads of accommodation, restaurant and event businesses.

This guide follows a guest through direct bookings, channel-manager handoffs, modification links, group rooming lists, table reservations, event enquiries, gift cards and refunds, shows where each step can put a guest's details within reach of the wrong person, and gives you a guest-journey checklist of test cases to run on your own site with invented guests.

Guest-journey checklist for accommodation, restaurant and event businesses

Twenty-six rows follow a guest through an accommodation, restaurant or event business, grouped by step: before testing (B), accommodation, including channel-manager handoffs, modification links and group rooming lists (A), restaurant reservations (R), events (E), gift cards (G), refunds (M), payment page scripts (S), and change, clean-up and evidence (Z). Each row runs left to right through the details the step carries, who should and should not reach them, the test case, the expected result, the evidence to keep and, on the rows that name one, the duty or request it may relate to, the row's limits, and its references.

How to use it

Rows B1 and B2 come first. B1, A3, S2, Z1 and Z3 are read only; B2 reads settings and then creates the test identities, S1 loads pages without typing into payment fields or submitting anything, and Z2 deletes only records carrying the run's marker. Every other row runs on your own site, on a staging copy where one exists, or in a vendor's documented test mode only within the vendor's written answer that B1 records, using only invented guests (guest-a, guest-b), invented organisers (org-a, org-b) and staff test accounts, only inboxes and phone numbers the business controls, a marker such as STAYTEST-1115 in every test record, never a real card, the small number of requests printed on each row, and no load. A response showing a real person's details ends the row: stop and record it. Links that work for whoever holds them are opened only for the invented records and never pasted into the evidence, and no password, key or signing secret goes into any record. Swap in your own names for the examples, mark any step the business does not run as not applicable, and write the expected result before sending anything. Apart from WSTG-BUSL-10, taken from the edition the OWASP site labels Latest and read on 15 November 2026, WSTG ids are from v4.2; ASVS ids are from 5.0.

26 rows

Guest-journey checklist for accommodation, restaurant and event businesses

Row and stepDetails involvedWho should reach them, and who should notTest caseExpected resultEvidence to keep, and the duty or request it may relate toLimits of this rowReferences
B1. Before testing: systems, owners, terms and the questions settled business by businessNone. This row reads documents and asks questions.The owner decides what is tested. Each vendor (booking engine, channel manager, property or reservation system, event or invoicing tool, gift card service, payment provider) and the host sets the terms for its own system. For questions on compliance validation, the PCI SSC points merchants to their acquirer or payment brand. The business's own privacy adviser answers whether the Privacy Act covers it.Read only. List every system a later row touches, who runs it, and which of its pages sit on the business's own domain. For each vendor and the host, read its own terms on security testing and on test modes or test properties, note the date, and ask in writing where the terms leave doubt. Ask the acquirer (merchant bank) or payment brand in writing how the business's PCI DSS validation is set, including whether Requirements 6.4.3 and 11.6.1 apply to a booking flow that hands the card to a provider's page or fields, and ask the payment provider which parts of card handling it takes on. Ask your adviser whether, and how, the Privacy Act covers the business.Every system has a dated answer before the first row that sends a request, and any system whose terms leave doubt is left out of the run until its vendor replies.Each terms page with its address and the date read, each written answer, and the answers on card handling and privacy coverage. May relate to: compliance validation questions, which the PCI SSC's Merchant Resources FAQ directs to the acquirer (merchant bank) or payment brand; and the coverage provisions of the Privacy Act 1988 in sections 6(1), 6C and 6D.Read only. No request goes to the site or to any vendor's system.PCI SSC Merchant Resources FAQ; Privacy Act 1988, Compilation No. 104. What each vendor permits is in its own terms, not on this page.
B2. Before testing: confirm the staging copy and create invented guestsWhatever the staging copy holds. A copy cloned from the live site can hold real guests' bookings and live connections.Settings on the copy are changed only by the person who manages it. This row reads them and then adds the run's test identities.Read only, then create identities. Check that the copy is the business's own and is not the live site. Read the mode of each booking, reservation, gift card and payment connection on the copy, and where each email and text message route ends. Then create invented guests guest-a and guest-b and invented organisers org-a and org-b, each with an inbox and a phone number the business controls; a staff test account for each role the rows name, such as reservations, front office, restaurant host, events coordinator and manager; and the marker STAYTEST-1115, or your own, in every name and note.Every connection on the copy in a test mode its vendor documents or pointing at a test account, every message route ending at an inbox or number the business controls, and the live site in live mode. If any reading says otherwise, stop: changing a mode or a connection is a task for whoever manages it, not a step in this checklist.Each mode and route as read, with the date and the reader, and the list of test identities.Reading only, except for adding the invented guests, organisers and staff test accounts on the staging copy, with any welcome email or text going to an inbox or number the business controls, and no load. If a mode is shown only on a screen that also displays keys, get the reading from whoever manages that integration. Real guests' records on the copy stay unopened: rows that list or export records then end at their read-only part, and rows A1 and G2 leave out their neighbouring references and codes. If any screen shows a real guest's details, stop and record where.This page's own set-up.
A1. Accommodation, direct bookings: confirmation, lookup and invoiceGuest name, email address, phone number, arrival and departure dates, adults and children, room and rate, special requests, and the payment or deposit summary the site shows, on the confirmation page, the booking lookup and the invoice or receipt.The guest who booked, and reservations and front office staff. Not another guest, and not a visitor with no session or link.As guest-a and guest-b, make one test booking each through the business's own booking page, and note each address that shows guest-a's: the confirmation page, any booking lookup (by reference with a surname or email address), and the invoice or receipt file. As guest-b, request each address with guest-a's booking reference or id in place of guest-b's own, then send each request again with no session. Compare guest-a's and guest-b's references to see whether they run in sequence and, only where B2 found no real guests' records on the copy, try the references either side of guest-a's once each in the lookup.Every request refused with the same response the site gives for a booking that does not exist, no response holding any of guest-a's details, and a lookup that answers only when the reference and the second detail belong to the same booking.Each request and response, marked with the identity and session used, with names, contact details and tokens redacted, and whether references are sequential. May relate to: APP 11.1 of the Privacy Act 1988 and the steps it concerns, if the Act covers the business.Your own booking page on the staging copy, or the booking engine's documented test mode within the answer B1 records. guest-a and guest-b only, one test booking each, each request once and two neighbouring references at most, confirmations only to inboxes the business controls, never a real card, no load. If any response shows a real guest's details, stop, record the request and tell the owner.WSTG v4.2 WSTG-ATHZ-04 and WSTG-ATHZ-02; ASVS 5.0 v5.0.0-8.2.2; OWASP IDOR Prevention Cheat Sheet.
A2. Accommodation, direct bookings: rates, held rooms and the last roomRoom type, dates, occupancy, the rate and any promotion code, and the number of rooms left to sell.The booking system sets the rate and the availability. The guest chooses a room, dates and occupancy only.As guest-a, watch the booking requests in the browser's developer tools. If any request carries a nightly rate, a total or a price per extra guest, including in a hidden field, change one value once and complete the test booking. Then, on a test room type with one room left on one night, have guest-a and guest-b submit three bookings for it at nearly the same moment, once. Where the site holds a room during checkout, start one hold as guest-a, leave it unpaid, and check when the room returns to sale against the business's own rule.The changed value ignored or refused and the total equal to the rate the server holds; one of the three bookings succeeding and the room count reading zero, never below; the held room back on sale when the business's rule says. ASVS 5.0 requirement v5.0.0-2.3.4 asks that business logic level locking mechanisms are used to ensure that limited quantity resources cannot be double-booked by manipulating the application's logic.The original and changed requests, the totals, the three responses and the room count afterwards, and the time the hold was released.Your own booking page on the staging copy, or a test property the booking engine documents, within the answer B1 records. guest-a and guest-b only, a test room type only, at most five booking submissions across the row with three in the burst sent once, payment provider in test mode, never a real card, confirmations only to inboxes the business controls. The burst checks timing; it is not load testing. If any response shows a real guest's details, stop and record it.WSTG v4.2 WSTG-BUSL-03; ASVS 5.0 v5.0.0-2.3.4; WSTG-BUSL-10, Race Conditions; OWASP OAT-021 Denial of Inventory.
A3. Accommodation, channel-manager handoff: the mapEach booking as it passes between online travel agencies, the channel manager, the property system, the booking engine and the business's own site: guest names, contact details, dates, rates and special requests.Each system the business names, and the staff and outside parties, such as an agency or revenue manager, who hold accounts in it. Not former staff, and not anyone using another person's login.Read only. Draw the handoff as the business can see it: which system sends each booking to which, by what route (a direct connection, an email or a file), where booking notification emails land, and who can read that inbox. For each system, list the accounts that can see bookings, the person behind each, the role it holds, and whether it has its own sign-in with a second factor where the system offers one. Ask each vendor about anything the business cannot see for itself, rather than opening a settings screen that shows keys.Every connection with an owner, every account named to a current person with the role their work needs, no shared logins, and the notification inbox open only to the staff who handle bookings.The dated map and account lists. May relate to: APP 11.1, if the Act covers the business; and the account questions on a corporate client's questionnaire or an insurer's form.Read only. No request goes to any vendor's system, and nobody signs in as anyone else. This page makes no statement about how any channel manager works.WSTG v4.2 WSTG-IDNT-01; ASVS 5.0 v5.0.0-8.2.1.
A4. Accommodation: booking messages into the business's own siteBookings, changes and cancellations that another system sends to an address on the business's own site or app, with guest names, dates and rates.The sending system the business named in A3. Nobody else should be able to create, change or cancel a booking this way.Only where the business's own site or app receives such messages; otherwise mark the row not applicable. To the staging copy's receiving address only, send one message with no signature or credential, and one copy of a genuine test message with its booking reference or dates altered. Then, in a test mode the sending system's documentation describes, have it resend one genuine message once.The unsigned and altered messages refused, and the resent message causing no second booking, change or confirmation email.Each delivery, the site's response and the booking records afterwards.The staging copy's address only, never the live site's and never a vendor's. Test bookings only, one delivery of each message, any confirmation emails only to inboxes the business controls, no load. Resending from a vendor's documented test mode follows the answer B1 records. If any response shows a real guest's details, stop and record it.This page's own checks, following the signature and duplicate-delivery checks that the Stripe webhook security guide sets out for payment events.
A5. Accommodation: modification and cancellation linksEverything A1 shows, plus the power to change dates, add requests or cancel, carried in a link in the confirmation email.The guest holding the email, for as long as the business's own rule says. Not another guest, and not any third-party host that the linked page sends requests to.Write the rule first: what the link may do, and when it stops, such as after a cancellation, after a newer link is sent or after departure. From guest-a's confirmation email: (1) read the link's address for the guest's name, email address or booking details in plain view; (2) open it in a browser that has never signed in; (3) change its token or reference once to guest-b's; (4) open the page with the developer tools network panel open, and note whether any request to a third-party host carries the token or the booking reference, and which Referrer-Policy the page sends; (5) where the site can resend the link, request a new one and open the old one; (6) cancel guest-a's booking and open the old link again; (7) ask the developer what ends the link after departure, and once the departure date of guest-b's test booking has passed, open guest-b's link.No personal detail in the address; the changed token refused; the token and reference absent from third-party requests; each old link refused, or showing only a status, at the points the business's rule names. A link that can still change or cancel a booking after the rule says it stops is a finding.The rule as written, each request and response with tokens redacted, the third-party hosts the page called, and the Referrer-Policy value. May relate to: APP 11.1, if the Act covers the business.Your own site, on the staging copy where one exists. guest-a's and guest-b's test bookings only, one changed-token request, each link opened once per numbered step, the cancellation only on guest-a's test booking, emails only to inboxes the business controls, never a real card, no load. Record the link's parts with the token redacted, and never paste the link itself into the evidence. Where a vendor's booking engine issues the link, every step runs in its documented test mode and only within the answer B1 records, which should name steps 3, 5 and 6. Never open a real guest's link. If any response shows a real guest's details, stop and record it.WSTG v4.2 WSTG-ATHZ-04; ASVS 5.0 v5.0.0-14.2.1 and v5.0.0-14.2.3; OWASP Forgot Password Cheat Sheet, on reset tokens and URL tokens, used as a yardstick by this page's choice; OWASP Session Management Cheat Sheet, on identifiers in URLs.
A6. Accommodation and events: group rooming listsEvery traveller's name, who shares with whom, arrival and departure dates, contact numbers and any notes, in a file an organiser uploads or downloads, or a copy emailed or shared.The group's organiser and the staff handling the group. Not another group's organiser, and not anyone holding the file's address without a session.First, read only: list every place a rooming list arrives and is kept (an upload area, an inbox, a shared folder, the property system), who can open each, and how long each copy is kept after the group departs. Then, where organisers upload or download lists through the business's own site: as org-a, upload a test list of invented travellers with the marker; as org-b, request org-a's list by its id; request the file's address with no session and after signing out; upload one harmless file of a type the business does not accept; and upload a CSV whose first traveller name cell reads =1+1. Open the staff export of that list in a spreadsheet program on a staff test device.org-b's and the no-session requests refused; the unaccepted type refused; the =1+1 cell showing as text, not as 2; each copy's keeping period written down. OWASP's CSV Injection page says that when a spreadsheet program such as Microsoft Excel or LibreOffice Calc is used to open a CSV, any cells starting with = will be interpreted by the software as a formula.The list of copies with who can open each and how long it is kept, each request and response, and what the spreadsheet showed. May relate to: APP 11.1 and APP 11.2 of the Privacy Act 1988, if the Act covers the business.Your own site on the staging copy only. org-a and org-b with invented travellers only, one upload of each test file, each request once, any notification emails only to inboxes the business controls, no load. Use the =1+1 cell only, which adds two numbers and nothing more; never use any other formula. If a list on the copy holds real travellers, do not open it: record its location and who can open it, and stop. If any response shows a real person's details, stop and record it.WSTG v4.2 WSTG-BUSL-08, WSTG-ATHZ-04 and WSTG-ATHZ-02; OWASP File Upload Cheat Sheet; OWASP CSV Injection; ASVS 5.0 v5.0.0-14.2.7, on retention, a Level 3 requirement.
A7. Accommodation: dietary, allergy and accessibility notes for a stayFree-text notes and tick-boxes on the booking or pre-arrival form, such as a food allergy, a dietary requirement, a mobility or hearing need, or an occasion.The guest, and the staff who act on each note, such as front office, housekeeping or the kitchen, as the business decides. Not another guest, not staff who do not act on it, and not analytics, advertising or chat scripts on the page.As guest-a, add an invented note carrying the marker, such as "STAYTEST-1115 test peanut note", on the booking or pre-arrival form, with the developer tools network panel open. Note whether the note appears in the page's address or in any request to a third-party host. As guest-b, request guest-a's pre-arrival form or booking by its id, once. Then, read only: follow the note to every place it appears (the confirmation email, staff screens, housekeeping or kitchen lists, exports, the property system) and list the staff roles that can read each.The note sent to the server only in the request body, absent from every third-party request, refused to guest-b, and readable only by the roles the business names.The network record, guest-b's request and response, and the list of places and roles. May relate to: the definitions of personal information and sensitive information in section 6(1) of the Privacy Act 1988 and of health information in section 6FA, which this page does not apply to any note; and APP 3.3 and APP 11.1, if the Act covers the business. Whether a note falls within any definition is for your adviser.Invented notes only, never a real guest's medical or personal detail. Your own form on the staging copy, or the booking engine's documented test mode within the answer B1 records. guest-a and guest-b only, one note, each request once, emails only to inboxes the business controls, no load. Follow the note only on the copy or in the test mode; where a list or screen also shows real guests, record its name and who can read it, and read no further. If any response shows a real guest's details, stop and record it.ASVS 5.0 v5.0.0-14.2.1 and v5.0.0-14.2.3; WSTG v4.2 WSTG-ATHZ-04; Privacy Act 1988, Compilation No. 104.
R1. Restaurants: reservation confirmation, change and cancel linksThe diner's name, phone number, email address, party size, date and time, and notes, on the confirmation page, in the email or text message, and behind its change and cancel links.The diner who booked, and front-of-house staff. Not another diner, and not any third-party host that the reservation pages send requests to.As guest-a and guest-b, make one test reservation each, and note the confirmation page and each link the email or text message carries. Open each of guest-a's links in a browser that has never signed in, and read its address for personal details. Then: where diners sign in, request guest-a's reservation page once while signed in as guest-b; change the token or reference in one of guest-a's links once to guest-b's; cancel guest-a's reservation and open its old links again; and once guest-b's reservation time has passed, open guest-b's change link.No personal detail in any address; the changed token and guest-b's request refused; the old links refused, or showing only a status, after the cancellation and after the reservation time, as the business's rule says.Each request and response with names, phone numbers and tokens redacted, and the rule as written. May relate to: APP 11.1, if the Act covers the business.Your own reservation page on the staging copy, or, where a vendor's platform holds the reservation, its documented test mode and only within the answer B1 records. One test reservation for guest-a and one for guest-b, one changed-token request, each link opened at most twice, text messages only to numbers and emails only to inboxes the business controls, no load. Never paste a link itself into the evidence. If any response shows a real diner's details, stop and record it.WSTG v4.2 WSTG-ATHZ-04 and WSTG-ATHZ-02; ASVS 5.0 v5.0.0-14.2.1; OWASP Forgot Password Cheat Sheet, used as a yardstick by this page's choice.
R2. Restaurants: dietary, allergy and accessibility notes on a reservationThe reservation's notes field and any tick-boxes for allergies, dietary requirements, high chairs, prams or wheelchair access, and wherever they are copied: the booking screen, kitchen or floor lists, reminder messages and the diner's record for later visits.The diner, and the front-of-house and kitchen staff the business names. Not other diners, not staff roles that do not act on notes, and not third-party scripts on the reservation page.As guest-a, reserve with an invented note carrying the marker, with the developer tools network panel open, and note whether the note appears in the address or in a request to any third-party host. Then, read only: follow the note to each list, screen and message it reaches; record whether it is kept for guest-a's later reservations, who can read it there and how long it stays; and read the reminder message for whether it repeats the note.The note absent from addresses and third-party requests, shown only where the business has decided it should be, and kept only as long as the business has decided.The network record and the list of places, roles and keeping periods. May relate to: the Privacy Act provisions listed in row A7, where the Act applies, with the same caveat.Invented notes only. Your own reservation page on the staging copy, or the platform's documented test mode within the answer B1 records where a vendor's platform holds the reservation. One test reservation for guest-a, texts and emails only to numbers and inboxes the business controls, no load. The rest of the row is read only, on the copy or in the test mode. If any screen shows a real diner's details, stop and record it.ASVS 5.0 v5.0.0-14.2.1, v5.0.0-14.2.3 and v5.0.0-14.2.7.
R3. Restaurants: covers, held tables and the last slotEach sitting's capacity, the reservations against it, and any limit per diner, phone number or email address.The reservation system enforces capacity and the business's own limits. No diner should be able to hold more tables than the business allows.Write the capacity and any per-diner limit first. On a test sitting with room for one more party, have guest-a and guest-b submit three reservations at nearly the same moment, once. Separately, with the test sitting's per-diner limit set to two, make three reservations for the same evening as guest-a.One of the three reservations succeeding and the sitting never past its capacity; the third reservation beyond the limit refused or flagged, as the business's rule says. ASVS 5.0 requirement v5.0.0-2.3.4 asks that business logic level locking mechanisms are used to ensure that limited quantity resources cannot be double-booked by manipulating the application's logic.The responses, the sitting's count afterwards and how the limit behaved.A test sitting on the staging copy, or a test venue the reservation platform documents, within the answer B1 records. guest-a and guest-b only, six reservations in all, with the three in the burst sent once, texts and emails only to numbers and inboxes the business controls. This is a timing and limit check, not load testing. If any response shows a real diner's details, stop and record it.ASVS 5.0 v5.0.0-2.3.4 and v5.0.0-2.3.2; OWASP API6:2023, which gives making a reservation among its common examples of sensitive business flows; OWASP OAT-021 Denial of Inventory.
R4. Restaurants: deposits and card holdsThe deposit or hold amount the business sets, the reservation's status, and card details, which should reach only the payment provider's page or fields.The business sets the amount and the payment provider takes the card. The reservation is confirmed only once the provider confirms the payment.Read only first: read the labels and help text of the reservation form and its notes field for anything that invites a card number. Then, in test mode, as guest-a: make a reservation that needs a deposit and, if the amount travels in a request or a hidden field, change it once; leave a second deposit unpaid at the provider and request the reservation's confirmation step directly; and load the confirmation page of the paid reservation a second time.No form inviting a card number; the amount charged equal to the amount the business set; the unpaid reservation not confirmed; the second load creating no second confirmation, charge or message.The form labels as read, each request, the amount in the provider's test dashboard and the reservation statuses. May relate to: the questions about card handling that B1 puts to the acquirer or payment provider.Staging copy or the reservation platform's documented test mode within the answer B1 records, payment provider in its test mode with its documented test card, never a real card, guest-a only, at most two deposit submissions, each page loaded at most twice, texts and emails only to numbers and inboxes the business controls, no load. If any response shows a real diner's details, stop and record it.WSTG v4.2 WSTG-BUSL-03; ASVS 5.0 v5.0.0-2.3.1; PCI SSC Merchant Resources FAQ.
E1. Events: the enquiry formThe organiser's name, company, email address and phone number, the date, guest numbers, budget, dietary and accessibility requirements, and any attachment the form accepts, such as a floor plan or draft run sheet.The events team. Not other enquirers, not anyone holding an attachment's address, and not third-party scripts on the form page.As org-a, submit one enquiry with invented details and the marker, with the developer tools network panel open, and note whether any field appears in the address or in a request to a third-party host. Where the form accepts attachments, attach one harmless file of an accepted type and one of a type the business does not accept, then request the stored attachment's address with no session. Read the form's labels and help text for anything that invites a card number. Then send two more enquiries within a minute to the same controlled inbox and note whether any limit applies. Finally, read only: list where enquiries land (an inbox, a CRM, a spreadsheet) and who can open each.Fields absent from addresses and third-party requests; the unaccepted file refused; the stored attachment refused without a session; no field inviting a card number; and any limit the business has set on repeated submissions applying as written.The network record, each request and response, and the list of places and who can open them. May relate to: APP 11.1, if the Act covers the business, and the Privacy Act provisions in row A7 for any dietary or accessibility detail.Your own form on the staging copy. org-a only, three enquiries in all, any acknowledgement email only to an inbox the business controls, harmless test files only, each request once, no load. If any response or list shows a real enquirer's details, stop and record it.WSTG v4.2 WSTG-BUSL-08 and WSTG-ATHZ-02; ASVS 5.0 v5.0.0-14.2.3 and v5.0.0-2.4.1; OWASP API4:2023, on resources paid for per request, such as emails and SMS.
E2. Events: proposals, function sheets and guest lists shared by linkThe event's details and prices, the run sheet, and guest lists with each guest's meal choice and dietary or accessibility notes.The event's organiser and the events team, for as long as the business's rule says. Not another organiser, and not anyone given a forwarded link after the rule says it stops.Write the rule first. For a test event for org-a and one for org-b, share each document the way the business does. In a browser that has never signed in, open org-a's link; change its id, token or file name once to org-b's; and read whether the shared document carries more than its reader needs, such as a full guest list with notes where a headcount would do. Once org-a's test event date has passed, or the rule's end point is reached, open the link again.The changed link refused, each document holding only what its reader needs, and the link refused, or showing only a status, after the rule's end point.Each request and response, redacted, and the rule as written. May relate to: APP 11.1 and APP 11.2, if the Act covers the business.Your own system on the staging copy, or a document-sharing tool only in a test mode its vendor's documentation describes and within its vendor's answer in B1. Test events for org-a and org-b only, one changed-link request, each link opened at most twice, any sharing emails only to inboxes the business controls, no load. Never paste a share link itself into the evidence. If any response shows a real person's details, stop and record it.WSTG v4.2 WSTG-ATHZ-04 and WSTG-ATHZ-02; OWASP IDOR Prevention Cheat Sheet, on filenames and tokens as object references; ASVS 5.0 v5.0.0-14.2.6, a Level 3 requirement.
E3. Events: deposit and balance invoices paid by linkInvoice amounts, the event's details, the organiser's contact details and the payment status.The organiser of that event. Not another organiser.For org-a's and org-b's test events, issue a deposit invoice each. From org-a's link, change the invoice id once to org-b's. Pay org-a's deposit in test mode and, where the amount travels in the payment request, change it once in that payment. Then open the paid link again and submit it once more.org-b's invoice refused to org-a's link, the amount charged equal to the invoice, and the paid invoice taking no second payment and sending no second receipt.Each request and response, the amounts in the provider's test dashboard and the invoice statuses.Staging copy, or the invoicing tool's documented test mode within the answer B1 records, payment provider in its test mode with its documented test card, never a real card, org-a and org-b only, at most two payment submissions, each request once, emails only to inboxes the business controls, no load. Never paste an invoice link itself into the evidence. If any response shows a real person's details, stop and record it.WSTG v4.2 WSTG-ATHZ-04 and WSTG-BUSL-03; ASVS 5.0 v5.0.0-2.3.1.
G1. Gift cards: buying and delivering oneThe buyer's name and email address, the recipient's name and email address, a message, the code and its value.The buyer and the recipient. Not other buyers, and not third-party scripts on the purchase or delivery pages.As guest-a, buy one test gift card in test mode for a recipient whose inbox the business controls, with the developer tools network panel open. Note whether the code appears in any page address or in a request to a third-party host. As guest-b, request guest-a's order or e-card by its id, once.The code absent from addresses and third-party requests, and guest-b refused.The network record, the request and response with the code redacted, and where the code appears in the delivery email.Staging copy, or the gift card service's documented test mode within the answer B1 records, payment provider in test mode with its documented test card, never a real card, one purchase, each request once, emails only to inboxes the business controls, no load. If any response shows a real buyer's details, stop and record it.ASVS 5.0 v5.0.0-14.2.1 and v5.0.0-14.2.3; WSTG v4.2 WSTG-ATHZ-04.
G2. Gift cards: balance checks and guessable codesGift card codes and their balances.The holder of a code. Not someone working through codes until one answers.On the staging copy, issue three test codes one after another and note their length and whether they follow a sequence or a pattern. Then, only where B2 found no real gift cards on the copy, send five balance checks for invented codes, each one character away from a test code, and note whether any limit, delay or refusal appears.Codes that cannot be worked out from one another, and repeated misses met with the limit the business has set. OWASP's automated threat OAT-002, Token Cracking, lists voucher, gift card and discount enumeration among its other names and examples.The code format, never a live code, the five responses and how any limit behaved.Staging copy, or the gift card service's documented test mode within the answer B1 records, three test codes issued, payment provider in test mode where issuing one takes a payment, never a real card, five balance checks in all, any emails only to inboxes the business controls, no load. Never try codes against the live site. If a check returns a real card's balance, stop and record it.OWASP OAT-002 Token Cracking; ASVS 5.0 v5.0.0-2.4.1; the rate limiting guide.
G3. Gift cards: spending one balance twiceA gift card's balance and the bookings, reservations or orders it pays for.One spend for each unit of balance.Give guest-a a test gift card that covers one booking or deposit. Set up three checkouts, each spending the full balance, and send all three at nearly the same moment, a single time.One checkout succeeding and the balance never below zero. Among the indicators of vulnerability in WSTG-BUSL-10 are negative balances after concurrent debits.The three responses, what was created, and the balance afterwards.Staging copy, or the gift card service's documented test mode within the answer B1 records, payment provider in test mode, never a real card, guest-a only, three submissions sent once, emails only to inboxes the business controls. The three submissions check timing, not how the site copes with load. If any response shows a real person's details, stop and record it.WSTG-BUSL-10, Race Conditions; the race conditions guide.
M1. Refunds: cancellations by the guestThe amount paid, the cancellation policy, the refund due and the payment reference.The guest, for the amount the policy sets. Nobody gets back more than was paid.Write the policy's outcome first for the test dates you will use. As guest-a, in test mode, cancel one paid test booking through its modification link and compare the refund with the policy. Send the cancel request a second time. Where a refund amount or a percentage travels in the cancel request, change it once on a second test booking. On a third, change the booking to a cheaper rate, then cancel it.Each refund equal to what the policy sets for those dates, no second refund from the repeated request, the changed amount ignored, and the total refunded on each booking never more than was paid.The policy as written, each request, the provider's test dashboard and the bookings' records.Staging copy, or the booking engine's documented test mode within the answer B1 records, payment provider in test mode with its documented test card, never a real card, guest-a only, three test bookings, each request once apart from the one repeated cancel request, emails only to inboxes the business controls, no load. If any response shows a real guest's details, stop and record it.WSTG v4.2 WSTG-BUSL-03 and WSTG-BUSL-06; ASVS 5.0 v5.0.0-2.3.1; the business logic vulnerabilities guide, whose invariants include that the total refunded on a booking never exceeds the total paid on it.
M2. Refunds: staff refunds and returned depositsBooking, reservation and event payments, their references, and the guest's or organiser's contact details.The staff roles the business names for refunds, with a second person for refunds above a level the business sets. Not other staff roles, and not guests.First, read only: in every system that can send money back (the booking engine, reservation platform, event or invoicing tool, gift card service and the payment provider's dashboard), list the roles that can refund and who holds them. Then, on the business's own system in test mode, capture a small partial refund on one of M1's paid test bookings, made by a staff test account allowed to refund, and send that request again from a staff test account without the permission and with no session. Note whether a refund can be sent anywhere other than the original payment.Only the named roles succeed, the provider's test dashboard shows no refund from any other request, and refunds go back to the original payment.The role lists, each request and response, and the provider's test dashboard. The role definitions test in WSTG v4.2, WSTG-IDNT-01, says sensitive admin functionality should leverage a maker-checker principle, or use MFA to ensure that the administrator is conducting the transaction.The role lists are read only in every system. Requests only on the business's own system on the staging copy, payment provider in test mode, M1's paid test bookings only, staff test accounts only, each request once, emails only to inboxes the business controls, no load. If any response shows a real person's details, stop and record it.WSTG v4.2 WSTG-ATHZ-02 and WSTG-IDNT-01; ASVS 5.0 v5.0.0-8.2.1 and v5.0.0-2.3.5, a Level 3 requirement.
S1. Payment pages: which scripts load, and who approved themCard details typed into the payment fields, and anything else a script on the page can read.Only scripts the business has approved, each for a stated reason.Read only. List every page in the journey that takes money: the booking payment step, table deposits, event invoices and the gift card checkout, and mark each as on the business's own domain or a vendor's. Load each page on the business's own domain once on the staging copy with the developer tools network panel open, typing nothing into payment fields. For each script host, record its business reason, who approved it, and how its integrity is checked, such as Subresource Integrity, which MDN says enables browsers to verify that resources they fetch are delivered without unexpected manipulation, by providing a cryptographic hash that a fetched resource must match. For a vendor's page, record the vendor and put the question to it.Every host on the business's own pages with an owner, a reason, an approval and an integrity method, or a written reason for none. Any host nobody can account for is raised with the owner.The dated list of pages and scripts. May relate to: PCI DSS v4.x Requirements 6.4.3 and 11.6.1, which the PCI SSC post says focus on ensuring that payment page scripts are properly authorised, checked for integrity and monitored for tampering. Whether they apply to the business is a question for the acquirer or payment brand, recorded in B1.Page loads only. Nothing typed into payment fields, no form submitted, and no script removed; removing one is a change for the owner to make.MDN Subresource Integrity; OWASP Third Party JavaScript Management Cheat Sheet; PCI SSC post of 10 March 2025.
S2. Payment pages: headers, change alerts and the accounts that can edit themThe payment pages' response headers, and the accounts that can change what those pages load.Named people who maintain the site, its plugins or apps and its tag manager, and one named person who is told of a change.Read only. Using the responses from S1's page loads, note each security-related response header by name, such as Content-Security-Policy or Content-Security-Policy-Report-Only. List the accounts that can change what each payment page loads: site administrators, plugin or app installers, tag manager users and the agency. Ask who would be told, and how, if a script or header on a live payment page changed.Change alerts reach a named person, and the account list matches the people who maintain the pages today. OWASP's Content Security Policy Cheat Sheet says Content-Security-Policy-Report-Only delivers a policy that is not enforced, and that violation reports are still printed to the console, and delivered to a violation endpoint if the report-to and report-uri directives are used; note which header each page sends.Header names and values as read, the alert route and the account list. May relate to: the post's statement that the requirements also address the need for careful management of both scripts and security-impacting HTTP headers to prevent unauthorised changes to webpages. Whether that applies to the business is a question for the acquirer or payment brand.Read only. Nothing is changed: headers, tags and accounts stay as found.OWASP Third Party JavaScript Management Cheat Sheet, on tag managers; OWASP Content Security Policy Cheat Sheet; PCI SSC post of 10 March 2025.
Z1. Significant change: when to run rows againWhatever the change touches.The owner decides; the developer, agency or vendor names each change before it ships, where it can.Planning. For each change below, run its rows again on the staging copy, ideally before the change goes live, otherwise as soon after release as you can. A new booking engine, channel manager or property system: A1 to A7 and S1. A new reservation platform: R1 to R4 and S1. A new event enquiry, proposal or invoicing tool: E1 to E3. A new gift card service: G1 to G3 and S1. A new payment provider, or a change to how a payment page takes the card: S1, S2, R4, E3 and M1. A new script, tag or tag manager change on any booking or payment page: S1 and S2. A change to confirmation, reminder or pre-arrival emails: A5, A7, R1 and R2. A changed cancellation, deposit, capacity or refund policy: A2, R3, R4, M1 and M2. A change of agency, developer or host, or new staff roles in any system: every row, starting with B1 and A3.Every change the business logs is matched by a dated rerun of its rows and the results.What changed, which rows were rerun, on what date and against which build. May relate to: PCI DSS compliance validation, which the PCI SSC's Merchant Resources FAQ directs to the acquirer (merchant bank) or payment brand; this page sets no testing or scanning schedule.Planning only. Each rerun row keeps its own limits.This page's own list; PCI SSC Merchant Resources FAQ.
Z2. Clean-upEverything the run created.Records in each system are removed by that system's owner.List every test booking, reservation, enquiry, event, rooming list, note, gift card, refund and test account the run created, each carrying the marker, and each vendor test account that received any of them. Remove them on the staging copy, and ask each vendor or system owner to remove them from its system.No record carrying the marker remains, or each one that does is listed with who removes it and when.The clean-up list with dates.Deletes only records that carry the run's marker.This page's own list.
Z3. The evidence pack and the duties or requests it may relate toThe run's records, redacted.The pack stays with the owner, who decides who may see it.Planning. Gather into one pack: B1's dated terms and answers, B2's readings, each row's redacted requests and responses with the build and date, the lists from A3, A6, A7, R2, S1, S2 and M2, Z1's change log and Z2's clean-up list.Every item carries its date, its holder and who may see it.May relate to: APP 11.1 to 11.3 of the Privacy Act 1988, if the Act covers the business; the Notifiable Data Breaches scheme, as the OAIC explains it, if a breach occurs; PCI DSS validation, which the PCI SSC's Merchant Resources FAQ sends to the acquirer or payment brand, and PCI DSS v4.x Requirements 6.4.3 and 11.6.1 as the PCI SSC post describes them (S1, S2); and security questionnaires from corporate clients and insurers' forms, covered by the security questionnaires and cyber insurance checklist guides. Whether any of these applies is for the owner to establish with their own privacy adviser and, for card payments, the acquirer or payment brand.No password, key, secret, card number or real guest record goes in the pack.Privacy Act 1988, Compilation No. 104; OAIC, About the Notifiable Data Breaches scheme; PCI SSC Merchant Resources FAQ; PCI SSC post of 10 March 2025.

Row and step

Details involved

  1. B1. Before testing: systems, owners, terms and the questions settled business by business
    Details involved
    None. This row reads documents and asks questions.
    Who should reach them, and who should not
    The owner decides what is tested. Each vendor (booking engine, channel manager, property or reservation system, event or invoicing tool, gift card service, payment provider) and the host sets the terms for its own system. For questions on compliance validation, the PCI SSC points merchants to their acquirer or payment brand. The business's own privacy adviser answers whether the Privacy Act covers it.
    Test case
    Read only. List every system a later row touches, who runs it, and which of its pages sit on the business's own domain. For each vendor and the host, read its own terms on security testing and on test modes or test properties, note the date, and ask in writing where the terms leave doubt. Ask the acquirer (merchant bank) or payment brand in writing how the business's PCI DSS validation is set, including whether Requirements 6.4.3 and 11.6.1 apply to a booking flow that hands the card to a provider's page or fields, and ask the payment provider which parts of card handling it takes on. Ask your adviser whether, and how, the Privacy Act covers the business.
    Expected result
    Every system has a dated answer before the first row that sends a request, and any system whose terms leave doubt is left out of the run until its vendor replies.
    Evidence to keep, and the duty or request it may relate to
    Each terms page with its address and the date read, each written answer, and the answers on card handling and privacy coverage. May relate to: compliance validation questions, which the PCI SSC's Merchant Resources FAQ directs to the acquirer (merchant bank) or payment brand; and the coverage provisions of the Privacy Act 1988 in sections 6(1), 6C and 6D.
    Limits of this row
    Read only. No request goes to the site or to any vendor's system.
    References
    PCI SSC Merchant Resources FAQ; Privacy Act 1988, Compilation No. 104. What each vendor permits is in its own terms, not on this page.
  2. B2. Before testing: confirm the staging copy and create invented guests
    Details involved
    Whatever the staging copy holds. A copy cloned from the live site can hold real guests' bookings and live connections.
    Who should reach them, and who should not
    Settings on the copy are changed only by the person who manages it. This row reads them and then adds the run's test identities.
    Test case
    Read only, then create identities. Check that the copy is the business's own and is not the live site. Read the mode of each booking, reservation, gift card and payment connection on the copy, and where each email and text message route ends. Then create invented guests guest-a and guest-b and invented organisers org-a and org-b, each with an inbox and a phone number the business controls; a staff test account for each role the rows name, such as reservations, front office, restaurant host, events coordinator and manager; and the marker STAYTEST-1115, or your own, in every name and note.
    Expected result
    Every connection on the copy in a test mode its vendor documents or pointing at a test account, every message route ending at an inbox or number the business controls, and the live site in live mode. If any reading says otherwise, stop: changing a mode or a connection is a task for whoever manages it, not a step in this checklist.
    Evidence to keep, and the duty or request it may relate to
    Each mode and route as read, with the date and the reader, and the list of test identities.
    Limits of this row
    Reading only, except for adding the invented guests, organisers and staff test accounts on the staging copy, with any welcome email or text going to an inbox or number the business controls, and no load. If a mode is shown only on a screen that also displays keys, get the reading from whoever manages that integration. Real guests' records on the copy stay unopened: rows that list or export records then end at their read-only part, and rows A1 and G2 leave out their neighbouring references and codes. If any screen shows a real guest's details, stop and record where.
    References
    This page's own set-up.
  3. A1. Accommodation, direct bookings: confirmation, lookup and invoice
    Details involved
    Guest name, email address, phone number, arrival and departure dates, adults and children, room and rate, special requests, and the payment or deposit summary the site shows, on the confirmation page, the booking lookup and the invoice or receipt.
    Who should reach them, and who should not
    The guest who booked, and reservations and front office staff. Not another guest, and not a visitor with no session or link.
    Test case
    As guest-a and guest-b, make one test booking each through the business's own booking page, and note each address that shows guest-a's: the confirmation page, any booking lookup (by reference with a surname or email address), and the invoice or receipt file. As guest-b, request each address with guest-a's booking reference or id in place of guest-b's own, then send each request again with no session. Compare guest-a's and guest-b's references to see whether they run in sequence and, only where B2 found no real guests' records on the copy, try the references either side of guest-a's once each in the lookup.
    Expected result
    Every request refused with the same response the site gives for a booking that does not exist, no response holding any of guest-a's details, and a lookup that answers only when the reference and the second detail belong to the same booking.
    Evidence to keep, and the duty or request it may relate to
    Each request and response, marked with the identity and session used, with names, contact details and tokens redacted, and whether references are sequential. May relate to: APP 11.1 of the Privacy Act 1988 and the steps it concerns, if the Act covers the business.
    Limits of this row
    Your own booking page on the staging copy, or the booking engine's documented test mode within the answer B1 records. guest-a and guest-b only, one test booking each, each request once and two neighbouring references at most, confirmations only to inboxes the business controls, never a real card, no load. If any response shows a real guest's details, stop, record the request and tell the owner.
    References
    WSTG v4.2 WSTG-ATHZ-04 and WSTG-ATHZ-02; ASVS 5.0 v5.0.0-8.2.2; OWASP IDOR Prevention Cheat Sheet.
  4. A2. Accommodation, direct bookings: rates, held rooms and the last room
    Details involved
    Room type, dates, occupancy, the rate and any promotion code, and the number of rooms left to sell.
    Who should reach them, and who should not
    The booking system sets the rate and the availability. The guest chooses a room, dates and occupancy only.
    Test case
    As guest-a, watch the booking requests in the browser's developer tools. If any request carries a nightly rate, a total or a price per extra guest, including in a hidden field, change one value once and complete the test booking. Then, on a test room type with one room left on one night, have guest-a and guest-b submit three bookings for it at nearly the same moment, once. Where the site holds a room during checkout, start one hold as guest-a, leave it unpaid, and check when the room returns to sale against the business's own rule.
    Expected result
    The changed value ignored or refused and the total equal to the rate the server holds; one of the three bookings succeeding and the room count reading zero, never below; the held room back on sale when the business's rule says. ASVS 5.0 requirement v5.0.0-2.3.4 asks that business logic level locking mechanisms are used to ensure that limited quantity resources cannot be double-booked by manipulating the application's logic.
    Evidence to keep, and the duty or request it may relate to
    The original and changed requests, the totals, the three responses and the room count afterwards, and the time the hold was released.
    Limits of this row
    Your own booking page on the staging copy, or a test property the booking engine documents, within the answer B1 records. guest-a and guest-b only, a test room type only, at most five booking submissions across the row with three in the burst sent once, payment provider in test mode, never a real card, confirmations only to inboxes the business controls. The burst checks timing; it is not load testing. If any response shows a real guest's details, stop and record it.
    References
    WSTG v4.2 WSTG-BUSL-03; ASVS 5.0 v5.0.0-2.3.4; WSTG-BUSL-10, Race Conditions; OWASP OAT-021 Denial of Inventory.
  5. A3. Accommodation, channel-manager handoff: the map
    Details involved
    Each booking as it passes between online travel agencies, the channel manager, the property system, the booking engine and the business's own site: guest names, contact details, dates, rates and special requests.
    Who should reach them, and who should not
    Each system the business names, and the staff and outside parties, such as an agency or revenue manager, who hold accounts in it. Not former staff, and not anyone using another person's login.
    Test case
    Read only. Draw the handoff as the business can see it: which system sends each booking to which, by what route (a direct connection, an email or a file), where booking notification emails land, and who can read that inbox. For each system, list the accounts that can see bookings, the person behind each, the role it holds, and whether it has its own sign-in with a second factor where the system offers one. Ask each vendor about anything the business cannot see for itself, rather than opening a settings screen that shows keys.
    Expected result
    Every connection with an owner, every account named to a current person with the role their work needs, no shared logins, and the notification inbox open only to the staff who handle bookings.
    Evidence to keep, and the duty or request it may relate to
    The dated map and account lists. May relate to: APP 11.1, if the Act covers the business; and the account questions on a corporate client's questionnaire or an insurer's form.
    Limits of this row
    Read only. No request goes to any vendor's system, and nobody signs in as anyone else. This page makes no statement about how any channel manager works.
    References
    WSTG v4.2 WSTG-IDNT-01; ASVS 5.0 v5.0.0-8.2.1.
  6. A4. Accommodation: booking messages into the business's own site
    Details involved
    Bookings, changes and cancellations that another system sends to an address on the business's own site or app, with guest names, dates and rates.
    Who should reach them, and who should not
    The sending system the business named in A3. Nobody else should be able to create, change or cancel a booking this way.
    Test case
    Only where the business's own site or app receives such messages; otherwise mark the row not applicable. To the staging copy's receiving address only, send one message with no signature or credential, and one copy of a genuine test message with its booking reference or dates altered. Then, in a test mode the sending system's documentation describes, have it resend one genuine message once.
    Expected result
    The unsigned and altered messages refused, and the resent message causing no second booking, change or confirmation email.
    Evidence to keep, and the duty or request it may relate to
    Each delivery, the site's response and the booking records afterwards.
    Limits of this row
    The staging copy's address only, never the live site's and never a vendor's. Test bookings only, one delivery of each message, any confirmation emails only to inboxes the business controls, no load. Resending from a vendor's documented test mode follows the answer B1 records. If any response shows a real guest's details, stop and record it.
    References
    This page's own checks, following the signature and duplicate-delivery checks that the Stripe webhook security guide sets out for payment events.
  7. A5. Accommodation: modification and cancellation links
    Details involved
    Everything A1 shows, plus the power to change dates, add requests or cancel, carried in a link in the confirmation email.
    Who should reach them, and who should not
    The guest holding the email, for as long as the business's own rule says. Not another guest, and not any third-party host that the linked page sends requests to.
    Test case
    Write the rule first: what the link may do, and when it stops, such as after a cancellation, after a newer link is sent or after departure. From guest-a's confirmation email: (1) read the link's address for the guest's name, email address or booking details in plain view; (2) open it in a browser that has never signed in; (3) change its token or reference once to guest-b's; (4) open the page with the developer tools network panel open, and note whether any request to a third-party host carries the token or the booking reference, and which Referrer-Policy the page sends; (5) where the site can resend the link, request a new one and open the old one; (6) cancel guest-a's booking and open the old link again; (7) ask the developer what ends the link after departure, and once the departure date of guest-b's test booking has passed, open guest-b's link.
    Expected result
    No personal detail in the address; the changed token refused; the token and reference absent from third-party requests; each old link refused, or showing only a status, at the points the business's rule names. A link that can still change or cancel a booking after the rule says it stops is a finding.
    Evidence to keep, and the duty or request it may relate to
    The rule as written, each request and response with tokens redacted, the third-party hosts the page called, and the Referrer-Policy value. May relate to: APP 11.1, if the Act covers the business.
    Limits of this row
    Your own site, on the staging copy where one exists. guest-a's and guest-b's test bookings only, one changed-token request, each link opened once per numbered step, the cancellation only on guest-a's test booking, emails only to inboxes the business controls, never a real card, no load. Record the link's parts with the token redacted, and never paste the link itself into the evidence. Where a vendor's booking engine issues the link, every step runs in its documented test mode and only within the answer B1 records, which should name steps 3, 5 and 6. Never open a real guest's link. If any response shows a real guest's details, stop and record it.
    References
    WSTG v4.2 WSTG-ATHZ-04; ASVS 5.0 v5.0.0-14.2.1 and v5.0.0-14.2.3; OWASP Forgot Password Cheat Sheet, on reset tokens and URL tokens, used as a yardstick by this page's choice; OWASP Session Management Cheat Sheet, on identifiers in URLs.
  8. A6. Accommodation and events: group rooming lists
    Details involved
    Every traveller's name, who shares with whom, arrival and departure dates, contact numbers and any notes, in a file an organiser uploads or downloads, or a copy emailed or shared.
    Who should reach them, and who should not
    The group's organiser and the staff handling the group. Not another group's organiser, and not anyone holding the file's address without a session.
    Test case
    First, read only: list every place a rooming list arrives and is kept (an upload area, an inbox, a shared folder, the property system), who can open each, and how long each copy is kept after the group departs. Then, where organisers upload or download lists through the business's own site: as org-a, upload a test list of invented travellers with the marker; as org-b, request org-a's list by its id; request the file's address with no session and after signing out; upload one harmless file of a type the business does not accept; and upload a CSV whose first traveller name cell reads =1+1. Open the staff export of that list in a spreadsheet program on a staff test device.
    Expected result
    org-b's and the no-session requests refused; the unaccepted type refused; the =1+1 cell showing as text, not as 2; each copy's keeping period written down. OWASP's CSV Injection page says that when a spreadsheet program such as Microsoft Excel or LibreOffice Calc is used to open a CSV, any cells starting with = will be interpreted by the software as a formula.
    Evidence to keep, and the duty or request it may relate to
    The list of copies with who can open each and how long it is kept, each request and response, and what the spreadsheet showed. May relate to: APP 11.1 and APP 11.2 of the Privacy Act 1988, if the Act covers the business.
    Limits of this row
    Your own site on the staging copy only. org-a and org-b with invented travellers only, one upload of each test file, each request once, any notification emails only to inboxes the business controls, no load. Use the =1+1 cell only, which adds two numbers and nothing more; never use any other formula. If a list on the copy holds real travellers, do not open it: record its location and who can open it, and stop. If any response shows a real person's details, stop and record it.
    References
    WSTG v4.2 WSTG-BUSL-08, WSTG-ATHZ-04 and WSTG-ATHZ-02; OWASP File Upload Cheat Sheet; OWASP CSV Injection; ASVS 5.0 v5.0.0-14.2.7, on retention, a Level 3 requirement.
  9. A7. Accommodation: dietary, allergy and accessibility notes for a stay
    Details involved
    Free-text notes and tick-boxes on the booking or pre-arrival form, such as a food allergy, a dietary requirement, a mobility or hearing need, or an occasion.
    Who should reach them, and who should not
    The guest, and the staff who act on each note, such as front office, housekeeping or the kitchen, as the business decides. Not another guest, not staff who do not act on it, and not analytics, advertising or chat scripts on the page.
    Test case
    As guest-a, add an invented note carrying the marker, such as "STAYTEST-1115 test peanut note", on the booking or pre-arrival form, with the developer tools network panel open. Note whether the note appears in the page's address or in any request to a third-party host. As guest-b, request guest-a's pre-arrival form or booking by its id, once. Then, read only: follow the note to every place it appears (the confirmation email, staff screens, housekeeping or kitchen lists, exports, the property system) and list the staff roles that can read each.
    Expected result
    The note sent to the server only in the request body, absent from every third-party request, refused to guest-b, and readable only by the roles the business names.
    Evidence to keep, and the duty or request it may relate to
    The network record, guest-b's request and response, and the list of places and roles. May relate to: the definitions of personal information and sensitive information in section 6(1) of the Privacy Act 1988 and of health information in section 6FA, which this page does not apply to any note; and APP 3.3 and APP 11.1, if the Act covers the business. Whether a note falls within any definition is for your adviser.
    Limits of this row
    Invented notes only, never a real guest's medical or personal detail. Your own form on the staging copy, or the booking engine's documented test mode within the answer B1 records. guest-a and guest-b only, one note, each request once, emails only to inboxes the business controls, no load. Follow the note only on the copy or in the test mode; where a list or screen also shows real guests, record its name and who can read it, and read no further. If any response shows a real guest's details, stop and record it.
    References
    ASVS 5.0 v5.0.0-14.2.1 and v5.0.0-14.2.3; WSTG v4.2 WSTG-ATHZ-04; Privacy Act 1988, Compilation No. 104.
  10. R1. Restaurants: reservation confirmation, change and cancel links
    Details involved
    The diner's name, phone number, email address, party size, date and time, and notes, on the confirmation page, in the email or text message, and behind its change and cancel links.
    Who should reach them, and who should not
    The diner who booked, and front-of-house staff. Not another diner, and not any third-party host that the reservation pages send requests to.
    Test case
    As guest-a and guest-b, make one test reservation each, and note the confirmation page and each link the email or text message carries. Open each of guest-a's links in a browser that has never signed in, and read its address for personal details. Then: where diners sign in, request guest-a's reservation page once while signed in as guest-b; change the token or reference in one of guest-a's links once to guest-b's; cancel guest-a's reservation and open its old links again; and once guest-b's reservation time has passed, open guest-b's change link.
    Expected result
    No personal detail in any address; the changed token and guest-b's request refused; the old links refused, or showing only a status, after the cancellation and after the reservation time, as the business's rule says.
    Evidence to keep, and the duty or request it may relate to
    Each request and response with names, phone numbers and tokens redacted, and the rule as written. May relate to: APP 11.1, if the Act covers the business.
    Limits of this row
    Your own reservation page on the staging copy, or, where a vendor's platform holds the reservation, its documented test mode and only within the answer B1 records. One test reservation for guest-a and one for guest-b, one changed-token request, each link opened at most twice, text messages only to numbers and emails only to inboxes the business controls, no load. Never paste a link itself into the evidence. If any response shows a real diner's details, stop and record it.
    References
    WSTG v4.2 WSTG-ATHZ-04 and WSTG-ATHZ-02; ASVS 5.0 v5.0.0-14.2.1; OWASP Forgot Password Cheat Sheet, used as a yardstick by this page's choice.
  11. R2. Restaurants: dietary, allergy and accessibility notes on a reservation
    Details involved
    The reservation's notes field and any tick-boxes for allergies, dietary requirements, high chairs, prams or wheelchair access, and wherever they are copied: the booking screen, kitchen or floor lists, reminder messages and the diner's record for later visits.
    Who should reach them, and who should not
    The diner, and the front-of-house and kitchen staff the business names. Not other diners, not staff roles that do not act on notes, and not third-party scripts on the reservation page.
    Test case
    As guest-a, reserve with an invented note carrying the marker, with the developer tools network panel open, and note whether the note appears in the address or in a request to any third-party host. Then, read only: follow the note to each list, screen and message it reaches; record whether it is kept for guest-a's later reservations, who can read it there and how long it stays; and read the reminder message for whether it repeats the note.
    Expected result
    The note absent from addresses and third-party requests, shown only where the business has decided it should be, and kept only as long as the business has decided.
    Evidence to keep, and the duty or request it may relate to
    The network record and the list of places, roles and keeping periods. May relate to: the Privacy Act provisions listed in row A7, where the Act applies, with the same caveat.
    Limits of this row
    Invented notes only. Your own reservation page on the staging copy, or the platform's documented test mode within the answer B1 records where a vendor's platform holds the reservation. One test reservation for guest-a, texts and emails only to numbers and inboxes the business controls, no load. The rest of the row is read only, on the copy or in the test mode. If any screen shows a real diner's details, stop and record it.
    References
    ASVS 5.0 v5.0.0-14.2.1, v5.0.0-14.2.3 and v5.0.0-14.2.7.
  12. R3. Restaurants: covers, held tables and the last slot
    Details involved
    Each sitting's capacity, the reservations against it, and any limit per diner, phone number or email address.
    Who should reach them, and who should not
    The reservation system enforces capacity and the business's own limits. No diner should be able to hold more tables than the business allows.
    Test case
    Write the capacity and any per-diner limit first. On a test sitting with room for one more party, have guest-a and guest-b submit three reservations at nearly the same moment, once. Separately, with the test sitting's per-diner limit set to two, make three reservations for the same evening as guest-a.
    Expected result
    One of the three reservations succeeding and the sitting never past its capacity; the third reservation beyond the limit refused or flagged, as the business's rule says. ASVS 5.0 requirement v5.0.0-2.3.4 asks that business logic level locking mechanisms are used to ensure that limited quantity resources cannot be double-booked by manipulating the application's logic.
    Evidence to keep, and the duty or request it may relate to
    The responses, the sitting's count afterwards and how the limit behaved.
    Limits of this row
    A test sitting on the staging copy, or a test venue the reservation platform documents, within the answer B1 records. guest-a and guest-b only, six reservations in all, with the three in the burst sent once, texts and emails only to numbers and inboxes the business controls. This is a timing and limit check, not load testing. If any response shows a real diner's details, stop and record it.
    References
    ASVS 5.0 v5.0.0-2.3.4 and v5.0.0-2.3.2; OWASP API6:2023, which gives making a reservation among its common examples of sensitive business flows; OWASP OAT-021 Denial of Inventory.
  13. R4. Restaurants: deposits and card holds
    Details involved
    The deposit or hold amount the business sets, the reservation's status, and card details, which should reach only the payment provider's page or fields.
    Who should reach them, and who should not
    The business sets the amount and the payment provider takes the card. The reservation is confirmed only once the provider confirms the payment.
    Test case
    Read only first: read the labels and help text of the reservation form and its notes field for anything that invites a card number. Then, in test mode, as guest-a: make a reservation that needs a deposit and, if the amount travels in a request or a hidden field, change it once; leave a second deposit unpaid at the provider and request the reservation's confirmation step directly; and load the confirmation page of the paid reservation a second time.
    Expected result
    No form inviting a card number; the amount charged equal to the amount the business set; the unpaid reservation not confirmed; the second load creating no second confirmation, charge or message.
    Evidence to keep, and the duty or request it may relate to
    The form labels as read, each request, the amount in the provider's test dashboard and the reservation statuses. May relate to: the questions about card handling that B1 puts to the acquirer or payment provider.
    Limits of this row
    Staging copy or the reservation platform's documented test mode within the answer B1 records, payment provider in its test mode with its documented test card, never a real card, guest-a only, at most two deposit submissions, each page loaded at most twice, texts and emails only to numbers and inboxes the business controls, no load. If any response shows a real diner's details, stop and record it.
    References
    WSTG v4.2 WSTG-BUSL-03; ASVS 5.0 v5.0.0-2.3.1; PCI SSC Merchant Resources FAQ.
  14. E1. Events: the enquiry form
    Details involved
    The organiser's name, company, email address and phone number, the date, guest numbers, budget, dietary and accessibility requirements, and any attachment the form accepts, such as a floor plan or draft run sheet.
    Who should reach them, and who should not
    The events team. Not other enquirers, not anyone holding an attachment's address, and not third-party scripts on the form page.
    Test case
    As org-a, submit one enquiry with invented details and the marker, with the developer tools network panel open, and note whether any field appears in the address or in a request to a third-party host. Where the form accepts attachments, attach one harmless file of an accepted type and one of a type the business does not accept, then request the stored attachment's address with no session. Read the form's labels and help text for anything that invites a card number. Then send two more enquiries within a minute to the same controlled inbox and note whether any limit applies. Finally, read only: list where enquiries land (an inbox, a CRM, a spreadsheet) and who can open each.
    Expected result
    Fields absent from addresses and third-party requests; the unaccepted file refused; the stored attachment refused without a session; no field inviting a card number; and any limit the business has set on repeated submissions applying as written.
    Evidence to keep, and the duty or request it may relate to
    The network record, each request and response, and the list of places and who can open them. May relate to: APP 11.1, if the Act covers the business, and the Privacy Act provisions in row A7 for any dietary or accessibility detail.
    Limits of this row
    Your own form on the staging copy. org-a only, three enquiries in all, any acknowledgement email only to an inbox the business controls, harmless test files only, each request once, no load. If any response or list shows a real enquirer's details, stop and record it.
    References
    WSTG v4.2 WSTG-BUSL-08 and WSTG-ATHZ-02; ASVS 5.0 v5.0.0-14.2.3 and v5.0.0-2.4.1; OWASP API4:2023, on resources paid for per request, such as emails and SMS.
  15. E2. Events: proposals, function sheets and guest lists shared by link
    Details involved
    The event's details and prices, the run sheet, and guest lists with each guest's meal choice and dietary or accessibility notes.
    Who should reach them, and who should not
    The event's organiser and the events team, for as long as the business's rule says. Not another organiser, and not anyone given a forwarded link after the rule says it stops.
    Test case
    Write the rule first. For a test event for org-a and one for org-b, share each document the way the business does. In a browser that has never signed in, open org-a's link; change its id, token or file name once to org-b's; and read whether the shared document carries more than its reader needs, such as a full guest list with notes where a headcount would do. Once org-a's test event date has passed, or the rule's end point is reached, open the link again.
    Expected result
    The changed link refused, each document holding only what its reader needs, and the link refused, or showing only a status, after the rule's end point.
    Evidence to keep, and the duty or request it may relate to
    Each request and response, redacted, and the rule as written. May relate to: APP 11.1 and APP 11.2, if the Act covers the business.
    Limits of this row
    Your own system on the staging copy, or a document-sharing tool only in a test mode its vendor's documentation describes and within its vendor's answer in B1. Test events for org-a and org-b only, one changed-link request, each link opened at most twice, any sharing emails only to inboxes the business controls, no load. Never paste a share link itself into the evidence. If any response shows a real person's details, stop and record it.
    References
    WSTG v4.2 WSTG-ATHZ-04 and WSTG-ATHZ-02; OWASP IDOR Prevention Cheat Sheet, on filenames and tokens as object references; ASVS 5.0 v5.0.0-14.2.6, a Level 3 requirement.
  16. E3. Events: deposit and balance invoices paid by link
    Details involved
    Invoice amounts, the event's details, the organiser's contact details and the payment status.
    Who should reach them, and who should not
    The organiser of that event. Not another organiser.
    Test case
    For org-a's and org-b's test events, issue a deposit invoice each. From org-a's link, change the invoice id once to org-b's. Pay org-a's deposit in test mode and, where the amount travels in the payment request, change it once in that payment. Then open the paid link again and submit it once more.
    Expected result
    org-b's invoice refused to org-a's link, the amount charged equal to the invoice, and the paid invoice taking no second payment and sending no second receipt.
    Evidence to keep, and the duty or request it may relate to
    Each request and response, the amounts in the provider's test dashboard and the invoice statuses.
    Limits of this row
    Staging copy, or the invoicing tool's documented test mode within the answer B1 records, payment provider in its test mode with its documented test card, never a real card, org-a and org-b only, at most two payment submissions, each request once, emails only to inboxes the business controls, no load. Never paste an invoice link itself into the evidence. If any response shows a real person's details, stop and record it.
    References
    WSTG v4.2 WSTG-ATHZ-04 and WSTG-BUSL-03; ASVS 5.0 v5.0.0-2.3.1.
  17. G1. Gift cards: buying and delivering one
    Details involved
    The buyer's name and email address, the recipient's name and email address, a message, the code and its value.
    Who should reach them, and who should not
    The buyer and the recipient. Not other buyers, and not third-party scripts on the purchase or delivery pages.
    Test case
    As guest-a, buy one test gift card in test mode for a recipient whose inbox the business controls, with the developer tools network panel open. Note whether the code appears in any page address or in a request to a third-party host. As guest-b, request guest-a's order or e-card by its id, once.
    Expected result
    The code absent from addresses and third-party requests, and guest-b refused.
    Evidence to keep, and the duty or request it may relate to
    The network record, the request and response with the code redacted, and where the code appears in the delivery email.
    Limits of this row
    Staging copy, or the gift card service's documented test mode within the answer B1 records, payment provider in test mode with its documented test card, never a real card, one purchase, each request once, emails only to inboxes the business controls, no load. If any response shows a real buyer's details, stop and record it.
    References
    ASVS 5.0 v5.0.0-14.2.1 and v5.0.0-14.2.3; WSTG v4.2 WSTG-ATHZ-04.
  18. G2. Gift cards: balance checks and guessable codes
    Details involved
    Gift card codes and their balances.
    Who should reach them, and who should not
    The holder of a code. Not someone working through codes until one answers.
    Test case
    On the staging copy, issue three test codes one after another and note their length and whether they follow a sequence or a pattern. Then, only where B2 found no real gift cards on the copy, send five balance checks for invented codes, each one character away from a test code, and note whether any limit, delay or refusal appears.
    Expected result
    Codes that cannot be worked out from one another, and repeated misses met with the limit the business has set. OWASP's automated threat OAT-002, Token Cracking, lists voucher, gift card and discount enumeration among its other names and examples.
    Evidence to keep, and the duty or request it may relate to
    The code format, never a live code, the five responses and how any limit behaved.
    Limits of this row
    Staging copy, or the gift card service's documented test mode within the answer B1 records, three test codes issued, payment provider in test mode where issuing one takes a payment, never a real card, five balance checks in all, any emails only to inboxes the business controls, no load. Never try codes against the live site. If a check returns a real card's balance, stop and record it.
    References
    OWASP OAT-002 Token Cracking; ASVS 5.0 v5.0.0-2.4.1; the rate limiting guide.
  19. G3. Gift cards: spending one balance twice
    Details involved
    A gift card's balance and the bookings, reservations or orders it pays for.
    Who should reach them, and who should not
    One spend for each unit of balance.
    Test case
    Give guest-a a test gift card that covers one booking or deposit. Set up three checkouts, each spending the full balance, and send all three at nearly the same moment, a single time.
    Expected result
    One checkout succeeding and the balance never below zero. Among the indicators of vulnerability in WSTG-BUSL-10 are negative balances after concurrent debits.
    Evidence to keep, and the duty or request it may relate to
    The three responses, what was created, and the balance afterwards.
    Limits of this row
    Staging copy, or the gift card service's documented test mode within the answer B1 records, payment provider in test mode, never a real card, guest-a only, three submissions sent once, emails only to inboxes the business controls. The three submissions check timing, not how the site copes with load. If any response shows a real person's details, stop and record it.
    References
    WSTG-BUSL-10, Race Conditions; the race conditions guide.
  20. M1. Refunds: cancellations by the guest
    Details involved
    The amount paid, the cancellation policy, the refund due and the payment reference.
    Who should reach them, and who should not
    The guest, for the amount the policy sets. Nobody gets back more than was paid.
    Test case
    Write the policy's outcome first for the test dates you will use. As guest-a, in test mode, cancel one paid test booking through its modification link and compare the refund with the policy. Send the cancel request a second time. Where a refund amount or a percentage travels in the cancel request, change it once on a second test booking. On a third, change the booking to a cheaper rate, then cancel it.
    Expected result
    Each refund equal to what the policy sets for those dates, no second refund from the repeated request, the changed amount ignored, and the total refunded on each booking never more than was paid.
    Evidence to keep, and the duty or request it may relate to
    The policy as written, each request, the provider's test dashboard and the bookings' records.
    Limits of this row
    Staging copy, or the booking engine's documented test mode within the answer B1 records, payment provider in test mode with its documented test card, never a real card, guest-a only, three test bookings, each request once apart from the one repeated cancel request, emails only to inboxes the business controls, no load. If any response shows a real guest's details, stop and record it.
    References
    WSTG v4.2 WSTG-BUSL-03 and WSTG-BUSL-06; ASVS 5.0 v5.0.0-2.3.1; the business logic vulnerabilities guide, whose invariants include that the total refunded on a booking never exceeds the total paid on it.
  21. M2. Refunds: staff refunds and returned deposits
    Details involved
    Booking, reservation and event payments, their references, and the guest's or organiser's contact details.
    Who should reach them, and who should not
    The staff roles the business names for refunds, with a second person for refunds above a level the business sets. Not other staff roles, and not guests.
    Test case
    First, read only: in every system that can send money back (the booking engine, reservation platform, event or invoicing tool, gift card service and the payment provider's dashboard), list the roles that can refund and who holds them. Then, on the business's own system in test mode, capture a small partial refund on one of M1's paid test bookings, made by a staff test account allowed to refund, and send that request again from a staff test account without the permission and with no session. Note whether a refund can be sent anywhere other than the original payment.
    Expected result
    Only the named roles succeed, the provider's test dashboard shows no refund from any other request, and refunds go back to the original payment.
    Evidence to keep, and the duty or request it may relate to
    The role lists, each request and response, and the provider's test dashboard. The role definitions test in WSTG v4.2, WSTG-IDNT-01, says sensitive admin functionality should leverage a maker-checker principle, or use MFA to ensure that the administrator is conducting the transaction.
    Limits of this row
    The role lists are read only in every system. Requests only on the business's own system on the staging copy, payment provider in test mode, M1's paid test bookings only, staff test accounts only, each request once, emails only to inboxes the business controls, no load. If any response shows a real person's details, stop and record it.
    References
    WSTG v4.2 WSTG-ATHZ-02 and WSTG-IDNT-01; ASVS 5.0 v5.0.0-8.2.1 and v5.0.0-2.3.5, a Level 3 requirement.
  22. S1. Payment pages: which scripts load, and who approved them
    Details involved
    Card details typed into the payment fields, and anything else a script on the page can read.
    Who should reach them, and who should not
    Only scripts the business has approved, each for a stated reason.
    Test case
    Read only. List every page in the journey that takes money: the booking payment step, table deposits, event invoices and the gift card checkout, and mark each as on the business's own domain or a vendor's. Load each page on the business's own domain once on the staging copy with the developer tools network panel open, typing nothing into payment fields. For each script host, record its business reason, who approved it, and how its integrity is checked, such as Subresource Integrity, which MDN says enables browsers to verify that resources they fetch are delivered without unexpected manipulation, by providing a cryptographic hash that a fetched resource must match. For a vendor's page, record the vendor and put the question to it.
    Expected result
    Every host on the business's own pages with an owner, a reason, an approval and an integrity method, or a written reason for none. Any host nobody can account for is raised with the owner.
    Evidence to keep, and the duty or request it may relate to
    The dated list of pages and scripts. May relate to: PCI DSS v4.x Requirements 6.4.3 and 11.6.1, which the PCI SSC post says focus on ensuring that payment page scripts are properly authorised, checked for integrity and monitored for tampering. Whether they apply to the business is a question for the acquirer or payment brand, recorded in B1.
    Limits of this row
    Page loads only. Nothing typed into payment fields, no form submitted, and no script removed; removing one is a change for the owner to make.
    References
    MDN Subresource Integrity; OWASP Third Party JavaScript Management Cheat Sheet; PCI SSC post of 10 March 2025.
  23. S2. Payment pages: headers, change alerts and the accounts that can edit them
    Details involved
    The payment pages' response headers, and the accounts that can change what those pages load.
    Who should reach them, and who should not
    Named people who maintain the site, its plugins or apps and its tag manager, and one named person who is told of a change.
    Test case
    Read only. Using the responses from S1's page loads, note each security-related response header by name, such as Content-Security-Policy or Content-Security-Policy-Report-Only. List the accounts that can change what each payment page loads: site administrators, plugin or app installers, tag manager users and the agency. Ask who would be told, and how, if a script or header on a live payment page changed.
    Expected result
    Change alerts reach a named person, and the account list matches the people who maintain the pages today. OWASP's Content Security Policy Cheat Sheet says Content-Security-Policy-Report-Only delivers a policy that is not enforced, and that violation reports are still printed to the console, and delivered to a violation endpoint if the report-to and report-uri directives are used; note which header each page sends.
    Evidence to keep, and the duty or request it may relate to
    Header names and values as read, the alert route and the account list. May relate to: the post's statement that the requirements also address the need for careful management of both scripts and security-impacting HTTP headers to prevent unauthorised changes to webpages. Whether that applies to the business is a question for the acquirer or payment brand.
    Limits of this row
    Read only. Nothing is changed: headers, tags and accounts stay as found.
    References
    OWASP Third Party JavaScript Management Cheat Sheet, on tag managers; OWASP Content Security Policy Cheat Sheet; PCI SSC post of 10 March 2025.
  24. Z1. Significant change: when to run rows again
    Details involved
    Whatever the change touches.
    Who should reach them, and who should not
    The owner decides; the developer, agency or vendor names each change before it ships, where it can.
    Test case
    Planning. For each change below, run its rows again on the staging copy, ideally before the change goes live, otherwise as soon after release as you can. A new booking engine, channel manager or property system: A1 to A7 and S1. A new reservation platform: R1 to R4 and S1. A new event enquiry, proposal or invoicing tool: E1 to E3. A new gift card service: G1 to G3 and S1. A new payment provider, or a change to how a payment page takes the card: S1, S2, R4, E3 and M1. A new script, tag or tag manager change on any booking or payment page: S1 and S2. A change to confirmation, reminder or pre-arrival emails: A5, A7, R1 and R2. A changed cancellation, deposit, capacity or refund policy: A2, R3, R4, M1 and M2. A change of agency, developer or host, or new staff roles in any system: every row, starting with B1 and A3.
    Expected result
    Every change the business logs is matched by a dated rerun of its rows and the results.
    Evidence to keep, and the duty or request it may relate to
    What changed, which rows were rerun, on what date and against which build. May relate to: PCI DSS compliance validation, which the PCI SSC's Merchant Resources FAQ directs to the acquirer (merchant bank) or payment brand; this page sets no testing or scanning schedule.
    Limits of this row
    Planning only. Each rerun row keeps its own limits.
    References
    This page's own list; PCI SSC Merchant Resources FAQ.
  25. Z2. Clean-up
    Details involved
    Everything the run created.
    Who should reach them, and who should not
    Records in each system are removed by that system's owner.
    Test case
    List every test booking, reservation, enquiry, event, rooming list, note, gift card, refund and test account the run created, each carrying the marker, and each vendor test account that received any of them. Remove them on the staging copy, and ask each vendor or system owner to remove them from its system.
    Expected result
    No record carrying the marker remains, or each one that does is listed with who removes it and when.
    Evidence to keep, and the duty or request it may relate to
    The clean-up list with dates.
    Limits of this row
    Deletes only records that carry the run's marker.
    References
    This page's own list.
  26. Z3. The evidence pack and the duties or requests it may relate to
    Details involved
    The run's records, redacted.
    Who should reach them, and who should not
    The pack stays with the owner, who decides who may see it.
    Test case
    Planning. Gather into one pack: B1's dated terms and answers, B2's readings, each row's redacted requests and responses with the build and date, the lists from A3, A6, A7, R2, S1, S2 and M2, Z1's change log and Z2's clean-up list.
    Expected result
    Every item carries its date, its holder and who may see it.
    Evidence to keep, and the duty or request it may relate to
    May relate to: APP 11.1 to 11.3 of the Privacy Act 1988, if the Act covers the business; the Notifiable Data Breaches scheme, as the OAIC explains it, if a breach occurs; PCI DSS validation, which the PCI SSC's Merchant Resources FAQ sends to the acquirer or payment brand, and PCI DSS v4.x Requirements 6.4.3 and 11.6.1 as the PCI SSC post describes them (S1, S2); and security questionnaires from corporate clients and insurers' forms, covered by the security questionnaires and cyber insurance checklist guides. Whether any of these applies is for the owner to establish with their own privacy adviser and, for card payments, the acquirer or payment brand.
    Limits of this row
    No password, key, secret, card number or real guest record goes in the pack.
    References
    Privacy Act 1988, Compilation No. 104; OAIC, About the Notifiable Data Breaches scheme; PCI SSC Merchant Resources FAQ; PCI SSC post of 10 March 2025.

What hospitality cyber security covers on the web

A guest can book a room, change the dates, reserve a table for the first night, ask about a function for forty people and buy a gift card for a friend without speaking to anyone.

Each of those steps can leave the guest's details somewhere: in a booking engine, a channel manager, a reservation platform, an inbox, a rooming list spreadsheet, a payment provider's records. Seen from the web, hospitality cyber security means tracing those copies: where each one sits, which people and systems can reach it, and which links and pages open it. Hospitality data breach prevention, in the part a website controls, starts with that map.

Much of the software involved can belong to someone else. Where a booking engine, channel manager, reservation platform or gift card service is bought in, it is its vendor's product, and how it works inside is for the vendor to describe.

What the business sets is the part around it: what its own website collects and where each form sends it, the links its confirmation emails carry, which staff and outside parties hold accounts in each system, the scripts on its booking and payment pages, and its rules for deposits, cancellations and refunds. This guide tests that part, and the business's side of each handoff to a vendor's system.

It is written for the owner, general manager, operations manager or technical lead of a hotel, motel, holiday park, bed and breakfast, restaurant, café or events venue, and for the developer or agency who looks after its website. Accommodation, restaurant and event workflows each get their own rows in the checklist, because each can put different details in different places.

It is not legal advice, and it stops at what a browser or an API can reach: the office network, staff devices, guest Wi-Fi and in-venue card terminals are left out.

Where guest details travel in an accommodation, restaurant or event business

A business may run accommodation, restaurant and event workflows from one website, or only one of them.

The subsections below take each workflow in turn, then gift cards and refunds, which can cross every workflow. Each names the details a step carries and the checklist rows that test it.

Hotel website security: direct bookings, channel managers and modification links

A direct booking can carry the guest's name, email address and phone number, the arrival and departure dates, the number of adults and children, the room and rate, any special requests, and a payment or deposit reference. 2 min read

Restaurant website security: reservations, notes and deposits

A table reservation can be small: a name, a phone number or email address, a party size, a date and time, and a notes field. 1 min read

Event enquiries, proposals and guest lists

An event can start as an enquiry: an organiser's name, company, email address and phone number, a date, guest numbers, a budget, dietary and accessibility requirements and, where the form allows it, an attachment such as a floor plan or a draft run sheet. 1 min read

Gift cards and refunds, across rooms, tables and events

A gift card is a balance behind a code. 1 min read

Where access breaks in a guest journey, and the guide that covers it

Each kind of failure has its own guide in this library.

This section names the step, the failure and the guide, and leaves the test case to the checklist.

  • Booking and reservation lookups. A confirmation page, invoice or manage-booking screen that opens a booking by its reference, without checking that the person asking is the guest who made it, lets anyone holding another reference open that booking. That is an insecure direct object reference, and the broken access control and IDOR guide explains it and gives a two-account test matrix. OWASP's IDOR Prevention Cheat Sheet treats replacing enumerable numeric identifiers with more complex, random ones as an additional defence-in-depth measure, and says access control checks are essential even with complex identifiers.
  • Modification and cancellation links. A link that never stops working, still works after a cancellation or opens a different booking when its reference changes is a weakness in how the link is issued or checked. OWASP's Forgot Password Cheat Sheet says reset tokens and codes should be generated with a cryptographically secure random number generator, be long enough to protect against brute-force attacks, be linked to an individual user in the database, be invalidated after they have been used and be stored securely, and its quick reference adds that they should be single use and expire after an appropriate period. A manage-booking link is not a password reset and can be opened more than once, so holding it to the properties that fit is this page's choice. The broken authentication guide sets out rules for reset links, and the session management guide covers how a session identifier should be issued and ended.
  • Tokens carried in addresses. In OWASP's Session Management Cheat Sheet, session ID exchange mechanisms where the ID is included in the URL might disclose the session ID in web links and logs, web browser history and bookmarks, the Referer header or search engines. On this page's reading, a booking token in a link's address can travel the same routes, and row A5 also checks whether any request the manage-booking page sends to a third-party host carries it. Requirement v5.0.0-14.2.1 of ASVS 5.0, at Level 1, asks that sensitive data is sent to the server only in the HTTP message body or header fields, and that the URL and query string do not contain sensitive information, such as an API key or session token.
  • Dietary, allergy and accessibility notes. A note that appears in a page address, in a request to an analytics or advertising host, or in a screen or export open to staff who do not act on it has reached people and systems with no use for it. ASVS 5.0 requirement v5.0.0-14.2.3, at Level 2, asks that defined sensitive data is not sent to untrusted parties, such as user trackers, to prevent unwanted collection of data outside of the application's control. Which data the business defines as sensitive for that requirement is its own decision, and this page does not make it. The sensitive data exposure guide covers what responses and exports should hold, and where a personal response can end up stored.
  • Rooming lists and enquiry attachments. An upload that accepts any file, or a stored file served to any request that knows its address, is the ground of the file upload security guide. Where names and notes typed by guests or organisers are exported to a spreadsheet for staff, the checklist adds a spreadsheet check. OWASP's CSV Injection page says that when a spreadsheet program such as Microsoft Excel or LibreOffice Calc is used to open a CSV, any cells starting with = will be interpreted by the software as a formula.
  • Capacity, held rooms and balances. Two bookings for the last room, three reservations for a sitting with room for one more party, or two spends of one gift card balance at the same moment are where race conditions show up, and the race conditions guide covers them. WSTG-BUSL-10, in the edition of OWASP's Web Security Testing Guide that the OWASP site labels Latest and says may frequently change, read on 15 November 2026, names one-time-use tokens or codes, with coupons, gift cards and referral bonuses as its examples, and resource allocation with limited availability, with inventory, seats and registrations as its examples, among the cases where race conditions are particularly impactful. Holding rooms or tables without paying is a question of how often a flow can be used, which the business logic vulnerabilities guide introduces through OWASP's API6:2023 and leaves to the rate limiting guide.
  • Staff accounts in many systems. A front desk can work across a booking engine, a channel manager, a reservation platform, a payment dashboard and the website itself, each with its own accounts. Shared logins and accounts left open after someone leaves are access questions the business answers for itself. The credential stuffing guide covers what multi-factor sign-in changes for a login, and the MFA security guide covers the paths around a second factor.
  • Refunds. A refund sent from a role that should not hold the permission is a vertical access failure, covered in the broken access control guide. A refund larger than what was paid, or a second refund on a booking already refunded in full, breaks a business rule, and the business logic vulnerabilities guide writes "the total refunded on a booking never exceeds the total paid on it" as one of its invariants.
  • Payment page scripts. OWASP's Third Party JavaScript Management Cheat Sheet says that when third-party code is executed, the third party is granted the exact same privileges that were granted to the user, similar to XSS attacks, and that the content a tag manager returns can be dynamically changed by host site employees, such as the marketing part of the business. Third-party code in general is the supply chain attacks guide's subject, and the payment page section below describes what rows S1 and S2 record about each payment page.

Dietary, allergy and accessibility notes: what the Privacy Act text says, and what it leaves to you

A notes field is the smallest part of a booking form, and what goes into it is up to the guest.

Whether a given note is treated differently in law is a question this page does not answer, because the answer depends on the note, the business and whether the Privacy Act 1988 applies to the business at all. What the page can do is set out the text.

Section 6(1) of the Act defines personal information as information or an opinion about an identified individual, or an individual who is reasonably identifiable, whether the information or opinion is true or not, and whether it is recorded in a material form or not.

Its definition of sensitive information includes information or an opinion about an individual's racial or ethnic origin, or religious beliefs or affiliations, among other listed matters, that is also personal information, and it includes health information about an individual.

Section 6FA says health information includes information or an opinion about the health, including an illness, disability or injury, (at any time) of an individual, that is also personal information, and goes on to further categories.

Where the Australian Privacy Principles apply, APP 3.3 says an APP entity must not collect sensitive information about an individual unless the individual consents to the collection of the information and, if the entity is an organisation, the information is reasonably necessary for one or more of the entity's functions or activities (the clause sets a different test for an agency), or subclause 3.4 applies in relation to the information.

Whether an allergy, a meal choice, a mobility need or a request for a hearing loop falls inside any of these definitions, and what follows for the way a form asks for it, is for you to settle with your own privacy adviser.

For testing only, the checklist gives every note the same care: rows A7, R2 and E1 use invented notes or details, check whether they reach a page address or a third-party request, and record where they land and who can read them. That record is evidence for the conversation with your adviser, not a classification.

Payment pages in a booking flow, and PCI DSS Requirements 6.4.3 and 11.6.1

A hospitality business can take money on several pages: the booking engine's payment step, a table deposit, an event invoice and a gift card checkout.

Some of those pages can sit on the business's own domain with the payment provider's fields inside them, and some can belong entirely to a vendor. Row S1 starts by listing which is which, because a script on a vendor's page is a question for that vendor, and a script on the business's own page is a question for whoever maintains it.

The PCI Security Standards Council's post of 10 March 2025, announcing its information supplement "Payment Page Security and Preventing E-Skimming", says PCI DSS v4.x includes Requirements 6.4.3 and 11.6.1, which aim to reduce the risk during e-commerce transactions, and that these requirements focus on ensuring that payment page scripts are properly authorised, checked for integrity and monitored for tampering.

It says they also address the need for careful management of both scripts and security-impacting HTTP headers to prevent unauthorised changes to webpages, whether in the server environment or as rendered in the consumer's browser.

The same post says the Council does not enforce compliance or determine whether specific implementations are compliant, and that entities should collaborate with the organisations managing their compliance programmes, such as acquirers or payment brands, to understand any specific compliance validation and reporting responsibilities.

The Council's Merchant Resources FAQ says PCI DSS is intended for all entities involved in payment processing, including merchants, regardless of their size or transaction volume, and that whether a small merchant is required to validate compliance is determined by the individual payment brands.

For questions regarding compliance validation and reporting requirements, it says merchants should contact their acquirer (merchant bank) or the payment brand they do business with, as applicable. This page does not say whether either requirement, or PCI DSS as a whole, applies to a booking flow that hands the card to a provider's page or fields.

Row B1 puts that question in writing to your acquirer or the payment brand, the contacts the FAQ names for questions on compliance validation and reporting requirements, and asks your payment provider which parts of card handling it takes on. Rows S1 and S2 collect the script and header record to take to that conversation.

Card details can also reach a business away from a payment page: typed into a booking notes field, an event enquiry or a reply to a confirmation email. Rows R4 and E1 read each form's labels and help text for anything that invites a card number. How card details that arrive outside a payment page should be handled is another question for your acquirer or the payment brand.

Booking engine security testing: your side of the handoff

Some questions in a hospitality journey are settled business by business, not by a guide.

What each booking engine, channel manager, reservation platform, gift card service and host permits by way of security testing is in its own terms, and where the terms leave doubt, the vendor answers in writing. What the payment provider takes on comes from the provider, and how the business's card payments are validated comes from its acquirer or the payment brand.

And whether the Privacy Act covers the business is a question for its own adviser. Row B1 records each answer, with its date, before any row sends a request. Nothing on this page describes what any vendor permits.

Within that, booking engine security testing on this page means the business's side: its own pages that link to or embed the engine, what those pages send to it, the confirmation emails and links that come back, and the accounts the business's staff hold.

Every checklist step that touches a vendor's system runs only within the vendor's written answer recorded in B1, and only in a test mode or test property the vendor's own documentation describes.

Changing references, replaying requests and sending altered messages are the steps to name when you ask, and each row that can touch a vendor's system says so in its limits.

Duties and buyer requests that may bear on a hospitality business

Each statement below is what its source says and who it covers.

Whether it applies to your business is for you to establish: with your own privacy adviser for the Privacy Act, and with your acquirer or the payment brand for card payments.

Whether the Privacy Act 1988 covers the business

Section 15 of the Act says an APP entity must not do an act, or engage in a practice, that breaches an Australian Privacy Principle, and section 6(1) says APP entity means an agency or organisation. 1 min read

APP 11 and the copies a guest journey leaves

Where the Act applies, APP 11.1 says that if an APP entity holds personal information, the entity must take such steps as are reasonable in the circumstances to protect the information from misuse, interference and loss, and from unauthorised access, modification or disclosure. 1 min read

Notifiable data breaches

The OAIC explains how the Notifiable Data Breaches scheme applies to entities covered by the Privacy Act 1988: under the scheme, an organisation or agency covered by the Act must notify affected individuals and the OAIC when a data breach is likely to result in serious harm to a person whose personal information is involved. 1 min read

Questionnaires from corporate clients and insurers

A company booking accommodation or functions for its staff, or an insurer at renewal, can send its own security questions. 1 min read

How to run the guest-journey checklist

A manager can work through the read-only rows without help; the rows that send requests are for a developer or tester.

Keep one copy per business, in a spreadsheet, and mark a row not applicable where the business does not have that step, rather than leaving it blank.

  • Rows B1 and B2 come first. Nothing that sends a request runs until B1 holds a dated answer for every system the row touches and B2 confirms the staging copy, the test modes and the test identities.
  • Test only your own systems: your own website, on a staging copy where one exists, and a vendor's system only in a test mode or test property its own documentation describes, within the written answer B1 records.
  • Use invented people only: guests guest-a and guest-b, organisers org-a and org-b, and a staff test account in each role the rows name. Every confirmation, reminder, text message, gift card and refund notice goes to an inbox or phone number the business controls. Never use a real guest's booking, and never a real card.
  • Keep to each row's cap. The bursts in A2, R3 and G3 are three near-simultaneous requests, sent a single time. Nothing in the checklist measures how much traffic a site or a vendor can take.
  • Write the expected result before you send anything, from your own rules: the rate plan, the cancellation and deposit policy, the capacity of each sitting, the gift card terms and the refund permissions. Where nobody can say what the rule is, settle it with whoever owns it before the row runs.
  • Change one thing per request, keep each request and response with names, contact details and tokens redacted, and read the stored booking afterwards as well as the response.
  • If any response shows a real guest's details, stop that row, record the request, open nothing further and tell the owner.
  • Rows marked read only change nothing: they read settings, lists, terms and documents. Leave passwords, keys and signing secrets out of every record. Where a row needs to know that one exists, ask whoever manages it for the setting's name rather than opening a screen that shows it.
  • Links that work for whoever holds them, such as modification, invoice, share and gift card links, are opened only for the invented records and are never pasted into the evidence.
  • End the run with the Z2 clean-up, then gather the results into the evidence pack Z3 describes.

Which rows send requests

Rows B1, A3, S2, Z1 and Z3 are read only. B2 reads settings and then creates the test identities, S1 loads pages without typing into payment fields or submitting anything, and Z2 deletes only records carrying the run's marker. Every other row signs in, submits a form or changes a request, and carries its own limits in the seventh column.

When to run rows again

A clean run describes the site and its connections on the day it ran. Row Z1 lists the changes this page treats as significant for a hospitality business, each with the rows it reruns: a new booking engine, channel manager, property system, reservation platform, event tool, gift card service or payment provider, or a change to how a payment page takes the card; a new script or tag on a booking or payment page; a change to the confirmation, reminder or pre-arrival emails that carry links and notes; a changed cancellation, deposit, capacity or refund policy; and a change of agency, developer or host, or new staff roles in any system.

What a guest-journey review cannot show

A completed checklist records what was tried, on which copy, on which day.

It stops at these edges.

  • Whether the live site behaves like the staging copy. A copy can carry different settings, scripts and connections, and a clean result covers what the copy carried on the day.
  • What happens inside a booking engine, channel manager, reservation platform, gift card service or payment provider. Each is tested only as far as its own terms allow, and the checklist records what the business sends to each and who owns it.
  • Whether a script on a booking or payment page changes after it was read. S1 records the scripts on the day, and S2 records who would be told of a change.
  • That a timing gap is closed. A burst in A2, R3 or G3 that behaves as expected shows how the site handled those requests on that day, not that no gap exists.
  • How guest details are handled once printed, read out at the front desk or pinned up in the kitchen. The checklist follows the website, its emails and its exports.
  • Whether the site or any vendor's system has already been compromised. That is incident response work, and the hacked website guide covers the first hour.
  • Whether any duty applies to the business. Where a row's evidence cell names what a record may relate to, that is a pointer, not a finding: whether a duty applies is settled with your privacy adviser and, for card payments, your acquirer or the payment brand.

Hotel and restaurant website security testing with Clever Ops

Clever Ops tests what guests and staff reach through a browser or an API, and which service fits depends on what the business runs itself.

A brochure site that links to or embeds a vendor's booking engine or reservation widget suits the website security check: an external review of what anyone on the internet can see without logging in, including certificates and transport security, security headers, cookie settings, exposed files and admin paths.

It does not look behind a login. A hosted booking page on a hostname that points at another business's service stays out of the check's scope unless that business agrees.

A WordPress site suits the WordPress security audit, which follows each role that can log in and checks the installed plugin and theme versions with evidence; WooCommerce stores and member sites add customer accounts, orders and checkout pages to its scope. Where one site spans more than one service, such as a WordPress site with a custom booking plugin, the scoping call combines them.

A booking, reservation or event application built for the business, with guests or staff signing in, falls under the web application and API penetration test. That test signs in as each role and checks what each role can see and change, whether one guest can reach another guest's records, authentication and sessions, payment and billing flows, file uploads, the API called directly rather than only through the screens, and the business rules the application is meant to enforce.

On the payment side, the test covers the application's part of the payment, not the payment provider's platform, and uses a staging copy linked to a non-live payment account wherever one is available, so no real card is charged.

Some of the work goes elsewhere. Services run by other businesses, such as a booking engine, channel manager, reservation platform or the payment provider's platform, stay out of scope unless their owner agrees. Clever Ops is not a PCI Approved Scanning Vendor or a Qualified Security Assessor, so PCI DSS external scans and assessments are referred to providers that hold those roles.

Work for a tender or corporate client contract that requires a CREST-accredited provider is also referred: Clever Ops is not CREST accredited, so we refer that work to a provider that is.

Work on internal networks, servers and staff devices goes to a network specialist, and load or denial-of-service testing to a load-testing specialist with the host's written approval.

A site that may already be compromised needs an incident response specialist first. Clever Ops does not provide incident response or malware cleanup; an audit can follow once the cleanup is done.

Where Clever Ops built or hosts the site, the same work is a security review rather than an independent test, and the report names the builder and the host. Either way, the report is evidence for someone else's decision, such as a customer's or an auditor's, and it is not a certificate.

Bring the filled-in checklist to the scoping call: it shows which steps the business runs itself, which systems it hands guests' details to and which terms are already answered, which is what a scope needs.

Frequently asked questions

Only on the parts that are yours, and your side of the handoff. A bought-in booking engine, channel manager or reservation platform belongs to its vendor, and what it permits by way of security testing is in its own terms, which this page does not describe. Read them, ask the vendor in writing where they leave doubt, and record the answer in row B1. Every checklist step that touches a vendor's system, including making test bookings there, waits for that written answer and then runs only in a test mode or test property the vendor's documentation describes. Name the steps that go furthest, such as changing references or replaying requests, when you ask.

This page does not decide that. Section 6(1) of the Privacy Act 1988 includes in its definition of sensitive information health information about an individual, and information or an opinion about an individual's religious beliefs or affiliations, among other listed matters, that is also personal information. Section 6FA says health information includes information or an opinion about the health, including an illness, disability or injury, (at any time) of an individual, that is also personal information. Whether a particular note falls within either, and whether the Act covers your business at all, are questions for your privacy adviser. For testing, the checklist gives every note the same care.

Not this page. For questions regarding compliance validation and reporting requirements, the PCI Security Standards Council's Merchant Resources FAQ says merchants should contact their acquirer (merchant bank) or the payment brand they do business with, as applicable, and it says whether a small merchant is required to validate compliance is determined by the individual payment brands. Ask in writing, including how a booking engine, table deposit or gift card checkout that hands the card to a provider fits, and which parts of card handling the provider takes on. Keep the answer with row B1.

As long as the business decides, and the checklist tests that the decision holds. OWASP's Forgot Password Cheat Sheet says reset tokens and codes should, among other things, be linked to an individual user in the database, and its quick reference adds that they should expire after an appropriate period. A manage-booking link is opened more than once and is not a reset link, so using the properties that fit as a yardstick is this page's choice. Write the rule down, such as no changes after a cancellation, after a newer link is sent or once the stay has ended, and row A5 checks each part of it. A link that can still change or cancel a booking after the rule says it stops is a finding.

It depends on what the business runs itself. If guests book through a vendor's engine or widget and only the business's own editors sign in to its site, the website security check covers what anyone can see from outside, and hostnames that point at the vendor's service stay out of scope unless the vendor agrees. A WordPress site suits the WordPress security audit. A booking, reservation or event application built for the business, with guests or staff signing in, needs the web application and API penetration test. The checklist shows which steps you run yourself, which is what the scoping call starts from.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.