The Helpdesk's Role in Security Culture
The warehouse clerk at Northgate Retail rang the desk. He said a pop-up had told him his computer was infected and he should call a number. He had not called the number. He had called the desk. The technician who reset his password in the spring had said, while doing it, 'if anything ever asks you for your password or tells you to ring somebody, ring us first, we don't mind'. The technician had said it in about four seconds. It was the most effective piece of security training the clerk had ever received. It had happened inside a password reset, which is where most security training that works actually happens.
This series is about the four seconds. It covers every ticket as a teachable moment, with one sentence delivered at the moment of gratitude and never a lecture. It covers spotting incidents early from the queue. The desk sees the lockouts, the odd sign-ins and the three reports of one email before anyone else does. The series covers security without blame, which is the only culture that reports. It covers the desk's own security habits, because the desk is the example everyone watches. Then comes working with the security function, or being it, in the small organisation that has none. It covers measuring security culture from the desk without shaming anyone. The desk is not the security team. It is the security team's eyes, ears and best teacher, and it should know it.
Articles in This Series
- Every Ticket a Teachable Moment: Security in One Sentence
The password reset, the found USB stick, the shared account, the forwarded attachment; the one-sentence lesson at the moment of gratitude; never a lecture; and the teachable-moment lines. - Spotting Security Incidents Early From the Help Desk Queue
The odd sign-in alert, the cluster of lockouts, three reports of one email, and the account doing things its owner did not do. Covers the route to the security function, and the signals sheet. - Security Without Blame: The Culture That Reports in Minutes
The click reported in minutes against the click hidden for days, the thank-you, the manager's role, never a per-person list, and the no-blame statement. - The Desk's Own Security Habits: Being the Example People See
The verification standard, the internal note that never carries a secret, admin account discipline, the locked screen, remote session consent, the desk as the example, and the checklist. - Working With the Security Function, or Being It
Who does what, the handoff, the feedback loop, the shared vocabulary, the small organisation with no security function, and the desk-security working agreement. - Measuring Security Culture From the Help Desk
Reports, time-to-report, teachable moments delivered, the trend, never shaming and never per person, the line in the leadership report, and the security culture line.
Explore More Topics
This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.