Keyfactor
Keyfactor offers a portfolio covering managing protected keys, certificates or signing operations. The entries in this catalog include EJBCA, Keyfactor Command and SignServer. EJBCA focuses on public key infrastructure and certificate issuance. Keyfactor Command focuses on certificate inventory and lifecycle management. SignServer focuses on digital signing services and signing policy. When reviewing Keyfactor, compare the named products individually: a platform family, a specific module and a managed service can have different scopes and purchasing requirements. Selection should account for key ownership, certificate discovery, integration requirements and recovery procedures for critical trust infrastructure. Portfolio detail - EJBCA: the catalog lists Certificate lifecycle management, Certificate discovery, Cryptographic key protection. - Keyfactor Command: the catalog lists Certificate inventory governance, Certificate lifecycle management, Certificate discovery. - SignServer: the catalog lists Centralized signing services, Certificate lifecycle management, Certificate discovery. For procurement, map each required capability to a named offering and confirm the edition, dependencies and delivery responsibility with the vendor. Product-level entries below provide the operational context and evaluation questions for that comparison.
Documented Software Products (3)
EJBCA
EJBCA from Keyfactor focuses on public key infrastructure and certificate issuance. It is cryptographic key or certificate technology used for managing protected keys, certificates or signing operations. Capabilities - Certificate lifecycle management: Coordinates certificate discovery, issuance, renewal or retirement within the documented management scope. - Certificate discovery: Builds visibility into certificates or cryptographic assets before lifecycle policies are applied. - Cryptographic key protection: Provides the documented protections for keys used in cryptographic operations. - Public key infrastructure services: Supports certificate issuance and trust infrastructure within the vendor's product scope. - Code signing workflows: Supports signing software or artifacts using the product's documented key access and policy model. - Certificate automation: Helps reduce repetitive certificate handling through the automation mechanisms described by the vendor. Use and operational context EJBCA is a certificate-authority and PKI entry. Assess issuance policy, administrator permissions and integration with relying applications, alongside the operational procedures needed to protect trust infrastructure and maintain certificates throughout their lifecycle. Deployment and evaluation Deployment: Cloud service / SaaS; Self-managed / on-premises option documented by the vendor. Before adoption, review key ownership, certificate discovery, integration requirements and recovery procedures for critical trust infrastructure. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? EJBCA focuses on managing protected keys, certificates or signing operations. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Keyfactor Command
Keyfactor Command from Keyfactor focuses on certificate inventory and lifecycle management. It is cryptographic key or certificate technology used for managing protected keys, certificates or signing operations. Capabilities - Certificate inventory governance: Brings certificate discovery and lifecycle information into a centrally administered inventory. - Certificate lifecycle management: Coordinates certificate discovery, issuance, renewal or retirement within the documented management scope. - Certificate discovery: Builds visibility into certificates or cryptographic assets before lifecycle policies are applied. - Cryptographic key protection: Provides the documented protections for keys used in cryptographic operations. - Public key infrastructure services: Supports certificate issuance and trust infrastructure within the vendor's product scope. - Code signing workflows: Supports signing software or artifacts using the product's documented key access and policy model. - Certificate automation: Helps reduce repetitive certificate handling through the automation mechanisms described by the vendor. - Signing policy controls: Applies controls to how signing operations or protected keys can be used. Use and operational context Keyfactor Command is relevant to teams operating cryptographic trust services when the requirement centers on managing protected keys, certificates or signing operations. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS; Self-managed / on-premises option documented by the vendor. Before adoption, review key ownership, certificate discovery, integration requirements and recovery procedures for critical trust infrastructure. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Keyfactor Command focuses on managing protected keys, certificates or signing operations. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
SignServer
SignServer from Keyfactor focuses on digital signing services and signing policy. It is cryptographic key or certificate technology used for managing protected keys, certificates or signing operations. Capabilities - Centralized signing services: Provides the documented signing-service workflow for applications or organizations that need controlled digital signing. - Certificate lifecycle management: Coordinates certificate discovery, issuance, renewal or retirement within the documented management scope. - Certificate discovery: Builds visibility into certificates or cryptographic assets before lifecycle policies are applied. - Cryptographic key protection: Provides the documented protections for keys used in cryptographic operations. - Public key infrastructure services: Supports certificate issuance and trust infrastructure within the vendor's product scope. - Code signing workflows: Supports signing software or artifacts using the product's documented key access and policy model. - Certificate automation: Helps reduce repetitive certificate handling through the automation mechanisms described by the vendor. - Signing policy controls: Applies controls to how signing operations or protected keys can be used. Use and operational context SignServer is relevant to teams operating cryptographic trust services when the requirement centers on managing protected keys, certificates or signing operations. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review key ownership, certificate discovery, integration requirements and recovery procedures for critical trust infrastructure. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? SignServer focuses on managing protected keys, certificates or signing operations. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.