What it is
Default-deny architecture is the security principle that an exam device is permitted to reach only the destinations explicitly authorized by the assessment policy; everything else, including unknown and future threats, is blocked by default.
Why it matters
Detection-based and allow-then-observe models are always one cheating tool behind the attacker; default-deny flips the asymmetry so new tools have no reachable infrastructure inside the session.
How Aiseptor implements it
Aiseptor is default-deny end-to-end: the exam policy lists the allowed domains, and the enclave blocks all other network traffic without needing to recognize specific cheating binaries.
Definition
Canonical definition
Default-deny architecture is the application of a classic network security principle, deny by default and allow only what is explicitly listed, to exam integrity. In a default-deny exam environment, the candidate device operates inside a policy that names the resources the assessment legitimately requires (the exam UI, a specific documentation site, a permitted IDE) and blocks every other destination. This eliminates an entire class of defensive pressure: the system does not have to recognize Cluely, or its forks, or the next overlay tool that appears on GitHub next week; it only has to recognize what the exam is supposed to touch. The alternative, a default-allow posture that blocks specific known-bad destinations as they're discovered, is a losing race by construction: it is always exactly as good as its last signature update, and every new fork or renamed binary buys the attacker a free window until the list catches up. The result is a durable security posture whose effectiveness does not decay as new cheating vendors emerge, because the allowed surface, not the attacker surface, is what the policy encodes.
In practice
A concrete example
An exam policy for a take-home systems-design assessment names three permitted destinations: the assessment platform, a specific internal documentation wiki, and nothing else. Midway through the session, a background process on the candidate's laptop, unrelated to any cheating tool, attempts to reach a cloud AI API to auto-complete a code snippet in an editor plugin the candidate forgot was installed. Under default-allow, that request would need to already be on a blocklist to be caught. Under default-deny, it fails silently because it was never on the allow-list in the first place, regardless of what sent it or why.
Citations
- [1]NIST Special Publication 800-207, Zero Trust Architecture (2020)
- [2]Aiseptor architecture whitepaper (public version) (2026)