Why reporting fast is the whole game
At 4:50 on a Friday, Rosa Mendes types her login into a page from a supplier-looking email and realises the web address was slightly off. The temptation is to close the laptop and hope for the best. The chapter's point is that nobody catches every scam, because attackers are patient professionals who only need to succeed once. A strong team is measured by how fast it finds out.
After a clicked link, a stolen password, a misdirected payment or a lost phone there is usually a window: the attacker still has to use what they took, a bank may be able to stop or recall a payment, and a lost device can be locked and wiped. Like a small kitchen fire, it is easy to deal with in the first thirty seconds and much harder ten minutes later. Your job is not to fix it or be certain; do not investigate yourself by clicking the link again, which wastes time and can cause more harm. Raise the alarm and let the security team diagnose.
What is worth reporting: more than you think
When in doubt, report. The list is broad: a link or attachment you are unsure about, details typed into a page that may be fake, suspicious emails, texts or calls even if you did not fall for them, a payment or bank-detail change you now doubt, data sent to the wrong person, a lost or missing device, a computer behaving strangely, a ransom message, an unusual request from someone claiming to be IT or a bank, or simply a nagging feeling.
You do not need proof, and you do not need to have caused the problem. A report is about the event, not about fault, so something forwarded by a colleague or sent from a supplier's hacked account still counts. Reporting a phishing email you spotted protects colleagues who received the same message and may not spot it, because IT can warn everyone and block the sender.
Speed beats secrecy, and blame kills security
Two natural forces work against reporting. Secrecy hands attackers the one thing they cannot get for themselves, which is time, so a problem that could have been contained in minutes becomes a breach that takes weeks. Blame is partly the organisation's responsibility: if people expect to be punished, they hide mistakes rather than becoming more careful.
At Meridian, security lead Aiko Tanaka says plainly that nobody is punished for reporting a click, reply or mistaken send; the team is grateful to the person who told them fast. The chapter tells managers that the first reaction to a reported mistake teaches the whole team whether it is safe to come forward. Separate the understandable mistake from the response, and reward the fast report.
Exactly who to tell, and how
Know your contacts in advance. At Meridian, the IT service desk, where Lucy Fernández works, handles most things, and Aiko Tanaka is there for anything serious, sensitive or uncertain. Phone for anything urgent rather than relying on an email that may sit unread, use the report-phishing button if your email has one, and keep the evidence instead of deleting the message or tidying up. For payments or bank-detail changes, say so clearly straight away, because money has the tightest clock.
No technical explanation is needed; a sentence like 'I think I clicked something I shouldn't have' is a perfect start. Keep the service desk number somewhere you can reach if your computer or phone is the thing that failed, such as your personal phone or a card by your desk. Rosa called Lucy within the hour; Lucy thanked her, reset her password while they were still on the line, checked the account and blocked the email, so the stolen password was useless before the weekend.
What happens after you report, and why near-misses count
The first thing you get is help, not scrutiny. The team asks a few calm questions, contains the risk by resetting a password, checking an account, contacting a bank or locking a device, and usually that is the end of your involvement. For bigger incidents, any review looks at how the attack got through so defences can improve, not at who to blame.
Near-misses are the most undervalued reports: the phishing email you spotted just in time, or the fake bank-detail change you caught before paying. They show the security team exactly which tricks are being tried right now, without any harm done. Red flags include a voice saying you will keep quiet and see, pressure not to tell IT, thinking an incident is too small, putting the report off until later, or wanting to delete the evidence first.
KEY POINTS
Key points
- Save your IT service desk phone number somewhere you can reach even if your computer or work phone is unavailable.
- The moment something feels wrong, call for help before trying to confirm or fix it yourself.
- Use the report-phishing button for suspicious emails, including ones you did not fall for.
- Keep suspicious messages instead of deleting them so IT can examine the evidence.
- Report any doubtful payment or bank-detail change immediately and say clearly that money is involved.
- If you manage people, make 'thank you for telling me' the first response to every report.
QUESTIONS
Common questions
- What should I do if I entered my password on a phishing site?
- Tell your IT service desk immediately, by phone if possible, even if you are not sure. In the book's example, the service desk reset the password during the call, checked the account for misuse and blocked the email, so the stolen password became useless before it could be used. Do not wait until after the weekend or try to investigate yourself.
- Should I report a phishing email if I did not click it?
- Yes. If you received a convincing phishing email, many colleagues probably did too, and some may not spot it. Your report lets IT warn everyone, block the sender and remove the message. Use the report-phishing button in your email if your organisation has one.
- Will I get in trouble for reporting that I clicked a malicious link?
- In a well-run organisation, no. The chapter describes a no-blame approach in which people are thanked for reporting quickly, and the only behaviour that causes real trouble is hiding a problem until it grows. Blame makes people secretive, which gives attackers more time, so good security teams make reporting safe.
- What counts as a security incident worth reporting?
- More than most people think: unsure clicks, details typed into suspicious pages, suspicious messages or calls, doubtful payments or bank-detail changes, data sent to the wrong person, lost or missing devices, strange computer behaviour, ransom messages and unusual requests from people claiming to be IT or a bank. Even a nagging feeling with no proof is worth reporting.
- Should I delete a suspicious email after reporting it?
- Do not delete it before IT has seen it, and do not try to tidy up the problem before reporting. The message and your steps are evidence that helps the security team understand what happened and protect others. Report first and follow their instructions.
- What happens after I report a security incident?
- You receive help, not scrutiny. The service desk or security team asks a few simple questions and then contains the risk, for example by resetting a password, checking an account, contacting the bank or locking a device. For larger incidents, a review focuses on improving defences, and the person who reported is treated as a help, not a suspect.