Penetration testing on the Gold Coast for ticketing, tour and attraction systems
Clever Ops tests websites, booking systems and APIs for Gold Coast businesses remotely, from its base in Gippsland, Victoria.
This page takes an invented Gold Coast attraction and turns the rules its ticketing system enforces, from timed entry and weather changes to reseller vouchers, gift cards, waivers and group check-in, into test cases, each with the account that runs it.
On this page
Ticketing business-logic test cases for an invented Gold Coast attraction
Synthetic: the operator, its rules and its accounts were invented for this page. Find the feature your system shares, read the rule, and run or commission the test case with the account named.
How to use itHide the instructions
Accounts are ticket holders A and B (synthetic ticket holders on staging), group leaders GL-A and GL-B, gate staff, the duty manager, and reseller keys RV-1 and RV-2. OWASP references are WSTG v4.2 test ids, ASVS 5.0 requirement ids in the v5.0.0 form and OWASP API Security Top 10 2023 ids, attached only where that page covers the case; the rest are marked "Extra, no OWASP id". Payments run on a non-live payment account and every message goes to a capture inbox.
36 rows
Feature and rule
Test case
Timed entry: no session sells past its capacity
- Test case
- With two places left in a test session, buy them from two accounts at the same moment, and send one request for more tickets than remain.
- Account that runs it
- Ticket holders A and B
- OWASP reference
- ASVS v5.0.0-2.3.4; ASVS v5.0.0-15.4.2
- What a failure would let someone do
- Put more people at the gate than the session holds, leaving refunds or turned-away guests on the day.
Timed entry: places held at checkout return to sale if payment is not completed
- Test case
- Start checkout for every remaining place in a test session, abandon it, and record whether and when the places return. Repeat the hold a few times to see whether a session can be kept showing as sold out.
- Account that runs it
- Ticket holder A
- OWASP reference
- WSTG-BUSL-04; API6:2023
- What a failure would let someone do
- Keep sessions looking sold out without paying, so paying customers go elsewhere.
Timed entry: the price comes from the session booked
- Test case
- Buy an off-peak ticket, then change the session or price tier to a peak session in the checkout request and in the change-booking request.
- Account that runs it
- Ticket holder A
- OWASP reference
- WSTG-BUSL-02; WSTG-BUSL-03; ASVS v5.0.0-2.2.2
- What a failure would let someone do
- Book peak sessions at off-peak prices.
Timed entry: a child ticket needs an adult ticket on the same booking
- Test case
- Send a booking request with child tickets only, and others with quantities of zero, below zero or with a decimal point.
- Account that runs it
- Ticket holder A
- OWASP reference
- WSTG-BUSL-01; ASVS v5.0.0-2.2.3
- What a failure would let someone do
- Create unaccompanied child bookings the gate has to turn away, and orders with totals the rules never allowed.
Timed entry: a ticket admits once, to its own session, inside its entry window
- Test case
- Scan one test ticket twice, then on two gate devices at the same moment, then outside its session's entry window.
- Account that runs it
- Gate staff, with ticket holder A's ticket
- OWASP reference
- WSTG-BUSL-05; WSTG-BUSL-04; ASVS v5.0.0-15.4.2
- What a failure would let someone do
- Share one paid ticket among several people, or use it for a busier session than the one bought.
Timed entry: only the ticket holder can open a ticket
- Test case
- Change the booking reference or ticket id in the ticket download and booking page requests to ticket holder B's.
- Account that runs it
- Ticket holder A, with ticket holder B's booking reference
- OWASP reference
- WSTG-ATHZ-04; ASVS v5.0.0-8.2.2
- What a failure would let someone do
- Copy someone else's valid ticket, along with their name, email address and phone number.
Timed entry: a ticket is issued only after the payment provider confirms payment
- Test case
- Reach the success page without completing payment, and send the payment notification route a message without a valid signature. Stripe's fulfilment guide says fulfilment cannot rely on the checkout landing page alone.
- Account that runs it
- Ticket holder A, on the non-live payment account
- OWASP reference
- WSTG-BUSL-06; ASVS v5.0.0-2.3.1
- What a failure would let someone do
- Collect valid tickets for unpaid orders.
Weather change: free changes apply only to sessions the duty manager has closed
- Test case
- Send the free-change request for a booking in a session that is still open, and for one in a session that ran yesterday.
- Account that runs it
- Ticket holder A
- OWASP reference
- WSTG-BUSL-02; ASVS v5.0.0-2.3.2
- What a failure would let someone do
- Move any booking for free, or claim weather credit for a fine day.
Weather change: a closed booking gets one free change or one credit, not both
- Test case
- Take the free change, then claim the credit for the same booking; then send two credit claims at the same moment.
- Account that runs it
- Ticket holder A, with the twilight tour booking in the closed test session
- OWASP reference
- WSTG-BUSL-05; ASVS v5.0.0-15.4.2
- What a failure would let someone do
- Collect two lots of compensation for one closure, the second as credit that spends like cash.
Weather change: the old ticket stops working once a booking moves
- Test case
- After moving a booking, scan its old ticket at the gate and try to move the old booking a second time.
- Account that runs it
- Ticket holder A, then gate staff
- OWASP reference
- ASVS v5.0.0-2.3.3
- What a failure would let someone do
- Hold two working tickets for the price of one.
Weather change: a moved booking respects the new session's capacity
- Test case
- Move a closed booking into a session with fewer places left than the booking holds.
- Account that runs it
- Ticket holder A
- OWASP reference
- ASVS v5.0.0-2.3.4
- What a failure would let someone do
- Oversell the next fine day through weather moves.
Weather change: only the duty manager can close a session
- Test case
- Call the close-session route as gate staff, as a ticket holder and with a reseller key.
- Account that runs it
- Gate staff; ticket holder A; reseller key RV-1
- OWASP reference
- WSTG-ATHZ-02; ASVS v5.0.0-8.2.1; API5:2023
- What a failure would let someone do
- Trigger free changes, credits and closure messages for every booking in any session.
Weather change: closure messages go only to the closed session's ticket holders
- Test case
- Close a test session and check whose messages reach the capture inbox; then call the send-messages route a handful of times in a row and record whether any limit applies.
- Account that runs it
- Duty manager
- OWASP reference
- Repeated calls to the send-messages route: API4:2023; ASVS v5.0.0-2.4.1. Extra, no OWASP id: whose messages reach the capture inbox
- What a failure would let someone do
- Message the wrong customers, and run up a text message bill nobody planned for.
Reseller voucher: a voucher is redeemed once
- Test case
- Redeem one test voucher from two ticket holder accounts at the same moment, and again after it has been used.
- Account that runs it
- Ticket holders A and B, with a voucher sold through RV-1
- OWASP reference
- WSTG-BUSL-05; ASVS v5.0.0-15.4.2
- What a failure would let someone do
- Turn one sold voucher into several entries.
Reseller voucher: a reseller sees and cancels only its own vouchers
- Test case
- With RV-1's key, look up, cancel and redeem vouchers RV-2 sold, by changing the voucher id or code in each request.
- Account that runs it
- Reseller keys RV-1 and RV-2
- OWASP reference
- API1:2023; ASVS v5.0.0-8.2.2
- What a failure would let someone do
- Read another reseller's sales, or cancel its customers' vouchers.
Reseller voucher: a voucher buys only the product it was sold for
- Test case
- Redeem an off-peak canopy walk voucher against a peak session or the twilight tour by changing the product in the redemption request.
- Account that runs it
- Ticket holder A, with an RV-1 voucher
- OWASP reference
- WSTG-BUSL-02
- What a failure would let someone do
- Exchange cheap vouchers for dearer experiences.
Reseller voucher: a cancelled voucher stops working
- Test case
- Cancel a voucher with RV-1's key, then redeem it at checkout and scan its ticket at the gate.
- Account that runs it
- Reseller key RV-1; ticket holder A; gate staff
- OWASP reference
- Extra, no OWASP id
- What a failure would let someone do
- Get in on a voucher the reseller has already refunded.
Reseller voucher: a reseller holds no more places than its allocation
- Test case
- Hold places in a test session with RV-1's key beyond its allocation, and leave the holds unpaid.
- Account that runs it
- Reseller key RV-1
- OWASP reference
- API6:2023; ASVS v5.0.0-2.3.2
- What a failure would let someone do
- Use one reseller key to block a day's sessions from direct sale.
Reseller voucher: a reseller key reaches only reseller functions
- Test case
- Call operator-only routes, such as session pricing, refunds and the staff list, with a reseller key.
- Account that runs it
- Reseller key RV-1
- OWASP reference
- API5:2023; ASVS v5.0.0-8.2.1
- What a failure would let someone do
- Let a reseller, or anyone holding its key, change prices or issue refunds.
Reseller voucher: codes cannot be found by guessing
- Test case
- Look across a batch of test voucher codes for a visible pattern, then submit a short run of wrong codes and note whether the application slows, blocks or raises an alert. How codes are generated is confirmed from the code or with the developer.
- Account that runs it
- Ticket holder A
- OWASP reference
- WSTG-BUSL-07; ASVS v5.0.0-2.4.1; ASVS v5.0.0-11.5.1
- What a failure would let someone do
- Find working codes by trial, each one a free entry.
Gift card: a card exists only once its purchase is paid for
- Test case
- Finish a gift card purchase without a confirmed payment, and resend a payment notification for a purchase already fulfilled.
- Account that runs it
- Ticket holder A, on the non-live payment account
- OWASP reference
- WSTG-BUSL-06; WSTG-BUSL-05
- What a failure would let someone do
- Create balances nobody paid for.
Gift card: the balance cannot be spent twice
- Test case
- Apply one test gift card to two checkouts at the same moment, each for more than half its balance.
- Account that runs it
- Ticket holders A and B
- OWASP reference
- ASVS v5.0.0-15.4.2; ASVS v5.0.0-2.3.3
- What a failure would let someone do
- Spend more than the card holds.
Gift card: amounts come from the server, and gift cards cannot buy gift cards
- Test case
- Send a purchase or top-up with a negative, zero or altered amount, and try to pay for a new gift card with an existing one.
- Account that runs it
- Ticket holder A
- OWASP reference
- WSTG-BUSL-01; ASVS v5.0.0-2.2.2
- What a failure would let someone do
- Create value from nothing, or roll balances into new cards against the rules.
Gift card: the balance check is not a code-guessing tool
- Test case
- Call the public balance check repeatedly with wrong codes, signed out and then signed in, and record any delay, block or alert that follows.
- Account that runs it
- No account, then ticket holder A
- OWASP reference
- WSTG-BUSL-07; ASVS v5.0.0-2.4.1; ASVS v5.0.0-11.5.1
- What a failure would let someone do
- Find live card codes and balances by trial and spend them.
Gift card: a refund for a gift card payment goes back to the gift card
- Test case
- Pay for a ticket partly by gift card and partly by card, cancel it inside the refund window, and check where each part of the refund goes; then change the refund destination in the request.
- Account that runs it
- Ticket holder A, on the non-live payment account
- OWASP reference
- WSTG-BUSL-02
- What a failure would let someone do
- Turn gift card value into money on a payment card.
Waiver: no ropes course check-in until every participant has signed the current waiver
- Test case
- Check in a participant with no waiver from the gate app, and mark a waiver as signed by calling its route directly without signing.
- Account that runs it
- Gate staff; ticket holder A
- OWASP reference
- WSTG-BUSL-06; ASVS v5.0.0-2.3.1
- What a failure would let someone do
- Put participants on the course with no signed waiver on file.
Waiver: only the signer and staff can open a signed waiver
- Test case
- Change the waiver id in the download request to one belonging to ticket holder B's participant.
- Account that runs it
- Ticket holder A, with ticket holder B's waiver id
- OWASP reference
- WSTG-ATHZ-04; ASVS v5.0.0-8.2.2
- What a failure would let someone do
- Read another participant's name, date of birth, emergency contact and health answers.
Waiver: a signed waiver cannot be changed
- Test case
- Change the hidden waiver version, a health answer or the signer's date of birth in the submission, and again after signing.
- Account that runs it
- Ticket holder A
- OWASP reference
- WSTG-BUSL-03
- What a failure would let someone do
- Leave a waiver on file that does not match the text shown or the answers given.
Waiver: a participant under 18 needs a guardian's signature
- Test case
- Submit the under-18 participant's waiver without the guardian's details, or change the date of birth after the guardian step.
- Account that runs it
- Ticket holder A, with its under-18 participant
- OWASP reference
- WSTG-BUSL-01; ASVS v5.0.0-2.2.3
- What a failure would let someone do
- Check in a minor on a waiver no guardian signed.
Waiver: names and notes show as text in staff screens
- Test case
- Put a harmless marker in a participant name and notes field, then open the gate app and the waiver admin screen.
- Account that runs it
- Ticket holder A, then gate staff and the duty manager
- OWASP reference
- WSTG-INPV-02
- What a failure would let someone do
- Run script in a staff member's browser, with that staff member's access.
Group check-in: a leader sees only their own group's list
- Test case
- Change the group id in the participant list request to GL-B's group.
- Account that runs it
- Group leader GL-A, with GL-B's group id
- OWASP reference
- WSTG-ATHZ-04; ASVS v5.0.0-8.2.2
- What a failure would let someone do
- Read another school's participant names, children's included.
Group check-in: no more participants than the group paid for
- Test case
- Add one more participant name than the booking holds, check in one participant twice, and check in more people than the list names.
- Account that runs it
- Group leader GL-A, then gate staff
- OWASP reference
- WSTG-BUSL-05; ASVS v5.0.0-2.3.2
- What a failure would let someone do
- Admit extra people on one group booking.
Group check-in: group size and price are fixed once paid
- Test case
- After payment, change the group size, which the screen shows but does not let the leader edit, in the request, and check whether the price or the list changes.
- Account that runs it
- Group leader GL-A
- OWASP reference
- WSTG-BUSL-03
- What a failure would let someone do
- Add unpaid places to a paid group.
Group check-in: gate staff cannot refund, change prices or see sales reports
- Test case
- Call the refund, price and sales report routes with the gate staff account.
- Account that runs it
- Gate staff
- OWASP reference
- WSTG-ATHZ-02; ASVS v5.0.0-8.2.1
- What a failure would let someone do
- Turn a lost or shared gate device into a way to issue refunds.
Session times: confirmations and tickets show Queensland time with the zone named
- Test case
- While New South Wales is on daylight saving, open the booking page, the confirmation email and the ticket on a device set to New South Wales time, and compare each session time with the operator's.
- Account that runs it
- Ticket holder A, New South Wales browser profile
- OWASP reference
- Extra, no OWASP id
- What a failure would let someone do
- No attacker needed: customers from over the border turn up an hour early or late for a session they paid for.
Cut-offs: change and refund cut-offs are worked out on the server in Queensland time
- Test case
- While New South Wales is on daylight saving, send a change just before and just after the cut-off by Queensland time, with the device and any time zone value in the request set to New South Wales time.
- Account that runs it
- Ticket holder A, New South Wales browser profile
- OWASP reference
- WSTG-BUSL-04; ASVS v5.0.0-2.2.2
- What a failure would let someone do
- Make changes up to an hour after the cut-off, while other customers are refused an hour early.
Penetration testing for Gold Coast businesses, delivered from Gippsland
Clever Ops is a small consultancy in Gippsland, Victoria, and its clients are Australian businesses with annual revenue between $1M and $50M.
Nobody from Clever Ops is based on the Gold Coast or anywhere else in Queensland, and it has no office there. A Gold Coast engagement runs online from the scoping call to the retest, against the targets the owner lists in a signed authorisation, and none of it involves anyone coming to your premises.
"Cyber security" on the Gold Coast can mean managed IT, network monitoring or testing. Clever Ops does the last of these, and only for what customers reach through a browser or an API. For website security on the Gold Coast, how deep to go depends on what the site does:
- Website security check, the answer to a request for a website security audit when the site has no customer logins. The tester reads what the site returns to any visitor, such as its certificate and transport settings, headers and cookies, stray files anyone can open, and the software versions it gives away.
- WordPress security audit, for WordPress sites and WooCommerce stores, signed in as each role the site has.
- Web application and API penetration test, for a booking system, customer portal or anything else people sign in to, pay through or redeem codes in. Web application penetration testing is the depth the worked case on this page needs.
- Vibe-coded app security check, for apps made with AI builders, and the AI chatbot and agent security test, for a chatbot that answers customers or changes their bookings.
- Once findings are in, a security fix sprint can follow, then retests.
Work this service does not cover
If your site has been hacked, Clever Ops does not do malware cleanup or incident response. Your host and an incident response specialist come first, and a security audit can follow once the site is clean. Office networks, staff devices, phishing simulations and round-the-clock monitoring sit outside the service as well and go to specialists, and load testing goes to a load-testing specialist with your host's written approval.
Live Shopify storefronts are outside this service too, which matters to an operator that sells gift cards or merchandise through one.
What the published Gold Coast visitor figures show, and what they leave out
The Gold Coast research behind this page is two releases from Experience Gold Coast, each reporting Tourism Research Australia data, opened on 14 November 2026.
Experience Gold Coast was founded in 2023, when five of the city's major entities merged, and it took over the functions of bodies including Destination Gold Coast and Major Events Gold Coast. Its remit is growth in the visitor economy, education, major events and arts and culture. Neither release is about security. They set the scale a Gold Coast ticketing system works at.
- Year ending June 2026, in a release dated 30 September 2026: 14.7 million visitors; 8.9 million domestic day trip visitors and 5.1 million domestic overnight visitors; and 656,000 international visitors. The same release counts 2.2 million domestic overnight visitors from interstate.
- Its chief executive said of that year that visitors are "prioritising day trips over overnight stays, seeking value, and making more deliberate choices about where they spend across dining, attractions and experiences."
- Calendar year 2025, in a release dated 23 March 2026: 14.4 million visitors, including 13.7 million domestic and 682,000 international visitors. Its chief executive said that "new theme park attractions gave visitors new reasons to fall in love with the Gold Coast."
Reading the figures with care
Both releases carry the same footnote: Tourism Research Australia adopted a new domestic tourism data methodology in January 2025, so 2026 domestic figures are not directly comparable with earlier years. Set them against older numbers only with that caveat attached.
The figures do not say how Gold Coast attractions and tour operators sell their tickets, which systems they use, or how often anything goes wrong. This page has not surveyed that. The ticketing features in the worked case belong to an invented operator, so check each one against your own system rather than assume it matches.
For a tester, the scale is the point. Each booking, voucher redemption and group check-in passes through rules somebody wrote down once and the system now enforces without anyone watching. Business-logic testing asks whether it really does.
Why ticketing rules sit at the centre of business-logic testing
The OWASP Web Security Testing Guide (WSTG) v4.2 says business logic flaws cannot be detected by a vulnerability scanner and rely on the skills and creativity of the penetration tester, and that a third-party tester has to ask the business whether different operations should be allowed.
A scanner has no way of knowing that a weather credit is issued once per booking, or that a child ticket needs an adult on the same order. The operator knows, and the tester has to be told.
Ticketing turns up in the standards' own examples. WSTG-BUSL-04 describes a ticketing application that locks or reserves seats pending payment, and asks what happens if an attacker keeps reserving seats without checking out: will the seats be released, or will no tickets be sold?
The OWASP API Security Top 10 gives making a reservation as an example of a sensitive business flow, where an attacker can reserve all the available time slots and prevent other users from using the system (API6:2023).
Requirement 2.3.4 of the Application Security Verification Standard (ASVS) 5.0 asks for business logic level locking, so that limited quantity resources such as theatre seats or delivery slots cannot be double-booked by manipulating the application's logic.
So the work starts with a rules list: each rule written as one sentence the tester can hold the system to, with the account that may break it, if any. The next sections set out that list for the invented operator and the accounts that test it. The table on this page turns each rule into test cases.
The worked case: an invented Gold Coast attraction and what it runs
This operator is synthetic.
It is not a Clever Ops client, it is not modelled on any real Gold Coast business, and no real operator's system is described or tested here. Its booking system, tickets.lab.test, and every feature below were written for this page.
The invented attraction sells a rainforest canopy walk in timed-entry sessions, a guided twilight tour, and a high ropes course that needs a signed waiver from every participant. A web agency built its booking application and API, which a cloud host runs. Payments go through Stripe Checkout. Third-party resellers sell its vouchers on their own sites and redeem them through a reseller API.
Its marketing site runs on WordPress, with Book Now buttons that hand visitors to the booking application, and some of its tours collect customers from pickup points over the border in New South Wales.
What the test reaches, and what it leaves to other businesses
In scope: the booking application and its API, the API behind the staff gate app, the reseller redemption API and the WordPress marketing site, tested on a staging copy linked to a non-live payment account. The WordPress site gets the WordPress security audit, signed in as each of its roles, rather than the ticketing test cases.
Out of scope, because other businesses own them: Stripe's hosted checkout and platform, the resellers' own websites and systems, the cloud host's platform and the text message provider. Each stays outside the test unless its owner agrees, and its own terms govern the rest. The test covers the operator's side of each connection instead: whether the booking application waits for Stripe to confirm a payment before issuing a ticket, what a reseller key can make the API do, and whether anything limits how many text messages the application can be made to send.
When the ticketing runs on a hosted booking platform
An operator that subscribes to a hosted ticketing or booking platform, rather than running its own application, owns much less of the system. Testing then reaches only what the operator controls: its own website and the pages that send visitors into the booking flow, anything it built on top of the platform, such as a group enquiry form or a custom waiver page, and the exports and integrations it set up itself.
The platform, including its booking pages, staff apps and API, belongs to another business.
It is out of scope unless that business agrees, and the platform's own terms govern whether and how it may be tested.
The rules list is still worth writing down. It is the yardstick for the platform settings you choose, and for the questions you put to the platform provider about how each rule is enforced.
The rules list: six ticketing features in plain sentences
Each feature below belongs to the invented operator, written the way its general manager might describe it.
The test cases in the table hold the system to these sentences.
Timed-entry tickets
Timed entry is where capacity and price meet, so its rules are enforced at the moment of booking and again at the gate.
- Each canopy walk session has a fixed capacity, and no session sells past it.
- Places are held for a set time during checkout and return to sale if payment is not completed.
- Peak sessions cost more than off-peak ones, and the price comes from the session booked.
- A child ticket needs an adult ticket on the same booking.
- A ticket is issued once the payment provider confirms payment, and admits once, to its own session, inside that session's entry window.
Weather-disruption changes
A weather closure turns an ordinary booking into one that is owed something, so the rules about who is owed what carry real money.
- Only the duty manager can close a session for weather.
- Each booking in a closed session may move once, free, to any session with room, or take a credit of the same value, but not both.
- Once a booking moves, its old ticket stops working.
- Closure messages go only to the closed session's ticket holders.
Reseller vouchers
Vouchers are sold by other businesses and honoured by the operator, so the reseller API is a door that other people hold keys to.
- Each reseller has its own API key and an allocation of places in each session.
- A voucher is for one named product, is redeemed once, and stops working when the reseller cancels it.
- A reseller can see and cancel only the vouchers it sold.
Gift cards
A gift card balance is value the operator holds for a customer, so every route that creates or spends it handles money.
- A gift card exists only once its purchase is paid for.
- Its balance can be spent across several bookings, and never below zero.
- A refund for a ticket paid by gift card goes back to the gift card.
- Gift cards cannot be used to buy gift cards.
Waiver forms
A waiver holds personal and health details, and the gate decides who goes on the ropes course by its status.
- Every ropes course participant signs the current waiver before check-in, and a parent or guardian signs for anyone under 18.
- A signed waiver cannot be changed, and only its signer and staff can open it.
Group check-in
Groups put many participants under one booking and one leader, and for a school group those participants are children.
- A school or coach group books as one group with a named leader, who can add participant names up to the number paid for.
- Gate staff check groups in, and cannot refund, change prices or close sessions.
- A leader sees only their own group's list.
The synthetic ticket-holder test account, and the accounts around it
Every test case names the account that runs it.
Ticket holder A is the synthetic account most of the table relies on, set up on staging before testing starts:
- Name: Test Holder A. No real person sits behind the account.
- Contact details: an email address in the tester's capture inbox and a mobile number the tester controls, so nothing is sent to a real customer.
- Participants: one adult, and one participant under 18 whose guardian waiver is signed during the test.
- Bookings: an off-peak canopy walk session, and a twilight tour in a test session the duty manager closes for weather during the test window.
- Payment: the non-live payment account, so no real card is charged.
- Holdings: a gift card with a known balance, and a voucher sold through the test reseller key RV-1.
- Devices: one browser profile set to Queensland time and one set to New South Wales time, for the time-window cases.
The other accounts in the table
Reset, lockout and deletion checks run only on these test accounts and their test records, where the rules of engagement allow them, and destructive actions are off by default for real people's accounts and records that existed before the test. Test sessions, vouchers, gift cards and accounts are tracked as they are created, then removed or listed in the report for the operator's team to remove.
- Ticket holder B: the same set-up with different records, so every access test runs in both directions between two people in the same role.
- Group leaders GL-A and GL-B: two synthetic school groups with made-up participant names.
- Gate staff: the check-in role used on the gate app.
- Duty manager: the role that closes sessions and issues credits.
- Reseller keys RV-1 and RV-2: two test resellers, each with a small allocation in the test sessions.
Queensland and New South Wales: a border service and time-window checklist
The NSW Department of Communities and Justice lists Queensland, New South Wales (except Broken Hill and Lord Howe Island), Victoria, the ACT and Tasmania on Australian Eastern Standard Time (AEST), UTC + 10 hours.
Daylight saving is not observed in Queensland. Where it is observed, New South Wales (with the same exceptions) and Victoria move to Australian Eastern Daylight Time (AEDT), UTC + 11.
For 2026 to 2027, the NSW Government gives the dates for New South Wales: daylight saving starts at 2 am AEST on Sunday 4 October 2026 and ends at 3 am AEDT on Sunday 4 April 2027. Between those times, a Gold Coast operator's clock is an hour behind a customer's across the border.
Clever Ops is in Gippsland, and Victoria also moves to AEDT for daylight saving, so the operator's clock and the tester's differ in the same way while it lasts.
The DCJ page notes that the regulation of time is a State Government responsibility. None of this changes what is tested. It changes how a test window, a stop and a handover are written down, and the rules below are ones the operator and the tester set between them:
- Name the scope's clock. The scope and the authorisation use Queensland time, with AEST written after every time, because the operator's sessions, gates and staff run on it.
- Write each window in both zones while daylight saving is on, such as "09:00 to 12:00 AEST (10:00 to 13:00 AEDT)", so nobody converts in their head.
- Restate the windows if the test dates cross a daylight saving change date, so the days after the change carry the right times.
- Agree blackout times and dates in AEST, such as gate opening, the first sessions of the day, school holiday peaks and any announced ticket release, when test traffic stays off the system.
- Name a stop contact on each side, with a phone number and the hours each can be reached written in AEST, and a second contact for the hours the first cannot cover. A request to pause from either side stops testing on that target until both agree to resume.
- Book the weather closure test. Closing a session and sending closure messages runs only on a test session, at a time inside the window the duty manager knows about, with messages routed to the capture inbox.
- Include one cross-border session. If tours collect customers in New South Wales, one test session should do the same, so the tester can see how the system stores and shows its pickup time on each side of the border.
- Decide how customer-facing times are written, such as Queensland time with the zone named on every confirmation, ticket and reminder, and add the test that checks it on a device set to New South Wales time.
- Hand over in both zones. The report walkthrough, the list of test data to remove and the retest dates are each written with their zone, and the removal list goes to a named person on the operator's side.
What a ticketing operator gets back
Each finding is written against the rule it broke, in the operator's own words, with the steps that reproduce it, the account that ran it, its OWASP reference where one applies, and what a failure would let someone do.
Each one carries two ratings, a CVSS v3.1 score and a business-risk rating, because a voucher that can be redeemed twice is a revenue problem before it is a technical one.
Rules that held are recorded too, for the accounts and records tried. "A voucher redeemed from two accounts at the same moment was accepted once" is a statement the evidence supports. "Vouchers cannot be reused" is not, because it claims more than the cases tried.
After fixes, one consolidated retest marks each finding fixed, partially fixed, still reproducible or not retested on a named build, and the report lists the test sessions, vouchers, gift cards and accounts left behind for removal.
If Clever Ops built or hosts the booking system, the same test cases run as a security review rather than an independent test, and the report says who built and who hosts it. When the reader of the report needs independence, choose a provider that neither built nor runs the system.
Frequently asked questions
No. The business runs from Gippsland, Victoria. It has no Gold Coast office and nobody based in Queensland, so Gold Coast work is done online from scoping through to the retest, without site visits.
Only the parts you control: your website, the pages that send visitors into the booking flow, and anything you built on top of the platform. The platform itself belongs to its provider, so it is out of scope unless the provider agrees, and its own terms govern the rest. Read the provider's terms before booking any test that touches it.
Payments are tested against a non-live payment account where one is available, so no real card is charged. Nothing is sent to a real customer: confirmation, reminder and weather messages go to a capture inbox or to numbers the tester controls, and session closures run only on test sessions.
No. Clever Ops does not do malware cleanup or incident response. Contact your host and an incident response specialist first. Once the site is clean, a website security audit or a penetration test can follow.
A website security audit, which Clever Ops calls a website security check, reads what the site returns to any visitor and suits a site with no logins or payments. Web application penetration testing logs in under each role, such as ticket holder, group leader, gate staff and reseller, and attempts to get the booking system to break its own rules. If customers book, pay, redeem codes or sign waivers on your system, the penetration test is the one that reaches those rules.
The scope names Queensland time as its clock and writes every window, blackout and handover with its zone, giving AEST and AEDT side by side while daylight saving is on. Queensland does not observe daylight saving, so during that part of the year its clock is an hour behind Victoria and New South Wales, apart from Broken Hill and Lord Howe Island.
Live Shopify storefronts are outside this service. Gift cards sold through an operator's own booking application, like the ones in the worked case, can be in scope.
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.