What Is Proctored Exam Device Security? (Lockdown Browser)
Proctored exam device security is the set of checks and controls used to limit or detect unauthorized activity during an online exam. A lockdown browser may restrict supported features on the device, but it cannot guarantee exam integrity or replace endpoint security. The exam provider’s current requirements determine which device, settings, and software are allowed.
A surprising detail in a typical system check is that a device can pass its technical test and still be unsuitable for a particular exam. The check may confirm a camera and microphone work, for example, but not prove that the device meets every exam rule or blocks every way of accessing outside help. I use a simple example throughout: a student’s laptop passes its basic check, but the exam requires an assistive tool that has not yet been approved.
The right approach is to verify the rules, prepare a supported device, test the actual setup, and record any approved exception. That protects exam access without weakening the device’s security or privacy safeguards.
What proctored exam device security means
Proctored exam device security means applying the exam provider’s approved settings and tools to a device used for a monitored test. A lockdown browser is one part of this setup. Depending on the exam and operating system, it may restrict or detect certain activity, but its functions are not universal.
A lockdown browser is an exam application designed to limit access to selected device or browser functions while an exam is active. The exact restrictions vary. One provider may block other applications; another may use a different control or add remote monitoring. Do not assume a feature exists unless the provider documents it for your exam.
A useful security model has three parts:
- Device controls: operating-system settings, accounts, and approved security software.
- Exam controls: the provider’s browser or application, exam rules, and proctoring process.
- User and environment controls: the permitted workspace, required peripherals, and exam-day conduct.
The browser does not make a device fully isolated. It may not prevent someone from using a second device, another account, or an unsupported system path. For higher assurance, use a provider-approved managed device and endpoint controls where required.
NIST SP 800-53 Rev. 5 offers three relevant principles. AC-3, access enforcement, means access should follow approved rules. AC-6, least privilege, means users should have only the access they need. CM-7, least functionality, means unnecessary features should be limited when doing so does not disrupt the exam or required tools. These principles guide setup; they do not replace provider instructions.
Plan the exam device and confirm provider requirements
Before changing settings or installing software, identify the exact exam, its provider, and its rules. There is no universal lockdown-browser specification: supported operating systems, versions, account rights, network needs, peripherals, and accessibility options differ by provider and exam configuration.
Start with the provider’s current documentation for the specific exam. Confirm:
- Supported operating system and minimum version.
- Whether installation or setup requires an administrator.
- Required camera, microphone, display, and browser or application.
- Network requirements, including any published destinations or ports.
- Permitted assistive technology and any approval process.
- Privacy notices, consent terms, and support contact details.
- Whether a personal, school, or managed device is allowed.
Record the source and date of the requirements. A system that worked for a past exam may no longer meet current rules after an operating-system update or policy change. If the instructions are unclear, ask the provider or authorized IT team before changing security settings. The next step is to compare each requirement with the actual device and network.
Check account, peripheral, network, and accessibility needs
Compatibility is more than installing the application. The device must meet the exam rules while keeping approved security controls and required access tools available. Check the account, hardware, connection, and accessibility needs together, since a change in one area can affect another.
Use this checklist before setup:
- Account: Confirm which user account will take the exam and whether installation needs administrator approval. Avoid leaving a shared exam account with unnecessary administrator rights.
- Peripherals: Check that the required camera, microphone, and display are present and recognized. Follow the provider’s specifications; there is no universal camera or screen requirement.
- Network: Use the provider’s published network guidance. Do not invent or apply a generic port list. On a managed network, ask its administrator to review any requested access.
- Accessibility: Confirm that screen readers, dictation, input devices, or other accommodations are permitted and supported. Request approval before disabling, replacing, or working around a tool.
- Privacy: Read what the monitoring application collects, when recording may occur, and how consent is handled. Contact the provider with questions before the exam.
Avoid disabling antivirus, endpoint protection, firewall rules, or operating-system security features just to get past an error. Instead, capture the error message and contact the provider or authorized IT support. A compatibility issue should be resolved through an approved path, not by weakening the device.
Install and configure the approved lockdown browser
Install only the application named in the current exam instructions, using the provider’s official or approved download source. Follow its steps in order, and do not use unofficial installers, hidden workarounds, or unsupported virtual-machine or remote-access setups.
A careful installation sequence is:
- Update the operating system and approved security software, if provider policy permits.
- Confirm the device, account, and exam mode meet the documented requirements.
- Download the official application from the provider’s approved source.
- Complete installation with authorized permissions. If approval is required, ask the device owner or IT administrator.
- Run the provider’s system check on the actual device and network intended for the exam.
- Test sign-in and each required camera, microphone, display, and approved accessibility tool.
- Read any prompts about permissions, monitoring, or consent before accepting them.
Do not disable a security control to force installation or bypass a failed check. A conflict may need a provider update, an approved exception, or a different supported device. If the provider permits a particular configuration, keep a record of that approval.
Verify system readiness and record exceptions
A system check is a practical test of the device against the provider’s current requirements. It is not proof that every exam control works in every situation. Test the full setup, document the result, and repeat the check after relevant software, device, network, or exam-policy changes.
Use a short readiness record:
| Item | What to record | If it fails |
|---|---|---|
| Device and operating system | Model or device name, OS, and version | Check provider support; contact authorized IT |
| Exam application | Official application name and version, if shown | Use provider instructions for updates |
| System check | Date, pass or fail result, and messages | Save the error; ask provider support |
| Camera and microphone | Whether the provider’s test recognizes them | Check permitted settings and device access |
| Network | Connection used and any provider check result | Ask the network administrator or provider |
| Accessibility tools | Tool and approval status | Do not disable; request a supported solution |
| Exception | Approval source, scope, and date | Confirm it remains valid for this exam |
Use the provider’s own pass criteria. There is no universal speed, port, screen-size, or hardware threshold that applies to every lockdown browser. If a check fails, record the exact message and the time it occurred. Avoid repeated unapproved changes, since they can make diagnosis harder or violate exam rules.
Real-world setup examples
These examples show how the same security principles apply to different situations. They are illustrative scenarios, not claims about a particular provider’s software. In each case, the provider’s published instructions and approved support path decide what is acceptable.
A personal laptop with a failed application check: The student’s camera works, but the exam application reports an unsupported operating-system version. The safe response is to check the current supported-version list and seek an approved update or alternate device. Do not install an unofficial version or bypass the check.
A managed work or school laptop: The user cannot install the browser because administrator approval is required. That restriction may be part of the organization’s security policy. Ask the authorized administrator to review the official application and exam instructions; do not remove management controls or use a hidden installer.
An approved accessibility tool is blocked: The device passes its basic check, but the student needs a screen reader or other accommodation. Contact the provider’s accessibility or exam-support channel before the exam. Ask which configuration is supported and document approval. Do not turn off protections or attempt an unapproved workaround.
In each scenario, the goal is not simply to make the application launch. It is to meet the exam rules while preserving approved security controls and access needs.
What a lockdown browser can and cannot secure
A lockdown browser can apply restrictions supported by its design, operating system, and exam configuration. It may also detect certain conditions. Its presence alone does not prove that the device is isolated or that every form of unauthorized assistance is prevented.
A clear comparison helps set expectations:
| Setup | What it can support | What it does not establish |
|---|---|---|
| Lockdown browser | Provider-defined limits or checks within its supported environment | Protection against every device-level threat or a second device |
| Updated device and security software | General endpoint protection and current system fixes | Compliance with every exam’s separate rules |
| Managed, provider-approved device | A more controlled setup when required | A guarantee that misconduct is impossible |
| Successful system check | Evidence that tested requirements passed at that time | Proof that all controls or future changes will work |
For higher assurance, follow the provider’s managed-device requirements and the organization’s endpoint policies. Keep normal security protections enabled. A browser restriction is one control in a wider process, not a substitute for device security or exam oversight.
Conclusion: prepare, test, and document
A dependable exam setup starts with the provider’s current rules, not a generic lockdown-browser checklist. Confirm the supported device and operating system, preserve approved security and accessibility tools, install only the official application, and test the exact setup you plan to use.
Record the system-check result and any approved exception. Recheck after relevant updates or policy changes. If a requirement conflicts with an organization’s security policy or an accessibility need, contact the provider and authorized IT support rather than using an unapproved workaround.
FAQ about proctored exam device security
These answers summarize the core setup rules. Providers differ, so use them as a starting point and confirm details in the instructions for your specific exam before installing software or changing device settings.
What does a lockdown browser do?
It applies exam-specific restrictions or checks supported by the application and device. Features differ by provider, operating system, and exam.
Does a lockdown browser prevent all cheating?
No. It cannot guarantee exam integrity or, by itself, prevent every system-level threat or use of a second device.
Is there one device specification for all proctored exams?
No. Supported operating systems, versions, peripherals, network rules, and account needs vary. Check the current requirements for your exam.
Should I turn off antivirus or my firewall if the browser fails?
No. Keep security controls enabled. Share the error with the provider or authorized IT support and follow their approved fix.
Can I install a lockdown browser without administrator access?
It depends on the application and device policy. Follow the provider’s installation instructions and request authorized approval if needed.
Can I use a screen reader or other assistive technology?
Possibly, but support and approval vary. Contact the provider before the exam and test the approved setup.
Does a successful system check guarantee exam readiness?
No. It confirms only what the provider’s check tested at that time. Recheck after relevant changes and follow all exam instructions.
Can I use a virtual machine or remote-access setup?
Only if the provider explicitly approves it. Unsupported configurations may fail checks or violate exam rules.
What should I record during setup?
Record the device and operating-system version, application version if shown, check date and result, support contact, and any approved exception.
What should I do if the exam app conflicts with my work or school device?
Do not bypass management controls. Ask the authorized administrator and exam provider to identify a supported option.
(This article was written by one of our staff writers, Garrett Vance. Visit our Meet the Team page.)
