Wedjat Back to site

Operator console · mock engagement

Watch an engagement run. Green means go.

This is the Wedjat engine walking a fictional in-scope estate. A Suite of recon runners fires in sequence, each one scope-gated before it touches anything. Findings stream into the console as they land. Open any one to see its proof: the exact command, the evidence hash, and the verdict. Find it, prove it, hand it off.

This is a demo on mock data. Nothing here scans a real host. The target (acme-demo.example and its RFC 5737 documentation IPs) is fictional, the findings are scripted, and no packet leaves your browser. It shows how the engine works, it does not run a live assessment.
run WDJ-DEMO-0042 · engagement acme-demo · posture covert
seeds acme-demo.example, www.acme-demo.example
ready
Findings
0 total 0 action needed 0 attention

    What you just watched

    Every line above is a command, not a claim.

    The engine does not hand you a risk score and a guess. It runs deterministic recon runners, records the exact argv and a hash of what it saw, and asserts a finding only when it can show the proof. The same evidence is what a report is built from, and what you can re-run yourself.

    01 · Find

    Scope-gated recon

    Each runner checks the target against the sealed scope before it executes. Out of scope is refused without a packet sent. Discovered hosts become new targets, re-checked at every hop.

    02 · Prove

    Evidence, hashed

    A finding carries the real argv, a sha256 of exactly what was stored, the tool version, and the box image. A replayer can verify it. No evidence reference, no finding.

    03 · Hand off

    Prove with a canary

    To show a door opens we write our own marker and read it back, then drop it. We demonstrate access. We never read your data, never flood, never exploit. Detection only.