"Clean Desk" 2.0: Securing Your Home Office from Physical Data Leaks

Tanya Wetson-Catt • 11 May 2026

In the traditional office, a “Clean Desk” policy was a simple habit: shred the sensitive stuff, lock it away, and don’t leave passwords where someone can see them.

In 2026, the same idea still matters but the “desk” has changed.


For many teams, the home office is now the default workspace, and that means physical access can quickly become digital access. An unlocked screen, a shared device, or a laptop left in the wrong place can expose the same systems your business runs on every day.


Clean Desk 2.0 isn’t about aesthetics. It’s about securing the physical-to-digital bridge.

If a houseguest, a delivery person, or a thief can sit down at your workstation, they don’t need to be a master hacker to cause real damage. They just need a few unattended minutes and an open session.


Why an Unlocked Screen is a Data Breach


Most small business owners treat multi-factor authentication (MFA) as the ultimate front-door lock. And it’s a great lock. The problem is that once you’re already inside, the “front door” isn’t the control that matters.


When you sign into a web app, your browser creates a session token (often stored as a cookie) so you stay logged in without being challenged on every click.


Kaspersky notes that session hijacking is “sometimes called cookie hijacking” because cookies commonly store the session identifier. Proofpoint says session tokens act like digital “keys.” If they’re stolen, attackers can impersonate legitimate users and bypass authentication measures “like MFA”.


That’s why physical access changes the game.


If someone can sit down at your workstation while you’re making a coffee, they don’t need to “crack” anything. They can reuse your already authenticated session and access the same cloud apps, CRM data, and financial tools you were just using, no MFA prompt required.


This is exactly why Clean Desk 2.0 needs an auto-lock culture. Set short screen-lock timers. Lock manually every time you step away. Treat an unlocked session the same way you’d treat a set of master keys left in the door.


Hardware "Legacy Debt" on Your Desk


Most people keep old tech for the same reason: it still works. But “still works” isn’t the same as “still safe”.


The same legacy debt that shows up in server rooms also shows up in home offices and often in the exact places that matter most, like routers, VPN gateways, and the “backup” laptop that hasn’t been updated in months.


The core problem is end-of-support. When a device reaches end-of-support (EOS), security fixes stop arriving.


The UK’s guidance on obsolete products notes, “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.”


In other words, you can’t patch your way out of something that no longer gets patches.

This matters even more for edge devices. These are anything internet-facing that sits between your home network and the rest of the world.


A Clean Desk 2.0 habit is to audit your home-office “edge” the same way you’d audit a server room:


  • Identify what’s internet-facing
  • Confirm it’s supported and patchable
  • Retire anything that isn’t.


Your Digital Employee Needs a Locked Door


As AI features get embedded into everyday tools, workstations aren’t just “where you work” anymore. They’re where automated actions happen.


An AI agent might update your CRM, draft client comms, schedule appointments, or move a workflow forward with minimal input once it’s been kicked off.


That creates a new physical risk because unattended sessions + automation don’t mix.

If an agent is running a process while you’re away from your desk, an unlocked screen turns into an open control panel. Someone doesn’t need to be technical to cause damage.

 

They just need to click, approve, change a destination account, or interfere with an in-flight task.


The fix isn’t banning automation. It’s treating AI-driven workflows like you’d treat any powerful business system: clear boundaries and clear approvals.


Decide upfront:


  • What decisions can the AI agent make without a human present?
  • What actions require an explicit approval step?
  • What are its spending limits and escalation rules if money is involved?
  • Which systems and data are the agents allowed to access, and which are off-limits?


Physical Efficiency and Cloud Waste


A Clean Desk 2.0 mindset isn’t only about security. It’s about operational discipline: knowing what you’re using, why you’re using it, and what should be switched off when it’s not needed.


Cloud waste is the digital version of leaving the lights on in an empty building. It shows up as underused servers, test environments that never power down, and storage that keeps growing because nobody owns the cleanup.


None of it looks dramatic day to day. It just quietly inflates your monthly bill.

The simple habit that fixes it is the same one that keeps a physical workspace under control: visibility and ownership.


Assign each environment and major resource to an owner, review what’s actually being used, and schedule non-production workloads to shut down outside business hours.


These “tidying” routines don’t just cut spending. They reduce clutter, limit exposure, and make your environment easier to manage when something goes wrong.


Building a 2.0 Foundation


Securing your home office from physical data leaks isn’t about paranoia. It’s about professionalism. In 2026, the home workspace isn’t a side setup. It’s part of your business perimeter.


Clean Desk 2.0 is really a set of modern defaults, like locked screens and supported devices. When those basics are consistent, small home-office lapses stop turning into bigger business problems.



Want help turning this into a simple, enforceable baseline for your team? Contact us for a technology consultation.

Let's Talk Tech

More from our blog

Micro-SaaS Vetting: The 5-Minute Security Check for Browser Add-ons

by Tanya Wetson-Catt • 25 May 2026
Browser add-ons have a funny reputation. They feel “small”. A quick install. A tiny productivity boost. A harmless little helper that lives in your toolbar. But in practice, a browser extension is more like a micro-SaaS vendor sitting inside your browser session. It can see what you see, interact with the pages you open, and sometimes access the same cloud apps your business runs on all day. That’s why a browser extension security check matters. Not because every extension is bad, but because it only takes one over-permissioned add-on or one bad update to turn “helpful” into exposure. The good news is you don’t need a 40-page policy to reduce the risk. A simple five-minute check can prevent most extension problems before they start. Why Browser Extensions Are a High-Leverage Risk Browser extensions sit in the most sensitive place in modern work: the browser tab where your staff live all day. That matters because extensions aren’t just “apps”. They’re granted special authorisations inside the browser. That makes them attractive targets and gives them leverage that’s disproportionate to how “small” they feel. UC Berkeley’s guidance says extensions get “special authorisations,” and the more you install, the bigger the attack surface becomes. The risk is often permission-based. OWASP calls out “permissions overreach” as a core problem. Extensions can request more access than they need, including access to “all tabs, browsing history, and even sensitive user data.” When an extension can read and modify what happens in the browser, it can potentially see data in cloud tools, capture what’s typed into forms, or alter content on a page. It’s also a “change over time” risk. A useful extension today can become a different extension tomorrow. The 5-Minute Browser Extension Security Check This browser extension security check is designed to be fast, repeatable, and realistic. It helps staff make safe decisions in minutes without turning every extension into a big IT ticket. Vet the developer like a real vendor If you wouldn’t give a random supplier access to your customer records, don’t give a random extension access to your browser. Start with the basics: Confirm the developer has a real website, support details, and a consistent name across listings Look for a track record (other products, a clear company presence, updates that look normal) Prefer official stores and trusted sources over “download this .zip” links

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.