Secure browsers and controlled environments aim to limit what a candidate can access during an assessment session. They are attractive because they can reduce obvious routes to misconduct without full live surveillance, but they only solve part of the integrity problem. The important question is whether restricting the device genuinely protects the construct being assessed or simply adds friction around a task that still needs redesign.

Secure browsers and controlled environments are tools that restrict access to websites, applications, clipboard actions, messaging, screenshots, or operating-system features during an assessment. In practice, they are often combined with authentication, logging, or proctoring rather than used alone;;.

These controls can be a proportionate response when the key risk is access to unauthorised resources on the candidate's own device. They are especially relevant when an assessment depends on unaided recall, tightly bounded procedure, or a standardised test-session experience.

- **Lockdown**: preventing access to external resources or system features. - **Controlled workstation**: a device or device state configured for assessment conditions. - **Construct alignment**: whether the restrictions fit what the assessment is meant to measure. - **Candidate friction**: the technical burden placed on the learner before or during the test.

The sources suggest that secure browsers are a common part of the assessment security stack because they address a simple problem clearly: access to unauthorised digital resources during a session;. There is also a practical consensus that browser controls work best when the misconduct route really is device access. They do less to solve impersonation, off-screen assistance, or tasks whose design already invites external support.

The main contest is about validity and proportionality. A browser lockdown may be sensible for one assessment and distortive for another. If the construct allows consultation, workflow tooling, or applied judgement, tight restriction can make the task less realistic rather than more defensible. There is also tension around user experience. Installation, compatibility, and support demands can turn a light-touch control into a heavy operational burden.

- accessibility barriers - device compatibility failures - increased candidate anxiety and support demand - false assurance if off-device misconduct remains easy - construct drift when restrictions no longer match the skill being assessed

1. Start with the assessment purpose, not the software feature list. 2. Decide whether restricting device access really protects the evidence you need. 3. Test on candidate hardware, networks, and accessibility setups. 4. Pair browser controls with clear incident handling and support. 5. Review whether the same assurance could come from redesign rather than tighter restriction.

| Option | Strength | Limitation | |---|---|---| | **Dedicated secure browser** | Clear control over the device environment | Installation and compatibility burden | | **Browser plus remote proctoring** | Better visibility of session behaviour | Higher privacy and review overhead | | **Centre-based controlled workstation** | Stronger environmental control | Less flexible and more expensive |

A higher education provider wants to stop students switching tabs during a timed remote exam. A secure browser can help with that specific risk, but if the task can still be outsourced through another device or a nearby helper, the real decision is whether the exam design itself needs strengthening.

- Supplier note on secure browser environments for e-assessments. - Supplier note on LockDown Browser and automated proctoring for higher education. - Supplier note on browser-based controls and assessment protection.

This part of the market sits between light-touch environment control and full remote proctoring. Some products pitch themselves as privacy-conscious alternatives to heavier surveillance, while others present browser restriction as one layer inside a broader proctoring stack.

### Are secure browsers enough to stop cheating? They can narrow one route to misconduct, but they do not solve identity, off-screen assistance, or weak task design. ### Are secure browsers more privacy-friendly than full remote proctoring? Often yes, but that depends on what other logging, monitoring, or integrations are bundled with them. ### When should I choose a secure browser over redesign? When device restriction clearly matches the construct and the main risk is on-device access. If the task is already unrealistic under those conditions, redesign is usually the stronger move.

Tim Burnett (Admin)

`Test Community Network. "Secure browsers and controlled environments." TCN Wiki. Last reviewed 2026-05-03. https://www.testcommunity.network/wiki/secure-browsers-and-controlled-environments`

- Supplier note on secure online assessments, identity and originality verification, content protection, privacy, encryption, and minimal PII. - Supplier note on LockDown Browser and automated proctoring for higher education. - Supplier note on secure browser environments for e-assessments.