Design Partner Program
REMEDIATION VERIFICATION

Remediation Verification: Close Findings on Evidence, Not on Tickets

A ticket marked done is not a closed exploit. Hayrok replays the original attack against the fixed system, tries the variants a partial fix would miss, and checks your own SIEM, EDR, WAF and API gateway telemetry. A finding closes only when the replay fails, and reopens if a later change brings it back.

fix_verification · replay planstep 1 / 4
01 · REPLAY• Original request for another customer's order ownership check Testing
02 · VARIANT Same request through the mobile API ownership check Queued
03 · VARIANT Numeric ID swapped for UUID ownership check Queued
04 · REGRESSION Order history still loads for the owner normal use Queued
VERDICTFix is partial: the web route is closed, but the mobile API still returns other customers' orders.
YOUR TELEMETRYWAFLoggedAPI gatewayLoggedSIEMNo alert
01 · THE PROBLEM

Closed Tickets Aren't Closed Risk

Fixes ship, tickets close, and dashboards turn green. Few teams check that the exploit actually stopped working, or that it stayed stopped.

TICKETS

Done in the tracker, open in production

A fix can ship to one route and miss the other three that reach the same code.

VARIANTS

The original payload is not the only payload

Fixes written for the reported request often miss an encoding or a second entry point.

REGRESSION

Fixes get undone

A refactor, a config rollback or a new service can quietly bring the exploit back.

02 · FIXES UNDER VERIFICATION

Every Fix, Its Replay, and What Actually Happened

Fixes reported by engineering, each replayed inside an approved plan. Filter by outcome to see which fixes failed and whether detection noticed the replay.

TESTTEAMREPLAYEDR AND GATEWAYSIEM
F-2201Order lookup IDOR via mobile APIordersStill worksNo alertNo alert
F-2204SSRF in image fetchmediaBlockedAlertedAlerted
F-2209Build runner can assume the backup roleplatformStill worksNo alertNot logged
F-2212Session not revoked on password resetidentityBlockedAlertedAlerted
F-2215SQL injection variant in JSON bodysearchStill worksAlerted lateNo alert
F-2218Stored XSS in support notessupportBlockedAlertedAlerted
F-2221Tenant ID accepted from request headerbillingBlockedAlertedNo alert
F-2226Debug endpoint re-exposed after rollbackpaymentsStill worksAlerted lateNo alert
03 · VERIFICATION TYPES

Every Kind of Fix, Verified the Same Way

Code changes, configuration changes, compensating controls and accepted risk each need different proof. Select a type to see what Hayrok checks.

REPLAYSupported

Original exploit

The exact request that proved the finding is replayed against the fixed build.

Request and response kept
VARIANTSupported

Variants and other routes

Encodings, alternate parameters and every route that reaches the same code are tried.

Variants listed per finding
REGRESSIONSupported

Normal use still works

The intended behavior is checked so the fix does not break the feature.

Pass or fail per check
04 · FIX QUEUES

Each Team's Fixes, With the Evidence Attached

Verification results go back to the team that owns the fix, with the replay request and response. Select a team to see its queue.

TEAMS5 of 5 need action
TEAM-ORDERS · PARTIAL FIX

team-orders · 6 fixes this month

SERVICES CHANGEDorders-apimobile-apiweb-checkout
Verified5 of 6
Still worksIDOR through the mobile API
Detection4 of 6 alerted
→ Mobile API route sent back with the failing replay attached.
05 · FIX IMPACT

Verified Fixes Break Whole Attack Paths

One verified fix can close several validated attack paths at once. Select fixes to see which paths their replays prove closed.

CANDIDATE FIXES
VALIDATED PATHS2 / 5 broken
P-401 · read order historyOpen Mobile appIDOR on mobile APIcustomer orders
P-404 · read order historyOpen Partner APIIDOR on mobile APIcustomer orders
P-409 · restore backupsBroken Build runnerbackup role trustbackup bucket
P-412 · dump search indexOpen InternetJSON body injectionsearch database
P-415 · restore backupsBroken Leaked CI tokenbuild runnerbackup role trustbackup bucket
A path counts as closed only after the replay against the shipped fix fails.
06 · VERIFICATION LIFECYCLE

From Finding to Closed, Every Step on Record

Each finding moves through the same four steps, and each step leaves evidence. Select a step to see what is recorded.

Prove the finding

The exploit is reproduced and its request, response and attack path are kept as the baseline for every later replay.

Exploit reproducedRecorded
Attack path mappedRecorded
Owner assignedteam-orders
07 · REGRESSION WATCH

Fixed Once Isn't Fixed Forever

Verified fixes are replayed when the services they touch change. When a replay succeeds again, the finding is flagged. Reopen each one to send it back to its owner.

REPLAYS AFTER CHANGE · LAST 30 DAYS5 verified fixes no longer hold
REOPENED F-2226 debug endpointExposed again after the payments-api rollback
REOPENED F-1980 open redirectLogin refactor removed the redirect check
WEAKENED F-2104 rate limit on /loginLimit raised from 10 to 200 attempts per minute
WEAKENED F-2033 storage bucket policyPublic read added for a new CDN origin
RETEST F-2204 SSRF in image fetchFetch library upgraded, replay queued
08 · FAQ

Remediation Verification FAQ

The original exploit, its known variants and every route to the same code are replayed against the fix, and all fail. The replay request and response are attached to the finding.

Book a Demo: See Your Fixes Verified

Bring a few findings your team has marked fixed. We will replay them, show what your telemetry recorded, and show how they stay verified as the system changes.

✓Original exploit and variants replayed after each fix ✓Fraud and security controls read from your telemetry ✓Regressions flagged when a fixed path reopens
Book a Demo