How to Secure Helpdesk Password Resets Against Social Engineering

Summary
A sponsored guide explains how attackers can exploit helpdesk password resets and recommends stronger identity checks, self-service adoption, secure temporary credentials, activity monitoring, and helpdesk training.
Key points
- The article says attackers believed linked to Scattered Spider gained initial access to Marks & Spencer by impersonating an employee and requesting a password reset through a third-party service desk.
- It describes the attackers using valid credentials to access Active Directory, obtain NTDS.dit, crack password hashes offline, move laterally, and deploy ransomware; the article reports resulting disruption to M&S operations.
- The guide recommends verifying identity before resets, such as sending a one-time code to a trusted device or using an existing identity provider.
- Organizations are advised to encourage self-service password reset enrollment to reduce helpdesk dependency.
- Temporary credentials should be strong, single-use, delivered through an encrypted channel, and expire quickly.
- The article recommends monitoring reset patterns and giving helpdesk agents consistent verification procedures and guidance for anomalies.
Article Details
- Defense Focus
- Prevent social engineering through helpdesk password resets by consistently verifying identity and monitoring reset activity.
- Detection Methods
- Review password-reset activity for frequent resets, repeated helpdesk requests, and patterns suggesting misuse.
- Track self-service password-reset adoption and recurring user difficulties as potential process or security issues.
- Verify identity using a one-time code sent to a trusted device or an existing identity provider.
- Data Sources
- Password-reset activity records
- Helpdesk password-reset requests
- Self-service password-reset enrollment and usage
- Platforms
- Helpdesk and service-desk identity-verification workflows
- Self-service password-reset systems
- Identity providers
- Defensive Actions
- Require consistent identity verification before every helpdesk password reset; do not leave verification to individual agent judgment.
- Prefer self-service password resets where possible and help users enroll and understand the process.
- Issue temporary credentials that are strong and single-use, deliver them through an encrypted channel, and ensure they expire within a few minutes.
- Give helpdesk agents visibility into reset activity and a defined policy for handling anomalies.
- Train helpdesk staff and provide clear guidance for requests that fall outside the standard process.
MITRE ATT&CK
T1003.003 · NTDSThe attackers extracted the Active Directory NTDS.dit file containing domain-user password hashes.T1078 · Valid AccountsA service-desk password reset gave the attackers credentials they used for account access.T1110.002 · Password CrackingThe attackers cracked the extracted password hashes offline to recover additional credentials.T1486 · Data Encrypted for ImpactThe attackers deployed ransomware that encrypted systems supporting payments, e-commerce, and logistics.T1656 · ImpersonationAttackers believed linked to Scattered Spider impersonated an M&S employee when contacting a third-party service desk.
Threat Actors
Vendors
Cisco DuoInstead of relying on information that can be found or guessed, agents can trigger a one-time code to a trusted device or use existing identity providers like Duo or Okta.OktaInstead of relying on information that can be found or guessed, agents can trigger a one-time code to a trusted device or use existing identity providers like Duo or Okta.Specops SoftwareSponsored by Specops Software
Products
Microsoft Active DirectoryFrom there, the attackers exploited Active Directory to extract the NTDS.dit file, the database storing password hashes for all domain users.Specops Secure Service DeskSolutions like Specops Secure Service Desk mean helpdesk teams can confirm user identity before any reset takes place.
