A new entrant with an integration pitch

Mave emerged from stealth October 22 with $34 million in funding, including a $28 million Series A led by Red Dot Capital Partners and a previously raised $6 million seed round. The company says its agents work across existing security and IT systems to investigate threats, hunt for related activity and support response. Its stated approach gathers context from connected tools without first requiring customers to move their telemetry into another centralized database.

Claims that need a customer test

Mave says it records the queries, evidence, reasoning and actions behind findings, with security teams deciding which actions require approval. It also reports use in more than 200 security operations centers. Those are company statements, not independently measured results from Cyber Security Journal. SecurityWeek’s October 25 coverage supplied the discovery lead; the company’s own launch announcement describes the architecture and funding. The announcement establishes a new competitor and a product proposition, but does not demonstrate how reliably it handles every customer environment.

Evaluate the incomplete investigation

Our analysis is that a useful evaluation should include missing evidence. A financial-services team could replay a historical investigation with one log source deliberately unavailable in a controlled test. Does the system identify that gap, explain which conclusions remain uncertain and avoid treating an unanswered query as evidence of safety? The customer should be able to inspect the queries and underlying records without reconstructing the entire case manually. Repeat the exercise with a stale asset owner or an identity that has recently changed role. These tests would examine the claimed value of live context while exposing dependencies on data quality.

Keep authority separate from confidence

For a professional-services firm, disabling an account during a client deadline may carry consequences beyond the alert under review. A pilot should name who can authorize that action, how an approval is recorded and how the analyst can reverse an incorrect decision. An impressive explanation should not silently expand the system’s permissions. Buyers can also measure the effort needed to maintain connectors and review exceptions, alongside time saved per investigation. These are proposed acceptance criteria rather than findings about Mave’s performance. The commercial question is whether the system produces a defensible decision with less analyst effort, while preserving the organization’s control over what happens next. Funding gives the company resources to pursue that goal; customer evidence must establish whether it succeeds.

Sources & further reading

Our practical suggestions are editorial guidance. Verify applicability against current source and vendor instructions.

Suggest a correction →