Design Partner Program
GOVERNANCE, RISK AND COMPLIANCE

Governance, Risk and Compliance: Prove Controls Work, Not Just That They Exist

Most control evidence is a screenshot or a policy document. Hayrok tests whether controls actually stop and detect attack behavior, reads the result from your own SIEM, EDR, WAF and cloud telemetry, and maps it to the frameworks you report on. Auditors get dated, replayable evidence. You see which controls are effective, which have gaps, and which are only attested.

control_assurance · Q3 2026tested in 142 runs mapping confirmed with your auditor
0%controls tested
and effective
Tested, effective18Tested, gap found5Attested only4Not tested yet3
SOC 2sample controls
CC6.1Logical access controlsCross-tenant read blocked after fix · replayed Tested, effective3 days ago
CC6.6Boundary protectionWAF missed an encoded payload on two APIs Tested, gap found6 days ago
CC7.2Monitoring for anomaliesSIEM alerted on 41% of tested steps Tested, gap found2 days ago
CC8.1Change managementApprovals recorded for every validation plan Tested, effectivecontinuous
01 · THE PROBLEM

A Configured Control Is Not an Effective One

A screenshot shows a WAF is on. It does not show whether it stopped an attack last Tuesday. Regulators and auditors increasingly ask for the second.

CONTROL TYPICAL EVIDENCE HAYROK EVIDENCE
Boundary protection WAF configuration export and a screenshot of the policy. Encoded payloads sent to public APIs, with the WAF and SIEM result for each.
Access control Role matrix and an access review sign-off. Each role tested against operations it should not reach, per tenant.
Monitoring A list of enabled detection rules. Measured rate of logged, alerted and triaged on tested attack steps.
Vulnerability management Scan reports and closed tickets. Reachable findings fixed and verified by a failed replay.
02 · HOW IT WORKS

Map, Test, Record, Report: Continuous Control Assurance

Controls are tested on a schedule and after changes, so evidence is current the day the auditor asks, not assembled the week before.

  1. 01 · MAPHive

    Map controls to tests

    Each control you report on is linked to the validation scenarios that exercise it.

  2. 02 · TESTNectar

    Exercise the control

    Scenarios run on a schedule and after relevant changes, inside approved plans.

  3. 03 · RECORDHive

    Read the result from telemetry

    Your SIEM, EDR, WAF and cloud logs show whether the control prevented, logged and alerted.

  4. 04 · REPORTRisk Engine

    Export evidence by framework

    Evidence records grouped by framework, with dates, approvals and replay history.

03 · EVIDENCE RECORD

Evidence an Auditor Can Test Again

Each record ties a control to the test that exercised it, what your telemetry showed, who approved the test, and when it ran. Select a test to see its record.

EV-2207 · evidence record Tested, gap found

Boundary protection on public APIs

CONTROLWAF rule set v42 on edge-prodTESTEncoded injection payloads to 6 public endpointsPLANPL-61 · approved by a.reyesRUNrun_0377 · 2026-07-08 02:14 UTCRETENTIONKept 7 years · immutable
TELEMETRY RESULTWAF5 of 6 blockedWAF logsAll 6 loggedSIEM4 of 6 alerted
MAPPED TOSOC 2 CC6.6ISO 27001 A.8.20PCI DSS 6.4NIST CSF PR.PS
04 · EXCEPTIONS AND RISK ACCEPTANCE

Accepted Risk, Tested Compensating Controls

Every exception has an owner, a reason and an expiry. Where a compensating control is claimed, Hayrok tests it, so an accepted risk does not quietly become an unprotected one.

EXCEPTIONOWNEREXPIRESCOMPENSATING CONTROLLAST TEST
RA-031Legacy reporting server cannot be patched until Q1team-data2026-12-31Network isolation to the reporting VLANHeld
RA-034Partner API keeps basic auth during migrationteam-partners2026-11-30WAF rate limit and IP allow listGap found
RA-038MFA exemption for a break-glass accountteam-identity2027-03-31SIEM alert on any sign-inHeld
RA-040EDR exclusion on /app for performanceteam-platform2026-11-15Application allow listingNot tested
RA-027Unencrypted backups on an old NASteam-infra2026-10-01 · pastRestricted share permissionsGap found
05 · EVIDENCE FABRIC

Evidence That Cannot Quietly Change

Every plan, approval, step, telemetry result and replay is written to Evidence Fabric as an append-only, hash-linked record. Anyone with access can check that the chain is intact. Try verifying it, then tamper with a record.

EV-2207 · LINEAGEChain intact · 5 of 5 records verified
01 · PLAN✓ PL-61 approved by a.reyes prev 0000…0000 hash 7f3a…c912
02 · RUN✓ run_0377 started · 6 endpoints prev 7f3a…c912 hash b41e…07d5
03 · STEP✓ Encoded payload sent to /v2/search prev b41e…07d5 hash 2c9d…e1a0
04 · TELEMETRY✓ WAF 5 of 6 blocked · SIEM 4 of 6 alerted prev 2c9d…e1a0 hash d87b…3f61
05 · MAPPING✓ Linked to SOC 2 CC6.6, ISO 27001 A.8.20 prev d87b…3f61 hash 51ca…9b0e
Each record carries the hash of the one before it. Changing any record breaks every link after it, so edits cannot go unnoticed.
06 · AUDITOR PORTAL

Give Auditors Scoped Access, Not a Shared Folder

Auditors get read-only access to the evidence you share for their engagement, nothing else. Requests, responses and every view are logged. Select a request to see it from the auditor's side.

AUDITOR PORTAL · READ ONLYSOC 2 Type II · FY2026 · external auditor Access expires 2027-02-281 open requests
PBC-014 · CC6.6 · SHARED
AUDITOR ASKEDProvide evidence that boundary protections were tested during the period, with results.
SHARED EVIDENCEEV-2207Encoded payloads to public APIs · gap foundTested, gap foundEV-2290Replay after WAF rule fix · effectiveTested, effective
ACCESS LOG11-04 09:12Request opened by auditor11-04 15:40Response approved by grc · l.chen11-05 10:03EV-2207 viewed by auditor11-05 10:09Chain verification run by auditor · intact
07 · FAQ

GRC FAQ: What Compliance Teams Ask

It runs approved attack scenarios that the control is meant to stop or detect, then reads your own SIEM, EDR, WAF and cloud telemetry to record whether it prevented, logged, alerted and was triaged.

Book a Demo: See Your Controls Tested, Not Attested

We will walk through mapping your controls, how each test is scored from your telemetry, an evidence record, and how exceptions and compensating controls are tracked.

✓Controls tested against real attack behavior ✓Dated, replayable evidence per control ✓Exceptions tracked with tested compensating controls
Book a Demo