Prepare a phishing report carefully before it goes out.
Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.
Gather the reported website and supporting details into a reviewable case. Check that the evidence is credible, identify the appropriate service contacts, and let an authorized person approve each report before anything is submitted externally.
Actual availability depends on published steps, supported connections, permissions, and provider approval.
“Organize the report and available evidence, identify relevant affected services, and prepare report drafts for authorized human review.”
Clear tasks, with review where it matters.
- Collect the suspected site and evidence
- Check the report for useful context
- Identify relevant service contacts
What this workflow could do
Helps a security reviewer organize suspected phishing reports and prepare service-specific submissions without sending them automatically.
A person must verify the website and evidence, confirm each recipient, and approve the exact report before submission. Never automatically accuse an operator, request a takedown, or trigger an account or site restriction.
How the idea could work
Select an illustrative task to explore its proposed role. No workflow runs here.
-
Record the reported website address, the reason it appears suspicious, and any supporting observations supplied by the reporter.
-
Identify missing details and ask a security reviewer to assess whether the evidence supports a report.
-
Determine which affected platform or hosting provider may need to receive a report, and verify the appropriate reporting destination.
-
Draft a factual summary that distinguishes observed evidence from assumptions and includes only relevant information.
-
Show the complete report and recipient to an authorized person. Send nothing externally unless that person approves the exact submission.
-
Keep the approval or rejection, recipient, submission status, and any follow-up in the case record.
Collect the suspected site and evidence
Record the reported website address, the reason it appears suspicious, and any supporting observations supplied by the reporter.
Proposed setup considerations
These are planning notes for the concept, not instructions for a currently available template.
- 01
Choose the restricted case record
Select a location accessible only to authorized security reviewers and define the details needed to assess a report.
- 02
Document evidence and recipient checks
Set expectations for verifying the site, supporting evidence, affected service, and current reporting destination.
- 03
Assign report approvers
Name the people allowed to approve external submissions and require approval of each complete report before sending.
- 04
Test review and stop paths
Check an approved report, an unverified claim, an uncertain recipient, and a rejected submission; ensure each stays unsent until approval.
Published templates and verified customer availability remain pending.
A little less busywork.
A little more room for you.
Explore the sample experience while launch details are being finalized.
View pricing status Explore the simulation