Choose what you want to validate.
Hayrok builds the plan.
Start with a security objective—not a scanner, tool, or test template. Hayrok recommends the scenarios, validation methods, telemetry, safety controls, and evidence requirements needed to evaluate the outcome.
Step by Step
The run-creation
flow.
Objective selection
Choose an objective (Internet Exposure, Ransomware Readiness, Identity, API, Cloud, Detection Coverage, Kubernetes, Supply Chain, AI, or Custom), each with a description, recommended asset types, expected outcomes, and available methods.
Scope selection
Select tenant/org, environment, asset groups, individual assets, domains/apps, APIs, cloud accounts, clusters, repos/pipelines, identities, crown jewels, and exclusions. Hayrok validates scope ownership and authorization before execution.
Scenario recommendation
The engine proposes scenarios from objective, asset capabilities, technologies, environment, exposure context, telemetry, integrated controls, prior findings, history, and safety policy—each showing name, why recommended, targets, method, safety level, required telemetry, expected evidence, and estimated impact.
Telemetry readiness
Hayrok checks whether required sources (SIEM, EDR, WAF, API gateway, cloud audit, identity, Kubernetes audit, runtime metrics, app logs) are connected and healthy—states: Ready, Partially ready, Missing telemetry, Degraded, Not required—so users know which outcomes may be limited.
Safety review
Summarizes environment, planned actions, safety classifications, maintenance window, potential impact, tool restrictions, rate/concurrency limits, blast-radius controls, stop conditions, cleanup, and approvals. Users acknowledge scope and safety before submission.
Planner output
Presents the final ordered workflow; each step shows action, agent, target, approved tool, preconditions, expected response, required evidence, policy result, approval status, and failure/fallback. Users may remove or defer actions but cannot bypass policy.
Run execution
After approval, Genesis launches; the screen shows run status, objective, scope, scenario progress, stage, active agents, evidence collection, control responses, detection events, policy decisions, warnings, timeline, and stop/pause controls.
Run summary
At completion: scenarios attempted/confirmed, controls validated, detections observed, detection gaps, evidence artifacts, findings created, attack paths affected, recommended next actions, and revalidation opportunities.
Objective-First
Why objective-first
run creation matters.
Tool-first workflows make the user responsible for translating a goal into tests and for enforcing safety. Starting from the objective lets Hayrok attach the right scenarios, telemetry checks, and guardrails automatically—so a run is both easier to create and harder to misconfigure.
Governed Launch
“A run built from the objective is easier to create and harder to misconfigure.”
Scenarios, telemetry checks, and guardrails attached automatically.
FAQ
Frequently asked
questions.
How do I start a validation?
Choose a security objective; Hayrok recommends scenarios, methods, telemetry, safety controls, and evidence requirements.
How does Hayrok know what's in scope?
You select scope explicitly, and Hayrok validates ownership and authorisation before execution.
What if I'm missing telemetry?
The telemetry-readiness check flags Ready/Partially ready/Missing/Degraded/Not required, so you know which outcomes may be limited.
Can I change the recommended scenarios?
Yes—review, add, remove, or defer scenarios before continuing.
What is the safety review?
A pre-submission summary of actions, classifications, limits, stop/cleanup conditions, and approvals you must acknowledge.
Can I edit the execution plan?
You can remove or defer actions with the right permissions, but you cannot bypass policy restrictions.
What can I do during a run?
Monitor progress and, if authorised, pause or stop execution.
What do I get at the end?
A run summary of confirmed scenarios, validated controls, detections, gaps, evidence, findings, affected attack paths, and next actions.
Is there a custom objective?
Yes—Custom Validation is available alongside the standard objectives.
Keep Exploring
What powers
the run.
Turn a security objective into a
governed validation workflow.
Choose what you want to validate and let Hayrok build the plan.