Design Partner Program
THREAT MODELING AND VALIDATION

Threat Modeling and Validation: Prove the Mitigations in Your Threat Model Work

A threat model lists what could go wrong and what should stop it. Most stay as diagrams. Hayrok takes each threat and its assumed mitigation, tests it in the running system, and checks your own SIEM, EDR, WAF and API gateway telemetry to see whether the mitigation held and whether anyone was alerted. When the system changes, the threats are tested again.

threat_model_validation · approved planstep 1 / 4
01 · SPOOFING• Forged service-to-service call to payments-api mTLS between services Testing
02 · TAMPERING Amount changed between cart and capture signed payment intent Queued
03 · DISCLOSURE Card metadata in error responses error sanitization Queued
04 · ELEVATION Support role reaches refund approval role check on approve Queued
VERDICTOne mitigation missing: verbose errors return card BIN and expiry on failed captures.
YOUR TELEMETRYWAFLoggedApp logsLoggedSIEMNo alert
01 · THE PROBLEM

Threat Models Describe Intent. They Rarely Prove It.

Teams invest in threat modeling, then ship. The mitigations get built, changed or skipped, and the model is never checked against what actually runs.

DRIFT

Models age with every release

The diagram shows last quarter's design. The code has moved on.

ASSUMPTIONS

Mitigations are assumed, not proven

"mTLS between services" is written down. Nobody checked the new service has it.

DETECTION

Detection is rarely in the model

Models say what should stop an attack, not whether anyone would see it.

02 · THREATS UNDER TEST

Every Threat, Its Mitigation, and What Actually Happened

Threats imported from your models, each tested inside an approved plan. Filter by outcome to see where the mitigation failed and whether detection noticed.

TESTMODELMITIGATIONEDR AND GATEWAYSIEM
TM-101Card metadata returned in capture errorspaymentsFailedNo alertNo alert
TM-104Forged service call to payments-apipaymentsHeldAlertedAlerted
TM-109Role change via bulk API with no audit recordidentityFailedNo alertNot logged
TM-112JWT claims edited client-sideidentityHeldAlertedAlerted
TM-115Analyst reads raw PII from the data lakedataFailedAlerted lateNo alert
TM-121Job role assumes warehouse admindataHeldAlertedAlerted
TM-126Assistant calls refunds without approvalassistantHeldAlertedNo alert
TM-133New internal service without mTLSplatformFailedAlerted lateNo alert
03 · SUPPORTED METHODS

Bring the Method You Already Use, We Test What It Says

Threats can come from STRIDE sessions, attack trees, ATT&CK-based models or your own templates. Select a method to see how its threats become tests.

S · TSupported

Spoofing and tampering

Each identity and data-integrity threat becomes a test against the service that should enforce it.

Per element in your data flow diagram
R · ISupported

Repudiation and disclosure

Audit logging and data exposure are tested by acting and checking what was recorded or returned.

Audit and response checks
D · EPartial

Denial and elevation

Resource limits are tested within safe bounds. Privilege paths are tested end to end.

Denial tests are bounded by plan
04 · MODELS UNDER TEST

Each System's Model, Checked Against What Runs

Each threat model is linked to the services it describes. When those services change, the model's threats are tested again. Select a system to see its latest result.

THREAT MODELS4 of 5 need action
PAYMENTS SERVICE · GAP FOUND

Payments service · STRIDE · 14 threats

SERVICES IN MODELweb-checkoutpayments-apiledger
Mitigations held12 of 14
MissingError sanitization, mTLS on new service
Detection9 of 14 alerted
→ Two mitigation gaps sent to team-payments with the failing requests.
05 · ATTACK TREES

Validated Attack Trees, Pruned by the Right Fix

Each branch of an attack tree is tested. Branches that worked are shown with the step that let them through, so you can see which mitigation cuts the most branches. Select fixes to see which branches close.

CANDIDATE FIXES
VALIDATED BRANCHES2 / 5 broken
B-1.1 · read card dataOpen Internetcapture errorcard metadata
B-1.2 · read card dataBroken Internal serviceno mTLSpayments-apicard metadata
B-2.1 · take over adminOpen Bulk role APIno audit recordadmin group
B-3.1 · read customer PIIOpen Analyst accountraw lake filescustomer PII
B-3.2 · read customer PIIBroken Internal serviceno mTLSdata-lakecustomer PII
Each closed branch is replayed once its fix ships, and stays closed only while the replay fails.
06 · FROM DESIGN TO PRODUCTION

One Model, Tested at Every Stage It Matters

A threat model is written once at design review and tested at each step after that. Select a stage to see what happens to the model's threats there.

Write the model

Threats and intended mitigations are captured at design review, in your method or template, and linked to the services they describe.

14 threats capturedRecorded
Mitigations named for eachRecorded
Services linked3 services
07 · MODEL DRIFT

When the System Moves, the Model Knows

Hayrok compares each model with what is actually deployed and flags the differences: new endpoints, new data flows, removed controls. Mark each one to update the model and test it.

PARTNER API MODEL · LAST REVIEWED 2026-08-145 differences between the model and what is deployed
NEW POST /partner/v3/bulk-ordersEndpoint deployed, not in the model
NEW GET /partner/v3/customers/{id}Returns customer data, not in the model
NEW webhook → fulfilment-svcNew data flow to a third party
CHANGED rate limit on /partner/*Raised from 50 to 500 requests per minute
REMOVED IP allow list on partner-gatewayMitigation in the model no longer deployed
08 · FAQ

Threat Modeling and Validation FAQ

No. Threats can be imported from common methods and templates, or entered directly. Supported import formats are confirmed during planning.

Book a Demo: See Your Threat Model Tested

Bring one threat model, in any format. We will show how its threats become tests, how your telemetry is read for each one, and how the model stays tested as the system changes.

✓STRIDE, attack trees, ATT&CK-based and custom models ✓Fraud and security controls read from your telemetry ✓Threats retested whenever the system changes
Book a Demo