---
title: "Audits and certificates"
description: "What is validated, what we test and how often, and what Clavitor does not hold."
lang: en
url: https://clavitor.ai/en/why
markdown: https://clavitor.ai/en/why.md
authoritative: true
translations: [de, fr, es, it, pt, nl, pl, sv, da, no, fi, uk, ru, tr, ja, ko, zh, hi, th, vi, id]
publisher: Clavitor LLC
---

# Audits and certificates: What is validated, what we test, and what we don't hold.

Three plain lists, so you can see where our claims stop.

## Validated: The encryption runs on a validated module.

Our servers, the command-line tool and the proxy use a **FIPS 140-3 validated cryptographic module** (AWS-LC, CMVP certificate #5314), in FIPS mode. The validation is the module's, not a certificate Clavitor holds. It covers data at rest and our side of every connection between Clavitor programs. In your browser, the same algorithms run without module validation. The details are on [Security](https://clavitor.ai/en/security).

## Tested: What we test, and how often.

- **Our promises are written as tests.** The key that protects your vault at rest doesn't open a credential or identity field, a failed decryption is an error and never hands back the encrypted bytes, and our encrypted channel reproduces, byte for byte, a handshake that an independent implementation wrote from our design document alone. The latest results are on [Security](https://clavitor.ai/en/security#tested), and you can [run four checks on any vault yourself](https://clavitor.ai/en/developers/agents).
- **Every week, we check the product against our written specification.** Where code and specification disagree, the specification stands and the difference is reported.
- **Each part gets adversarial reviews:** the vault, the gate, the command-line tool, the proxy and the extension. In our latest cycle, each part had at least two rounds that ended with nothing critical or high left live. Medium findings are tracked and worked down; some are still open.

We don't say "passed audit, no open critical or high findings". Nobody can promise that, and we don't know how many problems our own reviews miss.

## Not held: What we don't hold.

- **SOC 2 and ISO 27001.** We hold neither. Our controls are self-assessed against both frameworks, and your questionnaire is something we complete for you on the Enterprise plan. See [Enterprise](https://clavitor.ai/en/enterprise).
- **A FIPS certificate of our own.** We use a validated module; the module is validated, and Clavitor isn't.
- **HIPAA certification.** We don't hold one, and there is no official one to hold.
- **Our hosts' certificates.** Each hosting provider's certifications are theirs, listed with the provider on [Subprocessors](https://clavitor.ai/en/subprocessors).

## Questions about an audit or a certificate?

Write to us, and we'll answer in writing.
[security@clavitor.ai](mailto:security@clavitor.ai)
