After the Click: How to Report a Security Mistake

A security mistake can leave you writing and deleting the same message to your manager. You suspect something went wrong, but finding the words feels harder than it should. Plaintext with Rich explores the first useful conversation after a suspicious click, download, or account approval, including the response from the person receiving the report. A sample report and a sports replay analogy show why the sequence of events matters more than a polished explanation. You'll hear why opening a link, running a file, entering sign-in details, and sending money describe different situations, even when they all start with the same message. Drawing on Federal Trade Commission recovery guidance updated in June 2026 and advice from the UK's National Cyber Security Centre, the episode distinguishes workplace help, provider recovery, and public reporting. It also looks at the manager's part in making an uncertain account of events easier to give honestly. If you've ever hesitated to report a possible mistake, this conversation gives that awkward moment the attention it deserves. Leaders and colleagues who receive those messages will find a useful rehearsal here too, without needing to become the investigator. Listen for a calmer way to begin the conversation. One Topic, Ten minutes, No panic. Is there a topic/term you want me to discuss next? Text me!! YouTube more your speed? → https://links.sith2.com/YouTube Apple Podcasts your usual stop? → https://links.sith2.com/Apple Neither of those? Spotify’s over here → https://links.sith2.com/Spotify Prefer reading quietly at your own pace? → https://links.sith2.com/Blog Join us in The Cyber Sanctuary (no robes required) → https://links.sith2.com/Discord Follow the human behind the microphone → https://links.sith2.com/linkedin Need another way to reach me? That’s here → https://linktr.ee/rich.greene