Policy Red-Team: evidence, proof and selling tools
Official CAIN-42 IHVRK · New to this product? Learn it first
Don't trust CAIN-42. Verify CAIN-42. This is the Independent Human Verification Resource Kit for Policy Red-Team: every claim its page makes, as the exact request and the answer it must give, recorded live and signed. You check it on your own machine with a short Python script that uses no CAIN-42 code.
Every claim matched when recorded
Everything you can give a customer
Pitch, emails, call script, objection answers, one-page summary, proposal.
Evidence packThe figures and a ready email to an auditor or security reviewer.
Answers to buyer questionsPaste into a security questionnaire: YES, PARTIAL, NO or ASK.
Figures & benchmarksEvery number from the signed record, ready for a spreadsheet.
The kit
| Kit | policy-redteam-20261103T224717 |
|---|---|
| Recorded | 2026-11-03T22:47:17+00:00 against cainstudio.online |
| Claims | 5 |
| Zip SHA-256 | 4e3c2424a1b90cfe916916a5b9cd00b2ff70c4d10f7fed116467a863558c735f (also in SHA256SUMS) |
| Signing key fingerprint | 1cacdfc1fc2024b6bb4f8fb02c7c80f4a57f44c5adb11c507190781b5d613de3, published on cainstudio.online · mcpgate.online · clawx.click |
Verify it on your own machine
unzip cain42-ihvrk-policy-redteam.zip && cd cain42-ihvrk-policy-redteam python3 verify.py # offline: hashes, Ed25519 signature, recorded answers python3 verify.py --live # also re-send every request yourself and check the answers now
A claim that cannot be checked counts as a FAIL, never a pass. The live check is the one that depends on nothing we recorded.
The claims in this kit
| # | Claim | Answer must contain |
|---|---|---|
| C01 | Policy: Docs assistant: files and GitHub -> Reads the handbook under /srv/docs/ and the acme GitHub repos. The rules are string prefixes, so ../, encoded dots and a host written as a user name walk straight past them. | ["PATCHED"] |
| C02 | Policy: DevOps agent: a shell with an allow list -> May run git status/log/diff and kubectl get. The regex checks only how the command starts, so a second command after ; or && or inside $( ) rides along. | ["PATCHED"] |
| C03 | Policy: Analytics agent: SQL with a block list -> Runs read queries for dashboards; DROP and DELETE are blocked by substring. Lower case, an SQL comment inside the word or full-width letters get through. | ["PATCHED"] |
| C04 | Policy: Payments agent: outbound calls by host -> Calls Stripe and posts to Slack. The rule compares parsed host names, not URL prefixes, so the host tricks find nothing to exploit. A hardened policy should come back HELD. | ["HELD"] |
| C05 | Policy: Support agent: e-mail with a domain rule -> May e-mail customers at acme.com. The rule says the address contains @acme.com, so x@acme.com.evil.io passes, and no normalization can fix that: the rule itself is wrong. The red team reports a POLICY | ["PARTIAL"] |
Evidence links you can give your customers
- Kit download: /proof/bundle/ihvrk-kits/cain42-ihvrk-policy-redteam.zip
- Each file on its own: README.txt · claims.json · transcript.json · MANIFEST.json · MANIFEST.sig · kit-key.json · verify.py
- Run the live demo yourself on any of the three sites: cainstudio.online · mcpgate.online · clawx.click
- The product explained: /top25-policy-redteam.html · what it does not do: limits
- Signing key on three independent domains: cainstudio.online · mcpgate.online · clawx.click
- Three ready-to-send evidence pages: 1. Evidence pack · 2. Answers to buyer questions · 3. Figures & benchmarks
- Every kit: all IHVRKs · machine-readable index
Send this to your customer
Don't take our word for it. Verify Policy Red-Team yourself: 1. Download the official CAIN-42 IHVRK: https://cainstudio.online/proof/bundle/ihvrk-kits/cain42-ihvrk-policy-redteam.zip SHA-256: 4e3c2424a1b90cfe916916a5b9cd00b2ff70c4d10f7fed116467a863558c735f 2. Unzip it and run: python3 verify.py --live (Python 3, standard library only, no account) 3. Check the signing key fingerprint 1cacdfc1fc2024b6bb4f8fb02c7c80f4a57f44c5adb11c507190781b5d613de3 matches https://cainstudio.online/evidence-kit-key.json, https://mcpgate.online/evidence-kit-key.json and https://clawx.click/evidence-kit-key.json Live demo: https://cainstudio.online/top25-policy-redteam-lab.html What it does not do: https://cainstudio.online/top25-policy-redteam-limits.html
What this kit is, and is not
It shows what the live product answered to these inputs, and lets anyone check that again. It is not a third-party audit, a certification, or a promise about inputs not listed. The product's limits page lists what it does not do.