Setting Up a Suspicious Email Reporting Mailbox: A Practical Guide
· Regonance Cybersecurity · 9 min read
A dedicated suspicious email reporting mailbox — such as suspicious@yourdomain.com — gives every employee a clear, consistent place to send emails they are not sure about. Setting it up properly means configuring auto-acknowledgement so reporters know their submission was received, restricting access so only authorised staff can read reports, and defining the triage workflow so reports are assessed promptly instead of accumulating unread.
This guide walks through the practical setup from naming convention to triage workflow.
Step 1: Choose Your Naming Convention
The reporting address must be intuitive and memorable. Employees should be able to recall it without looking it up.
| Address | Pros | Cons |
|---|---|---|
| suspicious@yourdomain.com | Clear intent, easy to remember, professional | May feel formal for some cultures |
| report@yourdomain.com | Short, action-oriented | Ambiguous — could be confused with general reporting |
| phishing@yourdomain.com | Specific and clear | Limits scope — employees may not report BEC, scams, or other suspicious emails that are not technically phishing |
| security@yourdomain.com | Broad coverage | May receive unrelated security queries (password resets, access requests) |
Recommendation: Use suspicious@yourdomain.com. It covers the full range of suspicious emails — phishing, BEC, scams, impersonation, anything uncertain — without limiting scope. "Suspicious" is the one word that matches what the employee is feeling when they decide to report.
If your organisation already has an established reporting address, keep it — changing the address resets awareness. Add the preferred address as an alias if needed.
Step 2: Choose the Mailbox Type
Shared mailbox (recommended for most organisations)
A shared mailbox is accessible by multiple authorised team members without requiring a separate login. It appears in each member's email client alongside their personal mailbox.
Advantages: Multiple people can monitor and triage simultaneously, no single point of failure, built into Microsoft 365 and Google Workspace at no additional cost, does not consume a user licence.
Best for: Organisations of any size that want a simple, reliable setup without additional tooling.
Distribution list / group
A distribution list forwards incoming emails to the individual mailboxes of each list member.
Advantages: Easy to set up, each triage team member gets a personal copy.
Disadvantages: No single view of all reports, risk of duplicate investigation, difficult to track which reports have been triaged, original email may be re-forwarded (losing headers again).
Best for: Very small teams (2-3 people) as a temporary solution. Not recommended for sustained operations.
Dedicated reporting tool
Platforms like Microsoft Defender for Office 365 (with built-in reporting), or third-party phishing reporting tools, provide a structured intake system with automated analysis, case management, and metrics.
Advantages: Automated header analysis, IOC extraction, duplicate detection, metrics dashboards, integration with SIEM/SOAR.
Disadvantages: Cost, implementation complexity, potential over-reliance on automation.
Best for: Organisations at maturity Level 3+ (integrated response) with established security operations.
The practical starting point: Begin with a shared mailbox. It is free, built into your existing email platform, and operational within an hour. Move to a dedicated tool when report volume or operational maturity demands it.
Step 3: Configure Auto-Acknowledgement
Every report must be acknowledged immediately. This is non-negotiable for sustaining a reporting culture.
For Microsoft 365 shared mailbox:
Set up an automatic reply (Out of Office / Automatic Replies) on the shared mailbox:
Subject: Your report has been received
Body:
For Google Workspace shared mailbox:
Use a vacation responder or a Google Apps Script triggered on new messages to the mailbox.
Key elements of the acknowledgement:
- Confirms receipt — the report was not lost
- Sets expectations — the team will review, no further action needed from the reporter
- Invites escalation — if the employee interacted with the email, they should say so
- Reinforces value — "Your report helps protect the entire organisation"
Step 4: Set Access Controls
Only authorised personnel should have access to the reporting mailbox. Suspicious emails may contain malware, phishing links, or sensitive information about the attack.
Access should be granted to:
- Security team members responsible for triage
- IT operations staff designated for first-line triage (if no dedicated security team)
- Incident response leads
Access should NOT be granted to:
- General IT helpdesk (unless specifically trained and designated)
- Management or HR (they should receive summary reports, not direct access to raw submissions)
- Anyone who might casually open attachments or click links in reported emails
Configure the shared mailbox with "Send As" permissions only for authorised triage staff. Audit access quarterly.
Step 5: Define the Triage Workflow
A mailbox without a triage process is just a different kind of black hole. Define what happens when a report arrives:
Triage checklist (first 15 minutes per report):
- Log the report — Record: timestamp, reporter, subject line, sender address
- Initial classification — Is this obviously spam, probable phishing, BEC attempt, or uncertain?
- Interaction check — Did the reporter indicate they clicked, replied, or entered information?
- Campaign check — Have similar reports been received from other employees?
- Severity assessment — Does this report indicate a potential incident requiring escalation?
Triage outcomes:
| Outcome | Action | SLA |
|---|---|---|
| Spam / low risk | Log, close, notify reporter | Within 4 hours |
| Confirmed phishing (no interaction) | Block sender, quarantine similar emails, notify reporter, log indicators | Within 2 hours |
| Confirmed phishing (employee interacted) | Escalate to incident response, credential reset, endpoint check, notify reporter | Immediate |
| BEC / targeted attack | Escalate to incident response, assess financial exposure, check for similar targeting | Immediate |
| Uncertain | Hold for deeper analysis, acknowledge to reporter | Within 4 hours |
SLA targets:
- Acknowledgement: Immediate (auto-reply)
- First triage: Within 2 hours during business hours
- Reporter outcome notification: Within 24 hours
- Critical escalation: Immediate upon identification
Step 6: Communicate the Channel
A mailbox nobody knows about is a mailbox nobody uses. Communication must be persistent and multi-channel:
- Onboarding: Include the reporting address and a one-line instruction in every new employee's onboarding pack
- Email signature: Add a line to the IT or security team's email signatures: "Suspicious email? Forward as attachment to suspicious@"
- Intranet / internal wiki: A short page with the address, simple instructions, and a link to the forwarding guides
- Physical presence: Posters in common areas (kitchen, print room, near elevators) with the address and a QR code
- Recurring reminders: Monthly one-liner in the company newsletter or Slack channel: "Reminder: suspicious@ is your first stop for any email that doesn't look right"
Scaling: When to Move Beyond a Mailbox
A shared mailbox works well for organisations processing up to approximately 50-100 reports per month. Beyond that, or when the organisation reaches maturity Level 3 (Integrated Response), consider:
- A dedicated phishing reporting platform with automated analysis and case management
- Integration with your SIEM or SOAR for automated triage of known indicators
- API-based ingestion that extracts IOCs and creates tickets automatically
The transition should be seamless for reporters — the reporting address and process remain the same, only the backend changes.
Frequently Asked Questions
This article is part of the Every Report Matters knowledge series by Regonance Cybersecurity.
Related articles:
How to Build a Suspicious Email Reporting Process: The 9-Stage Lifecycle
A complete suspicious email reporting process follows 9 stages from recognition to improvement. Learn the lifecycle that turns every report into organisational resilience.
· 12 min read
Read article →Preserving Email Evidence: Why Forwarding Destroys What You Need Most
Forwarding a suspicious email strips critical forensic data. Learn how to preserve email evidence properly for incident investigation, regulatory compliance, and legal proceedings.
· 8 min read
Read article →Building a No-Blame Reporting Culture: Why Your Employees Delete Instead of Report
Employees delete suspicious emails instead of reporting them because the process is unclear, they fear blame, or reporting feels pointless. Here's how to fix it.
· 9 min read
Read article →Download the free Every Report Matters Methodology Brief → Download (email required)