Input data and information sources
Video, audio and screen content come from candidates' own configured computers. The system records candidates' faces, voices, names and exam performance.
Also known as: Online exam proctoring
The system monitors online exam candidates through camera, microphone and screen and flags possible cheating.
Understand the use case
It records video, audio, screen content and inputs, scores behaviour such as repeated looking away, and presents flagged passages to an invigilator. Universities use this for home-based exams; German and Dutch courts have reached differing decisions on its use.
This page describes a typical system design. Actual data flows and permissions depend on your implementation.
System design and data flows
Camera images, audio, screen content and inputs arrive from candidates' computers during the exam.
Video, audio and screen content come from candidates' own configured computers. The system analyses camera images, audio, screen content and keyboard inputs together.
The system detects faces, gaze, other people, sounds and switches to other windows and assesses behaviour.
The system processes signals recorded during an examination and flags events that deviate from the expected procedure. Depending on the tool, these may include video, audio or interaction events. A flag is initially a prompt for review; its significance emerges only through examination of the evidence and the assessment context.
Each candidate receives a score, with unusual passages flagged.
The result describes the defined model task. A match, category or forecast acquires its professional significance only in conjunction with the underlying data and intended use.
Invigilators review flagged passages and decide whether cheating occurred and whether the exam counts.
Integration determines whether the result is simply displayed, adopted after approval or written directly into a business application. These variants differ in their data flows and permissions.
Explore the system design: Select a component to see its task, incoming and outgoing data, and role in the use case. The guided walkthrough explains each phase. Then use Yes, Uncertain and No to represent your specific system variant.
7 review first9 clarify8 baseline threats
The diagram shows the typical architecture. Select a component to see what happens there and adapt its features to your system. Enable “Analysis guidance” to see which threats need reviewing for this architecture. The page's checklist continues to describe the typical case.
None yet. Each change will appear here.
In this system design: 7 to review first, 9 to clarify, 8 baseline threats.
External access: Depends on your system
To clarify
Input: Part of every AI system
Review first
Baseline for every AI system
Third-party content: Present
AI model: Part of every AI system
Baseline for every AI system
Provider service: Present
Review first
To clarify
Document collection: Depends on your system
Training and feedback: Depends on your system
To clarify
Result: Part of every AI system
Baseline for every AI system
Business application or equipment: Depends on your system
To clarify
person: Part of every AI system
Review first
Affected person: Present
Unapproved AI services: Depends on your system
To clarify
Supply chain and technical foundations: 5 baseline threats applying to every AI system
Baseline for every AI system
Automated assessment of exam performance (essay scoring)
Assesses answers themselves and awards marks
Biometric verification and video identification
Only checks at the start that the registered person is before the camera
Video, audio and screen content come from candidates' own configured computers. The system records candidates' faces, voices, names and exam performance.
Universities use vendors' software such as Proctorio.
Logging, retention periods and possible use for training must be established for the specific implementation.
Some systems terminate exams or block access on suspicion; others only flag events. Provider-side analysis sends recordings outside the university.
Using a provider does not automatically determine where processing takes place. Storage location, subcontractors, deletion periods and use for training must be checked for the specific deployment.
Assess risks and determine measures
Record data, participants, interfaces and permissions. Resolve uncertain characteristics in the model.
Relate review candidates to actual data flows: what could happen, and who would be affected?
Assess impacts and likelihood in the deployment context. The number of review candidates is not a risk score.
Select appropriate controls, assign responsibilities and define effectiveness checks. Document residual risks and approvals.
A total of 24 threats from the threat catalogue may be relevant to this use case.
Also review: whether the system disadvantages groups
Check whether selection, ranking or assessment disadvantages people with protected characteristics, such as sex, age or origin.
Candidates can substitute a virtual camera or recording for the live feed or use aids outside the frame. The system then assesses images unrelated to the exam.
Invigilators focus on flagged passages and accept the suspicion. Disability, a child in the room or poor lighting can then unfairly cast suspicion on candidates.
Sensitive Information Disclosure
Recordings show homes, housemates and open programs. Logging or sending them to the provider exposes many people's private circumstances.
Training data or an adopted base model can introduce hidden triggers for misbehaviour.
Listed because of this characteristic
Complex or high-volume inputs can exhaust model computing resources.
Listed because of this characteristic
Targeted queries can recover some personal or protected training data from the model.
Listed because of these characteristics
Exfiltration from ML Application
Protected data can leak through tools, network connections, storage or insiders.
Listed because of this characteristic
Up to 9 further threats may apply, depending on your system design. Nine threats need to be reviewed for every AI system. One of these is particularly important here and is therefore listed above.
Each Yes adds further threats to your checklist, up to 9 in total. If you cannot yet answer a question, include its threats in your review.
How your system is built
How you operate the system
Some systems terminate exams or block access on suspicion; others only flag events.
If yes, add
If yes, add
Behavioural scoring trained on recordings with confirmed cheating uses human-labelled examples.
If yes, add
If yes, add
These questions arise for almost every AI system.
If yes, add
If yes, add
If yes, add
If yes, add
If yes, add
Measures for the priority review areas are expanded. Each linked measure explains how to implement it.
Controls for the remaining threats are available on their pages in the threat catalogue.
For every AI system Applies since 2 February 2025.
Depending on use Review trigger since 2 February 2025.
In typical use Review trigger from 2 December 2027.
Applies if staff or appointed representatives operate or use AI systems.
Applies since 2 February 2025.
Detailed obligations
Applies if the system monitors candidates and is intended to detect prohibited behaviour, for example in university or certification exams.
Applies from 2 December 2027.
Detailed obligations
Applies if the system infers candidates' emotions, such as nervousness or stress, from faces or voices in an educational institution.
Applies since 2 February 2025.
Detailed obligations
Initial identity checks merely confirm that the registered person is participating. Annex III, point 1(a), excludes this verification.
Detailed obligations
Classify your system with the quick checker All obligations in the obligations compass
Review these threats for every AI system, whatever its purpose.
If any of these features does apply to your system, add the listed threats.
Does the system generate its own text, such as answers, drafts or summaries?
The system marks recording passages and returns a score, rather than text.
If yes, add
Does the system generate or edit images, sounds, voices or videos?
If yes, add
Does the system create new content from open-ended requests that people read, see or hear directly? Translation, reading aloud and transcription do not count.
If yes, add
Can users give the system natural language tasks that it then performs?
If yes, add
Does the system search its own collection of documents or records for relevant content?
If yes, add
Does the system formulate answers from retrieved documents?
If yes, add
Does the system use a knowledge graph storing concepts and their relationships?
If yes, add
Does the system remember content from earlier conversations or tasks and reuse it later?
If yes, add
Does the system call other programs, interfaces or search services itself, even if only to read?
If yes, add
Does the system determine its next steps itself based on earlier results?
If yes, add
Does the system delegate tasks to other AI agents or incorporate their results?
If yes, add
Is the system connected to tools or data sources through the Model Context Protocol (MCP)?
If yes, add
Can people outside your organisation use the system, including without login?
Only registered candidates and invigilators use the system, rather than the public.
If yes, add
Does the system generate code, scripts or database queries for further use?
If yes, add
Does the system execute programs, scripts or commands itself?
If yes, add
Is the system intended to maximise a specified metric, such as revenue, utilisation or clicks?
If yes, add
EU AI Act, Annex III, point 3(d)
The Act expressly lists AI systems monitoring students and detecting prohibited behaviour during exams in Annex III.
Society for Civil Rights, Monitoring online exams
The organisation describes use at German universities and the Thuringian Higher Regional Court's decision.
Amsterdam District Court, Judgment of 11 June 2020, ECLI:NL:RBAMS:2020:2917
The Court describes automated behavioural scoring from recordings and an invigilator reviewing footage where behaviour is flagged.
Updated: 30 September 2026. Review checklist rules version 0.3.2, threat catalogue version 2026.10.24.2. How these pages are structured