Ekera’s security and sovereignty
A tool that reads your information system’s dependencies must offer safeguards matching the data it handles. Ekera separates what is in place from what is planned.
Ekera’s security, up to what it analyses
A tool that reads your information system’s dependencies must offer safeguards matching the data it handles. Ekera separates what is in place from what is planned.
Large-company security, for a mid-sized company
Ekera brings a mid-sized company the security resources of a large group, shared among its customers. A tool that reads the map of your systems must itself meet the standards of a large group. Here is what is in place today, at the level of principle.
Your data
- Open-weight models served in France
- Each customer isolated at several levels, tested by cross-access attempts
- Every change is traced and can be compensated by a reverse operation
Access and writes
- Identity from your own directory; separate roles, including one dedicated to sharing
- Read-only by default; writes signed, single-use, recalculated by Ekera
- Collector with no inbound door; documents analysed in an isolated space
Development and website
- Review by a dedicated security role, independent review
- Code analysis, secrets searched across the full history, locked dependencies, licence checks, tests that replay every known bypass
- Website checked before any publication, no third party loaded
Also in place: hosting in Paris in two modes, the isolated platform, with one encryption key per customer and data made unreadable within 30 days at the end of the contract, or the dedicated instance, with its own keys and backups, destroyed at the end of the contract with an erasure certificate; fresh authentication before every write approval. Planned: external penetration test, PASSI audit, bug bounty, ISO 27001, SecNumCloud-qualified hosting. These tests cover Ekera itself: Ekera does not certify your architecture and does not replace your penetration tests; it targets them and tracks your exposure between two campaigns. Read the security documentation.
Get the security sheetSent after a first conversation.
Learning together, without confusing sharing with protection
Companies face risks that resemble each other: what one observes helps others understand the threats they meet. Ekera organises this sharing within a framework: signals validated before they are shared, to limit errors and manipulation; sharing only under the conditions each customer authorises; feedback that improves everyone’s analyses and proposed scenarios. Sharing a signal does not, on its own, guarantee that an attack is detected or blocked.
The security resources of a large group, shared among mid-sized companies
30% of our revenue is devoted to Ekera’s research, quality and security. It is a commitment on Ekera’s spending, for the benefit of every customer: it is neither a legally separate fund nor a reserve held on customers’ behalf. It mostly pays for people: R&D engineers who improve the reading of your documents, the calculation engine and the connectors; security engineers; analysts who validate the signals shared between customers. The rest funds Ekera’s tests, audits, qualified hosting and certifications.
These needs grow with Ekera: Ekera becomes a more attractive target, there are more tools to support, and operators of vital importance have stricter requirements. Every fix then benefits all customers, at no extra cost.
What is planned for Ekera’s security
- an external penetration test of Ekera by a provider;
- an audit by a PASSI-qualified provider, then regular audits and penetration tests;
- a large-scale test bench with hundreds of fictitious companies;
- a permanent bug bounty;
- ISO 27001 certification of Ekera;
- SecNumCloud-qualified hosting for operators of vital importance;
- a dedicated security team.
The tests, audits, certifications and qualified hosting listed are planned; they cover Ekera, not our customers’ architecture. With each customer’s consent and only in aggregate, from five companies, lessons learned also improve Ekera for everyone. Our R&D.
The vigilance of a very large IS, at the price of a mid-sized one
By sharing what they learn, Ekera’s customers will benefit from the vigilance of a large group without its teams. It works like a community navigation app: every driver who reports a traffic jam or a safety hazard helps all the others. At Ekera, when a customer spots an attack, an exploited flaw or an incident, the signal benefits everyone, and each receives the alerts and protections drawn from the others’ experience.
The difference that matters to a CISO: verified signals, to limit the risk of manipulation. Each signal is checked by two people at the customer, then by an Ekera analyst, and signed. It is shared only with the customer’s consent, given by a designated person, and only in aggregate, from five companies. No raw data leaves your premises. Signal analysis is funded by the shared 30% budget.
Complementary, not competing
Security plays out on three levels. AI accuracy: Ekera’s strength, tested on a bench of fictitious companies, hundreds in time, as in an AI lab. Security of the Ekera product: secure development already in place (code review by a dedicated role, automated analysis, secret scanning, verified dependencies, bypass tests, independent review), then an outside view planned and then by the shared budget: a penetration test of Ekera by a provider, a PASSI audit, ISO 27001 certification of Ekera (the roadmap). Security of your systems: Ekera does not run penetration tests and never enters your network. It reads, read-only, and computes what an attack would stop without launching it. PASSI-qualified providers remain essential, and become our partners.
Better-targeted penetration tests, and monitoring between campaigns
Ekera does not replace penetration testing: it targets it. It tells you what to test first, the attack paths and single points of failure that matter, and the estimated potential loss from an outage; you avoid paying to test what has no impact. The provider’s findings flow back into the map and the costing in euros, with the work to be done, and Ekera monitors continuously between two annual campaigns. The result: shorter or more useful penetration tests, and monitoring the rest of the year. Ekera does not certify your architecture and never tells you that you no longer need to test.
Learn more: who tests what, and Ekera with penetration testing
Request an assessment
A first 30-minute call: framing your need, the possible scope and the list of information needed for the assessment. The initial assessment starts from your documents and exports, with no direct access to your information system.
Read next
- Shared securityShared budget, shared vigilance, who tests what.
- Research and developmentA safe and verifiable architecture AI.
- Frequently asked questionsAccess to the information system, euro figures, NIS2, data, price.