The scenario

In Vulnverse v2, SaaS Company represents a service used by multiple tenants. A tenant dashboard, administration surface, public API and artifact browser form the public catalog. Private records cover workers and queues, internal metrics, and tenant object storage.

Review how tenant ownership should remain consistent across different kinds of information. A dashboard record, export artifact and worker job may refer to a tenant while passing through different operational contexts. An exercise can make those relationships explicit before attempting to validate an access assumption.

Public surfaces

Tenant users, administrators and API clients reach the service through these routes; the configured exercise inventory sets the actual scope.

Public routes declared in the SaaS Company catalog
RouteSurfaceContext
/tenant-dashboardTenant user dashboard and account workflow.
/adminadmin-consoleSaaS admin and support operations surface.
/apipublic-apiPublic API facade for tenant resources.
/artifactsartifact-browserCI/CD artifact and release metadata facade.

Private systems

worker-queue Private application

Private worker and queue simulation.

metrics-admin Private application

Internal metrics and admin API.

object-storage Private application

Tenant object storage and export data.

Exercise questions

  • How is tenant ownership represented across users, exports, audit events and worker jobs?
  • What should distinguish a tenant view from administration and internal metrics context?
  • Which release artifacts are appropriate for a public browser, and which reveal internal development or customer context?

What to hand in

Create a tenant and surface inventory, then report observed exposure against a stated ownership rule. Separate a recommended authorization design from behavior demonstrated by an actual endpoint.

Records and evidence

Tenants, users, audit events, object exports, CI artifacts, worker jobs and metrics provide several places to investigate tenant context. Compare the ownership represented in each category and document which records support a particular tenant or administrative view.

  • tenants
  • users
  • audit-events
  • object-exports
  • ci-artifacts
  • worker-jobs
  • metrics

Record each SaaS Company finding with the research method →