How-to

How to conduct online exams securely: preventing cheating in 2026

A practical guide to secure online exams: proctoring types, how AI detects cheating, secure browsers, identity checks, randomisation, and a step-by-step checklist.

Team XAM9 min read

Short answer

A secure online exam layers five controls: identity (the right person is taking it), content (no two candidates get the same paper, and the paper does not exist before the start time), environment (a locked-down browser or a monitored screen), behaviour (proctoring signals reviewed by a human) and evidence (a timestamped log you can defend in an appeal). No single one of these is sufficient; skipping any of them is where exams get challenged.

What does it mean to conduct an online exam securely?

It means that after the exam you can answer three questions with evidence: who took it, what they had access to, and what happened during the session. Security here is not the absence of cheating. It is the ability to detect it, bound its impact and prove your case if a result is disputed.

The failure mode of most online exams is not a dramatic hack. It is a result that cannot be defended: a candidate contests a score, the institution has a screenshot and a hunch, and the outcome turns on who argues better. Every control below exists to replace a hunch with a record.

What is remote proctoring, and what types are there?

Remote proctoring is the supervision of a candidate taking an exam outside a physical exam hall, using their webcam, microphone, screen and activity signals. There are four models in common use, and they trade cost against certainty in opposite directions.

TypeHow it worksBest forTrade-off
Live (synchronous) proctoringA human proctor watches candidates in real time and can interveneSmall, very high-stakes cohorts: licensure, final vivasHighest cost per candidate; needs scheduling and proctor supply
Record-and-reviewThe session is recorded; humans review afterwards, usually only flagged segmentsMedium cohorts where after-the-fact adjudication is acceptableCheating is detected, not prevented, during the exam
AI / automated proctoringSoftware scores video, audio and activity signals and raises flags with confidence levelsLarge cohorts, continuous or on-demand testingProduces false positives; requires human review before any penalty
Hybrid (AI-triaged, human-reviewed)AI flags a small percentage of sessions; humans review only thoseMost institutional exams at scaleNeeds a documented review workflow and a trained reviewer
The hybrid model is the practical default for most institutions: automation triages attention, humans make decisions.

How does AI proctoring detect cheating?

It does not “detect cheating”. It detects deviations from the expected pattern of an honest session and attaches a confidence score to each. Understanding the difference is what keeps an integrity process defensible.

SignalWhat it catchesCommon innocent explanation
No face in frameCandidate leaving the desk or the seat being swappedLighting, camera angle, a candidate leaning out of frame
Multiple faces detectedA second person helping, or a substitute taking overFamily member walking past in a shared home
Face mismatch against the ID captureImpersonationPoor lighting or low-resolution ID photograph
Focus loss / tab switch / window blurSearching answers in another tab or appNotification pop-up, accidental keystroke
Sustained gaze away from the screenReading notes off-screenThinking, or a second monitor legitimately disabled
Voice or conversation in the audio streamSomeone dictating answersHousehold noise, a television
Copy / paste and right-click eventsLifting question text out or answers inHabitual keyboard use
Anomalous timing and response patternsAnswer keys in circulation: implausibly fast, uniformly correct responsesA genuinely well-prepared candidate
Device, IP or session changes mid-examHandover to another person or locationNetwork drop and reconnection on mobile data
Every row has an innocent explanation. That is why a flag is a reason to look, never a verdict.

What is a secure or lockdown browser, and do you need one?

A lockdown browser is a restricted application that runs the exam full-screen and blocks the things a normal browser allows: other tabs, screen capture, virtual machines, copy-paste, screen sharing and commonly, external displays. It shifts you from detecting that a candidate opened another window to preventing it.

You need one when the exam is high-stakes and the answers are easily searchable. You can often skip it for open-book or long-form exams, where a quick search is worth little and forcing an install on every candidate's device costs more in support tickets than it buys in security. Browser-based monitoring with focus detection is the middle ground.

How do you verify that the right person is taking the exam?

Identity is checked at three moments, not one. Checking only at the start is the most common gap in online exam design. It leaves the whole session unverified after the first minute.

  1. Before entry: unique per-candidate credentials or links (never a shared password), photo-ID capture, and a live selfie matched against the ID.
  2. During the session: periodic presence checks, face continuity, single-face verification, and session binding so the same login cannot be active on two devices.
  3. In the answers themselves: at least one response type that carries the candidate's identity intrinsically, such as a spoken or recorded answer. This is the check that survives every form of screen-level trickery.

Does randomisation actually reduce cheating?

Yes, and it is the cheapest control on this list. Randomisation changes the economics: it converts a leak that would compromise everyone into one that compromises a single candidate.

  • Item pools. Draw each candidate's paper at run time from a bank several times larger than the paper. A 60-item exam drawn from 300 calibrated items means no two candidates see the same set.
  • Option shuffling. Randomise answer-option order so “the answer is C” is meaningless to a neighbour.
  • Section and question order. Shuffle at both levels to break screen-sharing coordination.
  • Sectional timers and one-way navigation. Removes the window in which a candidate photographs the whole paper and sends it out for answers.
  • Staggered start times where the calendar allows, so the cohort is never all sitting the same items simultaneously.

The prerequisite is an item bank large enough and calibrated well enough that different draws are comparably difficult. Randomising a pool of wildly uneven items trades integrity for unfairness, which is not a good trade.

How do you design questions that are hard to cheat on?

The most durable defence is not surveillance. It is asking for something a search engine, a chatbot or a person in the next room cannot supply on demand.

Question typeCheating resistanceWhy
Factual multiple choiceLowSearchable in seconds; a single letter can be passed to a neighbour
Numerical with randomised parametersMediumEach candidate computes a different answer from a different input
Scenario / applied questions with working shownHighRequires reasoning that is specific to the prompt and visible to the grader
Audio or video responsesVery highCarries the candidate’s voice, delivery and unrehearsed reasoning, so it resists both impersonation and key-passing
Live follow-up / viva on a submitted answerVery highCannot be prepared in advance; probes actual understanding
Cheating resistance rises with the specificity and the authorship evidence carried by the response.

How do you conduct a secure online exam, step by step?

A checklist you can run for any exam, from a 30-student quiz to a 5,000-candidate certification.

  1. Classify the stakes. Decide up front whether this is low-stakes (formative), medium, or high-stakes. Every control below is scaled by this answer. Do not proctor a practice quiz.
  2. Build an item bank, not a paper. Author 3–5× the number of items the exam needs, tagged by topic and difficulty.
  3. Mix response formats. Include at least one item type that carries authorship evidence: audio, video, or worked long-form.
  4. Configure randomisation. Pool draw, option shuffle, section order, sectional timers.
  5. Set the access model. Unique per-candidate credentials or links, exam window, single active session per candidate, and no shared passwords.
  6. Choose the proctoring level and decide, in writing, which signals you will act on and at what confidence threshold.
  7. Get consent and publish the rules. Tell candidates exactly what is recorded, for how long it is retained, who reviews it and how to appeal. Say it before they book, not on the exam screen.
  8. Run a mandatory system check. Camera, microphone, bandwidth and browser, at least 24 hours before the exam, so technical failures do not become integrity flags.
  9. Do a live dry run with a handful of real users on real devices, including one low-bandwidth connection and one older phone.
  10. Monitor during the exam and staff a support channel. Most mid-exam incidents are technical, and an unanswered candidate is a future dispute.
  11. Review flags with a human after the exam. Record the decision, the evidence and the reason for each flagged session.
  12. Retain the audit trail (event log, recordings, response timings) for the length of your appeals window, then delete it on schedule.

How do you stay fair, legal and defensible?

Proctoring processes biometric and household-environment data. Obtain explicit, informed consent in advance; state the retention period and stick to it; restrict reviewer access; and offer an alternative arrangement where a candidate genuinely cannot be recorded. XAM publishes a standard proctoring consent notice you can adapt as a starting point.

Accessibility and equity

Extra time, screen-reader compatibility and keyboard navigation must work with your lockdown settings, not against them. Assistive technology is a frequent source of false flags. Assume some candidates are on shared devices and unstable connections, and design the connectivity-loss recovery path deliberately.

Due process

Publish the appeal route, give the candidate the specific evidence against them, and let a person who was not the original reviewer decide the appeal. An integrity process without due process will not survive its first serious challenge.

XAM by Ankor, an assessment platform, implements these layers in one engine: authoring and item banks, randomised delivery, AI proctoring with confidence-scored flags and session replay, audio and video answers as a native question type, auto-evaluation and branded reports. The free tier runs 20 real sessions with no card, which is enough to test the checklist above end to end. See pricing or talk to us about an institutional rollout.

Sources

  • Practice described here reflects standard remote-assessment controls; the Indian exam-integrity context is documented in our NEET paper-leak explainer, which cites Supreme Court Observer, LiveLaw, Careers360, Tribune India and The Wire.
  • XAM proctoring consent notice: what is recorded, retention and review.

XAM by Ankor

Run the assessments that break Google Forms.

One engine for delivering, grading and reporting on assessments: audio and video answers, proctoring, auto-evaluation and branded reports. Start free, no card.

Keep reading