Agent vs. Agent: The New Frontline in Email Security
Email defenses have largely stayed the same for a decade: scan for something malicious and block it. That approach worked when threats lived in links and attachments. It fails when the danger is...

Email defenses have largely stayed the same for a decade: scan for something malicious and block it. That approach worked when threats lived in links and attachments. It fails when the danger is in the message's intent, and it is breaking down now that attackers are no longer human.
The evolution is clear. Phishing 1.0 was bad content - malicious links and infected attachments, which gateways handle well. Phishing 2.0 is bad intent - business email compromise and fake invoices, which rely on social engineering with no payload to scan. Phishing 3.0 is AI-powered and multi-channel: GenAI writes the lure, deepfakes carry it into voice and video, and the campaign spans email, collaboration tools, and live calls.
The economics of attack have shifted. Reconnaissance that once took an attacker hours now takes an agent seconds, allowing tailored attacks against any organization, not just high-value targets. In one widely reported case, engineering firm Arup lost about $25 million after a deepfake video call with synthetic colleagues closed a deal that started with a phishing email.
Data confirms the problem. An Osterman Research study of 128 security leaders found 88% experienced incidents undermining trust in digital communications, and 60% lack confidence in countering deepfake attacks. IRONSCALES analysis shows Microsoft 365 and Google Workspace missing hundreds of phishing messages per 100 mailboxes monthly.
The old detect-and-respond model is always a step behind. A Crogl and Ponemon study found SOCs average 4,330 alerts daily but investigate only 37%. The answer, experts say, is preemption - anticipating attacks and running defensive agents. Microsoft reports its autonomous triage agent found 6.5 times more malicious emails than manual review and saved one health network over 200 analyst hours monthly.
For practitioners, the advice is to measure post-delivery miss rates, extend threat models to voice and video, and judge automation by autonomy, not alert volume. Training should be reconnaissance-aware and personalized. Phishing 3.0 is already here, and the defenders who win will be those who put their own agents on the field.
Source: The Hackers News
Ready to Modernize Your Business?
Get your AI automation roadmap in minutes, not months.
Analyze Your Workflows →