A proctored Xobin session establishes candidate identity, runs an environment scan, locks the testing browser, and records the session for later review. Which of those layers is enabled depends on the risk profile of the assessment and the customer's compliance framework, so a short screening quiz and a final-round technical exam are never protected the same way. The intent is a session that is secure and auditable without being hostile to a genuine candidate.
We do not rely on a single tripwire. Face presence, tab activity, network anomalies, copy-paste behaviour, and content matching are treated as independent indicators, and a session is only flagged when the combination of signals crosses a documented threshold. Each flag carries the underlying evidence, so a reviewer can see why the session was raised — not just that it was.
The hiring team receives a proctoring summary alongside the score: what was monitored, what was flagged, the confidence level in the session, and the full timeline if a deeper review is needed. Evidence is retained under the customer's data-retention policy and can be exported for audit. A score without its proctoring context is an incomplete measurement, and we present them together for exactly that reason.
These integrity controls run on live hiring sessions, not just in the lab. Teams who want the same rigour in their own hiring can use it directly through Xobin.
The methodology described here is what runs inside every Xobin assessment and AI interview — so hiring teams can make talent decisions on evidence, not instinct. See Xobin.