Outsourced CompanyPowered by StealthAgents

Philippines staffing guide · Published

Write a phishing report triage script for an outsourced IT service desk

A forwarded phishing report can become a second incident if the desk clicks first. Give the service desk a triage script that contains the account, preserves the message, and tells the user what happens next.

Write a phishing report triage script for an outsourced IT service desk operations illustration

The short answer

A phishing triage script should stop the desk from opening the message, capture the original headers, and contain any exposed account before deeper analysis. The user needs a clear next step, and the security lead needs a record that survives the shift.

Take the report without clicking anything

Ask the user to forward the message as an attachment rather than as an inline copy. The attachment preserves the sender, the headers, the links, and any embedded files.

Tell the user not to click, reply, or delete the message yet. If the message is already deleted, ask the user to recover it from the deleted items folder and forward it the same way.

The desk should open the report in a controlled environment, not on a normal workstation. Use the client's approved analysis tool or a sandbox, and keep the original file unchanged.

Save a copy in the case record before any link is detonated. A triage that alters the evidence makes the later investigation harder to trust.

Separate credential exposure from attachment risk

Ask two questions first: did anyone enter credentials, and did anyone open an attachment. A credential entry is an account incident even when the page looked harmless.

An opened attachment may require endpoint scanning and a malware review. The answers decide the urgency, so the desk should not bury them under a long narrative.

If credentials were entered, treat the account as exposed and start containment. If an attachment was opened, isolate the device through the client's endpoint tool when that authority exists.

Record the time of the user's action, because the response window matters. The desk should not wait for a full analysis before taking the first containment step.

Contain the account before the analysis

Disable or restrict the account, revoke active sessions, and reset the password through the approved identity process. Check for new forwarding rules, mailbox delegates, and application consents that the attacker may have added.

These changes can survive a password reset, so they need a separate review. Record every action with the time and the administrator who performed it.

If the client uses multi-factor authentication, confirm the method and whether the attacker added a new device. Remove unknown devices and re-register the user through the approved process.

Tell the user not to approve a push notification they did not initiate. A prompt that arrives after a password reset is a warning, not a routine login.

If the user reused the password elsewhere, tell them to change it on the other services and report any unusual activity. Do not ask the user to send passwords or one-time codes to the desk.

The service desk should never collect a secret in a ticket, a chat, or an email. Use the identity tool's reset flow so the secret stays inside the approved system.

Preserve the message for investigation

Save the original message file, the sender address, the reply-to address, the subject, and the full header block. Extract the links without visiting them and record the domain.

If the case may become a legal or HR matter, follow the client's preservation instruction before deleting anything. A clean evidence folder is more useful than a detailed description written from memory.

Add the sender and the domains to the client's blocklist only after the security lead confirms the indicators. A hasty block can disrupt a legitimate sender or tip off the attacker.

Document the change and the reason so the next shift knows why the rule exists. The case record should show the path from report to containment to closure.

Keep the evidence folder limited to the people who need it. A phishing message can contain personal data, credentials, or a malicious file, so it should not circulate in a general channel.

Share a summary with the user and the full file only with the investigator. At closure, follow the client's retention rule instead of deleting the case as soon as the ticket is resolved.

Tell the user what to do next

Send the user a short message that names the containment step, the expected downtime, and the person who will follow up. If the user must change a password, give the approved link and a time by which to do it.

Avoid blaming language, because a frightened user may hide the next mistake. The goal is a fast report, not a confession.

Close the loop when the case is resolved, even if the answer is that the message was benign. A user who never hears back stops reporting.

Tell them what to watch for next time in one sentence. Keep the tone matter-of-fact so the reporting habit survives a busy week.

If the message came from a colleague's account, tell that colleague separately and ask them to stop using the account until it is cleared. Do not forward the suspicious message to a group as a warning.

That can spread the link and create more exposure. Use the client's awareness channel if a warning is needed.

Review the week's reports for patterns

At the end of the week, group the reports by sender domain, subject theme, and user department. A cluster aimed at finance may call for a targeted reminder, while a cluster from one external domain may call for a block.

Look also at reports that arrived late, because a slow report can point to a confusing reporting route. Bring the three largest groups to the security lead with a suggested action for each.

Share the pattern summary with the security lead and the client contact, not the raw message files. Keep the summary short enough to read in a meeting.

If the same user reports repeatedly after clicking, address the behavior through training rather than punishment. The reporting channel only works when people believe it will be used fairly.

Questions to copy for the sales call

  • "Did anyone enter credentials or open an attachment?"
  • "Is the original message preserved as an attachment?"
  • "Which account and session controls were applied, and when?"
  • "Who owns the follow-up with the user?"

Sources

Common questions

Should the desk click a link to see where it goes?

Only in an approved sandbox or analysis tool. Never open a link on a normal workstation or from the user's mailbox.

What if the user already deleted the message?

Recover it from deleted items and forward it as an attachment. If it cannot be recovered, record that and proceed with containment.

Does a password reset close the case?

Not by itself. Check sessions, forwarding rules, delegates, and application consents before closing the account review.

Who decides whether to notify regulators or customers?

The client's security and legal leads. The desk should preserve evidence and escalate without making that decision.

Philippines staffing intake

Define the position before hiring begins.

Share the tasks, tools, schedule, and approval limits for your Filipino team member. The intake turns those details into a practical staffing brief.

Contact Us