Products

ProctorEdge Browser

Installable exam browser for controlled ProctorEdge exam access, time-bound launch links, and minimized session-event logging.

Request Browser Demo How It Works

The browser is the controlled exam doorway.

ProctorEdge Browser is the installable application candidates use to open authorized exam links. It keeps navigation inside approved origins, blocks unsafe browser behaviors, and produces minimized audit events for review.

Current product position

The browser controls behavior inside the ProctorEdge application. Stronger production assurance such as signed release trust, backend attestation, update enforcement, and full owner dashboards are planned platform layers around the browser.

Candidate flow

Candidate exam-day flow.

From installation to controlled launch, every step is designed to keep exam access inside approved ProctorEdge boundaries.

01 Install ProctorEdge Browser

The candidate installs the approved ProctorEdge Browser before the scheduled exam slot.

02 Receive the exam link

The candidate receives a ProctorEdge-controlled exam URL during the activation window, such as one hour before the exam.

03 Open the link in ProctorEdge Browser

Normal browsers should show instructions only. The real exam starts only after ProctorEdge Browser and the backend approve the launch.

04 Take the exam in the controlled window

The browser applies approved navigation, popup, download, certificate, shortcut, permission, and recovery controls.

Live+ Proctoring handoff

For Live+ sessions, Secure Browser can launch the Candidate Companion with the shared exam session token — enabling proctor chat and session status without leaving the controlled exam environment. Companion apps are in active development; see Live Proctoring for the full platform story.

Verified controls

Verified browser controls.

Local browser enforcement for navigation, popups, downloads, certificates, shortcuts, permissions, and minimized event logging.

Approved-origin navigation

Top-level navigation is restricted to approved ProctorEdge origins using centralized URL policy checks.

Popup blocking

Unmanaged child windows and external popup escapes are denied by default.

Download cancellation

Downloads are cancelled in the current secure-browser scope to reduce uncontrolled file movement.

Certificate failure blocking

Certificate errors are rejected and routed to safe local recovery views.

Restricted shortcut guards

Browser and debug shortcuts are blocked in exam mode where Electron can enforce them.

Minimized event logs

The browser records structured security events without passwords, answers, raw keystrokes, page content, or personal files.

Roadmap

Roadmap controls around the browser.

Some high-assurance capabilities require platform and backend support beyond the local browser shell. They should be planned and verified before being treated as production controls.

Capability	Status	Why it matters
Signed production installer	Planned	Allows candidates and backend services to trust approved browser builds.
Signed updates and minimum-version enforcement	Planned	Prevents outdated or unapproved builds from starting exam sessions.
Backend launch-token validation	Planned integration	Binds candidate, provider, voucher, exam, time slot, and browser session.
Owner event dashboard	Planned integration	Lets authorized owners and reviewers inspect attempt timelines from backend records.
Device and environment risk signals	Future review	Must be privacy-reviewed, tested, disclosed, and treated as review signals.

Launch behavior

Browser-only exam link behavior.

The same exam URL behaves differently depending on whether it is opened in a normal browser or ProctorEdge Browser.

Normal browser

If the candidate opens the exam link in Chrome, Edge, Firefox, or another normal browser, the page should show installation and opening instructions and must not deliver exam content.