First action
Pause payment, document transfer or remote access. Reconnect through a known channel found outside the received message.

Topic pathway
Choose the right checks for messages, supplier payments, recruitment, fundraising and fake support.
Pause payment, document transfer or remote access. Reconnect through a known channel found outside the received message.
A record of the original request, independently reached contact, verified destination and payment or access decision.
A legitimate company, genuine invoice or correct logo does not authenticate the request. If a transfer has already occurred, contact the bank through its official channel immediately.







Record the fact being checked, the material reviewed, what remains unknown, the person responsible and the next review trigger. A result is useful when another reader can understand why an action was chosen and what would change it.
| Situation | Check | Record to keep |
|---|---|---|
| Changed bank details | Pause the change; call a known contact using a previously retained number. | Contact identity, confirmed destination and approval independent of the message. |
| Recruiter demanding an advance | Verify the opening through the employer and confirm the recruiter’s mandate. | Job reference and independently obtained response. |
| Support requesting remote access | Close the solicitation and independently open official support. | Original message and actions taken; notify IT if access was granted. |
| Urgent fundraising story | Identify organiser, beneficiary and payment route. | Source of need, donation destination and remaining unknowns. |
Requests for secrecy, urgency or bypassing normal approval warrant a pause. Do not let pressure choose the verification channel. If funds have already been sent, immediate contact with the bank takes priority over lengthy OSINT research.
No. A genuine account can be compromised. Check the action and beneficiary independently.
Original request, relevant times, action taken and a short timeline. Exclude passwords and temporary codes.
Reading technical evidence
A result copied into an email is not automatically trustworthy. Its origin in the mail chain matters.
| Observed item | What it means |
|---|---|
| authserv-id | Identify the service claiming to have performed the check. |
| spf=pass or dkim=pass | Read the mechanism and domain concerned, rather than just the word pass. |
| An upstream header | Ask the mail team which results originate from its trusted services. |
Preserve the original message and headers. Even a trustworthy result does not authorise a requested bank-account change.
Fictional learning scenario
The message is in the usual thread and quotes the exact invoice amount. The new account has not been approved.
The supplier and invoice are known. Authorisation of the bank change remains unknown: these are three separate facts.
Call the contact using a previously retained number, confirm the change under the internal procedure and retain the approval reference.
An independent callback contradicts the message: keep the change paused and pass the original to the responsible person. Independent confirmation allows the usual process to resume; it does not establish that the entire mailbox is secure.
A logo, signature, conversation thread or technically authenticated email cannot replace approval of the requested action.
Further reading
WORLD SOCIAL NETWORKS
Follow a social-platform pathway for checking a request through another channel and organising the material needed for a report.
WORLD HUMANITARIAN GUIDE
Explore practical criteria and official organisation links before responding to a humanitarian appeal.