Design Partner Program
SECURITY OPERATIONS

Security Operations: Know Your Detections Fire Before an Attacker Tests Them

Hayrok runs safe, approved attack emulation in your environment and reads your own SIEM, EDR and cloud telemetry for every step. You see what was logged, what was detected, what alerted, and what your team triaged in time. Gaps go to detection engineering with the events that prove them, and every rule change is retested.

detection_validation · prod-usstep 1 / 5
T+NECTAR · EMULATED STEPYOUR SIEM AND EDR
00:00 T1078.004Sign in with a leaked CI access key Waiting for telemetry… reading
01:35 T1580Enumerate cloud resources — queued
03:10 T1552.005Read instance metadata credentials — queued
04:45 T1098Attach an admin policy to the role — queued
06:20 T1530Read objects from a storage bucket — queued
LOGGED0 / 5
ALERTED0 / 5
NOT LOGGED0
MEDIAN TIME TO ALERT—
01 · THE PROBLEM

A Coverage Map Is Not a Detection

Mapping rules to ATT&CK shows what you intended to catch. It does not show whether the log source is on, the parser still works, the rule fires, or anyone looks at the alert. Each of those can fail silently.

  1. 01 · LOG SOURCE20 of 120 steps

    The data never arrives

    A sensor is missing, an exclusion is too broad, or a source stopped sending.

  2. 02 · PARSING15 of 120

    The data arrives, but unreadable

    A field changed name or format and the rule no longer matches.

  3. 03 · RULE35 of 120

    Nothing matches the behavior

    The rule exists on paper but misses how the technique runs here.

  4. 04 · RESPONSE18 of 120

    The alert fires, nobody acts

    It lands in a noisy queue and ages out before triage.

02 · HOW IT WORKS

Emulate, Observe, Score, Retest: Purple Teaming That Never Stops

No scheduling a red team, no spreadsheet afterwards. Every run is scored against your own telemetry, and every fix is checked the same way.

  1. 01 · EMULATENectar

    Run safe attack behavior

    Approved scenarios run on chosen hosts, accounts and cloud scopes, with benign payloads and cleanup.

  2. 02 · OBSERVEHive

    Read your own telemetry

    Hayrok queries your SIEM, EDR and cloud logs for each step, matched by time, host and identity.

  3. 03 · SCOREHive

    Logged, detected, alerted, triaged

    Each step is scored at every stage, with time to alert and time to triage.

  4. 04 · RETESTNectar

    Prove the rule change works

    After a rule or sensor change, the same step runs again and the score is updated.

03 · MEASURED COVERAGE

From Tested to Triaged: Where Detection Breaks Down

Every emulated step this quarter, followed through each stage of your detection pipeline. Select a gap to see the evidence and the suggested rule change.

DETECTION PIPELINE · Q3 2026 · 120 EMULATED STEPSread from your telemetry
Emulatedsteps run in approved plans 120
Loggedan event reached your SIEM 100−20
Parsedfields usable by detection rules 85−15
Alerteda rule fired on the behavior 50−35
Triaged in SLAan analyst acted within the window 32−18
LARGEST GAPSranked by steps affected
T1552.005 · NOT LOGGED

No EDR sensor on three CI runners, so metadata requests never reached the SIEM.

EVIDENCE FROM YOUR TELEMETRY
host=ci-runner-07  edr_events=0  window=02:14–02:19
cloud_audit: GetSessionToken by role ci-deploy  02:16:41
SUGGESTED CHANGE Deploy the EDR sensor to ci-runner-* and alert on metadata requests from non-agent processes.
→ Sent to endpoint engineering · retest queued
04 · DETECTION DRIFT

Catch the Rule That Quietly Stopped Firing

The same emulation runs every week, so a drop shows up as a change, not a surprise during an incident. Select a rule to see its weekly fire rate and what changed.

WEEKLY FIRE RATE ON EMULATED STEPS0 pts
W1W2W3W4W5W6W7W8W9W10W11W12
WHAT CHANGED No change. The rule fired on every emulated step for twelve weeks. → Keep in the weekly run
05 · MITRE D3FEND

Map Every Attack Step to a Countermeasure, Then Prove It Works

Each emulated ATT&CK technique is paired with the MITRE D3FEND countermeasures that should stop or catch it. Hayrok marks each one verified, failed or not deployed, based on what your telemetry showed. Select a cell to see the evidence.

Countermeasures mapped12
Verified by telemetry4
Failed in testing4
Not deployed4
ATT&CK TECHNIQUE D3FEND · HARDEN D3FEND · DETECT D3FEND · ISOLATE
T1059.001Encoded PowerShell
T1003.001LSASS memory access
T1021.002Lateral movement over SMB
T1552.005Cloud metadata credentials
T1505.003Web shell
T1567Exfiltration to web storage
T1059.001 · DETECT

Process Spawn Analysis

D3-PSA D3FEND ↗ Verified by telemetry

EDR flagged the encoded command from its parent process.

EDR · E-2041 · alerted after 4s
06 · PLAYBOOKS AND ALERTS

An Alert Is Only as Good as What Happens Next

For every alert an emulation raises, Hayrok checks whether it carried what an analyst needs, and whether the response playbook actually ran. Containment that fails on a permission error looks fine on a dashboard. Select an alert to replay its playbook.

ALERT QUALITY2 / 5 checks
✕Severity fits the behaviorMedium, but a service account read 48,210 customer rows.
✓ATT&CK technique taggedT1213 Data from Information Repositories.
✕Asset owner attachedorders-db has no owner in the alert.
✓Identity enrichedsvc-reporting resolved to team-data.
✕Routed to the right queueSent to SOC-general, not the data queue.
PB-Data-Exfiltration · PLAYBOOK RUN
  1. ✓ Enrich identityDirectory lookup for svc-reporting 12s
  2. ✓ Check data classificationcustomer_orders marked confidential 40s
  3. ⏸ Disable service accountWaiting on approval, no approver on call —
  4. – Open incidentNot reached, playbook ended —
VERDICTThe alert fired, but the playbook stopped at approval and the alert auto-closed after 26 hours.→ Approver rota and severity change sent to the SOC lead
07 · FAQ

Security Operations FAQ: What SOC Teams Ask

BAS runs a library of techniques and reports which ones a control blocked. Hayrok emulates full attack routes in your environment and reads your SIEM and EDR to score every stage: logged, parsed, alerted and triaged.

Book a Demo: See Which Detections Fire in Your Environment

We will walk through an approved emulation plan, how your SIEM and EDR telemetry is read for every step, and how gaps and drift reach detection engineering.

✓Logged, detected, alerted and triaged, per step ✓Gaps sent with the events that prove them ✓Weekly reruns that catch drift
Book a Demo