A convincing caller can turn a routine password reset into an account takeover. Enforcing identity verification before sensitive account changes helps service desks stop impersonators without leaving security decisions to an agent’s judgment.
An employee contacts the service desk requesting a password reset. They know their username, department, and manager’s name. But how can the agent be sure they’re speaking to the right person?
Increasingly, groups like Scattered Spider are exploiting this challenge, using social engineering as their entry point into organizations. It’s a reminder of why verifying a caller’s identity is essential.
Solutions like Specops Secure Service Desk help protect against social engineering by verifying callers before service desk agents can reset passwords or recover accounts. In this article, we’ll walk through how secure caller verification works in practice. You can also see the process for yourself with our interactive walkthrough.
The service desk plays an important role in keeping employees connected to the systems they need. But the ability to reset passwords, recover accounts and manage multifactor authentication (MFA) also makes it an attractive target for attackers.
Rather than trying to bypass security controls directly, attackers can target the people authorized to reset them. Scattered Spider, for example, are known to use phishing (vishing) to impersonate employees and add another layer of realism to trick service desk agents. The 2025 attacks against British retailers, including Marks & Spencer (M&S), demonstrate how damaging those calls can be; the resulting ransomware attack led to a five-day suspension of sales at M&S, costing an average of £3.8 million ($5.1 million) in daily losses.
The challenge for the service desk is spotting these attacks. Armed with information gathered from social media, data breaches or previous interactions, an impersonator may know what is needed to pass knowledge-based identity checks. They then typically combine that knowledge with a sense of urgency to pressure agents into acting quickly.
With AI enabling more convincing attacks, it’s harder than ever for agents to distinguish genuine employees from convincing impersonators without delaying legitimate support requests. Agents need a reliable way to confirm who they’re speaking to before making sensitive account changes.
Let’s walk through a typical password reset request to see how solutions like Specops Secure Service Desk help agents verify callers before making sensitive account changes.
An employee, John Doe, has forgotten his password, so calls the service desk requesting a password reset. The agent opens Specops Secure Service Desk to begin the verification process.
Although John provides his name and explains why he needs help, this isn’t enough to confirm his identity. Before resetting his password, the agent needs to verify that they’re speaking to the legitimate account owner.
The agent searches for John in Specops Secure Service Desk using his name, username or email address.
Once John’s account appears, the agent can see his current verification status. At this stage, John is marked as unverified, so the agent cannot proceed with the password reset. The agent still needs to confirm that the person requesting access is who they claim to be.
An approved verification method must be chosen to confirm John’s identity. With Specops Secure Service Desk, agents have access to more than 15 MFA factors, ensuring John can be securely verified whether he has access to a phone or not. The factors include:
Once John has successfully completed verification, Specops Secure Service Desk updates his status from unverified to verified. This unlocks the password reset option, allowing the agent to complete John’s request.
By making verification a required step, solutions like Specops Secure Service Desk help prevent attackers from using social engineering to convince agents to bypass identity checks. The agent can complete the request with confidence that John’s identity has been verified using an approved method.
Even experienced service desk agents can’t be expected to spot every social engineering attempt. That’s why caller verification needs to be a consistent, enforceable part of the process.
Flexibility is just as important. If an employee has lost their phone or can’t access their usual authentication method, agents need secure alternatives. Without them, there’s a risk that pressure to resolve the request quickly could lead to verification checks being bypassed.
With Specops Secure Service Desk, service desk teams can choose from a range of verification methods to suit different circumstances and security requirements, without compromising the need to verify identity before sensitive actions can proceed.
Want to see it in action? Explore our interactive walkthrough to experience how Specops Secure Service Desk verifies a caller before allowing resets or account recovery to take place.