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.
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.
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.
- 01
Objective & technique
The outcome being tested and the attacker technique used to test it.
- 02
Preconditions
Assets, identities and access the scenario needs before it can start.
- 03
Safety class & limits
Where it may run, what it may change, and the conditions that stop it.
- 04
Telemetry requirements
Which sources must observe the activity for the result to count.
- 05
Evidence contract
The artifacts that must be captured and sealed for every run.
- 06
Success criteria
The explicit condition that decides pass or fail — written before the run, not after.
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.
Observe
Read-only discovery and reachability checks. Nothing is written or executed on targets.
Emulate
Benign artifacts that mimic attacker behavior — no persistence, no data change.
Exercise
Controlled, reversible changes such as a role assignment, with automatic cleanup.
Controlled impact
Simulated impact on canary resources only, inside an approved window.
Class names and approval rules shown are illustrative; your policy in Nectar defines the real thresholds.
Objective Packs: Start From an Outcome, Not a Technique
Packs bundle the scenarios that together answer one business question. Run a pack, and the result is a verdict on the objective — not a pile of technique-level passes and fails.
Scenario Lifecycle: Select, Approve, Run, Revalidate
Select
Choose a pack or single scenario for the objective you need to prove.
Scenario LibraryApprove
The contract is reviewed against policy; the right owners approve scope and class.
Hive · NectarRun
Nectar executes within limits; every action is checked against the approved plan.
NectarRevalidate
Evidence is sealed. After a fix, the same scenario reruns and joins the record.
Evidence FabricNeed 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.
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.