Session & Workstation Security for Support Technicians

Every chapter so far has focused on requests, tickets, and data flowing through a support technician. This chapter turns to something more basic and easy to overlook: the technician's own workstation. It's not just one more employee's device — it's typically a hub with a reach far wider than any single account, and that reach is exactly why it deserves its own chapter.

Why This Workstation Specifically Matters More

A compromised regular employee workstation typically exposes that one person's own accounts and data. A compromised support workstation is different in kind: it often has active sessions into ticketing systems, remote-access tools (`remote1`'s own territory), and sometimes elevated or admin-capable credentials — reaching many other accounts and systems at once. Compromising it doesn't just expose one identity; it hands an attacker the exact tools this course has spent eight chapters teaching how to recognize being misused against someone else.

The Habit That Matters Most: Locking the Screen, Every Time

Chapter 3 covered physical impersonation — someone walking through a badge-locked door by looking like they belong. An unlocked, already-authenticated support workstation removes the need for any of that effort at all; the badge-locked door and the fake delivery uniform become irrelevant if the workstation itself is simply sitting open. Lock the screen every time you step away, including "just a minute" — that's precisely the length of time an opportunistic attempt actually needs.

Session Hygiene

• Close sessions when finished — per `remote1`'s own "clean disconnection" standard, don't leave remote-access sessions or admin panels open indefinitely once a ticket is resolved
• Short auto-lock timeouts — a workstation that locks itself after a brief idle period limits the damage of a forgotten manual lock
• Separate everyday and elevated accounts — per `remote1`'s own least-privilege material, don't stay logged into an admin-capable account as your default; switch into it only for the specific task that needs it

Physical Security Basics

• Use a cable lock or equivalent for a laptop in any semi-public space
• Never leave a workstation unattended in a public or semi-public area, even briefly
• Use a privacy screen if your desk has visual exposure to sensitive ticket or account data from a walkway or shared space
• Store any physical security tokens or hardware keys securely, separate from the device they unlock — the same reasoning as never leaving a house key in the lock

Credential Hygiene for Your Own Accounts

Everything Chapter 5 assumed on the end user's side applies just as directly to a support technician's own accounts: a unique, strong password per account, MFA enabled everywhere it's offered, and a password manager rather than reused or written-down credentials. A technician who skips this for their own accounts while enforcing it strictly for everyone else is protecting the wrong side of the relationship.

Hands-On Exercises