Supply Chain Email Security: Why Your Vendor's Reporting Maturity Is Your Risk
· Regonance Cybersecurity · 10 min read
Ninety-seven percent of firms surveyed in a major industry study reported being negatively impacted by a cybersecurity breach that occurred in their supply chain. Phishing through trusted vendor relationships is one of the most effective attack entry points because it exploits something technical controls cannot override: trust. When a vendor's email account is compromised and used to send a fraudulent invoice to your finance team, your email security gateway lets it through — because it is a real email from a real vendor. Your organisation's resilience to this attack depends not only on your own reporting maturity, but on your vendor's.
How Supply Chain Email Attacks Work
Supply chain email attacks exploit the trust relationships between organisations and their vendors, partners, and suppliers. The typical attack unfolds in stages:
Stage 1: Compromise the vendor. The attacker gains access to a vendor's email account through phishing, credential stuffing, or exploitation of a vulnerability. This may take weeks or months of patient reconnaissance.
Stage 2: Observe and learn. With mailbox access, the attacker monitors the vendor's communications — learning who they invoice, how they communicate, what payment terms they use, which individuals handle which accounts. The attacker may also create forwarding rules to silently copy communications to an external address.
Stage 3: Insert the attack. At the right moment — typically aligned with a real invoice cycle or known transaction — the attacker sends a fraudulent communication from the vendor's actual email account. This might be a modified invoice with altered bank details, a request to redirect payments to a new account, or a social engineering message designed to extract sensitive information.
Stage 4: Exploit trust. Because the email comes from the genuine vendor account, it passes all email authentication checks (SPF, DKIM, DMARC). The recipient has no technical reason to suspect the email is fraudulent. Only human judgment — a sense that something about the request does not match expectations — can catch it.
This is vendor email compromise (VEC), and it is one of the most damaging forms of business email compromise precisely because it weaponises legitimate trust.
Your Risk Is Your Weakest Vendor
An organisation can invest heavily in its own email security, employee training, and reporting processes — and still be exposed through a vendor with none of these controls. The supply chain is only as strong as its weakest link.
Where vendor reporting maturity creates risk for your organisation:
Slow detection at the vendor. If a vendor has no employee reporting culture, a compromised account may go undetected for weeks or months. Every day the compromise persists, the attacker gathers more intelligence and the risk of a successful attack against the vendor's clients increases.
No notification to clients. When a vendor discovers an account compromise, do they notify affected clients? Many organisations have no process for this. The vendor may address the compromise internally without informing anyone who may have received fraudulent communications.
Poor evidence preservation. When a vendor's email account is compromised and used to attack their clients, forensic evidence from the vendor's environment is essential for investigation. A vendor with no evidence preservation process may remediate the compromise (resetting passwords, clearing forwarding rules) before preserving the data needed for their client's investigation.
No intelligence sharing. A mature vendor would share indicators of compromise — the attacker's infrastructure, the types of fraudulent communications sent, the timeline of compromise — with affected clients. Immature vendors treat the compromise as a private embarrassment to be managed internally.
Assessing Vendor Reporting Maturity
The Every Report Matters 5-level maturity model can be applied to assess supply chain partners as part of vendor risk management:
| Level | Name | What It Means for You |
|---|---|---|
| 1 — Basic Awareness | The vendor knows phishing exists but has no dedicated reporting channel. Employees may or may not report suspicious emails. | High risk. Compromised accounts will be detected late, if at all. No notification or evidence sharing should be expected. |
| 2 — Managed Reporting | The vendor has a dedicated reporting channel. Reports are received and triaged with basic SLAs. | Moderate risk. Compromises are more likely to be detected internally, but the vendor may lack investigation capability and client notification processes. |
| 3 — Integrated Response | The vendor has a full reporting lifecycle — evidence preservation, investigation procedures, and regulatory notification mapping. | Lower risk. Compromises are detected, investigated, and documented. Client notification is likely part of the process. Evidence is available for your investigation. |
| 4 — Intelligence-Driven | The vendor analyses report patterns, extracts threat intelligence, and proactively hunts for compromises. | Low risk. The vendor is likely to detect and contain compromises before they are used to attack clients. Intelligence sharing is standard practice. |
| 5 — Collaborative Resilience | The vendor shares intelligence with clients and industry partners. Reporting is integrated across the supply chain. | Minimal risk. The vendor is an active contributor to your security posture, not just a managed risk. |
Questions to include in vendor risk assessments
When evaluating supply chain partners, consider adding these reporting-specific questions:
- Do you have a dedicated channel for employees to report suspicious emails?
- What is your average time from employee report to triage?
- Do you preserve original email evidence (including headers) when a suspicious email is reported?
- Do you have a documented process for notifying clients if your email systems are compromised?
- Can you share indicators of compromise with affected parties?
- How do you train employees to recognise and report business email compromise attempts?
- Have you tested your reporting process in the last 12 months?
These questions do not require vendors to reveal proprietary security details. They assess whether the vendor has a functioning reporting lifecycle — the absence of which is a material risk to your organisation.
NIS2 and Supply Chain Reporting
NIS2 (Directive (EU) 2022/2555) explicitly addresses supply chain security. Article 21(2)(d) requires essential and important entities to implement "supply chain security, including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers."
This means NIS2-regulated organisations have a legal basis — and a regulatory expectation — for assessing their suppliers' cybersecurity maturity, including incident detection and reporting capability.
When a supply chain email compromise triggers a significant incident at your organisation, the NIS2 early warning (24 hours) and notification (72 hours) must document the attack vector — including the supply chain dimension. Having assessed your vendor's reporting maturity in advance strengthens your incident report and demonstrates due diligence.
Improving Supply Chain Reporting Maturity
Beyond assessment, organisations can actively improve their supply chain's reporting posture:
1. Include reporting maturity in procurement criteria. When onboarding new vendors, include email reporting capability as a due diligence item alongside other security requirements. This does not need to be a pass/fail gate — it establishes expectations and opens conversation.
2. Share your reporting expectations. Provide vendors with a clear statement of what you expect in the event of an email compromise: timely notification, evidence preservation, and indicator sharing. Formalise this in contracts where appropriate.
3. Offer resources. For smaller vendors who lack the resources to build their own reporting process, sharing practical resources (reporting guides, policy templates, awareness materials) is more effective than demanding compliance they cannot achieve independently.
4. Conduct joint exercises. Tabletop exercises that simulate a supply chain email compromise — with both your team and the vendor's team participating — reveal gaps in the notification and evidence-sharing workflow before a real incident forces the issue.
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:
Business Email Compromise: Why Every Suspicious Email Report Is an Intelligence Opportunity
BEC is the costliest cybercrime, and technical controls cannot stop it alone. Learn how turning employee reports into intelligence disrupts BEC campaigns before financial loss occurs.
· 10 min read
Read article →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 →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 →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 →Download the free Every Report Matters Methodology Brief → Download (email required)