Skip to content

New: How We Design Technology - our seven-layer architecture model, explained in full. See the architecture

general

An Analyst Clicked a Phishing Link. What a Lab Does Next

11/17/2026

An analyst is standing in your doorway with her laptop open. She clicked a link in an email that looked like a case file shared by a detective, typed her password into the page that came up, and only then noticed the web address was wrong. Her first question is whether she's in trouble. Your first question is what that password unlocks.

How the next hour goes depends on what you do in the first ten minutes. Good phishing incident response in a forensic lab has two jobs running side by side: contain the account before anyone else uses it, and keep a record clean enough to stand up in a quality review or on cross-examination. Supervisors usually hear about the click first, so a lot of that starts with you.

At a glance

  • Thank the analyst for reporting, write down what happened while it's fresh, and call IT right away.
  • IT contains the Microsoft 365 account first, then checks whether the same password opens LIMS, instrument, or evidence systems.
  • Bring in your quality manager early and document the event the way you'd document anything that might reach a courtroom.

Start with the person who reported it

The analyst who walks into your office has done the most useful thing anyone can do after a click. If the response feels like blame, the next person who clicks will stay quiet, and a silent compromise is far harder to contain than a reported one.

Thank her, then get the facts while they're fresh. Ask her to stop using the laptop for anything except what IT asks for, and to leave the suspicious email where it is. Write down:

  1. The time she clicked and the time she reported it.
  2. The sender, subject line, and whether the message is still in her inbox.
  3. What she entered on the page: a password, an MFA approval, a code, or nothing.
  4. Whether anything downloaded or opened, and whether the laptop has acted strangely since.
  5. Which systems she signed in to that day, including LIMS and any instrument workstations.

An MFA approval or a one-time code typed into a fake page matters as much as the password. Some phishing pages pass both straight through to the real sign-in screen.

Make the right calls in the right order

Call whoever handles security for the lab, whether that's lab IT, agency IT, or an outside provider, and use a phone number you already have. Read them your notes. If the analyst's mailbox might be compromised, keep the coordination off email.

Tell your quality manager the same day. The event may need a quality record, and it's easier to build that record from the start than to rebuild it later. If the lab's systems hold criminal justice information, your agency's security contact needs to know too, for the reasons covered below.

What IT does to contain the account

Microsoft's guidance for a compromised Microsoft 365 account lays out the core steps. Expect your IT team or provider to:

  • Disable the account while they investigate, or at least reset the password and send the new one outside email.
  • Revoke active sessions so a stolen sign-in token stops working right away.
  • Review the registered MFA methods and remove anything the analyst doesn't recognize.
  • Check mail forwarding and inbox rules, including hidden ones, along with app consents and admin roles.
  • Pull the sign-in logs and audit records, and review what the account sent while it may have been under someone else's control.

Microsoft is clear that every step matters, because any one of them left open can give an attacker a way back in. If something downloaded, IT may also take the laptop off the network and examine it before it goes back into service.

Keep the analyst informed in plain terms. Being locked out of email for a few hours is a reasonable price for a clean account, and most people accept it once they know why.

Check the systems that touch casework

The mailbox is rarely the end of it. Ask IT to check every place the analyst's credentials might work.

LIMS and case management. If those systems sign in through the lab's Microsoft Entra ID accounts, the session revocation and password reset carry over. If they use separate local accounts, and the analyst used the same password, those accounts need resets too.

Instrument workstations. Many run vendor software with local or shared logins. Find out whether the analyst's password, or a shared one she knows, opens any of them.

Evidence and file shares. Check what the account could reach and whether anything was opened, changed, or downloaded during the window between the click and the reset.

Sign-in and audit logs answer most of these questions. They also turn "we think nothing happened" into "here's what the records show," which is a far better sentence to have in a report.

When criminal justice information is involved

Many forensic labs handle criminal justice information (CJI) or work alongside systems that do. The FBI's CJIS Security Policy expects agencies to have incident handling that covers preparation, detection and analysis, containment, recovery, and user response, and to track, document, and report incidents.

Reporting runs through your agency's security contacts and your state's CJIS Systems Agency, following that agency's procedures. Lab supervisors don't usually file those reports directly, but you supply the facts they rely on. If you aren't sure whether the analyst's account could reach CJI, say so early and let the agency decide.

Document it so it holds up later

A phishing click is a security event. In a lab, it can also become a quality event and, occasionally, a question from defense counsel about whether evidence systems were exposed. The record you build in the first day is the one people will read later.

Keep it factual and in time order: what was reported, what was checked, what the logs showed, what was changed, and who approved each step. Attach the log exports and the original message with full headers, stored where your quality system keeps records.

Your quality manager decides how the event fits the lab's procedures, whether that's a corrective action, a nonconforming work review, or a short entry closing it out. Avoid guessing in the record. "No sign-ins to LIMS from unfamiliar locations during the exposure window, per logs reviewed on this date" is far stronger than "nothing was affected."

Make the next click less dangerous

Phishing emails will keep arriving, and someone will eventually click one. The goal is to make that click cheap. Three changes do the most.

Phishing-resistant MFA. Microsoft's phishing-resistant options are FIDO2 security keys, Windows Hello for Business, and certificate-based authentication. These are tied to the real site or device, so a fake sign-in page can't relay them. Start with supervisors, LIMS administrators, and anyone with access to evidence systems. Our piece on passwordless authentication covers what that change feels like for staff.

A report button people actually use. Microsoft 365 includes a built-in Report button in Outlook that sends suspicious messages to your security team, to Microsoft, or both. Turn it on, tell people where it is, and thank them when they use it.

Short, realistic training. Ten minutes built around the lures your lab actually sees (fake case files, court notices, vendor invoices, instrument support emails) teaches more than an hour of generic slides.

Then run a short tabletop once a year. Walk a supervisor, IT, and the quality manager through a click like this one and see where the handoffs slow down.

Get the response ready before the next click

When an analyst reports a click, the lab's response should feel routine. Everyone should know who to call, what IT will do, which systems get checked, and how the record gets built.

At CTP, we help forensic labs set up the identity controls, logging, and response steps behind that routine, and we write each decision down so your quality system and your agency partners can follow it. See how we approach security and access for forensic laboratories, or schedule a conversation about how your lab handles a phishing report today.

Sources and further reading

Ask about something important for you.

Curious about our take on an industry or technology topic? Let us know.

Contact Us