Las actualizaciones de SignServer y EJBCA mejoran la flexibilidad de implementación y la preparación cuántica
We’re excited to announce the general availability of EJBCA 8.2 and SignServer 6.2, including updates to the software appliance, hardware appliance, and cloud editions. These releases highlight our commitment to moving the industry towards post-quantum readiness as well as providing our customers PKI and signing how and where they need it.
Estos son solo algunos aspectos destacados de las versiones:
- HSM support for post-quantum issuance and signing: Continue issuing certificates and signing artifacts in your test environments, now with Thales Luna 7 or TCT HSM, with more to come.
- Registration Authority (RA) Chaining: Want an RA inside your network to work with your EJBCA SaaS or PKI as a service deployment? Now you’ve got it.
- Automated certificate clean-up: Clear up extra database space by getting rid of expired certificates automatically based on a configurable window.
- Expanded SignServer REST API: Automate configuration and fully remote control with extended methods and endpoints for SignServer workers.
Echemos un vistazo más de cerca a las nuevas mejoras en EJBCA 8.2 y SignServer 6.2.
Soporte de HSM para la emisión y firma PQC
The requirement for post-quantum certificates and signing is only getting closer. Now is the time to prepare, not panic. The final post-quantum algorithms are still going through their final approvals, making now a perfect time to test them in your lab environments and ensure a smooth transition when deadline requirements hit.
En EJBCA 8.0 y SignServer 6.0, introdujimos soporte para la emisión y firma postcuántica, para que nuestros clientes puedan comenzar a probar su entorno de laboratorio. Ahora, hemos ido un paso más allá, permitiendo la integración con un HSM con capacidad cuántica para la generación de claves. Este es otro paso en nuestra hoja de ruta para ofrecer soluciones preparadas para la era cuántica en un mundo postcuántico.
This makes now a perfect time for you to get started if you’ve yet to look at testing post-quantum algorithms.
Flexibilidad mejorada con el encadenamiento de RA
Having a Certificate Authority (CA) or full PKI in the cloud has a ton of great benefits. But sometimes you want that extra layer of security on your enterprise network by only allowing communication to be initiated internally. For our cloud-hosted customers, if you wanted to interact with your Registration Authority (RA), you had to use API calls. Now with EJBCA 8.2 and RA Chaining, you can utilize a full RA from within your network, giving you both more functionality and security when connecting to your external services.

Limpieza automatizada de certificados
With the volume of certificates issued from your PKI, the size of your database can grow quickly. Now, you can purge your database of expired certificates that no longer need to be audited or tracked. Simply turn on clean up, specify the age you want expired certificates to be deleted after, and watch EJBCA free up your space.
API REST de SignServer ampliada
Lastly, we’ve also expanded the REST API for SignServer. Now you have even more granular remote control of your SignServer workers. The new methods can typically be used for automating SignServer setup as part of DevOps processes.
Para obtener más información sobre las versiones, consulte el portal de documentación.
Suscríbase a The Source
Stay secure with Keyfactor's monthly newsletter, packed with expert insights and practical steps for quantum-readiness.
Continuar leyendo
Nuevas capacidades de EJBCA refuerzan la seguridad de los dispositivos IoT
Leer más
Cifrado 28 veces más rápido: Intel y Bouncy Castle ofrecen cifrado Hardware
Leer más