Mave Secures $34M to Unify Enterprise Security Tools Into Single Agentic AI Platform

Israeli startup Mave Security Ltd. announced a $34 million funding round to accelerate research into frontier artificial intelligence for security operations, according to SiliconANGLE. The capital supports the company’s agentic platform, which connects an enterprise’s existing security tools into a unified system for threat handling. This approach allows organizations to manage incidents from initial alert through to response without migrating data to a central repository.

By the numbers

• $34 million raised in new funding to accelerate AI research and platform development.
• More than 400% annual recurring revenue growth recorded over the past year.
• Seven-figure deals being closed as the company expands its enterprise customer base.

What the figures mean

Mave’s platform operates by querying each security tool in its native language, reconciling results into a single incident account. Chief Executive Raziel Oren stated that analysts currently investigate threats one tool at a time, manually piecing together evidence while attackers act quickly. The company argues that AI-driven attacks have outpaced traditional security information and event management systems, leaving critical context outside the central store.

What should you do?

Managed service providers and security teams should verify that any agentic AI integration respects existing access controls and operational boundaries. Review vendor documentation to understand how the platform queries native tools and handles data reconciliation. Ensure that response actions are strictly limited to pre-defined rules set by your security team to prevent unauthorized system changes during automated investigations.

Operational impact

Security leaders must assess how agentic automation alters incident response workflows and analyst responsibilities. Teams usually need to redefine escalation paths when AI handles initial triage and evidence gathering. Check whether the platform’s native tool integration requires new administrative privileges or changes to existing identity configurations. Communicate these shifts to operations staff to ensure alignment between automated actions and human oversight, maintaining accountability for every decision made during an active threat event.

Background: Incident response plans

Incident response plans fail when teams assume they cover every attack vector or treat them as static documents. You must focus on decision trees, not scripts. Plan for communication breakdowns, not just technical fixes. Regular table-top exercises reveal gaps that documentation hides.

Read the full guide: Fix Incident Response Plans That Fail Under Pressure

What to do and how to stay safe: Mave Security

• Audit current security tool configurations to ensure they support native querying by external AI agents.
• Define strict rule sets for automated response actions to limit the scope of agent capabilities.
• Monitor for false positive reductions and verify that active campaign flagging aligns with internal threat intelligence.
• Once the vendor provides an update, test integration workflows in a non-production environment before full deployment.

Step-by-step guide: Shadow AI Explained: 8 Questions Answered for Secure Operations

General security guidance from the BitShield News newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

How does Mave’s platform differ from traditional SIEM systems?

Mave queries existing security tools in their native languages without ingesting data into a central database, allowing for faster context gathering.

Who are Mave’s primary customers?

The company serves Fortune 50 companies, global managed security service providers, and regulated financial and health care environments.

What is the background of Mave’s founders?

Raziel Oren and Guy Eshel, both veterans of Unit 8200, started the company in 2025 to address slow manual security investigations.