Subscribe to the Non-Human & AI Identity Journal

Notifications
Clear all

Phishing, account takeover, and vendor compromise: what teams need


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

TL;DR: IBM’s Cost of a Data Breach Report 2025 says phishing again leads breach entry at 16% of incidents, with average costs of $4.8 million and 254 days to detect and contain, while generative AI cuts phishing email creation from 16 hours to 5 minutes according to Abnormal AI. The lesson is that behaviour-driven detection and faster containment now matter more than static email filtering alone.

NHIMG editorial — based on content published by Abnormal AI: IBM Cost of a Data Breach Report 2025 analysis

By the numbers:

Questions worth separating out

Q: How should security teams reduce phishing risk without relying only on awareness training?

A: They should combine user training with behavioural detection, vendor verification, and tighter controls on high-risk identity actions.

Q: Why do phishing and account takeover keep driving expensive breaches?

A: Because attackers use trusted identities to bypass suspicion and then abuse the resulting access for financial fraud, data theft, or persistence.

Q: How can organisations tell whether their phishing controls are actually working?

A: Look at containment speed, identity revocation speed, and whether suspicious messages are being linked to downstream workflow abuse.

Practitioner guidance

  • Correlate mailbox behaviour with identity context Flag unusual sender patterns, travel context, payment changes, and relationship drift together so suspicious requests can be reviewed before approval or forwarding becomes a breach path.
  • Tighten controls around vendor-facing workflows Require step-up checks for payment changes, bank detail updates, and vendor contact changes, especially where a trusted mailbox could be used to impersonate a supplier.
  • Measure identity misuse containment speed Track time from first suspicious message to mailbox lockdown, token revocation, and vendor verification so response latency becomes a managed risk indicator.

What's in the full article

Abnormal AI’s full analysis covers the operational detail this post intentionally leaves for the source:

  • The IBM metric breakdown by breach type, including cost and containment comparisons across phishing, vendor compromise, and account takeover.
  • The behavioural detection logic Abnormal AI uses to distinguish normal from suspicious email patterns in cloud environments.
  • The specific implications of generative AI for personalised phishing volume, response automation, and defender workflow design.
  • The vendor’s interpretation of how email behaviour analysis fits into broader security lifecycle operations.

👉 Read Abnormal AI’s analysis of IBM’s 2025 breach findings on AI-driven phishing →

Phishing, account takeover, and vendor compromise: what teams need?

Explore further

View Full Forum →  |  NHI Foundation Course →



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

Phishing is now an identity governance problem, not just an email security problem. The IBM data shows that the real damage comes when a trusted identity channel is abused to impersonate a person, a vendor, or a routine business process. That puts IAM, PAM, and human behaviour controls in the same threat model as email security. Organisations that still treat phishing as an inbox-only issue are managing the symptom, not the governance failure.

A few things that frame the scale:

  • 72% of organisations have experienced or suspect they have experienced a breach of non-human identities, according to The 2024 ESG Report: Managing Non-Human Identities.
  • Two-thirds of enterprises have endured a successful cyberattack resulting from compromised non-human identities, with a quarter encountering multiple attacks.

A question worth separating out:

Q: Who is accountable when a phishing attack turns into vendor fraud or account takeover?

A: Accountability usually spans security, IAM, finance, and business process owners because the breach crosses identity and operational boundaries. The critical question is not only who clicked, but who owned the workflow that allowed a trusted request to become a validated action.

👉 Read our full editorial: AI-powered phishing is still driving the costliest breaches



   
ReplyQuote
Share: