A $36 Million Bet on AI-Driven Email Defense

Email security startup AegisAI has secured $36 million in a Series A round led by Battery Ventures, with participation from Accel and Foundation Capital. The announcement came Thursday, bringing the company’s total raised to $49 million since its founding in 2025.

The fresh capital isn’t just a milestone—it’s fuel for a specific mission. AegisAI plans to expand its lineup of autonomous detection agents, push its Vanguard agent toward general availability, and scale its enterprise go-to-market efforts. In plain terms: they’re gearing up for a serious fight against a new breed of cyber threat.

From Google’s Security Team to Email’s Front Lines

AegisAI was founded by Cy Khormaee and Ryan Luo, two veterans of Google’s security team who helped build reCAPTCHA, Safe Browsing, and Web Risk. The company emerged from stealth in September 2025 with a clear thesis: traditional email security is no match for AI-powered attacks.

Their platform is built around a network of AI agents that scrutinize incoming email for phishing, business email compromise, and other threats. Instead of relying on static rules or known-bad signatures, the system evaluates the intent and identity behind each message. It’s a fundamental shift from the blocklist-and-keyword approach that has dominated the industry for decades.

How Vanguard Investigates Threats Like a Human

The product connects to Microsoft 365 and Google Workspace through an API, requiring no changes to a customer’s MX records. That’s a deliberate choice—deployment friction is often the death of security tools, and AegisAI clearly wants to avoid that trap.

In March, the company introduced Vanguard, a companion agent that takes a more proactive approach. It investigates suspicious links and attachments by navigating to them the way a human recipient would, then compiles a threat report within minutes. This mimics the curiosity of a cautious employee—but at machine speed.

The Rise of AI Spear Phishing

AegisAI frames its work around what it calls AI spear phishing: attacks that use language models to research a target, map their professional relationships, and produce a personalized lure at a fraction of the cost such an effort once required. The economics of attack have changed, and so must the defense.

Why Human Training Isn’t Enough

Khormaee, who serves as CEO, didn’t mince words about the threat landscape. “The most immediate, catastrophic risk to your organization isn’t an AI agent hacking your firewall. It’s an AI model manipulating someone in your organization into handing over the keys,” he said.

His critique of traditional security awareness programs is pointed: “If your security program still relies on template-based phishing tests and awareness training, you are training your people to spot last year’s threat, not a capable agent crafting a novel lure just for them.” His conclusion is stark—”When the attack is AI, the defense has to be AI.”

What This Means for the Email Security Market

The funding round signals growing investor confidence in AI-native security solutions. Battery Ventures’ leadership role is notable, given the firm’s history of backing enterprise infrastructure companies. With Accel and Foundation Capital also on board, AegisAI has the backing of three heavyweight investors who clearly see a gap in the market.

The $49 million total funding gives the startup runway to compete with established players in the email security space. But the real test will be whether its AI agents can consistently catch threats that slip past traditional filters—and whether enterprises are ready to trust an AI to guard their inboxes.

For CISOs watching the space, the takeaway is clear: the email security landscape is shifting, and the next generation of tools will look very different from what came before. Whether that’s a good thing depends on how well companies like AegisAI deliver on their promises.

USB Auto-Install: The Unexpected Attack Surface

Plugging in a USB stick feels routine. You expect a quick notification and maybe a driver install. But a team of researchers just turned that mundane process into a full SYSTEM-level compromise on a fully patched Windows 11 machine.

The attack abuses Windows Plug and Play (PnP) to fetch signed vendor software for an emulated USB device. Then it chains privileged installation components to escalate straight to SYSTEM. No zero-day kernel exploits. No password cracking. Just the trust Windows places in signed drivers and its own auto-install logic.

Here’s the scary part: the same PnP path works over Remote Desktop, no physical hardware required — provided Plug and Play or low-level USB redirection is enabled.

How the Windows 11 USB Attack Chain Works

The attack starts with a malicious or emulated USB device that presents itself as legitimate hardware. Windows PnP queries the device, looks for a matching signed driver package, and downloads it from Windows Update or the vendor’s server.

That’s by design. But the researchers found a way to hijack the process mid-stream. Here’s the breakdown:

• Emulated device: The attacker crafts a USB descriptor that mimics a real peripheral, like a network adapter or printer.
• Driver fetch: Windows PnP automatically retrieves a signed vendor driver for the emulated device.
• Privileged component: The driver package includes an installer or utility that runs with elevated privileges.
• SYSTEM escalation: The attacker exploits that privileged execution to drop a payload with SYSTEM rights.

The chain is elegant because it never triggers a UAC prompt. Windows trusts its own PnP pipeline, and the vendor’s signature validates the package as safe.

Remote Desktop USB Redirection Expands the Threat

Physical access was once the limiting factor for USB attacks. The researchers removed that barrier. With Remote Desktop’s Plug and Play redirection or low-level USB redirection enabled, an attacker can trigger the same PnP path remotely.

That means a compromised RDP session — or a malicious admin on the same network — could deliver the emulated USB device virtually. The victim’s Windows 11 machine would fetch the signed driver, run the privileged installer, and hand over SYSTEM access without ever touching a physical port.

Microsoft’s response? The company says the behavior is by design, noting that the attack requires either physical access or an already-compromised RDP session. That’s cold comfort for anyone relying on USB redirection for remote work.

Why Signed Drivers Make This Hard to Stop

Vendor signatures are the crown jewel of Windows driver trust. They tell the OS, “This code is safe to run.” The researchers didn’t break that trust — they weaponized it.

By using a legitimate signed driver’s installer, the attack avoids the usual red flags. Antivirus tools see a valid signature and often skip deep inspection. The result: a stealthy privilege escalation that evades detection.

Mitigations for Windows 11 USB PnP Attacks

There’s no magic patch coming, since Microsoft views this as intended functionality. But you can reduce your exposure:

• Disable USB redirection in Remote Desktop settings unless absolutely necessary.
• Restrict PnP device installation via Group Policy to approved device classes.
• Monitor driver installation events in Event Viewer for unexpected signed driver activity.
• Use device control software to block unauthorized USB devices at the endpoint.
• Limit RDP access to trusted users and networks, and enforce strong authentication.

For most organizations, the biggest win is locking down RDP USB redirection. It’s a feature few users genuinely need, and it’s the easiest remote path to this attack.

What This Means for Windows Security

This research is another reminder that Windows’ convenience features are attack surface. Plug and Play was designed for a world where physical trust was assumed. That assumption no longer holds.

We’ve seen similar issues with Windows driver signature bypass techniques and privilege escalation via legitimate services. The pattern is consistent: attackers abuse what Windows trusts, not what it fails to secure.

For defenders, the takeaway is practical. Audit your RDP configuration. Review driver installation policies. And remember that a signed driver is not a guarantee of safety — it’s just a promise from a vendor who might not know how their installer is being abused.

The researchers’ full technical details remain limited, but the proof-of-concept is clear: Windows 11 USB auto-install is no longer just a convenience. It’s a potential backdoor.

Urgent Patch Alert for Check Point Customers

Check Point has confirmed that a critical zero-day vulnerability in its Security Management and Multi-Domain Management products is being actively exploited. The flaw, tracked as CVE-2026-16232, allows attackers to bypass authentication and seize full administrative control.

This is not a theoretical risk. Check Point states that the vulnerability has been observed in the wild, specifically hitting a limited number of customers whose management environments were exposed to the internet without IP restrictions. If your management interface is publicly reachable, you are in the crosshairs.

The Anatomy of the Authentication Bypass

The core issue is an authentication bypass that lets an unauthenticated attacker obtain an application login token. With that token in hand, they can log into the SmartConsole with administrator privileges. From there, it’s game over: they can rewrite security policies, alter configurations, and effectively neutralize your firewall defenses.

This is the kind of access that turns a perimeter security product into a liability. Organizations running Check Point Security Management should treat this as an emergency.

What’s Affected?

• Security Management: The central console for policy management.
• Multi-Domain Management: Used to manage multiple security domains from a single interface.

Both products are prime targets because they hold the keys to the entire security infrastructure.

CISA Weighs In: Federal Agencies Must Act by July 25

The Cybersecurity and Infrastructure Security Agency (CISA) has added CVE-2026-16232 to its Known Exploited Vulnerabilities catalog. This is a big deal. The KEV list is reserved for flaws that are actively being exploited, and federal agencies are now under a binding directive to patch by July 25. If you’re in the private sector, consider that your own deadline too.

This marks the third Check Point vulnerability to land on the KEV list. The previous entries include CVE-2026-50751, which was exploited as a zero-day in May, and CVE-2024-24919, which was leveraged in 2024. The pattern is clear: attackers are circling Check Point products.

More Than Just One Flaw: Two Additional CVEs Patched

Check Point’s latest security update doesn’t stop at CVE-2026-16232. The company also patched two other vulnerabilities discovered during an internal review:

• CVE-2026-62144: A critical authentication bypass and privilege escalation flaw affecting Security Management and Multi-Domain Management.
• CVE-2026-62145: A high-severity local privilege escalation issue affecting Firewall, Multi-Domain Management, and Multi-Domain Log Server products.

All three were found internally. The unsettling part is that analysis showed CVE-2026-16232 had already been exploited as a zero-day before the patch was ready.

Who’s Behind the Attacks?

Check Point hasn’t attributed the attacks to a specific group. However, the timing is notable. The Qilin ransomware gang has recently been observed targeting Check Point appliances. While there’s no confirmed link to this specific zero-day, the correlation is hard to ignore.

Ransomware groups are increasingly shifting from spraying ransomware to conducting surgical strikes. A vulnerability like this gives them exactly what they need: a silent entry point to disable security controls before deploying malware.

Immediate Steps for Security Teams

If you’re running Check Point Security Management or Multi-Domain Management, here’s what you need to do right now:

1. Patch immediately. Check Point has released updates. Don’t wait for a maintenance window; treat this as a critical incident.
2. Check for exposure. If your management interface is accessible from the internet without IP restrictions, assume compromise. Audit logs for any suspicious login activity.
3. Review IoCs. Check Point has published indicators of compromise. Use them to hunt for signs of intrusion in your environment.
4. Implement mitigations. Even if you’ve patched, restrict management access to trusted IPs only. This is a basic hygiene step that would have prevented most of these attacks.

This situation echoes other recent incidents, like the ServiceNow vulnerability exploitation seen days after disclosure. Attackers are moving faster than ever. Your patching cadence needs to keep pace.

The bottom line: This Check Point zero-day is a serious threat, but it’s manageable with swift action. Patch, audit, and lock down your management interfaces. The attackers are counting on you being slow. Don’t prove them right.