Design Partner Program
INTEGRATIONS

Your security stack, measured under real attack.

Hayrok doesn't replace the tools you run — it tests them. Integrations give validation the context to aim, the telemetry to see how every control responded, and a route to deliver proven findings where your teams already work.

CONTEXT
Where to aim
AW AWSOK OktaWZ WizGH GitHub
TELEMETRY
What defenses did
SP SplunkCS CrowdStrikeCF CloudflareEL Elastic
DELIVERY
Who fixes it
JR JiraSN ServiceNowSL SlackMT Teams
01 · WHAT INTEGRATIONS DO

Security Tool Integrations: Three Jobs in the Validation Loop

Every connection has one job. Context tells validation where to aim. Telemetry proves what your defenses did. Delivery puts the result in front of the owner — and brings the fix back for retest.

01
CONTEXT

Aim validation at what's real

Cloud, identity, container and code sources tell Hayrok which assets exist, how they're configured, and which exposures are already known.

TOOLS · Cloud · identity · Kubernetes · CI/CD · cloud security ACCESS · Read-only
02
TELEMETRY

Measure every control's response

SIEM, EDR and WAF sources report what each layer saw while a scenario ran — blocked, detected, late, or silent.

TOOLS · SIEM · EDR · WAF & CDN ACCESS · Read-only
03
DELIVERY

Route proof to the owner

Ticketing and messaging tools receive validated findings with evidence and a retest link, and carry approval requests to the right people.

TOOLS · Ticketing · ITSM · messaging ACCESS · Scoped write
02 · SIGNAL TRACE

One Validation Run, Every Tool's Response

Follow one scenario through a connected stack. Each integration reports what it saw — and the gaps show up on their own.

Checkout API → Customer PII SC-0518 · T1190 · Exploit Public-Facing Application
00:00 WZ WizCONTEXT Checkout API flagged internet-exposed with a reachable vulnerable package. Context
00:02 NC NectarVALIDATION Approved technique executed against the public endpoint with a benign payload. Executed
00:02 CF Cloudflare WAFTELEMETRY Request logged and scored, but allowed through. Not blocked
00:04 CS CrowdStrike FalconTELEMETRY No detection on the application host for the follow-on activity. No alert
00:41 SP SplunkTELEMETRY Correlation rule fired on anomalous data access — 41 minutes after entry. Late alert
00:42 JR JiraDELIVERY Validated finding opened for the checkout team with evidence and retest link. Ticket opened
Result: the path was validated. The WAF and EDR didn't stop it, the SIEM caught it 41 minutes late — and the checkout team already has the ticket.
03 · COVERAGE MAP

Security Visibility Gaps: See What Validation Can't See Yet

Validation runs without every integration — but each unconnected layer is a blind spot in the trace. Toggle the layers in your stack to see what a run would and wouldn't tell you.

5 of 8 layers visible to validation

Validation still proves exploitability — but the trace will be silent on EDR, Kubernetes, CI/CD. Select a card to connect it.

04 · DIRECTORY

Integration Directory: What Connects, and How

Every entry shows the job it does and the access it needs — nothing more.

TOOL JOB WHAT HAYROK USES IT FOR ACCESS
AW AWSCloud CONTEXT Asset inventory, configuration, IAM permissions and audit logs for cloud attack paths. Read-only
AZ Microsoft AzureCloud CONTEXT Subscriptions, resources, role assignments and activity logs. Read-only
GC Google CloudCloud CONTEXT Projects, resources, IAM bindings and audit logs. Read-only
WZ WizCloud security CONTEXT Existing cloud findings and exposure context to aim validation. Read-only
K8 KubernetesContainers CONTEXT Workloads, RBAC, service accounts, policies and audit events. Read-only
OK OktaIdentity CONTEXT Identities, groups and sign-in events for identity attack paths and SSO. Read-only
EN Microsoft Entra IDIdentity CONTEXT Users, roles, conditional access and sign-in logs. Read-only
A0 Auth0Identity CONTEXT Application identities and authorization context. Read-only
GH GitHubSource & CI/CD CONTEXT Repository and build context; trigger revalidation on release. Read + trigger
JK JenkinsCI/CD CONTEXT Pipeline context and post-deploy revalidation triggers. Read + trigger
SP SplunkSIEM TELEMETRY Match validation activity to alerts and detection rules; measure time to detect. Read-only
EL ElasticSIEM TELEMETRY Correlate validation activity with events and detections. Read-only
CS CrowdStrike FalconEDR TELEMETRY Prevention and detection outcomes on endpoints during validation. Read-only
CF CloudflareWAF & CDN TELEMETRY Request handling and WAF decisions for perimeter validation. Read-only
AK AkamaiWAF & CDN TELEMETRY Edge security events and policy decisions. Read-only
FS FastlyWAF & CDN TELEMETRY Edge and WAF request outcomes. Read-only
JR JiraTicketing DELIVERY Open validated findings with evidence; close the loop on retest. Write: issues
SN ServiceNowITSM DELIVERY Route findings and approvals into existing ITSM workflows. Write: records
SL SlackMessaging DELIVERY Approval requests, run status and SLA alerts. Post messages
MT Microsoft TeamsMessaging DELIVERY Approval requests, run status and SLA alerts. Post messages

Vendor logos are trademarks of their owners.

06 · BRING YOUR OWN FINDINGS

Scanner Findings Import: Validate the Backlog You Already Have

Import findings from the scanners you run today. Hayrok de-duplicates them, maps them to assets, and validates the ones on a reachable path — so the backlog shrinks to what's proven.

TN TenableQL QualysR7 Rapid7WZ WizSK SnykSG SemgrepGH GitHub Advanced SecurityBP Burp Suite
FROM IMPORTED TO PROVEN
Imported 4,812
Unique, mapped 2,140
On a reachable path 318
Validated exploitable 27

Findings that aren't validated aren't discarded — they stay in your scanner with a recorded reason, and are revalidated when the environment changes.

07 · SETUP

Integration Setup: From First Connection to First Trace

Four steps, done by your team with a Hayrok engineer alongside. Times are typical for one tool in each job.

01 ~15 min

Connect

Authorize each tool with a scoped, read-only credential. Delivery tools get write access only to the objects you choose.

DONE WHEN · Health check passes
02 ~30 min

Scope

Choose environments, assets and owners. Hayrok proposes scope from connected context; you approve it.

DONE WHEN · Scope approved in Hive
03 ~10 min

Verify

A harmless canary event confirms each telemetry source is visible and timestamps line up.

DONE WHEN · Every source reports the canary
04 Same day

First trace

Run one approved scenario and get a control-by-control trace, delivered to the owner's queue.

DONE WHEN · Trace and ticket delivered
08 · CONNECTION SECURITY

Least-Privilege Integrations: Read First, Write Only Where It Helps

A validation platform that connects to your security stack must be held to a higher bar than the tools it tests. Every connection is scoped, logged and revocable.

Visit the Trust Center →
01

Read-only by default

Context and telemetry connections never need write access.

02

Scoped write, by choice

Only delivery and trigger integrations write — to the objects you allow.

03

Every call logged

Integration activity is recorded alongside the validation run it served.

04

Revocable anytime

Disconnect a tool and its credentials are removed from Hayrok.

09 · API & WEBHOOKS

Not on the List? Connect It Yourself

Push context in, pull verdicts and evidence out, and subscribe to events — so internal tools, data lakes and custom workflows get the same proven findings as everything else.

webhook · finding.validated
{ "event": "finding.validated", "scenario": "SC-0518", "path": "checkout_api → svc_orders → pii_store", "controls": { "waf": "logged_not_blocked", "edr": "no_alert", "siem": "alert_after_41m" }, "evidence_id": "ev_7f3a…", "retest_url": "…/runs/SC-0518/retest" }
10 · FAQ

Integrations FAQ

No. Hayrok tests them. Integrations supply context and telemetry so validation can measure how your existing controls respond to real techniques.

BRING YOUR STACK

See how your controls respond — through the tools you already own.

Connect read-only, run one scenario, and get a trace of what every tool saw.