There is a difference between monitoring and surveillance. Most programs running online assessments haven’t thought carefully about which one they’re actually doing, and that gap is where trust starts to erode.

Monitoring confirms that the right person completed the assessment, stayed engaged, and followed the rules. Surveillance collects everything it can, flags anything it doesn’t recognize, and leaves the program to sort out what any of it means.

One produces a defensible result. The other produces liability.

If your proctoring tool accesses the file system of a personal device, stores recordings your team will never review, or generates hundreds of automated flags with no human judgment behind them, it’s not monitoring. It’s surveillance. And your learners know the difference.

What monitoring is actually supposed to do

Every program administering online assessments has the same core need: confirm identity, verify participation, and produce a result that holds up to scrutiny.

That’s it.

You’re not trying to catalog everything that happens in a candidate’s home. You’re not trying to build a behavioral profile. You’re trying to answer three questions:

1. Was this the right person?
2. Did they complete the assessment under appropriate conditions?
3. Can you stand behind the result if it’s challenged?

A well-designed proctoring approach answers all three. An over-engineered one tries to answer questions nobody asked, and in doing so, creates new problems. More data. More noise. More privacy exposure. And a test-taking experience that generates complaints before a single result is issued

Where surveillance starts

Privacy-first proctoring is not a softer version of security. It’s a more precise one.

It starts with a design principle: collect only what is necessary to confirm identity and verify engagement. Nothing beyond that scope. No recordings stored by default. No system-level device access. No behavioral data used outside the bounds of the specific assessment.

In practice, that looks like this:

No downloads or extensions. The assessment runs in a browser. No software installs, no hidden permissions, no access to personal files or background applications. A test taker can sit the exam on any device without IT involvement or configuration.

Proportionate data collection. Every feature and every data point collected should have a clear answer to the question: why does this make the result more defensible? If the answer is “it doesn’t,” it shouldn’t be collected. Surveillance produces volume. Monitoring produces clarity.

Data minimization by design. The only data collected is what’s needed to produce a defensible result: identity verification, participation confirmation, and a reviewable record of any flagged behavior. Sensitive data, including ID images, is deleted within 24 hours.

Compliance built in, not bolted on. GDPR, PIPEDA, FERPA, and SOC2 compliance aren’t checkbox items. They reflect a commitment to proportionate data collection, the kind of approach that holds up when regulators or institutional counsel start asking questions.

Human review is what makes the result defensible

Here’s what automated flags can’t tell you: whether a behavior was actually a problem.

An algorithm can detect that a second face appeared in the frame. It cannot tell you that the second face belongs to a child who walked in, not an accomplice. It can flag an unusual eye movement pattern. It cannot determine whether that pattern indicates academic dishonesty or a medical accommodation. It can detect a background sound. It cannot decide whether that sound matters.

Those determinations require a person.

At Integrity Advocate, every flagged session is reviewed by a trained human reviewer before any outcome is issued. Not as a premium tier. Not as an add-on. As the standard, at every price point.

That’s the difference between a defensible result and an automated flag you have to explain to a grievance committee.

Programs that rely on automated proctoring alone are producing outcomes they cannot fully stand behind. When a result is challenged, and eventually one will be, “the algorithm flagged it” is not a sufficient answer. A documented, human-reviewed decision is.

The question your program should be asking

Before your next contract renewal or platform evaluation, ask this: what does your current proctoring tool collect, and who reviews it before a result is issued?

If the answer is “a lot” and “no one,” that’s the surveillance model. It may feel thorough. It isn’t defensible.

Privacy-first online proctoring isn’t about doing less. It’s about doing exactly what’s necessary, with human judgment behind every decision that matters. That’s what produces results your program can stand behind. It’s what earns trust from your learners. And it’s what holds up when the stakes are highest.

Integrity doesn’t require surveillance. It requires precision.

{{post-cta}}

A waiter is taking an online assessment to earn their alcohol serving certification. They’re at home, using a personal laptop. They scan their government ID to verify their identity. And as soon as the test starts, their webcam is on. So is screen sharing.

{{post-stat-highlight}}

Here’s the thing: online assessments like these need oversight. But that doesn’t mean they need to feel like surveillance. When proctoring tools overstep, they don’t just violate privacy—they break trust, reduce engagement and risk the credibility of the certification itself.

This isn’t about watching more screens. It’s about building systems that respect boundaries, protect integrity and actually work. 

What test administrators are actually looking for

If you’re leading training, certifying professionals or managing compliance programs, chances are you didn’t wake up this morning thinking, “Let’s go shopping for proctoring software.”

What you are looking for is peace of mind. You want to:

• Make sure the right person is taking the test
• Confirm they were engaged and followed the rules
• Keep your programs compliant and your reputation protected

That’s it. You're not trying to invade someone’s personal space or collect more data than necessary—you just need reliable verification and fair oversight.

But too many platforms miss the point. They require installs that clash with IT policies, ask for broad system access, or quietly gather data that goes far beyond what's needed. And in some cases, they’ve failed to keep that data safe.

In 2020, nearly half a million user accounts from a widely used online proctoring tool—including names, email addresses, phone numbers and home addresses—were leaked after a breach. Institutions from the U.S., UK and Australia were all impacted, and the fallout was swift: student backlash, privacy concerns and institutional scrutiny from all sides.

It was a wake-up call. When proctoring crosses the line, the risks aren’t theoretical. They’re reputational—and very real.

With Integrity Advocate, privacy isn't an afterthought. It's the starting point. No excess data collection. No invasive tech. No guesswork about where that information ends up.

Because when you’re asking users to trust you with their identity, you better be ready to protect it.

Why more surveillance doesn’t mean more security

In the race to stay compliant, it’s easy to assume that collecting more data means covering more bases. But the truth is, adding layers of surveillance doesn’t make an assessment more secure—it just makes it harder to manage risk.

Think of it like airport security with no filters: scanning every bag, flagging every item and then leaving one person to sort through it all. It’s noisy, it’s overwhelming and it misses the point. 

It’s the same with proctoring. 

Tools that over-collect create a false sense of control while actually increasing privacy exposure, friction for users and administrative burden. What organizations really need is technology that collects only what’s necessary, and human context to help make sense of it. And now, that kind of clarity isn’t just a nice-to-have. It’s becoming a requirement.

The compliance standard is rising

This isn’t just about ethics. It’s about meeting the new reality of compliance.

ANSI/ASSP Z490.1-2024 raises the bar for how training is delivered and verified. It’s not enough to say a course was offered; you now need to prove it was completed by the right person, in the right conditions, with engagement that can stand up to scrutiny.

That means identity verification. Participation monitoring. Records that hold up under audit.

But nowhere in the standard does it say you need to surveil someone’s entire desktop or store unnecessary data just to meet the mark.

The spirit of ANSI Z490.1 is accountability—not overcollection. If your current system makes compliance feel more like risk exposure, it’s time to rethink what you're using to prove integrity in the first place.

Oversight ≠ Overreach

For us, this work has never just been about tech.

It started with a simple, serious belief: when it comes to safety-critical training, the integrity of an assessment isn’t optional. It’s how lives are protected. And how organizations prove they’re doing things the right way.

That’s why we approach oversight differently.

At Integrity Advocate, we’re not here to control every click. We’re here to confirm that the right people are showing up, engaging fully and earning results that matter.

We do that by designing for trust—not surveillance.

• No installs. No plug-ins. No hidden tracking.
• Only collecting what’s necessary to confirm identity and engagement.
• Human review of flagged sessions to ensure fairness, accuracy and discretion.
• Clear, transparent policies that respect the user and reduce risk for the organization.

Our goal isn’t to catch someone. It’s to build systems that make cheating irrelevant, because integrity is built in from the start.

Scale doesn’t have to come at a cost

Meeting compliance isn’t a small-scale problem. You might be onboarding thousands of learners, recertifying entire workforces or delivering credentials across dozens of jurisdictions.

The stakes are high. And so is the volume.

But here's the good news: you don’t have to trade trust for efficiency.

When Smart Serve Ontario needed to recertify tens of thousands of workers after a provincial policy shift, they didn’t have months to redesign their program or train their users. They needed a solution that scaled overnight.

By partnering with Integrity Advocate, they got:

• No software installs.
• No new platforms to learn.
• No additional support surge.

Just seamless, secure delivery that respected their learners, stood up to scrutiny and worked at scale.

That’s what smart oversight looks like. When compliance needs to move fast, you need a partner who can keep up without cutting corners.

So, where does secure proctoring end and privacy invasion begin?

It ends the moment the solution starts collecting more than it needs. It begins the second the user feels monitored instead of supported.

That’s the line.

For compliance officers, credentialing bodies and training leaders, that line matters more than ever. The tools you choose don’t just reflect your operational standards—they reflect your values.

Proctoring should confirm identity, not compromise it. At Integrity Advocate, we don’t believe you have to choose between security and simplicity or between compliance and compassion. You can have both. You should have both.

If your current solution is starting to raise questions about trust and compliance, it might be time for a conversation. We’re ready when you are.

{{post-cta}}

The US Department of Education's Privacy Technical Assistance Center published a presentation titled Security Threats: Education Systems in the Crosshairs, in which security advisor Mike Tassey documented how data breaches, hacks, and privacy incidents have affected organizations across virtually every sector, from NASA and Citigroup to local school systems.

The warning is directly relevant to any organization using online proctoring. The data that proctoring services collect, including names, government-issued ID, biometric images, and session recordings, is exactly the kind of information that makes education systems a target.

The Threat Landscape Has Changed

Cyber-theft has become fully commoditized. There is an active black market for personal data, and an underground economy where over two million pieces of malware are built and sold every year. This malware is designed to gather precisely the kind of information proctoring platforms collect: Social Security numbers, addresses, birth dates, and identity credentials.

Tassey specifically noted that children's identities are particularly valued by data thieves because they are, in his words, fresh. A child's identity may go undetected for years before the theft is discovered, making it a high-value target for long-term fraud.

The alarming part is how malware typically gets onto devices. It is not usually through pirated software or poor security settings. It enters through plugins and browser extensions that users install themselves, often for legitimate purposes. The installation is the vector.

Why Proctoring Plugins Create Specific Risk

Most online proctoring services require users to install browser extensions or plugins to enable monitoring. Each of these installations represents an opportunity for malware to enter the device, either during the initial installation or through a subsequent update, without the user's knowledge or permission.

Tassey's research notes that on average there are one to five bugs for every 1,000 lines of code. For organizations that have not completed independent code reviews of the proctoring software they deploy, those bugs represent an unexamined attack surface. Malware can be introduced into code updates without detection, meaning a plugin that was clean at installation may not remain so.

At minimum, organizations should be instructing learners to disable or uninstall proctoring plugins and extensions immediately after use. The risk does not end when the exam does.

What a Code Review Should Cover

Organizations that require learners to install proctoring software should conduct, or require their vendor to provide evidence of, a code review that addresses:

• Potential malware embedded in the plugin or extension code
• Errors or vulnerabilities that could be exploited by third parties
• Whether the software receives automatic updates, and what review process governs those updates
• What data the software transmits, to where, and under what conditions

If a vendor cannot provide clear answers to these questions, the software should not be deployed on learner devices.

The Case for No-Installation Proctoring

The most effective way to eliminate installation-based security risk is to remove the installation requirement entirely. Integrity Advocate's platform is browser-based and requires no plugin, extension, or application installation in most cases. There is nothing to install, nothing running in the background after the session ends, and no update mechanism that could introduce malware without the user's knowledge.

For use cases that do require a lockdown browser, Integrity Advocate's solution uses fully open source code, does not accept automatic updates after installation, and does not transmit data beyond what is required for the session. The code is publicly available for inspection.

The US Department of Education's guidance on protecting student privacy points to the same principle: the safest data handling approach minimizes what is collected, minimizes how long it is retained, and minimizes the software footprint on learner devices.

{{post-cta}}