The scenario

A hosting provider combines its own operational surface with the applications it hosts for customers. In Vulnverse v2, this scenario makes that distinction visible through a provider portal, hosted storefront, support, administration, a legacy application facade and service status. The private model includes a provider API and backup storage context.

The breadth of public routes suits an inventory and responsibility exercise. A customer site, support attachment and administrative page may share an entry point while representing different owners and access expectations. Identify those differences and test the boundaries configured for the exercise.

Public surfaces

Customers, support staff and provider administrators share these entry points; the configured exercise inventory sets the actual scope.

Public routes declared in the Hosting Provider catalog
RouteSurfaceContext
/provider-portalMain customer and provider account portal.
/shophosted-shopHosted customer storefront simulation.
/supportsupport-deskSupport tickets, uploads and customer context.
/adminadmin-consoleProvider administrative surface.
/legacylegacy-appLegacy customer application facade.
/statusstatus-apiPublic status and health API simulation.

Private systems

internal-api Private application

Private provider API.

backup-store Private data

Private backup and artifact storage path.

Exercise questions

  • Which routes represent the provider itself, and which represent hosted customer activity?
  • Where could support or backup context reveal a relationship between otherwise separate tenants?
  • How should the administrative and legacy surfaces be inventoried alongside the normal customer portal?

What to hand in

Produce an ownership-aware surface inventory and observed exposure record. Distinguish tenant context, provider administration, backup artifacts and development artifacts instead of reporting them as one undifferentiated application.

Records and evidence

Tenants and hosted sites define the customer population. Support tickets, backups, status events and development artifacts add operational context. Use the configured exercise inventory and recorded observations to establish which artifacts exist before reviewing provider and tenant boundaries.

  • tenants
  • support-tickets
  • hosted-sites
  • backups
  • status-events
  • dev-artifacts

Record each Hosting Provider finding with the research method →