Mistral has launched a public preview of Mistral Large 4 and says it will release the model's weights on 27 October. The French company is positioning the system as a European open-weight alternative for coding, agentic workflows, multimodal tasks and specialised enterprise work.

Mistral says Large 4 contains 1.05 trillion total parameters, with 49 billion active at a time, and supports a one-million-token context window. It was trained on the company's European infrastructure using 3,800 Nvidia Grace Blackwell GPUs. The training data covered more than 160 languages, including every official language of the European Union, according to the company.

Before the weights are released, cybersecurity partners and state authorities are being given access to a version with reduced moderation and expanded cyber capability. Mistral claims the model leads several open-weight systems on internal and external tests, including cybersecurity tasks. Those performance statements remain vendor claims and will require independent replication across real enterprise workloads.

The combination of open weights and strong cyber capability raises both strategic and governance questions. Self-deployment can improve sovereignty, continuity and policy control, but it also transfers more safety, monitoring and access-management responsibility to the operator. Regulated buyers should evaluate deployment autonomy alongside model-risk documentation, red-team results and the controls surrounding higher-risk capabilities.

Execution Level Governance- What audit-ready agent governance actually looks like
David Girvin, founder and CEO of Assury argues that model-in-the-loop review, AI governing AI, is fundamentally unreliable for regulated environments: even the best-performing models miss a meaningful share of violations, the reviewing model is typically provided by the same vendor being reviewed, and prompt injection or context poisoning can compromise both the acting agent and its supposed overseer simultaneously. He makes the case for deterministic, architecturally enforced controls instead, walking through Assury’s approach of autonomy zones, session risk accumulation, and credential starvation, which lets a compromised agent be cut off from its tools instantly rather than relying on time-boxed access. The conversation touches on why David is sceptical of just-in-time credentialing as a solution for agent security more broadly, since agent sessions don’t run on predictable human timescales, along with the current gap between how identity and security vendors are pitching agent protection and what he sees happening at the execution layer in practice. He also discusses the compliance and audit implications of probabilistic decision-making, arguing that regulated industries will increasingly need tamper-evident, hash-chained audit trails that can withstand scrutiny from auditors and regulators who are only beginning to understand agentic risk, and reflects on a named frontier lab’s own published framework as an example of the gap between research and practitioner reality. Elsewhere, David reflects candidly on building a bootstrapped security company in an increasingly crowded market, why he turned down aggressive VC funding to stay in control of the product, and what a credible third-party assessment of his own gateway would need to look like given that Assury sits directly in the execution path for every customer’s agents.
BrightTALK
Share this post
The link has been copied!