Summary
Flags DNS tunnelling from query length, entropy and request rate per host, and queues each alert with the queries that triggered it. Evaluated on the replayable campus traffic set with three tunnelling tools injected.
InstituteCommunityPublic
Claims to check
- C1Detects all three injected tunnelling tools in the test set
- C2False alerts stay under 2 per 10,000 hosts per day on clean traffic
- C3Runs on a single 4-core machine at campus traffic volume
Evidence submitted
Automated checks
CHECKS / AI-PRF-0049v1.1.04 OF 5 PASSCLEAN ENV
- pass iodine tunnel detected · alert at 00:03:12
- pass dnscat2 tunnel detected · alert at 00:01:48
- pass dns2tcp tunnel detected · alert at 00:05:31
- pass False alerts on clean day · 1.4 per 10,000 hosts
- FAIL CDN hostnames excluded · 3 alerts on a video CDN
Checks run by the Institute on submission. A pass here is not a verdict.
Version history
- v1.1.02026-10-07Allowlist for long CDN hostnames, after community review
- v1.0.02026-09-21Submitted
Reviews already filed
- RV-2026-0099CommunityB. SiregarRequest changes10/15 · read v1.0.0
- RV-2026-0101CommunityY. HakimAccept14/15 · read v1.1.0
The rubric, in full
- Works as briefed. Does it run from the instructions and do what the brief asks, on the test data? Must pass
- Claims match evidence. Is every claim in the write-up backed by a test, data or a demo you could rerun?
- Reproducible. Did a clean environment reproduce the reported results with the documented steps? Must pass
- Limits stated. Are failure cases and the limits of scope written down where a reader will see them?
- Responsible use. Are data sources cited and permitted, and are risks and human oversight addressed where relevant?
0 Missing · 1 Weak · 2 Meets · 3 Strong. Below Meets needs a written reason.