The scenario

In Vulnverse v2, Rail Operator combines passenger information with a separate view of operational systems. Public routes represent passenger information, tickets, train status and vendor maintenance. Private context covers signalling telemetry, crew rosters, asset maintenance and yard inventory.

A suitable exercise asks how public service information and supplier work relate to internal operations without assuming they share access rights. Participants can inventory visible routes, identify the synthetic records they expose, and explain the boundary between a service alert and the maintenance or crew context behind it.

Public surfaces

Passengers and maintenance vendors reach the operator through these routes; the configured exercise inventory sets the actual scope.

Public routes declared in the Rail Operator catalog
RouteSurfaceContext
/passenger-infoPassenger information and service alert portal.
/ticketsticketingTicketing and passenger account facade.
/statusstatus-apiPublic train status and station API simulation.
/vendorsvendor-maintenanceVendor maintenance and parts workflow.

Private systems

signalling-telemetry Private application

Signalling telemetry representation.

crew-roster Private application

Crew scheduling and roster data.

asset-maintenance Private application

Rolling stock and track maintenance service.

yard-inventory Private data

Yard inventory and equipment location data.

Exercise questions

  • Which details belong in a public service alert, and which should remain in crew or maintenance records?
  • How should vendor maintenance context be limited relative to the wider asset and yard inventory?
  • Can an investigator distinguish ticket or passenger information exposure from operational telemetry context?

What to hand in

Write an information boundary report organized around passengers, vendors and internal operations. Include supporting records and limit operational impact claims to the observations recorded during the exercise.

Records and evidence

Stations, service alerts and tickets form the passenger context. Crew rosters, maintenance orders and yard assets supply the operational perspective. Use both groups to explain where passenger information ends and internal staffing, maintenance and equipment context begins.

  • stations
  • service-alerts
  • tickets
  • crew-rosters
  • maintenance-orders
  • yard-assets

Record each Rail Operator finding with the research method →