Out-of-band verification

In a support workflow, out-of-band verification checks a request through a separately established communication route instead of relying only on the interaction that initiated it.

A second route, established separately

The point is to check a request without asking the same unverified person to vouch for it. Mandiant recommends a registered-number callback or confirmation through a known corporate email for high-risk changes. Callback verification is one specific way to do this.

Switching apps is not enough by itself. If an attacker controls both the initiating message and the destination you use to confirm it, you have added a step without getting an independent answer. Choose the second route based on how it was established and whether it could be affected by the suspected compromise.

Why NIST’s authentication term is different

NIST uses out-of-band authentication for a defined protocol. A short-lived secret connects an authentication attempt on the primary channel with control of a device on a separate channel. An ordinary support callback does not automatically meet those requirements.

NIST excludes email from that authentication method and states that out-of-band authentication is not phishing-resistant. That does not make every business confirmation email a NIST authentication attempt. A support procedure checking a request and a sign-in protocol proving possession of a device are different uses of the phrase.

Sources

See it in practice