MIND Raises $72m to Tackle AI-Driven Data Security Risk

What happened

MIND, a data security company, has raised $72 million in new funding, with the round framed around the growing urgency AI is creating for organisations to protect sensitive data. The raise, reported by FinTech Global, positions MIND to expand its platform as businesses grapple with how generative AI and large-scale data use are reshaping risk.

Details on the specific investors, valuation or planned use of funds were not disclosed in the available reporting. The core narrative is straightforward: as enterprises adopt AI more widely, the volume, velocity and sensitivity of data flowing through their systems is rising, and MIND's funding reflects investor appetite for tools that help organisations keep pace with that shift.

Why it matters

AI adoption is forcing a re-think of data security architecture. Traditional data protection tools were built for a world of structured databases and predictable access patterns; AI systems ingest, generate and move data in ways that are harder to monitor and classify. A funding round of this size signals that investors see data security-for-AI as an urgent, well-funded category rather than a niche add-on.

For leaders running digital transformation programmes, the signal is that AI rollout and data governance can no longer be sequenced separately. Deploying AI capability without an equivalent investment in visibility and control over the data it touches creates exposure that scales as fast as the AI use case itself.

By the numbers

• $72 million raised by MIND in its latest funding round.

The Renascence take

The headline framing — AI making data security "urgent" — is doing a lot of work, and it's worth being precise about what's actually urgent. It isn't AI itself; it's the pace at which AI adoption is outrunning organisations' ability to know where their sensitive data lives, who or what can touch it, and what happens when a model is trained on or exposed to it.

Most organisations treat data security as a back-office compliance function, bolted on after the AI use case is already live. That sequencing is backwards, and it's a customer-experience issue as much as a technical one: a single data exposure event erodes trust faster than any AI-driven service improvement can rebuild it. Operators serious about AI should be mapping data flows and access controls before scaling a use case, not after — treating data visibility as a design constraint on the AI roadmap rather than a cleanup task that follows it.