Meet procurement and RFP requirements that mandate a FIPS-validated module in your company's name.
Available exclusively to Engineering and Enterprise Support customers, giving your organization its own validated FIPS certificate at no extra cost.
Procurement teams, auditors, and government buyers increasingly require a FIPS 140 certificate issued to your organization — not a third party's. Rebranding gives you a validated module under your own name, so you can answer an RFP, pass an audit, or sell into a regulated market without re-running validation yourself.
Meet procurement and RFP requirements that mandate a FIPS-validated module in your company's name.
Hand auditors a certificate listed on the NIST CMVP under your organization — clear, verifiable, official.
Reuse OpenSSL's existing validated module instead of funding and running a full FIPS validation yourself.
Engineering and Enterprise Support customers are entitled to complimentary FIPS rebranding. This service issues a validated OpenSSL FIPS Provider certificate in your organization’s name, managed exclusively in partnership with Lightship Security.
OpenSSL 3.1.2, validated under FIPS 140-3 and issued certificate #4985, is now available for rebranding. This validation remains active until 10 March 2030, ensuring long-term compliance with the latest cryptographic standards.
Organizations may also reference prior validated modules — certificates #4282 and #4811 (OpenSSL 3.0.8 / 3.0.9, FIPS 140-2, valid until 21 September 2026) — as part of OpenSSL’s ongoing record of FIPS-certified releases.
Validation and rebranding are handled by Lightship Security, an accredited cryptographic-module testing laboratory — so your certificate is issued through an official CMVP-recognized process.
A guided process, managed end-to-end with Lightship Security. You bring the organization details; we handle the validation mechanics.
Rebranding is included with Engineering and Enterprise Support. We confirm your plan and the module you need.
We map the validated OpenSSL module to your requirements and gather the details for the certificate.
Lightship manages the CMVP-recognized rebranding process against the active OpenSSL FIPS validation.
You receive a validated FIPS 140-3 certificate issued to your organization — ready for audits, RFPs, and customers.
The current module (OpenSSL 3.1.2, certificate #4985) is validated under FIPS 140-3 and remains active until 10 March 2030. Prior validated modules #4811 and #4282 (OpenSSL 3.0.8/3.0.9, FIPS 140-2, valid until 21 Sep 2026) can also be referenced.
Yes — that’s the purpose of rebranding. The certificate is issued in your organization’s name so you can deploy and sell it within your own products and regulated environments.
Lightship Security, an accredited cryptographic-module testing laboratory, manages the rebranding through the official CMVP-recognized process — backed by the OpenSSL Corporation.
Various modifications can be made during the rebranding effort to include new platforms. OpenSSL and Lightship will work with you to facilitate this.
Engineering Support includes one complimentary rebrand per year; Enterprise Support supports multiple rebrands annually — useful if you ship validated modules across several products.
FIPS rebranding is included at no extra cost with Engineering and Enterprise Support plans.