Author a scenario with a purpose
Which organization is represented? What must participants or agents investigate? Which systems, people and relationships make that question meaningful? What observations will support the review?
This guide covers what to decide when you configure an exercise in Vulnverse v2. It describes a planning model, not a particular editing interface.
Describe systems and their relationships
Identify the entry points, internal systems, records and dependencies involved in the task. Give each a role in the organization rather than adding disconnected components.
Describe which identities should reach each system and why. Use synthetic records to preserve those relationships without borrowing production credentials or personal data.
Give people and teams a defined context
Specify simulated roles, access, goals and intentions. Include emotions, stress or distractions when they matter to the question, and identify how team relationships affect the work.
Separate the context visible to a participant from material reserved for the operator or reviewer. A scenario should make its authorization boundaries clear without revealing every review conclusion in advance.
Connect activity to an observable question
Describe the tasks and interactions that belong to the organization. Then define the exercise question separately, including which decisions and system outcomes would make it answerable.
A useful objective might concern the handling of an access request or a handoff between roles. Its interpretation should depend on observations, not only a claim that the task succeeded.
Review the operating context
Define the authorized environment, participant scope, synthetic data, access and session ownership before the exercise. Establish the observations needed during the session and the material retained for review.
Define your exercise
- Organization: its operating context and connected systems.
- Question: the decision or outcome the session should examine.
- Roles: participant and simulated actor context, access and boundaries.
- Human conditions: relevant goals, intentions, emotions, stress and distractions.
- Activity: tasks, interactions and team relationships.
- Observations: the evidence needed to interpret decisions and outcomes.
- Exercise responsibilities: authorization, session ownership and evidence retention.
Start from an organization in the scenario catalog; Behavior and simulation and Social engineering simulation describe the human layer.