The scenario

Identity reviews span more than a login screen. In Vulnverse v2, Cloud Identity Lab places helpdesk requests, an application catalog, audit views and token metadata alongside private identity relationships and access review records. It gives a team a setting for discussing who may grant access, who may recover an account, and what evidence those decisions should leave.

Separate visible application access from the role and group relationships behind it. An exercise can follow an account recovery request or an application consent review through the available records, with explicit questions about approval and accountability.

Public surfaces

Helpdesk, application catalog, audit and token views form the visible side of the lab; the configured exercise inventory sets the actual scope.

Public routes declared in the Cloud Identity Lab catalog
RouteSurfaceContext
/helpdesk-portalHelpdesk and account recovery workflow facade.
/appsapp-catalogEnterprise app catalog and consent review surface.
/auditaudit-viewerAudit event viewer facade.
/tokenstoken-serviceToken and session metadata facade for lab review.

Private systems

identity-graph Private application

Private user, group, role and app relationship data.

access-review Private application

Privileged access review workflow simulation.

sso-config-store Private data

SSO and conditional access configuration store.

breakglass-workflow Private application

Break-glass account workflow representation.

Exercise questions

  • Which user, group, role and application relationships support a particular access decision?
  • What should a helpdesk operator see or change during account recovery, and what requires separate approval?
  • How would a reviewer distinguish ordinary access, application consent and emergency access in the available audit context?

What to hand in

Document the identity relationship under review, the expected approval boundary and the artifacts that support or fail to support it. Keep the proposed control separate from behavior actually observed in the range.

Records and evidence

Users, groups, application consents, access reviews, conditional access records and service principals support relationship analysis without real employee accounts. Keep conclusions tied to those synthetic records and the identity and access boundaries configured for the exercise.

  • users
  • groups
  • app-consents
  • access-reviews
  • conditional-access
  • service-principals

Record each Cloud Identity Lab finding with the research method →