Ejbca Enterprise Vs Open Source Ca
Ejbca Enterprise Vs Open Source Ca
In this eBook, you will learn how open source benefits all EJBCA users, what the differences
are between EJBCA Community and Enterprise, when to choose EJBCA Enterprise, and how
to upgrade from EJBCA Community to EJBCA Enterprise.
Cybersecurity is not a competition, it is a community-driven effort to defend against data breaches, hacks
and identity theft. Keyfactor envisions an Internet that is safe for everyone – where every transaction
between users, machines, devices, and applications is trusted and secure. Trust is built on openness and
transparency, and at Keyfactor, we’ve built open-source solutions to establish digital trust everywhere.
However, if you’re looking for an enterprise-grade PKI, EJBCA Enterprise is the better choice, offering
more advanced features and functionality, such as:
• Secure segmentation of PKI components, keeping CA, registration authority (RA), and valida-
tion authority (VA) on separate instances
• Enterprise security features, such as signed audit logs, tools to import and export configura-
tions and OAuth authentication
• Compliance with security regulations, such as Common Criteria, eIDAS (electronic IDentifi-
cation, Authentication and trust Services), or ICAO (International Civil Aviation Organization)
9303
• A trusted security partner with extensive experience and solid expertise in PKI and
cryptography
• Flexible deployment, such as cloud solutions and on-premises software and hardware
appliances
• Use cases that require Enterprise PKI, for example issuing certificates to ePassports, securing
mobile networks, and enabling DevSecOps
With EJBCA Enterprise, customers can securely segment the PKI components, keeping the RA and VA on
separate instances in the DMZ while communicating with the CA over mutually authenticated TLS. This
secure segmentation is implemented with the help of the peer systems protocol in EJBCA Enterprise.
Component segmentation also enables secure hybrid deployments, for example with the RA and VA in
the cloud and CA on-premises, as well as VA and RA redundancy for high availability settings.
Redundancy is needed for any PKI with high availability requirements over different geographical regions,
or a sizeable scale of certificate and validation requests, to ensure that the failure of a single instance
does not result in downtime. Redundancy for VAs and RAs is usually achieved using multiple standalone
instances with the help of the peer systems protocol. For CAs, redundancy is mainly achieved using
database clustering.
EJBCA Enterprise has for the past two decades been proven in large-scale production environments
within IoT, enterprises, and government organizations.
EJBCA Architecture
Distributed Roles
Example EJBCA architecture with secure segmentation of CA, RA and VA over TLS
Signed and integrity-protected audit logs that are available with EJBCA Enterprise ensure that log entries
can’t be edited or removed to hide signs of wrongdoing.
The EJBCA ConfigDump tool provided with EJBCA Enterprise allows you to export and import config-
urations, to facilitate mass deployments. The export is useful for auditing purposes and to compare
configuration changes made in EJBCA. With the import functionality, you can easily import a complete
configuration, to make sure that all your instances have the same settings, while minimizing the risk of
human errors.
EJBCA Enterprise also comes with OAuth authentication, allowing for seamless integration into existing
company identities and “one identity” policies. OAuth authentication can be used alongside or instead
of client certificate authentication and provides a powerful tool for managing all users of a PKI from
one single source.
Keyfactor has numerous Webtrust/ETSI and eIDAS audited installations, and our internal processes
are ISO 9001, 14001, and 27001 certified. Our PKI solutions help customers issue ePassports and eIDs
in compliance with the ICAO 9303 and Extended Access Control (EAC) specifications, as well as stay
compliant with standards and regulations such as NIS2, CSfC, FIPS, PSD2, CAB Forum, and GDPR.
Enterprise customers benefit from a trusted security partner with a long history in PKI and cybersecurity.
Our professional services team guides users through every step of the implementation process, from
installation to configuration, testing and production deployment of your PKI system.
With our expertise in PKI and cryptography, you can be sure that as technology advances, we help you
stay up to date with the latest protocols and algorithms – and stay crypto-agile.
Flexible deployment
To account for the unique business challenges of your organization, including security, budget and the
availability of internal resources, EJBCA Enterprise offers a combination of deployment options to suit
your needs today and allow you to grow flexibly over time.
With EJBCA Enterprise, the PKI deployment can be adapted to your organization and use case instead
of the other way around. An EJBCA PKI can be deployed as a turn-key software or hardware appliance,
on AWS or Azure cloud, or as a SaaS-delivered PKI. And if you need a combination of on-premises and
cloud, we can help you set up a hybrid solution.
In enterprise IT environments, the Microsoft Intune and auto-enrollment support in EJBCA Enterprise
allows you to overcome the limitations of the Active Directory Certificate Services (ADCS) PKI and still
seamlessly integrate into your Microsoft infrastructure. A single instance of EJBCA can provide PKI services
to all your Microsoft servers, workstations, and mobile devices, as well as non-Microsoft infrastructure
and integration with DevOps toolchains.
With EJBCA Enterprise, mobile operators can securely manage their LTE/4G mobile networks using
3GPP-compliant PKI, using CMPv2 with multiple vendor CAs and vendor certificate authentication.
Advanced HSM support (e.g. EdDSA, AWS CloudHSM, AWS KMS) No Yes
Security features
Component separation with peer connectors, for example to have RA or VA on a separate instance No Yes
Database integrity protection — wards against database tampering via signing database tables by row No Yes
Pre-issuance key validation — allows the CA to refuse to sign known weak keys or detect policy violations
No Yes
before issuance
Use cases
Microsoft Auto-enrollment support for managing Microsoft servers and devices No Yes
EST No Yes
ACME No Yes
For more details, see EJBCA Interoperability and Certifications in our online documentation.
Contact Us