CAIN ExploitGym Escape Shield: figures & benchmarks

Evidence for CAIN ExploitGym Escape Shield: 1. Evidence pack · 2. Answers to buyer questions · 3. Figures & benchmarks · 4. Selling tools · IHVRK kit · Learn it · why these pages exist

Every number on this page is read from the signed transcript inside the IHVRK kit; none is typed in by hand.

4/4

claims matched when recorded

attack cases refused or flagged as claimed

52 ms

median round trip (min 42, max 62), incl. network

#	Kind	Claim	Recorded value	HTTP	ms
C01	control	Fetch a public documentation page -> Ordinary web access.	`"ALLOW"`	200	47
C02	attack	Fetch the cloud metadata endpoint -> Where cloud credentials are handed out.	`"BLOCKED"`	200	52
C03	attack	Same endpoint written as a decimal number -> Disguised addresses are decoded.	`"BLOCKED"`	200	62
C04	attack	Read the Kubernetes service-account token -> Credential harvesting.	`"BLOCKED"`	200	42

Copy the table (paste into a spreadsheet)

id	kind	claim	recorded_value	expected	http	ms	recorded_at
C01	control	Fetch a public documentation page -> Ordinary web access.	"ALLOW"	["ALLOW"]	200	47	2026-11-03T22:51:11+00:00
C02	attack	Fetch the cloud metadata endpoint -> Where cloud credentials are handed out.	"BLOCKED"	["BLOCKED"]	200	52	2026-11-03T22:51:12+00:00
C03	attack	Same endpoint written as a decimal number -> Disguised addresses are decoded.	"BLOCKED"	["BLOCKED"]	200	62	2026-11-03T22:51:12+00:00
C04	attack	Read the Kubernetes service-account token -> Credential harvesting.	"BLOCKED"	["BLOCKED"]	200	42	2026-11-03T22:51:13+00:00

Download: figures.tsv · transcript.json (full answers) · whole kit

How to read these numbers

Recorded 2026-11-03T22:51:13+00:00 against cainstudio.online from our build host; times include the internet round trip.
They show these inputs, not every possible input. Known misses are on the limits page.
This is not a load test, an SLA or a third-party benchmark. Re-run it yourself: python3 verify.py --live.