The Essential Checklist for Securing Company Laptops at Home

Tanya Wetson-Catt • 7 April 2026

At home, security incidents don’t look like dramatic movie hacks. They look like stepping away from your laptop during a delivery, or leaving it unlocked while you grab something from another room.


Those ordinary moments, repeated over time, are how work devices end up exposed.

A remote work security checklist focuses on simple, practical controls that hold up in real life. Put it in place once, make it routine, and you’ll prevent the kinds of issues that hurt most because they were entirely avoidable. 

 

Why Home Is a Different Security Environment


A work laptop doesn’t magically become “less secure” at home. But the environment around it does.


In the office, there are built-in boundaries: fewer shared users, fewer casual touchpoints, and more predictable networks. At home, that same laptop is suddenly operating in a space designed for convenience, not control.


For starters, physical exposure goes up.


At home, devices move from room to room, sit on tables and countertops, and are left unattended for short stretches throughout the day.


 That’s why a remote work security checklist must treat physical security as part of cyber security.


In its training on device safety, CISA stresses the basics: keep devices secured, limit access, and lock them when you’re not using them. Those simple habits matter more at home because there’s no “office culture” quietly enforcing them for you.


Second, home is where work and personal life collide, and that creates messy, very human risks.


The NI Cyber Security Centre is blunt about it: don’t let other people use your work device, and don’t treat it like the family laptop.


Third, the network is different.


Home Wi-Fi often starts with default settings, old router firmware, or passwords that have been shared with everyone who’s ever visited.


CISA’s guidance on connecting a new computer to the internet offers the baseline steps many people skip at home: secure your router, enable the firewall, use anti-virus, and remove unnecessary software and default features.


Finally, remote access raises the stakes for identity. In its remote workforce security guidance, Microsoft’s best practices frames remote security around a Zero Trust approach and emphasizes that access should be strongly authenticated and checked for anomalies before it’s granted.


The Remote Work Security Checklist


Use this remote work security checklist as your “minimum standard” for company laptops at home. It’s designed to be practical, repeatable, and easy to enforce without turning everyone into part-time IT employees.


Lock the Screen Every Time You Step Away


Set a short auto-lock timer and get into the habit of locking manually, even at home.


Store the Laptop Like it’s Valuable


Assume that “out of sight” is safer than “out of the way.” When you’re finished, store your device somewhere protected, not on the couch, not on the kitchen counter, and never in the car.


Don’t Share Work Laptops with Family


At home, good intentions can still lead to accidental clicks. Even a quick “just checking something” can result in risky downloads, unfamiliar logins, or unwanted browser extensions.


Use a Strong Sign-In and MFA


Use a long passphrase, not a clever but short password, and never reuse it across accounts. Treat multifactor authentication (MFA) as a baseline requirement, not a nice extra.


Stop Using Devices That Can’t Update


If a laptop can’t receive security updates, it’s not a work device. It’s a risk.


Patch Fast


Updates are where most known issues get fixed. The longer you wait, the bigger the risk. Enable automatic updates and restart when prompted.


Secure Home Wi-Fi Like it’s Part of the Office


Use a strong Wi-Fi password and enable modern encryption. If your router still has the default admin login or hasn’t been updated in a long time, consider that your cue to fix it.


Use the Firewall and Keep Security Tools Switched On


Turn on your firewall, keep antivirus software active, and make sure both are properly configured. If security tools feel inconvenient, don’t switch them off, address the friction instead.


Remove Unnecessary Software


The more apps you install, the more updates you have to manage, and the more opportunities there are for something to go wrong. Remove software you don’t need, disable unnecessary default features, and stick to approved applications from trusted sources.


Keep Work Data in Work Storage


Storing work data in approved systems keeps access controlled, audit-ready, and much easier to recover if something goes wrong. Avoid saving work documents to personal cloud accounts or personal backup services.


Be Wary of Unexpected Links and Attachments


If a message pressures you to click, open, download, or “confirm now,” treat it as suspicious. When in doubt, verify the request through a separate, trusted channel before taking any action.


Only Allow Access From “Healthy Devices”


The safest remote setups gate access based on device health. Microsoft warns that unmanaged devices can be a powerful entry point and stresses the importance of allowing access only from healthy devices.


Are Your Laptops “Home-Proof”?


If you want remote work to remain seamless, your devices need to be “home-proof” by default.


That means treating the fundamentals as non-negotiable: automatic screen locks, secure storage, protected sign-ins, timely updates, properly secured Wi-Fi, and work data stored only in approved locations.


Nothing complicated, just consistent execution.


Start by adopting this remote work security checklist as your baseline standard. When the defaults are strong, you reduce avoidable incidents without slowing anyone down.



If you’d like help turning these basics into a practical, enforceable remote work policy, contact us today. We’ll help you standardise protections across your team so remote work stays productive, and secure.

Let's Talk Tech

More from our blog

LinkedIn "Social Engineering": Protecting Your Staff from Fake Recruitment Scams

by Tanya Wetson-Catt • 22 May 2026
A fake recruiter message is one of the cleanest social engineering tricks around because it doesn’t look like a trick. That’s why LinkedIn recruitment scams work so well inside real businesses. They don’t arrive as malware. They arrive as a normal conversation that nudges someone toward one small action: click this link, open this file, “verify” this detail, move the chat to a different app. A few simple checks, a couple of hard-stop rules, and an easy way to report suspicious outreach can shut these scams down without slowing anyone down. LinkedIn Recruitment Scams LinkedIn recruitment scams artfully blend into normal professional behaviour. The message doesn’t look like a “cyber attack.” It looks like networking, and it borrows credibility from recognisable brands, polished profiles, and familiar hiring language. At platform scale, the volume is also hard to wrap your head around. Rest of World reports that LinkedIn said it “identified and removed 80.6 million fake accounts” at registration from July to December 2024. A LinkedIn spokesperson claimed “over 99%” of the fake accounts they remove are detected proactively before anyone reports them. Even with that level of detection, enough scam activity still leaks through to reach real employees. That’s especially true when scammers tailor their approach to what looks credible in a specific industry and location. The other reason these scams succeed is that they follow a predictable persuasion pattern: urgency, authority, and a quick push to “do the next step.” The FTC describes scammers impersonating well-known companies and then steering targets toward actions that create leverage. These actions include handing over sensitive personal information or sending money for “equipment” or other upfront costs. Once someone is rushed into treating the process as real, the scam doesn’t need to be technically sophisticated. It just needs the victim to keep moving. The Scam Pattern Most Teams Miss 1. A polished approach on LinkedIn The profile looks credible enough, the role sounds plausible, and the message is written in a professional tone. The job post itself may still be oddly generic, though. Amoria Bond notes that fake job postings often “lack details” and lean on broad language to catch as many people as possible. 2. A quick push off-platform The conversation shifts to email, WhatsApp/Telegram, or a “recruitment portal” link. That shift is important because it removes the built-in friction of LinkedIn’s environment and makes it easier to send links, files, and instructions.

3. A credibility wrapper: “assessment”, “interview pack”, or “onboarding”

Airswift flags link/attachment requests and urgency tactics as common red flags. The story is usually something like: “Download this assessment,” “Review these onboarding steps,” or “Log in here to schedule.” Tag Apps Make decisions visible and repeatable by tagging apps. Microsoft explicitly calls tagging apps as sanctioned or unsanctioned an important step, because it lets you filter, track progress, and drive consistent action over time. 4. The pivot: money, sensitive info, or account takeover Scammers impersonate well-known companies and then ask for things legitimate employers typically don’t: payment for “equipment” or early requests for personal information. Another variation is more subtle: “verification” steps that are really designed to steal identity details or compromise accounts. 5. Pressure to keep moving If someone hesitates, the scam leans on urgency: “limited slots,” “fast-track hiring,” “complete this today.” That’s why Forbes frames the key skill as slowing down and checking details, because the scam depends on momentum. Red Flags Checklist for Staff Here are the red flags to look out for. Red flags in the job posting The role is oddly vague or overly broad. Generic responsibilities, unclear reporting lines, and “we’ll share details later” language are common in fake listings. The company's presence doesn’t match the brand name. Thin company pages, inconsistent logos/branding, or a web presence that feels incomplete are worth pausing on. The process is “too easy, too fast.” If the listing implies immediate hiring with minimal steps, treat it as suspicious. Red flags in recruiter behaviour They push you off LinkedIn quickly. Moving to WhatsApp/Telegram or personal email early is a common tactic. They use a personal email address or unusual contact details. Be specifically cautious of recruiters using free webmail accounts instead of a company domain. They avoid verification. If they dodge basic questions, treat that as a signal, not a scheduling issue Hard-stop requests Any request for money or fees. Application fees, equipment purchases, “training costs”, gift cards, crypto, that’s a hard stop. Requests for sensitive personal info early. Bank details, identity documents, tax forms, or “background checks” before a real interview process is established. Requests for verification codes. If anyone asks you to read back a one-time code sent to your phone/email, assume they’re trying to take over an account. Requests for non-public company information like org charts, internal system details, client lists, invoice processes and security tools. Look out for requisitions for anything beyond what a recruiter would reasonably need. Stop Scams With Simple Defaults LinkedIn recruitment scams don’t succeed because staff are careless. They succeed because the outreach looks normal, the process feels familiar, and the next step is always framed as urgent. The fix isn’t turning everyone into an investigator. It’s setting simple defaults that make scams harder to complete: slow down before clicking, verify the recruiter and role through official channels, keep conversations on-platform until identity checks out, and treat money requests, code requests, and early personal data demands as hard stops.  When those habits are standardised, the scam loses its leverage.

The "Legacy Debt" Audit: Identifying the 3 Oldest Risks in Your Server Room

by Tanya Wetson-Catt • 18 May 2026
The most dangerous thing in a server room is often the phrase, “Don’t touch that.” It’s usually said with a half-joke and a grimace. It refers to the old box that “still works”, runs something important, and has survived so many fixes and workarounds that nobody feels confident changing it anymore. That’s legacy debt. Not just “old tech”, but old tech that’s become a dependency. It’s the kind that quietly accumulates risk until it turns into downtime, security exposure, or an emergency upgrade at the worst possible time. A legacy debt audit is the fast way to bring that risk back into the light. What Legacy Debt Really Looks Like Legacy debt isn’t “old gear”. It’s old gear that has become normal. It’s the server that runs a critical app, the edge device nobody remembers buying, the workaround that turned into a dependency. Over time, that debt stacks up quietly. Infinite Lambda describes legacy debt as something that “happens even to the best systems,” “silently accruing costs and constraints,” and it can “accumulate basically unnoticed until it is too costly to ignore.” That’s why a legacy debt audit isn’t a theoretical exercise. It’s a visibility exercise to bring the oldest, highest-leverage risks back onto the list of things you actively manage. The security problem shows up when “old” becomes “unpatchable.” The UK’s NCSC guidance on obsolete products says, “Ideally, once out of date, technology should not be used,” and “the only fully effective way to mitigate this risk is to stop using the obsolete product.” If something can’t be updated, weaknesses don’t age out. They sit there, waiting for the wrong day. Legacy debt also looks like basic server hygiene slipping. NIST SP 800-123 frames secure server operations as an ongoing process: “Maintaining the secure configuration through application of appropriate patches and upgrades, security testing, monitoring of logs, and backups…” It also calls out foundational hardening steps like “Patch and upgrade the operating system” and “Remove or disable unnecessary services, applications, and network protocols.” When those basics become inconsistent, legacy debt turns into a reliability and incident-response problem, not just a security one. Finally, legacy debt often hides at the edge. If you have end-of-support internet-facing devices, you’ve got high-leverage risk in the most exposed place. The 3 Oldest Risks to Find First These three categories are where “old” most often turns into outsized risk, because they combine age with leverage: they either sit at the front door, can’t be fixed anymore, or have quietly drifted out of a safe baseline. Risk #1: End-of-support edge devices If you’re looking for high-leverage legacy debt, start at the edge. Firewalls, VPN gateways, routers, and other internet-facing devices are the front door to your environment. When they reach end-of-support (EOS), they don’t just become outdated. They become harder to defend because security fixes stop arriving. What to check in your audit List every edge device (firewall, VPN, router) and the support status for each one Confirm which ones are internet-facing and which services are exposed Identify devices that can’t run the current firmware or no longer receive updates. Risk #2: Obsolete products that can’t be fixed anymore Obsolete products are the purest form of legacy debt: things that are still operating but no longer receive security updates. That means every new vulnerability becomes permanent. In other words, there’s no clever workaround that makes an unsupported system “safe”. There are only risk reductions until you can replace it. What to check in your audit Identify anything past support: server OS versions, appliances, old hypervisors, and line-of-business apps Flag systems that require exceptions, like the ones with old protocols, weak auth, and special firewall rules Find the “business-critical but unsupported” systems. Risk #3: “It still works” servers with neglected basics This is the sneakiest risk because it looks normal. The server is supported. The hardware runs. Nobody’s complaining. But the basics have drifted: patching is inconsistent, unnecessary services are still running, and backups haven’t been proven under pressure. SP 800-123 Guide to General Server Security frames secure server operations as an ongoing discipline, including “patches and upgrades,” “monitoring of logs,” and “backups.” It also calls out core hardening steps like “Patch and upgrade the operating system” and “Remove or disable unnecessary services, applications, and network protocols.” Those are the unglamorous fundamentals that stop small problems from turning into long outages. What to check in your audit Patch reality: what’s the current patch level and how often do updates slip? Service sprawl: what’s running that doesn’t need to be running? Admin and service accounts: where are the broad permissions and shared credentials? Backup confidence: when was the last restore test and did it succeed? Change control: who can make changes, and how are they tracked? Stop Carrying Silent Risk Legacy debt doesn’t announce itself. It sits quietly in the background until the day it becomes downtime, exposure, or an emergency upgrade you didn’t plan for. A legacy debt audit gives you control back by turning “we should deal with that someday” into a shortlist you can act on. Start with the highest-leverage risks: end-of-support edge devices, obsolete products that can’t be patched, and servers where the basics have drifted. Then assign owners, set dates, and move one item at a time from “too scary to touch” to “handled”.  Contact us for help running your next legacy debt audit.

The "Session Cookie" Hijack: Why MFA Can’t Always Save You

by Tanya Wetson-Catt • 15 May 2026
MFA is a strong front-door lock. But it’s not the only thing that decides whether someone can get in. After you sign in, your browser keeps you logged in using a session token (often stored as a cookie). It’s the digital version of a wristband at an event: once you’ve been checked, the wristband proves you belong there. If an attacker steals that wristband, they may not need to beat your MFA prompt at all. That’s the core of session cookie hijacking. The attacker isn’t “cracking” MFA. They’re skipping it by replaying your already authenticated session. This isn’t a reason to stop using MFA. It’s a reason to stop treating MFA as the finish line. When sessions can be stolen, the practical defence shifts to layered controls: phishing-resistant sign-ins, device hygiene, tighter session policies, and detection that catches suspicious access early. Why MFA Isn’t a “Game Over” Control MFA is still one of the best upgrades most businesses can make, but it doesn’t end an attack on its own. The reason is that attackers don’t always try to beat the login step. They try to go around it. Cloudflare notes that “attackers are finding new ways to circumvent MFA” and that modern incidents are rarely one isolated technique. They’re “part of a chain of attacks.” In other words, MFA can block a lot of credential theft, but it doesn’t automatically protect what happens after a user successfully signs in. That’s where session cookie hijacking comes in. Microsoft has described adversary-in-the-middle phishing campaigns where attackers use a reverse-proxy site to “steal and intercept” a user’s password and the session cookie that proves they have an authenticated session. This is “not a vulnerability in MFA.” The attacker isn’t breaking the MFA. They’re reusing the session. What a Session Cookie Is and Why Attackers Want It When you sign into a web app, the site needs a way to remember that you’ve already proved who you are. That’s what a session is: a temporary “logged-in” state that saves you from entering your password and MFA code on every click. Kaspersky explains that session hijacking is “sometimes called cookie hijacking” because cookies are commonly used to store the session identifier that keeps you authenticated. Attackers want that session identifier because it’s the shortcut. Proofpoint describes session tokens as digital “keys” that let a user stay authenticated. It warns that stealing valid tokens lets attackers impersonate legitimate users and potentially bypass authentication measures “like MFA.” That’s why session cookie hijacking is so highly leveraged. If an attacker can steal the cookie or token that represents your active session, they’re not trying to defeat the login process. They’re attempting to reuse what you already completed, and access the same apps and data as if they were sitting at your keyboard. How Session Cookie Hijacking Actually Happens A lot of teams picture “account takeover” as someone guessing a password or tricking a user into approving an MFA prompt. Session cookie hijacking is different. The attacker’s goal is to steal the proof that you’re already logged in, then reuse it, often without triggering another sign-in challenge. 1.) AiTM phishing Adversary-in-the-middle (AiTM) phishing is the “proxy login” trap. You think you’re signing into a normal service, but you’re actually signing into a lookalike page that sits between you and the real site. The attacker relays the login in real time, so everything appears to work, including MFA. Attackers use AiTM phishing sites to “steal and intercept” a user’s password and the session cookie that proves the authenticated session. This is “not a vulnerability in MFA.” The attacker isn’t breaking the MFA. They’re capturing the session after MFA is completed and reusing it. One such campaign “ attempted to target more than 10,000 organisations ” since September 2021, which shows how scalable this approach has become. 2.) Browser-in-the-Middle session stealing Browser-in-the-middle (BitM) is similar in spirit, but it’s even more “hands-on” from the attacker’s side. Instead of stealing a password and running away, the attacker effectively places themselves in control of the browsing session. Google’s threat intelligence says, “Stealing this session token is the equivalent of stealing the authenticated session.” Once the token is stolen, “an adversary would no longer need to perform the MFA challenge.” In other words, the attacker isn’t trying to authenticate instead of you. They’re trying to ride along after you’ve authenticated. 3.) Cookie theft from the endpoint Not every session hijack starts with a fancy proxy. Sometimes the attacker simply steals session data from the device itself. Stealing valid session tokens allows attackers to impersonate legitimate users. Tokens act like digital “keys.” If an endpoint is compromised, those “keys” can be extracted and reused. Invicti explains that an attacker steals HTTP cookies and can gain access. The goal is often to obtain sensitive information stored in cookies. MFA Is a Baseline, Not a Finish Line MFA is still essential. It blocks a huge amount of credential theft and makes basic account takeover harder. But session cookie hijacking is a reminder that attackers don’t always try to defeat the login step. Sometimes they reuse what happens after it. The practical response is layered and realistic. Make phishing harder to pull off, and treat device health as part of identity. Tighten session behaviour for high-risk apps. Watch for suspicious access patterns that suggest a session is being replayed. When those controls work together, MFA stops being a comforting checkbox and becomes what it should be: a strong baseline that’s backed by protections around the session itself.  Contact us today for help protecting your login sessions from hijacking.