Assessment

How Mature Is Your Suspicious Email Reporting? A 5-Level Self-Assessment

· Regonance Cybersecurity · 12 min read

Most organisations sit at Level 1 or 2 of suspicious email reporting maturity — they know phishing exists and may have a reporting channel, but lack structured triage, evidence preservation, investigation procedures, or intelligence extraction. The gap between Level 2 (a mailbox exists) and Level 3 (a lifecycle operates) is where regulatory compliance becomes demonstrable, where incident response accelerates measurably, and where reports start producing organisational value beyond individual threat response.

This article presents the 5-level maturity model, a 10-question self-assessment to identify where your organisation stands, and a practical roadmap for moving to the next level.

The 5-Level Maturity Model

Level 1: Basic Awareness

What it looks like: Employees have received some security awareness training. They know phishing exists. There is no dedicated reporting channel — employees who suspect an email may forward it to their manager, mention it to IT informally, or delete it. There are no SLAs, no triage process, no evidence preservation, and no metrics.

Risk profile: High. Threats are detected inconsistently and addressed reactively. There is no documented trail for regulatory compliance. The organisation cannot demonstrate an incident detection capability under NIS2, DORA, or GDPR.

Common in: Small organisations without dedicated security staff, or larger organisations that have focused security investment on technical controls without addressing the human reporting process.

Level 2: Managed Reporting

What it looks like: A dedicated reporting channel exists — a specific email address (e.g., suspicious@yourdomain.com) or a reporting button in the email client. An auto-acknowledgement is configured. Reports are received and reviewed by IT or a designated security contact. Basic triage occurs, but it is informal — dependent on the individual reviewer's judgment rather than a standardised process. Evidence may or may not be preserved.

Risk profile: Moderate. Threats are detected more consistently, and reports create a basic audit trail. However, the lack of standardised triage, evidence preservation, and investigation procedures means the organisation struggles to meet regulatory notification requirements within required timelines.

Common in: Mid-sized organisations with IT teams that have taken on security responsibilities, or larger organisations early in their security maturity journey.

Level 3: Integrated Response

What it looks like: The full 9-stage lifecycle is in place. Reports are received through a dedicated channel with auto-acknowledgement, triaged against a standardised checklist, preserved in forensic format, investigated with documented procedures, and resolved with reporter feedback. Regulatory notification requirements (NIS2, DORA, CRA, GDPR) are mapped to the lifecycle stages, with decision trees and notification templates prepared in advance.

Risk profile: Lower. The organisation has a demonstrable incident detection and response capability. Regulatory notifications can be produced within required timelines from the evidence base the reporting lifecycle generates. The audit trail is complete.

Common in: Organisations with dedicated security teams or managed security service providers, or organisations that have made reporting maturity a deliberate investment area.

This is the compliance threshold. Organisations subject to NIS2, DORA, CRA, or GDPR need to operate at Level 3 or above to consistently meet their regulatory obligations. The jump from Level 2 to Level 3 is where the most significant operational improvement occurs.

Level 4: Intelligence-Driven

What it looks like: Beyond individual incident response, the organisation analyses patterns across all reports — looking for campaign indicators, targeting trends, recurring attack techniques, and evolving threat actor behaviour. Threat intelligence extracted from reports is fed back into detection rules, training content, and security strategy. Reporting metrics (volume, time-to-report, false positive ratio, report-to-detection conversion) are tracked and used to optimise the process.

Risk profile: Low. The organisation is not just responding to individual threats but anticipating them. The reporting process is a strategic intelligence capability, not just an operational control.

Common in: Organisations with mature security operations centres or strong security leadership that has invested in the intelligence dimension of reporting.

Level 5: Collaborative Resilience

What it looks like: The organisation shares threat intelligence derived from reports with industry peers, sector-specific information sharing groups, and supply chain partners. Supply chain vendors are assessed on their reporting maturity and supported in improving it. The reporting process is integrated across organisational boundaries — enabling cross-organisational detection and coordinated response.

Risk profile: Minimal. The organisation contributes to and benefits from collective defence, extending its detection and intelligence capabilities beyond its own boundaries.

Common in: Large organisations in regulated industries, critical infrastructure operators, and organisations that actively participate in information sharing communities.

The 10-Question Self-Assessment

Answer each question honestly based on your organisation's current state, not its aspirations or plans.

Reporting Infrastructure

1. Do you have a dedicated channel for employees to report suspicious emails?

  • ❌ No dedicated channel — employees handle suspicious emails themselves → Level 1
  • ✅ Yes — a specific email address, reporting button, or both → Level 2+

2. Does every report receive an automatic acknowledgement?

  • ❌ No — reporters do not know whether their report was received → Level 1-2
  • ✅ Yes — an auto-reply confirms receipt within minutes → Level 2+

3. Is the reporting channel communicated to all employees at least quarterly?

  • ❌ No — it was announced once or is buried in a policy document → Level 2
  • ✅ Yes — regular reminders through multiple channels → Level 3+

Evidence and Triage

4. Are reported emails preserved in their original format (including full headers)?

  • ❌ No — reports arrive as forwarded text or are not preserved at all → Level 1-2
  • ✅ Yes — originals are saved as .eml or .msg with full headers → Level 3+

5. Do you use a standardised triage checklist to assess every report?

  • ❌ No — assessment depends on the individual reviewer's judgment → Level 2
  • ✅ Yes — a documented checklist produces consistent, repeatable assessments → Level 3+

6. Does triage explicitly check whether the report triggers regulatory notification requirements (NIS2, DORA, GDPR, CRA)?

  • ❌ No — regulatory assessment happens separately, later, or not at all → Level 2
  • ✅ Yes — regulatory triggers are evaluated as part of the initial triage → Level 3+

Response and Feedback

7. Do reporters receive feedback on the outcome of their report?

  • ❌ No — reporters never hear what happened → Level 1-2
  • ✅ Yes — reporters receive a closing notification with the outcome → Level 3+

8. Are investigation and response procedures documented and followed?

  • ❌ No — investigations are ad hoc → Level 1-2
  • ✅ Yes — documented procedures produce consistent investigation outputs → Level 3+

Intelligence and Improvement

9. Do you analyse patterns across multiple reports to identify campaigns or trends?

  • ❌ No — each report is treated as an isolated event → Level 1-3
  • ✅ Yes — cross-report analysis reveals campaigns, trends, and attacker behaviour → Level 4+

10. Do you share threat intelligence from reports with external partners or industry groups?

  • ❌ No — reporting data stays internal → Level 1-4
  • ✅ Yes — indicators and intelligence are shared with peers and supply chain partners → Level 5

Scoring

Your ProfileLikely Maturity Level
Questions 1-2: NoLevel 1 — Basic Awareness
Questions 1-2: Yes, 3-6: Mostly NoLevel 2 — Managed Reporting
Questions 1-8: Yes, 9-10: NoLevel 3 — Integrated Response
Questions 1-9: Yes, 10: NoLevel 4 — Intelligence-Driven
All YesLevel 5 — Collaborative Resilience

This is a diagnostic overview. The full 16-checkpoint Reporting Readiness Scorecard in the Reporting Readiness Kit provides a more granular assessment with specific scoring criteria for each checkpoint.

Roadmap: Moving to the Next Level

From Level 1 to Level 2: Establish the Channel

Timeline: Days to weeks

What to build:

  • A dedicated reporting email address with auto-acknowledgement
  • Basic communication to all employees (onboarding, posters, email)
  • Assignment of responsibility for monitoring the mailbox

What it costs: Minimal — a shared mailbox is free in Microsoft 365 and Google Workspace. The primary investment is communication effort.

What it delivers: A documented reporting capability. Reports begin accumulating, creating visibility into threats that were previously invisible.

From Level 2 to Level 3: Build the Lifecycle

Timeline: 4-8 weeks

What to build:

  • Evidence preservation (configure for .eml/.msg retention)
  • Standardised triage checklist with regulatory triggers
  • Investigation procedures with defined outputs
  • Reporter feedback loop (closing notifications)
  • Regulatory notification templates and decision trees

What it costs: Moderate — primarily staff time to build and test the lifecycle. May require security team involvement if not already in place.

What it delivers: A demonstrable regulatory compliance capability. The organisation can meet NIS2, DORA, CRA, and GDPR notification deadlines from the evidence base the lifecycle generates.

From Level 3 to Level 4: Extract Intelligence

Timeline: 3-6 months (ongoing maturation)

What to build:

  • Cross-report analysis processes (campaign detection, trend identification)
  • Metrics tracking and reporting (volume, time-to-report, conversion rates)
  • Feedback loop from intelligence to detection rules and training content
  • Integration with threat intelligence platforms (if available)

What it costs: Significant — requires analytical capability (security team or managed service) and sustained investment in pattern analysis.

What it delivers: Proactive threat detection. The organisation anticipates attacks based on patterns rather than waiting for individual reports.

From Level 4 to Level 5: Share and Collaborate

Timeline: 6-12 months

What to build:

  • Intelligence sharing agreements with industry peers or sector groups
  • Supply chain reporting maturity assessment and support
  • Cross-organisational detection and response integration

What it costs: Primarily relationship and governance effort. Technical requirements are modest if Level 4 intelligence extraction is already in place.

What it delivers: Collective defence. The organisation benefits from and contributes to a broader intelligence network.

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.