The scenario

An airport publishes flight and baggage information while coordinating a much wider operational picture. In Vulnverse v2, Airport Operations gives an exercise those separate perspectives: passenger-facing routes, vendor workflows, gate assignments, baggage metadata and fuel records. The useful question is how much operational context a public surface reveals and which records belong behind a different access boundary.

Start with the information a passenger or supplier would reasonably see. Then use the private inventory to distinguish a public flight status from the operational records that support it. The scenario supplies a vocabulary for that investigation without connecting to a working airport.

Public surfaces

Passengers, vendors and baggage services reach the airport through these routes; the configured exercise inventory sets the actual scope.

Public routes declared in the Airport Operations catalog
RouteSurfaceContext
/passenger-portalPassenger information and airport services portal.
/flightsflight-infoFlight status and gate information facade.
/vendorsvendor-portalAirport vendor and tenant workflow surface.
/baggagebaggage-statusBaggage tracking status API simulation.

Private systems

ops-control Private application

Airport operations control data representation.

gate-scheduling Private application

Gate assignment and turnaround workflow data.

baggage-sortation Private application

Baggage sortation system metadata.

fuel-inventory Private data

Fueling inventory and service records.

Exercise questions

  • Which flight, gate and baggage details belong in passenger information, and which would reveal internal operational context?
  • What should distinguish a vendor view from airport operations access when both refer to the same terminal activity?
  • Can an investigator explain a public status observation using the relevant gate, baggage or operations artifacts without assuming every timestamp describes a live event?

What to hand in

Produce a surface inventory grouped by passenger, vendor and operations access. Attach the exact route or artifact behind each observation and identify the boundary to examine in the configured exercise.

Records and evidence

Flights and gates establish the public context. Baggage events and vendor records widen the investigation; fuel records and operations logs provide the internal perspective. Organize the evidence around the information each audience needs for its task.

  • flights
  • gates
  • baggage-events
  • vendors
  • fuel-records
  • ops-logs

Record each Airport Operations finding with the research method →