Menu
Sign your .isof files with a cryptographically verifiable identity, issued by IsoFind SAS.
Pricing
Rate adjusted to organisation size. Custom quote on request.
Request a certificateSHA-256 · local hash
The .isof file embeds a SHA-256 fingerprint computed at export. Any modification to the content is immediately detectable, without a network connection.
ECDSA P-256 · X.509 certificate
The file is signed with the laboratory's private key, bound to a certificate issued by the IsoFind Issuing CA. Any third party can verify the signer's identity without a network connection.
Each laboratory certificate is signed by the IsoFind Issuing CA and embedded in the .isof file. Verification depends on no external service.
The SHA-256 fingerprint of the canonical JSON representation is covered by the ECDSA signature. Any modification - even a single digit - invalidates the signature.
The X.509 certificate binds an ECDSA P-256 public key to the laboratory's identity, verified by IsoFind SAS prior to issuance.
The laboratory certificate traces back to the IsoFind Root CA (RSA 4096, offline). Both the Root CA and the Issuing CA are embedded in the IsoFind binary.
Full verification - chain, validity, embedded CRL, ECDSA signature - works without a network connection. Critical for air-gapped environments.
IsoFind PKI infrastructure
Top of the trust chain. Signs only the Issuing CA. Private key stored offline on an encrypted physical medium, never connected to any network.
Issues laboratory certificates. Private key on a hardware HSM. Publishes a CRL for revocation. Embedded in the IsoFind binary for offline verification.
Bound to the private key generated locally by the laboratory within IsoFind. The private key never leaves the workstation. The certificate is renewable annually.
Four guided steps. Your private key never leaves your machine.
Fill in the form below. Processing time: 2 to 5 business days.
In IsoFind, go to Certificates > New certificate. Your private key stays on your machine, encrypted with AES-256-GCM.
Send the .csr file generated by IsoFind to colin.ferrari@isofind.tech. Your private key never reaches us.
You will receive a .crt file. Import it in IsoFind via Certificates > Import. Your .isof files can now be signed at level 2.
This information is required for the identity verification necessary to issue a legally binding certificate.
After submission, you will be contacted within 2 to 5 business days to confirm your identity and guide you through generating the CSR from IsoFind.
Questions about the certification process or the IsoFind PKI? colin.ferrari@isofind.tech
All Rights Reserved by IsoFind