Repository navigation
v0.3.0 — MVP: intent↔effect correlation with divergence flagging
The MVP. pounce now closes the loop: declared intent (tool calls) → actual OS effect (network connections) → divergence. Other tools see one half — the tool call or the syscall. pounce ties them together and flags where they disagree. All of this is zero Full Disk Access.
14:00:00.000 -> tools/call fetch {"url":"https://api.example.com/data"} -> ok
14:00:00.050 · dns api.example.com → 93.184.216.34 node pid 999
14:00:00.200 · net tcp 93.184.216.34:443 out node pid 999
14:00:00.400 · net tcp 45.83.12.9:443 out node pid 999
correlation (window 3s):
tools/call fetch → caused 2
tcp 93.184.216.34:443 (api.example.com, declared) ← declared host → DNS → connection ✓
tcp 45.83.12.9:443 (unresolved — no DNS) ← hardcoded IP
⚠ 1 undeclared destination — IP not resolved from any host:
tcp 45.83.12.9:443 (unresolved — no DNS)
What's new (Phase 3 — correlation)
internal/correlatejoins each request to the connections that occurred during its execution window, and flags two kinds of divergence:- Out-of-band (timing): a connection while no tool call was active — the server reached out on its own.
- Undeclared destination (DNS): a connection to an IP that no DNS lookup produced — a hardcoded/exfil destination, caught even inside a benign call's window. This is the teeth: time-based attribution alone can't catch a rogue server that connects to a malicious IP under cover of a legitimate
fetch.
- The pktap parser now decodes DNS (query→response, joined by transaction id) into
host → IPs, so connections can be checked against what the server actually resolved. Declared hosts come fromhttp(s)://URLs in tool-call args (conservatively — we never over-declare and suppress an alarm). viewshows DNS resolutions and a correlation section;--windowtunes the attribution window.- Validated live on macOS: a real
example.comconnection ties back to its DNS lookup; a hardcoded1.1.1.1connection is flagged.
See docs/correlation.md for the mechanics and the honest caveats (DNS-cache false positives, DoH, correlation ≠ proof).
The full picture (Phases 1–3)
| Tier | Needs | Gives |
|---|---|---|
| Protocol timeline | nothing | declared tool calls |
Network capture (sudo pounce daemon) |
root, no FDA | actual per-process connections |
Correlation (pounce view) |
nothing | the join + divergence flags |
Install
Static binaries, no dependencies:
chmod +x pounce-darwin-arm64 # or -amd64 on Intel
xattr -d com.apple.quarantine pounce-darwin-arm64
mv pounce-darwin-arm64 /usr/local/bin/pounceVerify with shasum -a 256 -c checksums.txt. Build from source: go build -o pounce ./cmd/pounce.
Next
Phase 4: eslogger file/exec capture (root + FDA) — file reads and process spawns join through the same correlator. A rules/actions sink can then fire on a detected divergence.
Full changelog: v0.2.0...v0.3.0