CAIN-42 CLAWXCAIN Steganographic Firewall: figures & benchmarks
Evidence for CAIN Steganographic Firewall: 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.
3/3
claims matched when recorded
2
attack cases refused or flagged as claimed
35 ms
median round trip (min 34, max 36), incl. network
| # | Kind | Claim | Recorded value | HTTP | ms |
|---|---|---|---|---|---|
| C01 | control | Plain text -> Nothing hidden. | "ALLOW" | 200 | 36 |
| C02 | attack | Text with invisible zero-width characters -> Characters removed before sending. | "SANITIZED" | 200 | 35 |
| C03 | attack | A base64-encoded AWS key -> Encoded credential blocked. | "BLOCKED" | 200 | 34 |
Copy the table (paste into a spreadsheet)
id kind claim recorded_value expected http ms recorded_at C01 control Plain text -> Nothing hidden. "ALLOW" ["ALLOW"] 200 36 2026-11-03T22:54:53+00:00 C02 attack Text with invisible zero-width characters -> Characters removed before sending. "SANITIZED" ["SANITIZED"] 200 35 2026-11-03T22:54:54+00:00 C03 attack A base64-encoded AWS key -> Encoded credential blocked. "BLOCKED" ["BLOCKED"] 200 34 2026-11-03T22:54:54+00:00
Download: figures.tsv · transcript.json (full answers) · whole kit
How to read these numbers
- Recorded 2026-11-03T22:54:55+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.