Security teams should teach a simple independent verification habit for any unexpected or sensitive request. The safest pattern is to hang up or stop responding, then contact the requester through an official number or trusted internal channel. This breaks the attacker’s urgency, prevents credential disclosure, and gives employees a clear action they can repeat under pressure.
How to verify an unexpected request without giving an attacker the first move
The core control is a deliberate pause. For any unexpected request, especially one involving money, credentials, reset actions, approvals, or urgency, stop the conversation and re-establish contact through a known-good channel. That simple break defeats most phishing, vishing, and smishing scripts because it removes the attacker’s ability to keep control of the interaction.
A good verification habit is specific, repeatable, and easy to remember under pressure. Teams should prefer official callback numbers, internal directories, approved ticketing systems, or an in-person confirmation path that is already trusted. If the request came by phone or text, do not use the number, link, or reply path provided in the message itself.
Verification should also be proportionate to the request. A routine scheduling question does not need the same friction as a request to change payment details, approve a login, disclose a code, or reset access. The more sensitive the request, the more the team should insist on an independent callback, a second approver, or a known internal workflow.
Why callback verification works against phishing, vishing, and smishing
Callback verification works because most social engineering depends on momentum. Attackers try to create urgency, authority, embarrassment, or confusion so the target acts before thinking. When the target pauses and uses a separate channel, the attacker loses that momentum and usually loses the opportunity altogether.
This matters across channels, not just email. Voice scams can spoof caller identity and sound convincing. Text messages can look routine and can be embedded in an everyday workflow. In both cases, the safest response is the same: treat the message as untrusted until independently confirmed.
The practice is especially important for requests that try to move people away from normal controls, such as approving a login, sharing a one-time code, changing a payout destination, or bypassing a help desk check. Those are the moments when a well-drilled verification habit does the most work.
How to make verification routine instead of ad hoc
The strongest programmes turn verification into a default behaviour rather than a case-by-case judgement. That means staff should know in advance which numbers to call, which channels are authoritative, and which requests always require extra confirmation. If people have to invent the process during the incident, they are more likely to trust the attacker’s urgency.
Teams also need to make the trusted path easy to find. If official contact details are buried, out of date, or inconsistent, employees will fall back to whatever is in front of them. Good practice is to keep verified contact lists, internal lookup paths, and escalation steps easy to reach from the normal work environment.
Training should emphasise one behavioural rule above all: never verify through the channel that initiated the request. That single rule is simple enough to remember, and it scales well because it applies to email, phone, SMS, collaboration tools, and impersonation attempts that blend several of them together.
Risk and Threat Considerations
Unexpected requests succeed when attackers exploit trust, urgency, and channel spoofing. The main exposure is not the message itself, but the chance that a target will disclose credentials, approve access, or authorise an action before the request is independently checked.
Failure mechanism: The attacker uses a convincing pretext on one channel and then prevents the target from escaping that channel, so the victim cannot compare the request against a known-good source of truth.
Impact: A single successful verification failure can lead to account takeover, fraudulent payments, help desk compromise, or the disclosure of sensitive access material. If the request reaches a privileged user or a support workflow, the blast radius can be much larger than the initial message suggests.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while CIS Controls v8, NIST SP 800-53 Rev 5 and NIST SP 800-63 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS-14 — Security Awareness and Skills Training | Verification habits reduce phishing, vishing, and smishing success. |
| Recommendation — Train staff to verify unexpected requests through a known-good channel before acting. | ||
| NIST SP 800-53 Rev 5 | AT-2 — Awareness Training | Users need a repeatable verification habit for spoofed requests. |
| IA-5 — Authenticator Management | Unexpected requests often try to elicit secrets or reset actions tied to authenticators. | |
| Recommendation — Teach personnel to confirm unexpected requests through official contact paths. Protect authenticators by requiring independent confirmation before any secret disclosure or reset. | ||
| NIST SP 800-63 | Digital Identity Guidelines | The question centers on reducing social-engineering success against identity workflows. |
| Recommendation — Use phishing-resistant verification paths and avoid relying on the initiating channel for trust. | ||
| MITRE ATT&CK | T1566 — Phishing | The request patterns are classic phishing, vishing, and smishing delivery methods. |
| Recommendation — Map suspicious requests to T1566 patterns and reinforce out-of-band verification controls. | ||
Practitioner Guidance
What to verify: Verify the requester, the request, and the channel separately. A name alone is not enough, because a real name can be paired with a spoofed number, a compromised mailbox, or a fabricated callback path.
Decision rule: If the request is unexpected, time-sensitive, or asks for a secret, approval, or reset, stop the interaction and re-contact through a directory entry or internal process you already trust. If the request cannot survive that test, it should not be treated as valid.
What good looks like: Staff can explain the callback rule without hesitation, know where to find official contact details, and escalate unusual requests instead of negotiating with them in real time.
Practitioner takeaway: The goal is not to make every request slow; it is to make every sensitive request easy to verify out of band and hard to complete on urgency alone.
Related resources from NHI Mgmt Group
- Guide: Social Engineering Guide
- How should security teams reduce phishing, vishing, and smishing risk without relying only on passwords or one-time codes?
- How should security teams reduce phishing and vishing risk when attacks use AI-generated content and voice cloning?
- How should security teams implement social engineering risk assessments across phishing, vishing, and smishing channels?
- How should security teams reduce the risk from MMS-based phishing and smishing campaigns?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org