Design Partner Program
SCENARIO LIBRARY

Security validation scenarios, governed and ready to run.

Every scenario in the Hayrok library is a complete, reviewable unit of work: what it tests, what it needs, how far it may go, which telemetry must see it, and what evidence proves the result. Pick one, approve it, run it.

RANSOMWARE READINESS S1 · Emulate
Backup deletion attempt from finance segment
SC-0412 · T1490
✓ Objective & technique
✓ Preconditions
✓ Safety limits
✓ Telemetry
✓ Evidence contract
✓ Pass criteria
01 · EXPLORE

Attack Scenario Library: Find the Test for Your Objective

Filter by objective pack, validation mode or safety class. Select a scenario to read its full contract.

Preview · illustrative subset
17 of 17
02 · SCENARIO CONTRACT

Scenario Anatomy: Six Fields Before Anything Runs

A scenario is not a script. It is a contract that a security owner, a platform owner and an auditor can all read — and that Nectar enforces at runtime.

  1. 01

    Objective & technique

    The outcome being tested and the attacker technique used to test it.

  2. 02

    Preconditions

    Assets, identities and access the scenario needs before it can start.

  3. 03

    Safety class & limits

    Where it may run, what it may change, and the conditions that stop it.

  4. 04

    Telemetry requirements

    Which sources must observe the activity for the result to count.

  5. 05

    Evidence contract

    The artifacts that must be captured and sealed for every run.

  6. 06

    Success criteria

    The explicit condition that decides pass or fail — written before the run, not after.

scenario/ID-0412.yaml illustrative
# 01 objective objective: Ransomware cannot reach backup storage technique: T1490 · Inhibit System Recovery # 02 preconditions requires: [finance_segment_host, backup_vault_ro] # 03 safety safety_class: S1 # benign artifacts only environments: [staging, prod-readonly] stop_if: write_attempt_succeeds # 04 telemetry must_observe: [EDR, SIEM, backup_audit] # 05 evidence evidence: [request_log, control_verdict, alert_id] # 06 success pass_when: delete denied AND alert < 15m
03 · SAFETY CLASSES

Safe Attack Simulation: Four Classes, Four Approval Levels

Every scenario declares how far it may go. The class decides where it can run and who must approve it — so production testing is a policy decision, not a judgment call at 2 a.m.

S0

Observe

Read-only discovery and reachability checks. Nothing is written or executed on targets.

RUNS IN · Production APPROVAL · Policy auto-approves
S1

Emulate

Benign artifacts that mimic attacker behavior — no persistence, no data change.

RUNS IN · Production APPROVAL · Scenario owner
S2

Exercise

Controlled, reversible changes such as a role assignment, with automatic cleanup.

RUNS IN · Staging · prod with window APPROVAL · Owner + platform owner
S3

Controlled impact

Simulated impact on canary resources only, inside an approved window.

RUNS IN · Approved window only APPROVAL · Named approver + change ticket

Class names and approval rules shown are illustrative; your policy in Nectar defines the real thresholds.

05 · FROM LIBRARY TO EVIDENCE

Scenario Lifecycle: Select, Approve, Run, Revalidate

01

Select

Choose a pack or single scenario for the objective you need to prove.

Scenario Library
02

Approve

The contract is reviewed against policy; the right owners approve scope and class.

Hive · Nectar
03

Run

Nectar executes within limits; every action is checked against the approved plan.

Nectar
04

Revalidate

Evidence is sealed. After a fix, the same scenario reruns and joins the record.

Evidence Fabric

Need a scenario that isn't in the library?

Author your own against the same contract — your team's tradecraft, reviewed and enforced like every built-in scenario.

How Nectar governs custom scenarios →
06 · FAQ

Scenario Library FAQ

A scenario is a governed unit of adversarial testing: an objective, the technique used to test it, preconditions, a safety class, the telemetry that must observe it, the evidence it must produce, and the criteria that decide pass or fail.

PICK ONE OBJECTIVE

Walk the full library with a validation engineer.

Tell us the outcome you need to prove. We'll map it to a pack, show the contracts, and run the first scenario in a scoped pilot.