Join our Newsletter — 33% off our NHI Course
Home› Guides› Email & Communications Security Executive Briefing: What Boards…
Executive Briefing Email & Communications Security

Email & Communications Security Executive Briefing: What Boards Should Ask and Fund

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 13 min read
On this page

Email, chat and phone remain the cheapest way for a criminal to reach money, data and administrator access, and most boards still treat them as an IT hygiene topic rather than a business risk. This briefing is for board members, chief executives and the executives who answer to them for fraud, technology and operational risk. It explains why communications channels drive so many losses, what the mailbox providers and regulators now expect, how attacks have moved from the inbox to collaboration tools, text messages and help desk calls, and the questions that show whether management has the risk under control. It stays at board level: the technical controls are in the Email Security Guide and the staged capability detail in the Email Security Maturity Model.

The risk in one paragraph

Every organisation exposes its email addresses, chat tenants and phone numbers to the world by design, so communications channels are where attackers make first contact. Three things go wrong. Staff are persuaded to hand over credentials, approve a sign-in or pay a fake invoice. Criminals impersonate the organisation's own domains to defraud customers and suppliers. And once one mailbox or chat account is taken, it becomes a trusted platform for the next fraud, because messages now come from a real colleague. Filtering technology helps but never removes the risk; what limits the damage is authentication that cannot be phished, domains that cannot be spoofed, payment processes that do not trust a message on its own, and the ability to see and shut down a compromised account quickly. The board's role is to treat payment fraud and account takeover through communications as an enterprise risk with an owner, a budget and measures, not as a training exercise.

Why this is a board-level issue now

  • The losses are large and reported: the FBI Internet Crime Complaint Center's 2025 report records 24,768 business email compromise complaints with losses of about $3.05 billion, and phishing and spoofing as the largest complaint category at 191,561 complaints. Total reported losses across all crime types were about $20.9 billion. Reported figures understate the real total, because many victims never report.
  • It is the most common attack organisations see: the UK government's Cyber Security Breaches Survey 2025 found 43% of businesses and 30% of charities reported a breach or attack in the previous 12 months, and phishing was involved for 85% of those businesses and 86% of those charities.
  • The mailbox providers now enforce authentication: since February 2024 Google requires anyone sending more than 5,000 messages a day to Gmail addresses to authenticate their mail strongly and offer one-click unsubscribe, with Yahoo backing the same direction. Since 5 May 2025 Microsoft rejects mail from high-volume senders to Outlook.com, Hotmail and Live addresses that fails SPF, DKIM and a published DMARC record. Poor domain hygiene now costs revenue as well as security, because marketing and transactional mail stops arriving.
  • The standard itself has moved: the IETF published DMARC as a Standards Track specification, RFC 9989, in May 2026, replacing the earlier informational RFC 7489. See the DMARCbis Changes Guide.
  • Attackers have left the inbox: Verizon's 2026 Data Breach Investigations Report page states that attacks targeting mobile devices now see click rates about 40% higher than traditional email. Text messages, collaboration chat and phone calls to the help desk sit outside most email filters and most training.
  • Directors are expected to oversee cyber risk: the same 2025 survey found only 27% of UK businesses had a board member or trustee with explicit responsibility for cyber security, down from 30% in 2024, against 66% of large businesses. See the UK Cyber Governance Code of Practice Guide.

Four ways communications become losses

Most incidents fall into one of four patterns. Each needs a different owner and a different control, which is why a single "email security" budget line often leaves gaps.

PatternWhat happensBusiness impactControl that limits itNatural owner
Payment and invoice fraud (BEC)A real or spoofed supplier or executive asks for a payment or a change of bank detailsDirect, often unrecoverable financial lossOut-of-band verification of payee changes and urgent payments; dual approvalChief financial officer
Credential and session theftA link leads to a fake sign-in page that relays passwords and one-time codes in real timeMailbox and cloud account takeover, data theft, a launch point for ransomwarePhishing-resistant MFA (passkeys, FIDO2 security keys) and device-bound sessionsChief information security officer
Brand and domain impersonationCriminals send mail that appears to come from your domain or a look-alike to customers and suppliersCustomer fraud, reputational harm, mail delivery failuresDMARC at enforcement on every domain, look-alike domain monitoringChief marketing or digital officer with security
Collaboration, SMS and voice social engineeringA fake IT support message in chat, a text message or a call persuades staff or the help desk to reset accessAdministrator takeover across identity and cloud systemsStrict caller verification, restricted external chat, no MFA reset on a phone call aloneChief information officer and service desk lead

The fraud side is covered in depth in the Deepfake and Payment Fraud Executive Briefing; this briefing focuses on the channels and accounts that make the fraud possible.

What the board should understand about the controls

  • Filtering is necessary but probabilistic: secure email gateways and cloud-integrated email security catch most malicious mail, but a small share always arrives, and messages from a genuinely compromised supplier pass every technical check. Budget for detection and response as well as prevention. See the ICES vs Secure Email Gateway.
  • Domain authentication protects others from you: SPF, DKIM and DMARC stop criminals sending mail that passes as your exact domain. The NCSC advises protecting all domains, including those used with cloud mail providers, with a DMARC policy telling receivers to discard untrusted mail. It does not stop look-alike domains or mail from a hijacked real account. See the DMARC, SPF and DKIM Guide.
  • The authentication method decides whether phishing works: codes sent by text or app can be relayed by a phishing kit in seconds. Passkeys and security keys are bound to the genuine site, so a fake page cannot use them. See the Phishing-Resistant MFA Guide and the AiTM Phishing Guide.
  • Training reduces clicks, process stops payments: a payment rule that requires a call-back to a known number defeats a perfect forgery; a training score does not. See the Human Risk and Security Culture Executive Briefing.
  • Collaboration tools need the same governance as email: external chat federation, guest access and file sharing are open doors unless restricted. See the External Collaboration and Federation Abuse Guide and the Email Bombing and Help Desk Impersonation over Teams Guide.

Where identity fits

Mailboxes are increasingly reached by software, not people. OAuth applications, connectors, automation accounts and now AI agents hold permissions to read and send mail, and these non-human identities rarely have MFA, owners or reviews. In the Microsoft Midnight Blizzard breach, a password spray against a legacy test account without MFA led to a forgotten OAuth application with elevated access; the attacker then granted its own applications the right to read mailboxes, including those of senior leadership. Email delivery services add another layer: their API keys can send mail as your domain if leaked. Directors should ask that every application with mailbox or send permissions has an owner, a justification and a review date. See the Consent Phishing and Illicit OAuth Grants Guide, the SendGrid, Mailgun and Mailchimp API Keys Security Guide and AI Agent Email Access Security.

Five questions for the board to ask

  1. Can a single convincing message move our money? Show us the rule for new payees, bank detail changes and urgent executive requests, how it is enforced in the payment system, and the exceptions granted in the last quarter.
  2. Can a phishing page take over our most important accounts? What share of staff, administrators and executives use phishing-resistant MFA, and which systems still accept a text or app code?
  3. Can anyone send email that passes as our domain? How many of our registered domains, including parked and non-sending ones, have DMARC at quarantine or reject, and are we meeting the Google and Microsoft sender requirements?
  4. How quickly would we notice and contain a compromised mailbox or chat account? When did we last test it, how long did it take to revoke sessions and remove malicious inbox rules and app grants, and who decides to notify customers?
  5. Which software can read or send our email? How many applications and service accounts hold mailbox permissions, who owns them, and when were they last reviewed?

Red flags in management answers

  • "Our filter blocks 99.9% of threats": a filtering rate says nothing about the mail that arrives or about compromised suppliers.
  • DMARC "in place" at p=none for years: monitoring mode reports on abuse but does not stop it.
  • Click rates as the only human metric: no measure of reporting speed or of payment verification compliance.
  • MFA "everywhere" that means text codes: coverage figures that do not distinguish phishing-resistant methods.
  • Help desk resets on a phone call: no verification step that a voice clone or a well-briefed caller cannot pass.
  • No inventory of mailbox-connected apps: nobody can say which third-party or internal applications can read executive email.

What good looks like

  • An approved email and communications security standard covering mail, chat, SMS and voice channels, with named owners. See the Email Security Policy Template.
  • Every registered domain inventoried, with DMARC at enforcement, sending sources documented and reports monitored.
  • Phishing-resistant MFA for administrators, executives, finance and help desk staff first, then everyone.
  • Payment controls that require independent verification of bank detail changes and dual approval above a threshold, embedded in the finance system rather than in a policy document. See the Business Email Compromise Awareness for Finance Teams Guide.
  • External chat, guest access and file sharing restricted to approved partners. See the Collaboration Tool Security Guide.
  • A one-click reporting button, a team that triages reports quickly and a tested response plan for a compromised mailbox. See the Business Email Compromise Response Playbook.
  • Owned, reviewed OAuth applications and service accounts with mailbox access, and user consent to new apps restricted.

Where to invest first

  1. Payment verification: the cheapest control with the most direct loss reduction; change the finance process before buying technology.
  2. Phishing-resistant MFA for high-value roles: administrators, executives, finance and the service desk, because their accounts unlock the most.
  3. Domain enforcement: move every domain to DMARC quarantine or reject, and lock down domains that never send mail.
  4. Help desk and chat hardening: a verification procedure for resets and restricted external federation.
  5. Detection and response: alerts on new inbox forwarding rules, unusual app consents and impossible travel, with a rehearsed playbook.

Metrics to track

MetricWhat it tells the board
Percentage of registered domains with DMARC at quarantine or rejectHow exposed customers and suppliers are to impersonation of the organisation
Percentage of privileged, executive and finance users on phishing-resistant MFAWhether credential phishing can take over the accounts that matter most
Median time from first user report to removal of a malicious message from all mailboxesWhether the reporting and response loop works
Payment change requests verified out of band, and attempted frauds stoppedWhether the finance control is followed and is catching attempts
Mailbox-connected applications with a named owner and review in the last 12 monthsNon-human access to email under governance
Time to contain a compromised account in the last exerciseReadiness to limit an incident

Where this sits in the frameworks

FrameworkReferenceWhat the board should see
NIST CSF 2.0PR.AA-03Users and services authenticated, with phishing-resistant methods for high-risk access
NIST CSF 2.0PR.AT-01Awareness that covers email, chat, SMS and voice social engineering
NIST CSF 2.0PR.DS-02Data in transit protected, including mail transport encryption
NIST SP 800-53 Rev. 5SI-8 Spam Protection, SI-3 Malicious Code ProtectionFiltering at entry points and on endpoints
NIST SP 800-53 Rev. 5AT-2(3) Social Engineering and MiningTraining on recognising and reporting social engineering
CIS Controls v8.1Control 9 Email and Web Browser ProtectionsDMARC, filtering and attachment controls. See the CIS Control 9 Email and Web Browser Protections Guide

A 90-day plan

  1. Days 1 to 30: name an owner for each of the four patterns; management reports the domain inventory and DMARC status, MFA coverage by method for high-value roles, and the current payment verification rule and exceptions.
  2. Days 31 to 60: enforce out-of-band verification for payee changes; roll phishing-resistant MFA to administrators, executives, finance and the help desk; restrict external chat federation and user consent to new mailbox apps; move the main sending domains to quarantine.
  3. Days 61 to 90: run an exercise simulating a compromised executive mailbox and a fraudulent supplier bank change; review all applications with mailbox permissions; the board receives the first metrics pack and a plan to reach reject on every domain. See the Board Cyber Risk Reporting Guide.

Common failure patterns

  • Security owns email, finance owns payments, nobody owns the fraud: the control that would stop the loss sits in a different department from the team measured on the attack.
  • Code-based MFA treated as the finish line: in the Twilio breach, text messages posing as IT led staff to look-alike sign-in pages that relayed one-time codes in real time; Twilio moved staff to FIDO2 security keys afterwards.
  • Legacy and test accounts forgotten: old tenants, shared mailboxes and test accounts escape MFA and monitoring policies applied to live users.
  • Parked domains left open: domains that never send mail have no DMARC record and are used for impersonation.
  • Chat treated as internal and safe: external federation lets anyone message staff as "IT support", outside the email filter and outside training.

Practitioner checklist

  • Inventory all registered domains and sending sources; publish SPF, DKIM and DMARC for every one.
  • Move DMARC to quarantine then reject, and monitor aggregate reports.
  • Confirm bulk and transactional mail meets the Google and Microsoft sender requirements.
  • Enforce phishing-resistant MFA for administrators, executives, finance and help desk staff.
  • Embed out-of-band verification and dual approval for payee changes in the finance system.
  • Restrict external chat federation, guest access and user consent to mailbox applications.
  • Alert on new forwarding rules, unusual app consents and risky sign-ins to mailboxes.
  • Review all applications and service accounts with mailbox permissions at least annually.
  • Rehearse compromised mailbox and fraudulent payment scenarios with finance and communications teams.

Standards and references

How NHI Mgmt Group can help

We provide independent identity and non-human identity risk assessments and board briefings, including how OAuth applications, service accounts, email delivery API keys and AI agents with mailbox access are governed. Our NHI Foundation Level Training Course helps security and IAM teams govern service accounts, API keys and secrets. Contact us to arrange a briefing.

Related NHI Mgmt Group resources: Email Security Guide · Email Security Maturity Model · Email Threat Statistics · Deepfake and Payment Fraud Executive Briefing

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 14 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.