WATCHTake a breath. Do these in order.
How you might know
- A message from a boss or colleague asks for something right now.
- It says do not call, it is confidential.
- A link to approve or pay.
- The tone or timing feels slightly off.
Do this now
Pause
Do not act on the message alone. A short delay almost never costs anything real.
Verify through a separate, known channel
Call or message the person using a number or app you already trust, not the one in the request.
Check the request in your normal process
Look it up in your ticketing, deploy or payment tool. If it is not there, it is not real.
Do not click the link
Go to the tool directly by typing its address or using a bookmark.
Report it
Tell your security contact even if you are not sure. Others may have received it.
Do not do this
- Do not approve high-impact actions from a chat message alone.
- Do not click links in the request.
- Do not feel bad for double-checking. It is the correct behavior.
Who to tell
- Your security contact
- The person being impersonated, through a trusted channel
What to save before you clean up
- The message and sender details
- Timestamps
In the next 24 hours
- Warn your team about the pattern.
- Require a second approver for high-impact actions.
- Review how the attacker knew project details.
Official help for the platforms involved
Links open each provider's own documentation, so you do not have to search for it.
What to write in the post mortem afterwards
- What made it believable
- Whether a second approver would have caught it
- Controls for high-impact approvals
Finished this one?
Add it to What I learned and earn 30 Trust. You can open your list from the badge at the bottom of the page.