Best Practice Checklists

An exclusive publication of

Essentials every leader should understand about IT


Issue 9 – Workstation Security, Standards, and Practices

Workstation Security, Standards, and Practices — download the printable PDF

Download this article as a PDF

Click Here to Download
Contact Us

Workstation Security & Standards

The device on every desk is the easiest way into your network

Workstations, the laptops and desktops your people use every day, are where most security incidents begin. They open the email, browse the web, and hold the credentials. Two things decide how much risk each one carries: how tightly it is locked down, and how consistently it is built, patched, and maintained. The situations below are ordinary, and each traces back to one of those two choices.

When it goes wrong

No workstation can be made perfectly secure, and that is not the goal. The goal is to remove the easy paths, the ones that turn a single mistake or a lost laptop into an organization-wide problem. The scenarios below are common, and in each case the outcome was largely decided before it happened.

The user who is also an administrator

An employee with local administrator rights on their laptop clicks a convincing attachment. Because the account can install anything, the malware installs itself, disables protections, and reaches for other machines on the network. The same click from a standard account would very likely have gone nowhere.

One ordinary mistake becomes a network-wide incident.

The machine nobody updated

A single workstation is skipped by patching and quietly left on an operating system that no longer receives security updates. Months later it is the one door still unlocked, and it is where an intruder gets in.

The whole network is judged by its least-maintained device.

The laptop left in a car

A laptop is lost or stolen. The login password feels like protection, but the drive is not encrypted, so the drive can be removed, attached to another computer, and read in full: every file, cached email, and saved password on it.

A missing laptop becomes a reportable data breach.

Fifteen machines, fifteen configurations

Workstations were set up one at a time, each a little different, with no standard build. Nobody can say with confidence what is installed, what is patched, or what is protected, so securing them consistently, or supporting them quickly, becomes guesswork.

You cannot secure or support what you cannot describe.

The common thread

None of these is exotic. Each traces back to the same two decisions: how much a single workstation is allowed to do (its privilege and exposure), and how uniformly the fleet is built, patched, and maintained over its life.

Almost every one of these outcomes could very likely have been prevented, not by spending more, but by limiting what each workstation can do and by building and maintaining every machine to one known standard. That is what the rest of this issue is about.

What to Ask Your IT Manager or Provider

and how to know if the answers are good ones

You do not need to manage a fleet of workstations yourself to oversee how they are secured. You need to know what to ask. Security is rarely convenient, and users understandably push back, so the commitment has to be visible and supported from the top. A short primer on some of the terms is provided at the end, for those who want it. First, the part that matters: run the checklist below with your IT professional. If any item is not marked green, it may warrant a closer look.

Standard, Documented Build

✓
–
?
Are workstations deployed from a standard, documented build (a common image or configuration baseline) rather than set up one at a time? A known-good standard build means every machine starts with the same protections, the same patch level, and only approved software. It is what makes a fleet possible to secure consistently, support quickly, and reason about at all. Ad-hoc builds are the opposite: each one is a small unknown.

Hardening Standards

✓
–
?
Have formal hardening standards been adopted for all workstations, with any exceptions documented? Hardening reduces the ways a workstation can be attacked, for example by restricting user rights, tightening the local firewall, and limiting cached credentials. The National Institute of Standards and Technology (NIST) publishes widely used benchmarks for this. They are not one size fits all; some settings may need adjusting so people can do their jobs, which is why exceptions should be written down rather than made quietly.

Least Privilege (No Local Admin Rights)

✓
–
?
Have local administrator rights been removed from everyday user accounts? Much malware needs administrative rights to take full effect: to install itself, disable protections, or change security settings. Removing local admin from normal accounts reduces the likelihood that a single click becomes a serious infection, and it also stops users from installing unauthorized software or bypassing policy. It is one of the highest-value, lowest-cost controls available.

Endpoint Protection

✓
–
?
Is centrally managed endpoint protection deployed and monitored on every workstation? Traditional signature-based antivirus still has a role, but on its own it misses a great deal. Modern endpoint detection and response (EDR) watches for suspicious behavior, not just known files, and lets a threat be isolated and investigated across the fleet. Many organizations now treat EDR, or a managed service built on it, as the baseline. Whichever approach is used, it should be centrally managed and actively monitored, not left to each machine on its own.

Patching and Supported Operating Systems

✓
–
?
Are operating systems and applications patched automatically, and are unsupported or end-of-life systems retired? Vendors release updates to close security holes, and unpatched machines are a favored way in. Just as important, an operating system past its end of support stops receiving those updates entirely. Windows 10, for example, reached end of support in October 2025, which makes Windows 11 the current baseline for most organizations (limited paid extended-update programs exist, but they are a bridge, not a destination). Machines that cannot run a supported system should be planned for replacement.

Whole-Disk Encryption

✓
–
?
Is whole-disk encryption enabled on every workstation and laptop, with recovery keys managed centrally? On an unencrypted device, a login password is little protection: the drive can be removed, attached to another computer, and read in full, including files, cached email, and saved passwords. Whole-disk encryption is designed to prevent that. The tools are built in (BitLocker on Windows, FileVault on Mac), but the keys should be managed and escrowed centrally, so encryption protects the data without locking the organization out of it.

DNS Filtering

✓
–
?
Do workstations browse through a DNS service that blocks known-malicious destinations? DNS filtering checks the sites a machine tries to reach against known-bad and suspected-bad lists, and steers traffic away from phishing pages, drive-by infections, and malware command sites before a connection completes. It adds a quiet, low-friction layer that catches a meaningful share of everyday web threats.

Multifactor Authentication and Strong Passwords

✓
–
?
Is access protected by multifactor authentication, backed by a strong password policy? A password alone is a single point of failure. Multifactor authentication adds a second requirement, something the user has, so a stolen or guessed password is not enough on its own. Longer, more complex passwords remain the necessary first factor. It is recommended that MFA be applied wherever it is practical.

Automatic Screen Lock

✓
–
?
Do workstations lock automatically after a short period of inactivity? An unattended, logged-in machine is an open door to anyone nearby. Users should lock their screens whenever they step away, and machines should also lock on their own after a brief idle period, commonly no more than fifteen minutes and ideally less.

Removable Media Controls

✓
–
?
Is the use of removable media, such as USB drives, controlled? Unmanaged USB devices cut both ways: they can carry malware in, and they can carry data out. Policy can disable unauthorized USB storage while still allowing approved devices to function. Because this touches how people actually work, it warrants testing and a review of workflows before it is enforced.

Authorized Software and Cloud Storage

✓
–
?
Is software limited to what the organization has vetted, and are personal cloud-sync tools controlled? Unvetted software introduces instability and unpatched flaws, degrades performance, and can shorten a workstation’s useful life. Consumer file-sync services (for example personal Dropbox or iCloud accounts) add their own risks: sensitive data leaving the organization’s control, and auto-sync silently spreading corrupted or ransomware-encrypted files to other machines. Both are best restricted to approved, managed options.

Remote Access Controls

✓
–
?
Is remote access limited to company-approved solutions, granted only where there is a business need? Remote access and VPN rights should go only to trusted staff who need them, reach only the systems they require, and be approved by both the relevant department and IT management. Any third-party remote-access tool should be vetted, documented, and formally approved before it is used.

Centralized Management and Monitoring

✓
–
?
Are workstations centrally managed and monitored, for example through a Remote Monitoring and Management (RMM) platform? Centralized management is how patches actually get deployed, how failures get noticed, and how protections stay consistent across every machine. Misconfigured or missing management is how workstations quietly drift out of compliance. It should be deployed and verified on every relevant device, not assumed.

Power Protection and Lifecycle

✓
–
?
Are workstations protected from power events and replaced on a planned lifecycle? Surges and brief outages can damage hardware and lose unsaved work, so equipment should run through surge protection, ideally with a small battery backup that allows a graceful shutdown, and never straight into a wall receptacle. Separately, aging machines should be replaced on a deliberate schedule. Stretching hardware past its useful life tends to cost more in support, downtime, and risk than it saves, and replacements are usually most economical when planned in groups.
A short primer on the termsPlain-English definitions, for whoever wants them. Optional.+

Least privilege and local administrator rights

A local administrator account can install software, change system settings, and disable protections on that machine. Least privilege means giving each account only the rights its work requires, which for most everyday users means not running as an administrator. It is one of the most effective ways to limit the damage a single mistake or piece of malware can do.

Hardening and NIST benchmarks

Hardening turns off or tightens system features that are not needed, reducing what an attacker can exploit. NIST maintains the National Checklist Program, a repository of security configuration checklists and benchmarks from multiple publishers. These references are starting points to evaluate and adapt; some settings will not fit every environment.

Endpoint protection: antivirus and EDR

Traditional antivirus works mainly by recognizing known-bad files. Endpoint detection and response (EDR) goes further, watching how software behaves and flagging suspicious activity even when the specific threat has not been seen before, and giving responders a way to isolate and investigate an affected machine. Many organizations now treat EDR, or a managed service built on it, as the baseline rather than signature antivirus alone.

Whole-disk encryption

Whole-disk encryption protects stored data so that a removed or stolen drive cannot simply be read without the required keys. Supported Windows editions provide BitLocker, commonly using a Trusted Platform Module (TPM). Macs provide FileVault; Apple silicon and T2-equipped Macs use the Secure Enclave for key protection. Recovery keys should be managed and stored securely so loss of an access credential does not become loss of the data.

Standard build (imaging)

A standard build, or image, is a single approved configuration (the operating system, settings, protections, and approved software) that every new or rebuilt workstation starts from. It makes machines predictable: easier to secure the same way, faster to support, and quicker to replace when one fails.

Download the printable PDF

To review how your organization’s workstations measure up against these practices, it is recommended that you consult your Sandbox Technologies Engineer, Consulting CIO, or Account Manager. Not a client yet? Contact us here to get started.

Contact Sandbox Technologies for a free, no-obligation consultation.

Headquartered in Los Angeles. Serving clients nationwide and internationally since 1997.

Nationwide (Toll-Free)

877-930-8324

Los Angeles

424-207-5130

Support Helpdesk

424-207-5140

    By submitting this form you are confirming that you have read and agree to our Privacy Policy

    * NOTE: Hardware purchase requests submitted via this form will not be honored. Hardware sales are facilitated in support of established customer accounts only.