Purpose of the Template
Phishing threats in Europe have surged dramatically, with Proofpoint's data showing a 4.5-fold increase from 2025 to 2026, compared to a 1.5-fold rise globally. The UK alone saw a six-fold increase. European users clicked on 8.3 out of every 100 threat messages, versus 2.0 globally. Your current phishing risk assessment may not reflect this significant regional gap.
This Regional Phishing Risk Assessment Record helps your team create a detailed entry for the Cybersecurity Risk Register. It links regional threat data to Compliance Controls, Key Control Indicators, and a defined Cyber Risk Appetite. Replace generic "phishing" entries with this detailed record to ensure auditors can test it effectively.
Prerequisites
Before using the template, ensure you have:
- A Cybersecurity Risk Register with an assigned risk owner for email and identity threats.
- A board-approved Cyber Risk Appetite statement.
- Access to your email security data (delivered threats, click rates, reported messages) by region or business unit.
- Identity provider logs for sign-in anomalies, mailbox rule creation, and OAuth app grants.
- An inventory of third-party and AI-enabled applications authorized through OAuth.
- The Regulatory Inventory for your European jurisdictions to map Regulatory Obligations to controls.
Record any missing elements in the template's assumptions field instead of estimating.
The Template
Copy the following block into your GRC Platform as a risk record or controlled document.
REGIONAL PHISHING RISK ASSESSMENT RECORD
1. Record Metadata
- Risk ID: [assign]
- Risk owner: [name, role]
- Region in scope: [e.g., UK, EU member states, combined Europe]
- Assessment date / next review date: [dates]
- Linked Regulatory Obligations: [list from Regulatory Inventory]
2. Threat Statement Describe the scenario in one paragraph. Example: "A threat actor uses targeted phishing or session hijacking to access a specific user account, then creates mailbox rules or links applications to maintain access and exfiltrate data."
3. Regional Threat Evidence
- External intelligence cited: [vendor, report, date]
- Regional versus global trend: [your figures, with source]
- Internal observed click rate by region: [your telemetry]
- Internal observed account-takeover indicators: [count, period]
- Confidence level in the data: [High / Medium / Low, with rationale]
4. Attack Pathway Analysis
- Broad-volume phishing exposure: [Y/N, describe]
- Precision cloud attack exposure: [Y/N, describe]
- Callback phishing exposure: [Y/N, relevant to sectors such as healthcare]
- AI-enabled application exposure (OAuth-connected apps): [count authorized, count reviewed]
5. Inherent and Residual Risk
- Likelihood (1-5): [score] | Impact (1-5): [score]
- Inherent Severity Level: [per your Risk Prioritization Matrix]
- Controls in place: [list Compliance Control IDs]
- Residual Severity Level: [per matrix]
- Position against Cyber Risk Appetite: [Within / Exceeds]
6. Control Design Summary For each control: ID, objective, owner, frequency, evidence source, test method.
- Phishing-resistant authentication for privileged and high-value users
- Session token protection and anomalous sign-in alerting
- Mailbox rule creation monitoring
- OAuth application consent governance
- Region-specific awareness training with simulated exercises
7. Key Control Indicators
- Click rate on simulated and real threats, by region
- Median time from user report to triage
- Percentage of OAuth grants reviewed within policy window
- Account-takeover events detected versus contained
8. Treatment and Escalation
- Treatment decision: [Mitigate / Accept / Transfer / Avoid]
- Approved Exception reference, if any: [ID, expiry]
- Escalation trigger: [Key Control Indicator threshold that sends the risk to the risk committee]
- Information Security Incident classification criteria: [link to Incident Response Structure]
9. Sign-Off Risk owner, CISO, and GRC lead attestation with date.
Customization Tips
Section 3: Use external statistics as context, but base your scores on your own data. If your click rate differs from Proofpoint's 8.3 per 100 figure, highlight that as a finding.
Section 4: Tailor this to your sector. For example, Proofpoint's data shows malware at 21% of threats in hospitality and leisure, and callback phishing up 257% in healthcare. Include only relevant pathways and justify exclusions.
Section 4's AI line: Proofpoint found over 188,000 AI-enabled applications connected through OAuth. Your exposure is the subset connected to your tenants. Get that count from your identity provider.
Section 5: Use your own scoring. Proofpoint reports 64% of European organizations targeted by precision cloud attacks showed compromise evidence. Challenge assumptions that email filtering alone keeps likelihood low for targeted account takeover.
Section 7: Set thresholds based on your Cyber Risk Appetite, not vendor benchmarks. An escalation trigger should force a decision.
Validation Steps
- Evidence check: Ensure every figure in Sections 3 and 7 traces to a named source. Remove untraceable figures.
- Control mapping check: Verify each Section 6 control has an owner, test method, and recent test result. Score controls without evidence as not operating.
- Test the detection path: Run a tabletop or red-team exercise simulating session hijacking and mailbox rule creation. Confirm alerts fire and triage meets targets.
- Appetite alignment: Have the risk owner and CISO confirm in writing that the residual rating matches the Cyber Risk Appetite statement. If it exceeds appetite, an Approved Exception or funded treatment plan must exist.
- Regulatory mapping review: Ensure compliance confirms each linked Regulatory Obligation maps to at least one control in Section 6.
- Review cadence: Schedule reassessment regularly and after any account takeover incident. Annual reviews alone are too slow given rapid threat changes.
Keep the completed record, test evidence, and sign-offs in your GRC Platform so Audit Fieldwork can trace the risk from threat statement to tested control without reconstruction.





