Security operations

A phishing report triage routine for a small IT team

A triage routine that preserves the reported message, applies a fixed verdict rubric, contains the account, and closes the loop with the reporter.

Short answer

Start with repeatable IT work that has a clear owner, clear access limits, and a review cadence. Keep risky technical decisions with the manager or provider who owns the system.

Delegation playbook

Best fitRepeatable IT admin
OwnerManager or IT lead
Risk ruleEscalate technical judgment
PilotTwo-week sample workflow
On this pageJump to section

A phishing report arrives as a forwarded message with no headers, a screenshot, or a vague warning that something looked wrong. The report is valuable, but only if the team can preserve the evidence and reach a verdict the same day. A triage routine gives every report the same path from intake to closure. It also tells the reporter what happened, which is the fastest way to keep reports coming.

Give reporters one clear route

Publish a single reporting address or button and put it in the mail client, the intranet, and the onboarding pack. Tell people to use it instead of forwarding to a colleague or a manager. Explain what to include, such as the message, the sender, and whether they clicked a link. Keep the instruction short enough to fit on a card beside the screen.

Confirm every report with an automatic reply that sets an expectation for the first response. Give the reporter a reference number so they can ask for an update without opening a new thread. Do not require them to judge whether the message is malicious, because that decision belongs to the triage process. A reporting route that demands analysis from the reporter will produce fewer reports.

Preserve the message before deleting

Save the original message with its full headers, not only the forwarded body. Export it as an email file and store it in the incident folder with the report reference. Capture the sender address, the reply-to address, the links, and the attachment names. A message that is deleted before it is preserved cannot support a later investigation. Store the exported file in a folder that the incident team can reach without the reporter.

Check whether other people received the same message by searching the mail system for the sender and the subject. Record the recipient count and the delivery time. Ask the mail administrator to hold the message rather than purge it immediately. Preservation should happen before containment so the evidence is not lost with the threat. Note the mail gateway rule that was applied so the block can be removed later.

Decide the verdict with a fixed rubric

Use a small set of verdicts such as malicious, suspicious, legitimate, or inconclusive. Write the evidence that supports each verdict and require the reviewer to record it. Check the sender domain, the link destination, the attachment type, and the language of the request. Apply the same rubric to every report so the outcome does not depend on who is on duty.

Escalate to the technical owner when the verdict is malicious or when the message reached a finance, executive, or administrator account. Record the escalation time and the person who accepted it. Keep the inconclusive category honest rather than forcing a decision with thin evidence. A verdict that cannot be explained is not a verdict the company can defend. Give the technical owner the case reference and the evidence file in the same message.

Contain the account and the message

If a recipient clicked a link or entered credentials, reset the password and revoke active sessions before anything else. Confirm that multi-factor authentication is enabled and that the recovery details still belong to the user. Check the mailbox for forwarding rules, inbox rules, and delegated access that the attacker may have added. Record each action with a timestamp. Check the sign-in log for the affected account and note any unusual location or device.

Remove the message from the mailboxes where it was delivered and block the sender or the link at the mail gateway. Keep a copy in the incident folder before removal. Tell the affected users what to do next and what to watch for. Containment is not complete until the account, the message, and the network path have all been addressed.

Close the loop with the reporter

Send the reporter a short outcome note that says whether the message was malicious, what action was taken, and whether they need to do anything. Thank them for reporting even when the message was benign. Avoid sharing details that would help an attacker or expose another person's account. A reporter who receives a clear answer is more likely to report the next message.

Use the outcome note to reinforce the reporting habit without turning it into a lecture. Include one line about what made the message convincing. Ask the reporter whether they clicked or replied so the containment step is accurate. Close the report only when the reporter has the answer and the evidence is filed. Add the reporter's question to the next awareness note if more than one person asked it.

Review reports monthly

Count the reports, the verdicts, the time to first response, and the time to containment. Look for a rise in reports that turn out to be legitimate, which may mean the filters are too aggressive. Check whether the same sender or link appears more than once. Share the pattern with the team without naming the reporters. Compare the monthly count with the number of messages the filter blocked automatically.

Update the reporting instructions and the rubric when the pattern changes. Add the common lure to the security awareness note for the month. Test the reporting route with a simulated message and confirm that the reply and the ticket are created. A monthly review keeps the routine current and shows whether people trust it. Record the change in the triage log so the next reviewer knows why the rubric moved.

Keep evidence for the incident file

Store the original message, the headers, the verdict, the actions, and the outcome note under one reference. Limit access to the people who need it and record who opened the file. Keep the evidence for the period required by the company's policy and any contract. A file that cannot be found later is the same as no evidence. Name the person who can retrieve the file if the primary reviewer is unavailable.

Write a one-page summary for serious cases that names the timeline, the accounts involved, and the lessons. Do not include passwords or full credential details in the summary. Review the file after thirty days and confirm that the containment still holds. The incident file supports the next review and any notification the company must make. File the summary with the report reference so the next incident can find the precedent.

Sources and next step

Use the CISA Cross-Sector Cybersecurity Performance Goals and the NIST Cybersecurity Framework 2.0 as primary references for the meeting room, vendor handover, phishing triage, battery, and calendar delegation practices discussed in these guides. The NIST SP 800-63B digital identity guidance supports the verification and delegation steps, and NIST SP 800-53 Rev. 5 supports the access and evidence records. Apply your own policies, contracts, and system documentation to the workflow.

Compare this guide with the vendor account manager handover note and the phishing report triage routine before changing a live process. If the coordination is recurring and your technical owner can define the boundaries, review the IT virtual assistant service areas and contact ITVirtualAssistant to discuss a limited pilot.

Operating brief

What this guide should help you decide

Delegate

Routine intake, status updates, records, screenshots, and documentation upkeep.

Keep ownership

Approvals, risky system changes, security decisions, and final technical judgment.

How to use this guide

Use this page to decide what an IT virtual assistant should handle first. If the task is recurring, documented, and easy to review, it is usually a better first delegation candidate than work that requires live technical judgment.

Treat the article as an operating brief, not just a topic overview. The goal is to turn loose IT work into a named workflow with inputs, outputs, permissions, review cadence, and a handoff rule that protects the business while reducing manager load.

Workflow

Recommended operating workflow

1

Define the request

Write what a phishing report triage routine for a small it team means in your company, where requests enter, and what finished work looks like.

2

Limit the access

Give the assistant only the tool permissions needed for intake, records, status updates, or documentation.

3

Run a pilot

Use a two-week sample period so the manager can review accuracy before expanding the workflow.

4

Review patterns

Summarize repeat issues, blocked requests, and escalation volume so the technical owner can improve the process.

Decision rules

QuestionVA fit signalEscalate when
Is the work repeatable?The same request appears weekly and can be described in steps.The request changes business policy or system design.
Can quality be reviewed?The manager can inspect the output without redoing the work.Only a senior technical person can judge correctness.
Is access contained?The assistant can work with read-only or role-limited access.Admin rights, customer data, or security settings are involved.

Delegation checklist

  • Write the intake source, expected output, and manager review cadence.
  • Confirm the assistant has only the permissions needed for the workflow.
  • List the events that require escalation before work continues.
  • Track examples for two weeks before changing the workflow.
  • Save examples of good and bad outputs so the assistant has concrete references.
  • Review the workflow monthly and remove permissions that are no longer needed.

Example first-week agenda

Day one should cover the workflow owner, tools, allowed actions, forbidden actions, and escalation language. By the end of week one, the assistant should have produced a small sample of completed work, a list of unclear requests, and a manager-reviewed improvement note.

What to review before delegating

Confirm the owner, access level, review cadence, and escalation path before assigning any recurring IT workflow to a remote assistant.

What should an IT virtual assistant handle first?

Start with repeatable, reviewable work such as ticket summaries, account records, documentation updates, and checklist follow up.

Get free IT support review