Aiseptor Secure Browser
Now in betaThe lockdown browser that doesn't stop at the browser.
A secure exam browser for macOS and Windows, backed by Aiseptor's OS- and network-layer enforcement. It locks the exam window like any lockdown browser, then closes the device and network path that invisible AI overlays, on-device LLMs, and remote-access tools depend on: the gap every browser-only lockdown tool leaves open. No webcam. No kernel driver.
A lockdown browser only sees one window.
A traditional secure browser (Respondus LockDown Browser, Safe Exam Browser, and every kiosk-mode tool like them) operates at the application layer. It controls tabs, clipboard, and navigation inside the exam window. Against the threats it was designed for, that works.
It is not the threat anymore. The cheating that matters in 2026 runs outside the browser: an invisible AI overlay drawing answers on top of the screen, an on-device LLM that needs no internet, a second laptop, or a remote-access helper. None of it produces a browser event, so a browser-only lockdown reports a clean session.
One browser. All three layers.
Aiseptor Secure Browser is the exam-window lockdown plus the two layers beneath it that every other secure browser leaves open. It's the same network-layer enforcement behind Aiseptor, delivered as a browser.
| Layer | Browser-only lockdown | Aiseptor Secure Browser |
|---|---|---|
| Application / browser | Locks the exam window, tabs, clipboard | Same window lockdown, plus Aiseptor Secure Browser |
| Device (OS) | Not covered: blind to overlays & local LLMs | OS-level signals: local inference, screen-capture flags, virtual displays |
| Network | Not covered: AI API calls leave freely | Default-deny policy: AI endpoints, RATs, second-device pivots blocked |
Switching from a legacy lockdown browser? See how Aiseptor compares to Respondus, Safe Exam Browser, and lockdown browsers as a category.
Real parity on the platform candidates actually use.
Mac support has long been the weak point of secure browsers: degraded features, compatibility breakage, or no support at all, which pushes candidates and institutions toward exclusions and workarounds. Aiseptor Secure Browser runs natively on macOS and Windows with the same enforcement on both, so a Mac candidate isn't a second-class case or a security hole.
macOS
Native build, full device- and network-layer enforcement, no kernel extension.
Windows
Native build with identical policy enforcement and signal coverage.
BYOD / unmanaged
~30s user-space deploy, no admin rights, self-removes at session end.
Secure the session without surveilling the candidate.
Because enforcement happens at the Device (OS) and Network layer, the browser only needs to know where the device is trying to go, not what the candidate is typing, saying, or looking at. That removes the privacy exposure, bias risk, and dispute surface of camera-based proctoring.
- No webcam. No microphone.
- No keystroke logging. No clipboard capture.
- No screen recording. No personal files read.
- 24-hour default data retention.
FAQ
Secure exam browser questions.
Is there a lockdown browser for Mac?
Yes. Aiseptor Secure Browser runs natively on both macOS and Windows with feature parity. It's currently in beta; institutions and platforms can join the early-access program and pilot it on live sessions before general availability.
What is a secure exam browser?
A secure exam browser (also called a lockdown browser) is an application that restricts a candidate's computer during an assessment, disabling other tabs, copy/paste, screen sharing, and navigation away from the exam. Traditional lockdown browsers only enforce at that application layer; Aiseptor Secure Browser adds OS-level signals (local inference, screen-capture flags, virtual displays) and a default-deny network policy underneath the same window lockdown, so it also catches AI overlays, on-device LLMs, and remote-access tools that never touch the browser.
How is Aiseptor Secure Browser different from Respondus LockDown Browser or Safe Exam Browser?
Respondus LockDown Browser and Safe Exam Browser cover only the application layer: tabs, clipboard, and navigation inside the exam window. Aiseptor Secure Browser matches that window lockdown, then adds a device layer (OS-level detection of local AI inference and virtual displays) and a network layer (default-deny blocking of AI endpoints, remote-access tools, and second-device pivots) that neither competitor covers. On procurement, Aiseptor is priced per session starting at $2, with no seat licenses or annual contract required to pilot; institutions already running Respondus or SEB can add Aiseptor alongside their existing exam platform rather than ripping it out.
Does Aiseptor Secure Browser require a webcam?
No. Aiseptor Secure Browser requires no webcam, no microphone, and no kernel driver. Enforcement happens at the OS and network layer, so it only needs to know where the device is trying to go, not what the candidate is doing on camera. It also does no keystroke logging, clipboard capture, or screen recording, and defaults to 24-hour data retention. For exams that also need identity verification or room monitoring, Aiseptor pairs with a physical proctoring provider rather than bundling its own camera feed.
Does it work on BYOD and unmanaged devices?
Yes. It deploys in user space in about 30 seconds, requires no admin rights or device-management push, and self-removes at session end. In practice this means an institution can roll it out for a single exam window without a help-desk queue, and candidates never need to keep it installed between sessions.
Want early access to Aiseptor Secure Browser?
Aiseptor Secure Browser is in beta on macOS and Windows. Assessment platforms, certification programs, and enterprise hiring teams can join the early-access program to pilot it on real sessions. Bring your hardest attacker.