How it works
Inside your account. Rules decide. Proof verifies offline.
Wardhand replaces manual screenshots with a repeatable loop inside your own AWS account. Your data stays in your account. The drafting model runs in your own cloud by default; using a hosted model is your explicit choice.
The five-step loop inside your AWS account
Fixed rules end to end1. Read configuration metadata—never customer data
Read-only boundaryEvery 15 minutes, Wardhand reads configuration metadata across your connected AWS accounts and GitHub repositories. It cannot read S3 objects or secrets, and stores hashed records in your own account.
Kept as returned by AWS
2. Fixed rules decide every check—guided by your policy
53 checksAll 53 checks across AWS and GitHub run by fixed rules mapped to SOC 2 criteria and your signed policy. If a read fails, Wardhand reports "could not test"—never a fake pass.
Decided by written rule
3. Check impact first, then fix or open a pull request
Human signedBefore changing anything, Wardhand shows attached servers, networks, or policies. Approve a reversible AWS fix, or open a minimal Terraform pull request checked by fixed rules—never auto-merged.
Signed human grant
4. Live re-read seals the receipt—or closes outside fixes
Self-closingAfter an approved fix, Wardhand re-reads AWS live and seals before-and-after proof into a signed receipt. If your team fixes or deletes the resource outside Wardhand, the next scan closes the finding.
Read back from system
5. Export one signed bundle your auditor verifies offline
Offline proofExport checks, policies, access reviews, exceptions, and fix receipts in one signed bundle. Your auditor verifies it offline with your public key—no access to your AWS account required.
Tamper-evident chain
One finding, every fact, one deliberate decision.
When a check or policy fails, Wardhand shows what is affected first. Choose a reversible AWS fix or a small Terraform pull request, with raw evidence kept underneath.
Shows exact before and after settings. One signed click applies the fix, re-reads AWS, and seals a receipt.
Opens a small pull request in GitHub for peer review. Fixed rules check every diff, and Wardhand never merges it.
Evidence your auditor can verify without trusting us.
The offline verifier checks the bundle against the public key and installation ID you provide. Change even one character, and verification fails immediately.
$ wardhand verify-workpaper \ --bundle wardhand-auditor-export-2026-Q4.tar.gz \ --public-key wardhand-public-key.json \ --installation northwind-prod {"ok":true,"records":249,"chain":"verified"}
$ wardhand verify-workpaper \ --bundle wardhand-auditor-export-edited.tar.gz \ --public-key wardhand-public-key.json \ --installation northwind-prod ERROR invalid_bundle_or_trusted_key signed export record digest mismatch
Every fact carries a mark saying how it is known.
The right-hand margin shows whether a line came from AWS, a live re-read, a human signature, a fixed rule, or a gap.
See the loop on your own AWS Organization.
Start read-only in 60 minutes. Zero writes, and your data stays in your account.