MaelGard security

How MaelGard protects your company's data, and what comes next.

In place

  • Analysis on the device

    Requests going to AI services are analysed locally by embedded models. Traffic not going to an AI service is not decrypted.

  • Sensitive values kept out of logs

    Storage and logs only keep detection metadata. Automated tests with witness values check that they never appear there.

  • Encryption at rest

    Local storage is encrypted; its key is protected by the device TPM when available, otherwise by the operating system.

  • Tamper-evident log

    The local log is chained: edits, deletions and rollbacks are detected and reported.

  • Authenticated link to the server

    Each device enrols with its own certificate and talks to the server over mutual TLS.

  • Pseudonymisation

    Identities sent to the server can be pseudonymised; re-identification requires dual approval.

  • Limited retention

    On the device, data is kept 90 days at most and within 2 GB, values adjustable by your policy.

  • Licence verified offline

    The licence is a signed document, verified on the device and the server without calling the vendor.

Next steps

  • Independent security audit: upcoming; its findings will be published on this page.
  • Stronger protection of the agent against being stopped by a local administrator: in development.
  • Certifications: none is claimed today; this page will list those obtained.

Report a vulnerability

Think you have found a vulnerability in MaelGard or on this site? Write to contact@maelgard.fr with the subject “Security”, describing the problem and how to reproduce it.

We acknowledge your report and keep you informed of its analysis and fix. Please do not disclose the problem before it is fixed, do not access other people's data and do not degrade the service.

The /.well-known/security.txt file repeats this information.

A security question? Book a demo or write to us from the contact form.

Book a demoGet notified of the launch