The planned scenario
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 reference routes describe possible entry points in the scenario model. They are not live customer services or a guarantee of the routes in a particular product release. Use your configured exercise inventory as the authoritative 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
These service names and segments describe the internal context of Telecom Provider. They help define exercise boundaries and interpret the generated records.
provisioning-apiSIM and eSIM provisioning API in private app subnets. Catalog segment: private application.
cdr-eventsCall detail record and event simulator data plane. Catalog segment: private application.
device-inventoryInternal inventory and device lifecycle service. Catalog segment: private data.
Configure your exercise
Choose a question for the assignment and define the evidence participants should collect.
- 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, service lines, invoices, support tickets and device records give the exercise a shared business context. Identify the records and observations that support each finding.
customersinvoicesticketssim-orderscdr-eventsdevice-inventorystaging-artifacts
Preserve the scenario and product version, the record or observation, and its source with each finding. Distinguish what a participant observed from what the reviewer inferred. Use synthetic data and your defined evidence-retention rules.
Public self-service at launch
Managed Verse is planned for 1 January 2027. Users will create an account, choose a scenario and configure their own authorized exercise boundaries. Vulnverse will host and operate the platform and cloud; users will not need to provision or maintain an exercise cloud.
Managed Verse is planned to replace all previous services. All new inquiries are paused during the transition. Read Managed Verse →.