suspicious emails reported to the UK's NCSC in 12 months — proving people will report if you make it simple
CYBERSECURITY · KNOWLEDGE · RESILIENCE
Suspicious email reporting — handled.
A practical methodology for recognising, reporting and responding to suspicious emails. Built for organisations that need to act, not just detect.
Don't click suspicious links. Don't open unexpected attachments. Don't reply. Report the original message to your organisation's security reporting channel — and through your email provider.
01 · THE REPORTING GAP
Most suspicious emails go nowhere useful
When someone receives a suspicious email, the usual advice is simple: don't interact with it, report it to your email provider, and delete it.
But that advice has a gap. The email provider learns about the message. The organisation being impersonated — the one whose customers, suppliers or employees are being targeted — often learns nothing.
The original evidence disappears. The security team never sees it. No investigation happens. No one connects it to the three other reports that arrived the same week from different people, all targeting the same payment process.
One suspicious email might be an isolated phishing attempt. It might also be the first visible sign of a business email compromise campaign, a supplier impersonation, a credential-harvesting operation, or a coordinated fraud targeting your organisation's identity.
Every report is a potential source of intelligence. Most organisations have no consistent way to capture it.
early-warning window after awareness of a significant NIS2 incident or a qualifying CRA reportable event — not every suspicious email
of breaches involved a non-malicious human element in Verizon DBIR 2024 — reporting supports the human line of defence
Sources: NCSC Annual Review 2026; NIS2 Article 23; Verizon DBIR 2024.
02 · THE EVERY REPORT MATTERS METHODOLOGY
From suspicious email to organisational intelligence — in nine stages
Every Report Matters is a practical, repeatable methodology for handling suspicious email reports. It connects individual awareness with organisational response and, where appropriate, collective intelligence. It complements existing cybersecurity standards including NIST CSF 2.0, ISO/IEC 27001, and established threat intelligence frameworks. It does not replace your email provider's reporting mechanism — it extends it.
- 01 →
Recognise
A stakeholder identifies a suspicious email
- 02 →
Report
The original message is submitted through an approved channel
- 03 →
Receive
The secure intake service acknowledges and records the submission
- 04 →
Preserve
Evidence and metadata are retained with integrity controls
- 05 →
Assess
The submission is classified and prioritised
- 06 →
Investigate
Analysts establish the threat, scope and potential impact
- 07 →
Respond
Containment and remediation actions are initiated
- 08 →
Resolve
The case is documented and outstanding risks escalated
- 09 →
Improve
Lessons are incorporated into security controls and awareness
Knowledge
Help people and organisations understand threats and make informed decisions
Response
Improve the handling of suspicious activity — from report to resolution
Intelligence
Turn validated observations into shared understanding and collective protection
03 · THE REGULATORY REALITY
Reporting isn't optional — regulation now demands it
The EU's cybersecurity regulatory landscape has changed fundamentally. NIS2, DORA, and the Cyber Resilience Act impose mandatory reporting duties for defined incidents or vulnerabilities, with tight deadlines. GDPR generally requires notification of personal data breaches within 72 hours of awareness unless the breach is unlikely to result in a risk to people's rights and freedoms.
Turning a suspicious email into a correct regulatory notification requires assessment of scope, severity and the applicable trigger. Every Report Matters helps build that internal capability — not every report requires external notification.
| Regulation | Scope | Reporting deadline | Effective |
|---|---|---|---|
| NIS2 | Essential and important entities across the EU | 24h early warning · 72h incident notification after awareness of a significant incident; specific trust-service rules differ | National law; Luxembourg: Act of 5 May 2026 |
| CRA | Manufacturers of products with digital elements | 24h early warning for actively exploited vulnerabilities or severe incidents impacting product security · 72h follow-up | 11 September 2026 reporting · 11 December 2027 full application |
| DORA | Financial entities; oversight framework for critical ICT third-party providers | Major ICT incidents: initial notice within 4h of classification and at most 24h after awareness; intermediate/final reporting follows | 17 January 2025 |
| GDPR Art. 33 | Data controllers processing personal data | Without undue delay and, where feasible, within 72h of awareness; risk-based exception applies | 25 May 2018 |
References: Luxembourg ILR · CRA Articles 14 and 71 · DORA reporting standards · GDPR Article 33
04 · PLAYBOOKS AND TOOLKITS
Everything you need to implement suspicious email reporting
REGONANCE CYBERSECURITY
Reporting Readiness Kit
Awareness materials, email forwarding guides, self-assessment scorecard, and a ready-to-use reporting policy template.
€29REGONANCE CYBERSECURITY
The Complete Reporting Playbook
Full implementation methodology — triage templates, escalation matrices, evidence preservation procedures, regulatory notification bridge (NIS2, DORA, CRA, GDPR), and staff communication templates.
€79REGONANCE CYBERSECURITY
Organisational Implementation Package
The Complete Reporting Playbook plus executive briefing, discovery questionnaire, readiness assessment checklist, and Methodology Brief.
The full methodology paper and recorded implementation walkthrough will be delivered to all package purchasers when available — at no additional cost.
€19905 · FREE METHODOLOGY BRIEF
Every Report Matters — Methodology Brief
The reporting gap, the 9-stage lifecycle, and why EU regulation now makes this urgent. 11 pages. The methodology overview behind our cybersecurity playbooks.
06 · FREE DOWNLOADS
Free Resources
Start building your reporting capability today
Reporting Readiness Checklist
A 16-point self-assessment across four domains — reporting channel, evidence handling, triage and response, culture and governance. Score your organisation against the Every Report Matters 5-level maturity model.
PDF — 8 pages
Download ChecklistSTOP. DON'T INTERACT. REPORT.
A ready-to-print A4 awareness poster for offices, break rooms, and onboarding packs. Customise the reporting address for your organisation.
PDF — A4 poster
Download Poster07 · CONSULTING SERVICES
Expert Support
When you need hands-on guidance
Reporting Readiness Review
A structured assessment of your organisation's current suspicious email reporting capability. We evaluate your reporting channel, evidence handling, triage procedures, and organisational culture against the Every Report Matters maturity model — and deliver a prioritised roadmap for improvement.
- Current-state assessment against the 5-level maturity model
- Gap analysis across all 16 checkpoints
- Prioritised improvement roadmap
- Executive summary with recommendations
Remote — typically 1–2 weeks
Book a Readiness ReviewImplementation Advisory
Hands-on guidance for organisations implementing the Every Report Matters methodology. We work alongside your team to establish the reporting channel, build triage procedures, map regulatory notifications, and embed reporting culture — tailored to your specific environment and regulatory obligations.
- Methodology implementation planning
- Reporting channel and triage process design
- Regulatory notification mapping (NIS2, DORA, CRA, GDPR)
- Staff awareness and culture programme design
- Ongoing advisory support
Remote — scoped to your requirements
Book an Advisory Call08 · ARTICLES AND INSIGHTS
From the Knowledge Hub
Expert articles on suspicious email reporting methodology, regulatory compliance, and implementation
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 →NIS2 Incident Reporting: How Suspicious Email Reporting Fits the 24/72-Hour Timeline
NIS2 requires a 24-hour early warning and 72-hour notification for significant incidents. Learn how structured suspicious email reporting helps you meet these deadlines.
· 11 min read
Read article →How Mature Is Your Suspicious Email Reporting? A 5-Level Self-Assessment
Most organisations sit at Level 1 or 2 of email reporting maturity. Use this 10-question self-assessment to find where you stand and what to build next.
· 12 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 →Every suspicious email your people ignore is intelligence you'll never have.
Start with the free methodology brief. Build from there.