The scenario
In Vulnverse v2, a telecom customer interacts with a portal while internal services manage provisioning, billing, support and device inventory. The scenario connects those perspectives through synthetic customer, connection and device records.
Study which role should see each record, how a customer request passes between systems and how a simulated support decision can cross an information boundary.
Public surfaces
These routes serve customers, billing and support, plus a network operations dashboard; the configured exercise inventory sets the actual scope.
| Route | Surface | Context |
|---|---|---|
/ | customer-portal | Customer login, plan management, invoices and account profile simulation. |
/billing | billing | Invoice, payment and billing support workflow. |
/support | support-crm | Support desk surface with customer ticket context. |
/noc | noc-dashboard | Network operations dashboard facade. |
Private systems
provisioning-apiPrivate applicationSIM and eSIM provisioning API.
cdr-eventsPrivate applicationCall detail record and event simulator data plane.
device-inventoryPrivate dataInternal inventory and device lifecycle service.
Exercise questions
- Which customer and service records should each role be permitted to access?
- How does a request connect customer, connection and device context?
- Does a simulated support decision follow the expected verification rule?
What to hand in
Describe the expected information boundary, the observed decision or response, and the evidence supporting your finding.
Records and evidence
Synthetic customers, invoices, support tickets, SIM orders, call detail events, device inventory and staging artifacts give the exercise a shared business context. Identify the records and observations that support each finding.
customersinvoicesticketssim-orderscdr-eventsdevice-inventorystaging-artifacts
Record each Telecom Provider finding with the research method →