What to Know Before Designing a Locked Down Workstation for Exam Proctoring

Most exam security failures do not come from a missing tool. They come from decisions made too late: a build that the exam vendor does not support, a network allowlist nobody maintained, or a lockdown that quietly blocks a candidate's screen reader on exam day. Before you configure a single policy, there are questions worth answering first.

This guide covers what to settle before you design the workstation: your risk level, vendor constraints, legal duties, budget, and operating model. Getting these right makes the technical build far easier and far less likely to be redone.

Why Planning Comes Before Configuration

A locked down workstation is a set of trade-offs. Tighter control raises security but also raises cost, support effort, compatibility risk, and the chance of locking out a legitimate candidate. Without clear requirements, teams tend to either under-protect high-stakes exams or over-engineer low-stakes quizzes.

Planning first helps you:

• Match controls to the actual threat, not to a generic checklist
• Avoid buying hardware or software the exam vendor will not support
• Build accessibility and privacy in from the start instead of patching them in
• Estimate true cost and staffing before committing
• Define what "success" looks like so you can test against it

1. Classify Your Exams by Stakes and Threat

Not every exam needs the same lockdown. Start by sorting your exams into tiers.

• Low stakes: Practice tests, weekly quizzes, and ungraded assessments. A secure browser on personal devices may be acceptable.
• Medium stakes: Course finals and internal certifications. Managed or institution-issued devices with a secure browser and basic proctoring are common.
• High stakes: Licensure, professional certification, admissions, and regulated testing. These usually justify managed hardware, full OS and network lockdown, and live or hybrid proctoring.

For each tier, identify the realistic threats:

• Looking up answers on other websites or AI tools
• Collaborating with another person, in the room or remotely
• Copying or capturing exam content to share later
• Impersonation, where someone else sits the exam
• Running a virtual machine or remote desktop to get outside help
• Tampering with the device or network

The more serious the consequences of a compromised exam, the more layers you need.

2. Understand Your Exam Vendor's Requirements

Your exam or proctoring platform often dictates the design. Before building anything, collect from the vendor:

• Supported operating systems and exact versions
• Hardware specifications, including webcam, microphone, and display requirements
• Required network destinations, ports, and bandwidth
• How their lockdown software works and what it does and does not enforce
• Whether they certify specific configurations or images
• Update and release schedules, so you can plan freeze periods
• Support terms if you run an unsupported configuration

A build that works beautifully but is unsupported by the vendor can leave you without help when something fails mid-exam.

3. Choose Your Deployment Scenario Early

Where the exam takes place shapes everything.

• Managed test centre or campus lab: Maximum control over hardware, network, and room.
• Institution-issued laptops: Good OS control, limited control over the room and home network.
• Bring-your-own-device: Lowest cost, but you can only enforce what the lockdown software can reach.
• Bootable secure environment: Better control on personal hardware, but needs compatibility testing.
• Virtual desktop for exams: Keeps the exam environment off the local machine, but depends heavily on network quality.

Be honest about what each scenario can and cannot guarantee. A BYOD secure browser cannot match the assurance of a managed lab, and your policies and exam stakes should reflect that.

4. Know Your Legal, Privacy, and Fairness Obligations

Proctoring involves sensitive personal data, and the rules vary by region and sector. Before design, find out:

• Data protection laws that apply to your candidates, such as GDPR, CCPA, or local equivalents
• What you intend to record: video, audio, screen activity, room scans, keystrokes, or biometric data
• Consent and notice requirements for each type of capture
• Retention limits for recordings and logs, and who may access them
• Education or certification regulations that govern assessment delivery
• Cross-border data transfer rules if recordings are stored in another country

Collect only what you need. Excessive surveillance damages candidate trust and increases legal risk without necessarily improving integrity. If you use automated or AI-based flagging, plan for human review so no candidate is penalized by an algorithm alone, and provide an appeals process.

5. Plan for Accessibility From Day One

Lockdown that excludes candidates with disabilities creates legal exposure and unfair outcomes. Decide up front:

• Which assistive technologies you must support, such as screen readers, magnification, speech input, and alternative keyboards
• How approved tools will be allowed through the application allowlist
• How accommodations such as extra time or rest breaks are handled in the exam system
• Who approves accommodations and how candidates request them
• How you will test assistive technology with the exam client before exam day

Treat accessibility as a design requirement, not an exception handled later.

6. Decide on Your Proctoring Model

The workstation must support the way you supervise exams.

• In-person: Needs room layout, camera coverage, sightlines, spacing, and privacy filters.
• Live remote: Needs reliable webcam, microphone, and screen streaming with enough bandwidth.
• Recorded and automated: Needs session recording, flagging, storage, and human review capacity.
• Hybrid: Combines automated monitoring with live intervention.

Each model has different hardware, bandwidth, staffing, and privacy implications, so choose before you finalize the build.

7. Assess Your Network and Infrastructure Reality

The most locked down device still fails if the network cannot carry the load or is too open. Check:

• Available bandwidth at peak concurrency, including logins, content downloads, and proctoring streams
• Whether you can create an isolated VLAN or segment for exam devices
• Whether you control firewall and DNS rules, or depend on another team
• Wired versus wireless availability in your exam rooms
• Internet reliability, and whether you need redundancy or local caching
• How candidates will resume after an outage without losing answers

If you cannot control the network, adjust your assumptions about the level of assurance you can offer.

8. Be Realistic About Skills and Support

A strong design needs people to run it. Ask:

• Do you have staff who can build, harden, patch, and troubleshoot the workstation image?
• Who covers exam windows, including evenings, weekends, and early mornings?
• Will you use in-house support, a vendor-managed service, a managed service provider, or a hybrid?
• What are your response and resolution targets during an exam?
• Where will spare hardware be kept, and who can swap it?
• Who decides what to do when a candidate's session fails or cheating is suspected?

Many projects underestimate ongoing support. The build is a one-time effort, but running exams reliably is continuous.

9. Estimate Costs Honestly

Costs vary widely by region, vendor, and scale, so request real quotes. Consider:

Upfront

• Workstations, webcams, headsets, and peripherals
• Lockdown and proctoring software licences
• Network segmentation, firewall, and wireless changes
• Room preparation, furniture, and privacy screens
• Image building, testing, and pilot exams

Ongoing

• Software subscriptions and per-exam or per-candidate fees
• Support staffing and exam-day coverage
• Patching, monitoring, and change control
• Bandwidth and connectivity
• Hardware repair, refresh, and spares
• Proctor training and candidate support
• Storage and secure retention of recordings

Compare options over a three to five year horizon. A cheap build that needs constant intervention can cost more than a better-designed one.

10. Define Success Measures and Test Plans

Decide in advance how you will know the design works.

• Technical measures: Session failure rate, login time, crash frequency, and recovery time
• Integrity measures: Number and type of incidents, escape attempts detected, and confirmed violations
• Candidate experience: Support requests, satisfaction, and accessibility issues
• Operational measures: Time to resolve incidents and exam-day staffing needs

Plan adversarial testing as well. Before candidates ever see the system, have your own team try to break it using keyboard shortcuts, USB devices, virtual machines, screen sharing, alternate boot options, and network bypasses.

Pre-Design Readiness Checklist

1. Have we classified exams by stakes and defined the threats for each tier?
2. Do we have the exam vendor's supported configurations and network requirements?
3. Have we chosen a deployment scenario for each exam type?
4. Do we understand our privacy, consent, and retention obligations?
5. Have we defined accessibility requirements and accommodation processes?
6. Have we chosen a proctoring model and confirmed its hardware and bandwidth needs?
7. Do we control, or have access to, the network changes we need?
8. Do we have the skills, staffing, and support model for exam windows?
9. Is our budget based on real quotes and a multi-year view?
10. Have we defined success measures and an adversarial testing plan?

If you cannot answer yes to most of these, resolve the gaps before building.

Common Mistakes to Avoid

• Designing before classifying risk, leading to over- or under-protection
• Ignoring vendor requirements, then discovering the build is unsupported
• Treating accessibility as an afterthought
• Collecting more data than needed, raising privacy risk
• Assuming the network will cooperate without confirming control and capacity
• Underestimating ongoing support effort
• Skipping adversarial testing
• Making changes close to exam day instead of enforcing a freeze period
• Relying on a single control, such as a secure browser alone

Conclusion

A locked down exam workstation succeeds or fails long before the first policy is applied. The strongest designs begin with clear exam risk tiers, vendor requirements, legal and privacy obligations, accessibility needs, and an honest view of network, staffing, and budget. With those answers in hand, the technical build becomes a matter of execution rather than guesswork.

Take the time to settle these questions first, test your own defenses before candidates do, and plan for support on exam day. You will end up with a workstation that protects exam integrity while remaining fair, stable, and respectful of the people who rely on it.

Frequently Asked Questions (FAQ)

1. What should I decide first when planning a locked down exam workstation?
Start by classifying your exams by stakes and identifying realistic threats. This determines how many layers of control you need, whether managed hardware is justified, and which proctoring model fits. Everything else, from budget to network design, follows from this risk assessment.

2. Why do I need to check with my exam vendor before building the workstation?
Exam platforms have specific requirements for operating systems, hardware, network access, and lockdown behavior. An unsupported configuration can cause failures during exams and leave you without vendor support. Collecting these requirements first prevents costly rework.

3. What privacy issues should I consider before proctoring candidates?
Identify what you will record, such as video, audio, screens, or room scans, and confirm the consent, notice, retention, and data transfer rules that apply to your candidates. Collect only what you need, secure stored recordings, and ensure human review of any automated flags.

4. How do I make sure lockdown does not exclude candidates with disabilities?
Define the assistive technologies you must support, allow approved tools through your application controls, and test them with the exam client before exam day. Set up a clear accommodation request and approval process so candidates can get the support they need.

5. How much should I budget for an exam proctoring workstation setup?
Costs depend on scale, hardware, software licences, network changes, and support needs, so get detailed quotes. Include both upfront costs and ongoing expenses such as subscriptions, staffing, patching, repairs, and recording storage, and compare options over three to five years.

Work with eSparks IT Solutions

Planning a project around this? We work with businesses in the United States, Canada and the UAE, as well as the UK and Australia. See a related project: Phone Vault. Explore our Programming services and portfolio, estimate your project cost, or book a free call.