Subscribe to the Non-Human & AI Identity Journal

Notifications
Clear all

Email trust abuse and alert sprawl: what IAM teams need to act on


(@nhi-mgmt-group)
Member Moderator
Joined: 1 year ago
Posts: 9016
Topic starter  

TL;DR: Attackers are compromising supplier accounts, abusing real collaboration links, and exploiting overlapping email tools to hide malicious messages until invoices, credentials, or tokens are stolen, according to Abnormal AI. The governance problem is no longer just detection quality, but whether identity and incident workflows can keep pace with trust abuse, duplicate alerts, and DORA-driven response deadlines.

NHIMG editorial — based on content published by Abnormal AI: Key Insights on 2025 email security trends

By the numbers:

Questions worth separating out

Q: How should security teams reduce business email compromise from trusted supplier accounts?

A: Security teams should baseline supplier communication patterns, including reply timing, billing cycles, and account-change behaviour, so deviations can be challenged before payment is approved.

Q: Why do collaboration-platform phishing lures bypass traditional email gateways?

A: They bypass gateways because the link often points to a legitimate cloud service, even though the content behind it is malicious.

Q: What do email security teams get wrong about duplicate alerts?

A: They often treat duplicate alerts as a sign of better coverage, when they actually create correlation debt and slow containment.

Practitioner guidance

  • Baseline supplier behaviour for payment-change requests Track normal reply timing, thread continuity, time zone patterns, and banking-detail changes for supplier accounts.
  • Treat collaboration links as identity events Detonate external Teams or Google Drive invitations in sandboxing workflows and warn users when a message arrives from a new tenant, multiple recipients, or outside business hours.
  • Consolidate overlapping email controls Inventory every control that modifies, inspects, or archives email, then keep the layer with the highest fidelity and retire redundant filters that create duplicate alerts.

What's in the full article

Abnormal AI's full research covers the operational detail this post intentionally leaves for the source:

  • Behaviour-based analytics examples for spotting supplier account abuse before invoice diversion.
  • Detection logic for collaboration-link phishing that looks beyond the URL and into session behaviour.
  • Operational guidance for reducing duplicate email alerts and simplifying SOC triage.
  • DORA-oriented investigation workflow detail for evidence collection and regulator notice preparation.

👉 Read Abnormal AI's analysis of 2025 email security trends and BEC risk →

Email trust abuse and alert sprawl: what IAM teams need to act on?

Explore further

View Full Forum →  |  NHI Foundation Course →



   
Quote
(@mr-nhi)
Member Moderator
Joined: 2 months ago
Posts: 8472
 

Email security has become an identity trust problem, not just a content-filtering problem. The article shows that the most dangerous messages often come from valid accounts, valid platforms, and valid workflows. That combination breaks the old assumption that legitimacy of transport or brand implies legitimacy of intent. Practitioners should treat supplier mail, collaboration invites, and payment-change requests as governed identity events, not just inbox content.

A few things that frame the scale:

  • 88.5% of organisations acknowledge that their non-human IAM practices lag behind or are merely on par with their human identity and access management efforts, according to The 2024 Non-Human Identity Security Report.
  • 59.8% of organisations see value in a solution that simplifies non-human access management and introduces dynamic ephemeral credentials.

A question worth separating out:

Q: Who is accountable when email-driven fraud or delayed incident reporting occurs?

A: Accountability sits across security operations, identity governance, and compliance because the failure is both operational and evidentiary. If the programme cannot produce a complete incident timeline quickly enough for a DORA-style deadline, the issue is not just investigation speed. It is an evidence management failure that leadership must own.

👉 Read our full editorial: Email security in 2025 is collapsing under trust abuse and alert sprawl



   
ReplyQuote
Share: