INTERACTIVE PRODUCT TOUR
See how Hayrok turns security objectives into evidence-backed outcomes .
Take a guided tour through the complete Hayrok validation workflow — from choosing what to validate to proving that remediation worked. Explore the product at your own pace.
CONFIRMEDCTRL FAILDET GAPVALIDATION LIFECYCLE
STEP 0 · PICK A PATH
Choose how you want to explore Hayrok
Follow the recommended journey, take a role-based path, or open the platform map and roam freely.
RECOMMENDED
6–8 min
Guided Tour
Follow the recommended product journey from validation objective to verified remediation.
Best for first-time visitors.
Start Guided Tour →
BY ROLE
5–7 min
Role-Based Tour
Choose the experience most relevant to your role — from CISO to MSSP partner.
CISOAppSecCloudDetection EngVuln MgmtSecOpsGRCMSSP
Choose Your Role →
SELF-DIRECTED
open ended
Explore Freely
Open the product map and visit any workflow, screen, or capability directly.
Operations · Governance · Assurance · Hay Assist.
Explore the Platform →
YOUR VALIDATION JOURNEY
Ten stages, one continuous lifecycle
The tour walks each stage in the product. Jump to any step below.
STEP 01
Choose Objective
Pick the outcome to validate
STEP 02
Define Scope
Authorize assets & exclusions
STEP 03
Recommend Scenarios
Engine proposes the plan
STEP 04
Readiness
Telemetry & safety checks
STEP 05
Review Plan
Approvals & policy gates
STEP 06
Monitor Execution
Live agent timeline
STEP 07
Investigate Finding
Confirmed, high confidence
STEP 08
Inspect Evidence
Request, control, detection
STEP 09
Attack Path
From entry to crown jewel
STEP 10
Report & Revalidate
Verify the fix
STEP 01 · OBJECTIVE
Start with what you want to validate
Hayrok begins with a security outcome rather than an individual tool or test. The objective drives which scenarios, telemetry, safety controls, and evidence contracts are recommended.
→Recommended asset types surface automatically
→Expected outcomes are stated before you begin
→Default tour objective: API Security
CHOOSE A VALIDATION OBJECTIVE
STEP 1 / 10
EX
Internet Exposure
RW
Ransomware Readiness
ID
Identity Security
API✓ SELECTED
API Security
CL
Cloud Security
DT
Detection Coverage
K8
Kubernetes
KubernetesSC
Supply Chain
AI
AI Security
RECOMMENDED ASSETS · API Security
Public APIs · Internal APIs · API gateways · App services · Data stores
EXPECTED OUTCOMES
Exposure · AuthN & AuthZ · Gateway / WAF · Detection · Reachability
DEFINE ASSETS AND SCOPE
ORGANIZATION
Acme Commerce
ENVIRONMENT
Production
ASSET GROUP
Customer APIs
INCLUDED ASSETS
12
EXCLUDED ASSETS
3
CROWN JEWEL
Customer Database
Application service · orders-apiIN SCOPE
Application service · customers-apiIN SCOPE
Application service · payments-apiIN SCOPE
Gateway · kong-prodIN SCOPE
Data store · customers-db (crown jewel)CROWN JEWEL
STEP 02 · SCOPE
Control exactly what Hayrok is authorized to validate
Scope is an authorization boundary. Agents cannot independently expand beyond approved targets — exclusions remain enforced during planning and execution.
→Group assets by application, service, environment, owner, technology, or criticality
→Mark crown jewels so findings map to business impact
→Every exclusion is honored end-to-end
STEP 03 · SCENARIO ENGINE
Hayrok builds the initial validation strategy
Recommendations are based on the objective, asset capabilities, technology context, prior validation history, available telemetry, and organizational policies.
SAFERECOMMENDED
Public API Exposure Validation
Why: Selected API is internet-facing
METHOD
Recon · Probe
TELEMETRY
Cloudflare, Kong
SAFERECOMMENDED
Authentication Control Validation
Why: API requires bearer-token authentication
METHOD
Auth Replay
TELEMETRY
App logs
CONTROLLEDRECOMMENDED
Object-Level Authorization
Why: API accesses customer-specific records
METHOD
Authorized Traversal
TELEMETRY
App logs, Splunk
SAFERECOMMENDED
API Gateway Control Validation
Why: Kong is connected as the API gateway
METHOD
Gateway Probe
TELEMETRY
Kong, WAF
SAFERECOMMENDED
API Detection Coverage
Why: Splunk & Cloudflare telemetry available
METHOD
Telemetry Correlate
TELEMETRY
Splunk, Cloudflare
CONTROLLEDRECOMMENDED
API → Database Reachability
Why: API connected to a crown-jewel data store
METHOD
Reachability Trace
TELEMETRY
App logs, Netflow
STEP 04 · READINESS
Know what Hayrok can observe before validation begins
Missing telemetry does not always prevent execution, but it may limit the conclusions Hayrok can support.
TELEMETRY READINESS
5 CHECKEDSplunk
SplunkSIEM detection correlation
READYCloudflare
CloudflareWAF and edge events
READYKong Gateway
API gateway logs
READYApplication logs
Backend activity
PARTIALEDR
Not required for this scenario
NOT REQUIREDSAFETY REVIEW
CONTROLLEDEnvironmentProduction
Rate limit10 req / sec
Concurrency2 scenarios
Data modificationDisabled
Destructive actionsProhibited
Approval requiredYes
Cleanup requiredNo
STEP 05 · PLAN & APPROVE
See the plan before execution
Teams can review what Hayrok plans to do before execution. Sensitive actions remain blocked until policy and approval requirements are satisfied.
OBJECTIVE
API Security
SCENARIOS
6
ASSETS
12
ESTIMATED STEPS
28
APPROVAL GATES
1
EVIDENCE ARTIFACTS
40–60
PLANNED WORKFLOW
ALLOWED BY POLICY
01Confirm API availabilityRecon AgentSAFE
02Validate authentication enforcementExploit AgentSAFE
03Evaluate object-level authorizationExploit AgentCONTROLLED
04Observe gateway and WAF responseValidation AgentSAFE
05Correlate detection telemetryValidation AgentSAFE
06Validate backend reachabilityValidation AgentCONTROLLED
07Collect evidenceEvidence AgentSAFE
08Classify outcomesReporting AgentSAFE
!
Approval gate · 1 required
Object-level authorization is a controlled action. Approver reviews objective, scope, actions, potential impact, safety controls, and expiration.
STEP 06 · LIVE EXECUTION
Follow the validation in real time
Every action, policy decision, control response, detection result, and evidence artifact is recorded as part of the validation history.
STEP 07 · INVESTIGATE A FINDING
Move from validation result to actionable finding
Findings combine technical proof, control behavior, detection coverage, runtime context, reachability, and business impact.
STEP 08 · EVIDENCE DRAWER
Every finding includes the proof behind it
Evidence Fabric links each artifact to the validation run, scenario, asset, agent, tool, timestamp, and resulting finding.
◆Request · sanitized headers & body
◆Response · owner mismatch, sensitive fields
◆Control · WAF, gateway, application authz
◆Detection · expected & observed events
◆Runtime · service version, environment
◆Reachability · public API → app → database
REQUEST · SANITIZEDt+00:04.19
GET /api/v1/customers/94821 Authorization: Bearer [REDACTED] X-Tenant: tenant-a
RESPONSE · FAILUREt+00:04.20
HTTP 200 Record owner: tenant-b Sensitive fields returned: 6
CONTROL
WAF · Allowed
Kong · Passed
App AuthZ · Failed
DETECTION
Expected · api_cross_tenant_access
Observed · none
REACHABILITY
Public API → App Service → Customer DB
Status · Reachable
STEP 09 · ATTACK PATH
See how the finding connects to business impact
Hayrok distinguishes modeled relationships from conditions supported by direct validation evidence.
STEP 10 · REPORT & REVALIDATE
Turn evidence into stakeholder-ready outputs
Then rerun the original scenario, collect new evidence, and verify the fix.
REPORT TYPES
Executive SummaryPREVIEW →
Technical Validation ReportGENERATE
Evidence PackageGENERATE
Detection Gap ReportGENERATE
Control Failure ReportGENERATE
Attack Path ReportGENERATE
Audit PackageGENERATE
Revalidation ReportGENERATE
REVALIDATION COMPARISON
RESOLVED & VERIFIED
Hayrok reran the original scenario, collected new evidence, confirmed the authorization control, observed the expected detection, and verified that the attack path was interrupted.
HAY ASSIST · CONVERSATIONAL MOMENT
Ask a question, get a cited answer
Responses cite the visible evidence cards from the tour.
Why is this finding critical?
What evidence confirmed the risk?
Which control failed?
Why was the activity not detected?
What should we fix first?
How do we revalidate the remediation?
Summarize this for the CISO.
◆
HAY ASSIST
Q · Why is this finding critical?
This finding is critical because an authenticated user can access records outside their tenant boundary. The condition is confirmed in production, the API is publicly reachable, existing controls allowed the request, and no detection was generated. The validated path reaches the customer database directly.
evidence · request/response
control · app authz failed
detection · none observed
path · public → app → db
Sample response generated from representative Hayrok evidence.
ROLE-BASED PATHS
Choose the path most relevant to your role
Each path emphasizes the workflows, evidence, and outputs that matter to that role.
CISO
5 min
Security Leader
Objective · risk posture · critical findings · executive reports · ROI
Selected →
APPSEC
7 min
Application Security
Scope · scenarios · planner · authorization · CI/CD revalidation
Start path →
CLOUD
7 min
Cloud Security
Cloud assets · IAM paths · workloads · reachability · cloud paths
Start path →
DET-ENG
6 min
Detection Engineering
Telemetry · expected detections · gaps · alert latency · ATT&CK
Start path →
VULN-MGMT
6 min
Vulnerability Mgmt
Ingestion · exploitability · runtime · reachability · prioritization
Start path →
SEC-OPS
6 min
Security Operations
Live execution · timeline · alert correlation · triage · handoffs
Start path →
GRC
6 min
Governance / GRC
Scope authorization · policy gates · approvals · audit · attestations
Start path →
MSSP
7 min
MSSP / Partner
Tenants · recurring runs · scenario packs · customer dashboards
Start path →
CISO · PATH PREVIEW
Security Leader
Objective → risk posture → validated critical findings → executive-ready evidence → measurable ROI.
Start this path →
STOPS ON THIS PATH
◆Objective
◆Risk posture
◆Critical findings
◆Executive Summary
◆ROI
FREE EXPLORATION
Open the product map
Every destination opens a short guided interaction or product screenshot.
OPERATIONS
TOUR COMPLETE
You've completed the Hayrok product tour
You've seen how Hayrok starts with an objective, applies policy and safety, coordinates validation agents, produces evidence-backed findings, maps validated attack paths, generates reports, and confirms remediation through revalidation.
FAQ
Interactive Product Tour · FAQ
Is this the live Hayrok platform?+
The tour uses representative product data and guided interactions to demonstrate the Hayrok experience. It is not connected to a customer environment.
Do I need an account?+
No. Visitors can explore the public tour without creating an account.
Does the tour use real customer data?+
No. The tour uses fictitious and sanitized sample data.
Can I see Hayrok with my own use cases?+
Yes. Book a personalized demo to explore Hayrok using your security objectives, environment types, and operational requirements.
Can I view a sample report?+
Yes. The tour links to a representative validation report and evidence package.
Can Hayrok run in private environments?+
Hayrok supports customer-runner and private deployment options based on plan and technical requirements.
Can I explore a specific solution?+
Yes. Launch role- and objective-based tour paths for API Security, Ransomware Readiness, Internet Exposure, Detection Coverage, Cloud Security, and other objectives.
Ready to see Hayrok in your environment?
The interactive tour shows how Hayrok works with representative data. A personalized demo shows how the platform can support your security objectives, assets, telemetry, controls, governance, and deployment model.