Awareness

The Cost of Not Reporting: What Happens When Suspicious Emails Go to Trash

· Regonance Cybersecurity · 10 min read

When an employee receives a suspicious email and deletes it, the immediate threat to that employee is neutralised. But the threat to the organisation has just become invisible. The email is gone, but the attack campaign behind it continues — targeting other employees, other departments, other organisations in the supply chain. No evidence has been preserved, no intelligence has been extracted, no one else has been warned, and the audit trail regulators expect does not exist. Deleting a suspicious email feels like a safe action. For the organisation, it is one of the most expensive decisions an employee can make.

What Deletion Costs

1. Lost Early Detection

A suspicious email report is the earliest possible signal that an attack is underway. It arrives before technical controls detect malicious activity, before compromised credentials are used, before data is exfiltrated. When that email goes to trash instead of to the security team, the earliest detection opportunity is gone.

The consequence is delayed detection. Without the employee's report, the organisation does not become aware of the attack until a later signal fires — an endpoint detection alert, an anomalous login, a financial discrepancy, or a customer complaint. Each hour of delay expands the attacker's window for lateral movement, data collection, and exfiltration.

Research consistently shows that the cost of a security incident correlates directly with the time between initial compromise and detection. Organisations that detect and contain breaches quickly incur significantly lower costs than those where breaches persist undetected for weeks or months. The employee who deletes rather than reports extends that detection gap by the one signal that could have shortened it.

2. Campaign Blindness

A single suspicious email is rarely a single attack. Most phishing and BEC campaigns target multiple employees simultaneously or in sequence. The first report of a campaign allows the security team to:

  • Search for similar emails across all mailboxes
  • Quarantine related messages before other employees interact with them
  • Alert the organisation to the specific threat
  • Block the sender's infrastructure

When the first recipient deletes the email, the campaign remains invisible. The second, third, and tenth recipients face the same email with no warning and no protection. Each deletion is a missed opportunity to protect every subsequent target.

The compounding effect: If 10 employees receive a phishing email and all 10 delete it, the campaign succeeds or fails based entirely on whether any of the 10 clicked before deleting. If even one of the 10 reports it, the security team can protect all 10 — and everyone else who might receive the next wave.

3. Destroyed Evidence

A deleted suspicious email is destroyed evidence. Even if the attack is later detected through other means, the original phishing email — with its headers, sender infrastructure, payload details, and delivery path — is gone.

This evidence is needed for:

Incident investigation. The original email headers reveal the attacker's infrastructure (sending IP, mail server, domain registration). Without them, investigators work with fragments — endpoint logs, authentication records — that tell them where the attacker went but not where they came from.

Regulatory notification. NIS2, DORA, CRA, and GDPR notifications all require documentation of the incident's nature, indicators of compromise, and the organisation's detection and response actions. A well-preserved phishing email provides direct evidence for each of these requirements. A deleted email provides nothing.

Legal and insurance purposes. Cyber insurance claims increasingly require evidence of the attack vector and the organisation's response posture. Law enforcement referrals require forensically sound evidence. A deleted email satisfies neither.

4. Regulatory Exposure

Under NIS2, DORA, CRA, and GDPR, organisations are expected to detect security incidents and report them within prescribed timelines. The regulatory framework assumes organisations have an incident detection capability — which, for email-based threats, means a reporting process.

When employees routinely delete suspicious emails instead of reporting them, the organisation cannot claim to have an effective detection capability. If a breach is later discovered through other means and regulators ask why the initial phishing email was not detected and reported, the answer — "the employee deleted it" — demonstrates a systemic failure in the detection process, not an individual oversight.

The regulatory penalties are material:

RegulationMaximum FineReporting Obligation
NIS2€10M or 2% global turnover24-hour early warning, 72-hour notification
DORADetermined by national authority4-hour initial notification
CRA€15M or 2.5% global turnover24-hour early warning
GDPR Art. 33€10M or 2% global turnover72-hour notification to supervisory authority

These penalties apply to notification failures — and a failure to detect (because the employee deleted the evidence) is often the root cause of a failure to notify on time.

5. No Improvement Loop

The 9th stage of the Every Report Matters lifecycle is Improve — extracting lessons from each incident to strengthen defences. This improvement loop depends on having data: What was the attack? How was it delivered? Who was targeted? What worked and what did not?

A deleted email contributes nothing to this loop. The organisation cannot learn from a threat it never saw. Training content is not updated because the attack type was never captured. Detection rules are not refined because the indicators were never extracted. The same attack works again next month because the organisation is still defending against last year's threats.

The ROI of Reporting

If deletion is costly, reporting is the inverse — and the return on investment is compelling:

Early detection saves money. The difference in total incident cost between early detection (days) and late detection (months) is measured in orders of magnitude. A phishing attack detected through an employee report and contained within hours costs a fraction of the same attack discovered weeks later through a financial audit.

Campaign disruption protects the whole organisation. One report that leads to the quarantine of a phishing campaign protects every employee who would have received the next wave. The protective value of a single report multiplies across the entire organisation.

Evidence preservation supports compliance. A preserved phishing email provides the evidence base for regulatory notifications, reducing the risk of fines for notification failures. The cost of building a reporting process is trivial compared to the potential penalties for inadequate detection.

Intelligence improves defences over time. Each reported and analysed email contributes to the organisation's understanding of its threat landscape. Over time, this intelligence informs strategic decisions about security investment, training focus, and technology deployment.

Reporting culture reduces click-through rates. Organisations with active reporting cultures consistently show lower phishing click-through rates — not because employees are better at spotting phishing, but because the reporting habit creates a pause-and-think moment that interrupts the attacker's urgency manipulation.

Making the Business Case

For executives and decision-makers, the business case for structured email reporting is straightforward:

The investment is small. A shared mailbox with auto-acknowledgement, a triage checklist, and an awareness communication campaign costs effectively nothing in licensing and infrastructure. The primary investment is staff time for triage and process design.

The risk reduction is large. A functioning reporting process detects threats earlier, reduces incident scope, supports regulatory compliance, and produces intelligence that strengthens defences over time. Each of these outcomes has a quantifiable financial impact.

The alternative is more expensive. Without reporting, the organisation relies entirely on technical controls and after-the-fact detection. Technical controls are necessary but insufficient — they do not catch BEC, targeted social engineering, or novel attacks that bypass automated filters. After-the-fact detection means the damage is already done before the response begins.

Frequently Asked Questions


This article is part of the Every Report Matters knowledge series by Regonance Cybersecurity. For the complete methodology and implementation guidance, explore the Reporting Readiness Kit, the Complete Reporting Playbook, or the Organisational Implementation Package.

Related articles:

Download the free Every Report Matters Methodology Brief → Download (email required)

Download the free Every Report Matters Methodology Brief

The reporting gap, the 9-stage lifecycle, and why EU regulation now makes this urgent. 11 pages.

We publish practical cybersecurity reporting articles. No spam. Unsubscribe with one click.