EJBCA sits close to the root of trust. Its administrators can create certificate authorities, issue certificates, change profiles, and alter roles. The product documentation makes a useful distinction: an EJBCA administrator is identified by the information in the client TLS certificate used for authentication. That makes certificate issuance and role membership one connected control plane.
The roles and access rules documentation says administrators can be managed through role templates or by editing access rules in advanced mode. Access rules inherit state from the parent rule unless the rule specifies otherwise. That inheritance is convenient, but it makes a top-level allow or deny decision influential. A review should inspect the effective rule tree and each role's inherited decision.
The product also has public web and RA interfaces. The bootstrap guidance describes removing the public access token from an unneeded public interface and restricting the SuperAdmin role. Operational practice should verify whether a public access token or a broad public role remains present in the live instance, regardless of what an older installation guide recommended.
A ZoomEye measurement on 2026-11-21 at 05:41 CST used page 1, page size 1, and sub_type=all:
The title result is a candidate list, not proof of a reachable administration interface. The app query did not produce a match in this one probe. External evidence must be paired with a review of the owned CA, its listener configuration, and the certificate used to authenticate the administrator.
Inventory administrator identities first. Record the certificate subject, issuing CA, validity period, renewal method, and mapped role. Confirm that only the intended certificate authorities can issue administrator credentials. Check Extended Key Usage and the client authentication path. A certificate that is valid for a public web session is not necessarily an administrator credential.
Then review rule inheritance and privilege separation. Separate CA administration, certificate issuance, revocation, auditing, and system configuration where the organization's roles allow it. The SuperAdmin role should not be the default operating account. Keep a break-glass credential offline or in a controlled vault, and test its recovery procedure.
Audit the RA and public interfaces separately. A role that can approve requests through the RA is distinct from a role that can edit CA configuration. Test a public request path with an unauthenticated client, then test a valid RA session against a function outside its role. Confirm that the denial occurs at EJBCA rather than only at a reverse proxy.
Review certificate lifecycle as an identity process. An administrator who leaves the organization must lose the certificate, the role membership, and any token that can obtain a new certificate. A role change should invalidate or reissue credentials as appropriate. The documentation notes that role updates can be cached, so a change may not appear instantly. Build that delay into the incident response expectation.
Monitoring should capture administrator authentication, role and access-rule changes, CA creation, certificate issuance, revocation, and failed authorization. Alert on out-of-band changes to the public access token or SuperAdmin membership. Preserve enough context to distinguish an approved maintenance action from a credential compromise.
EJBCA's security value depends on a well-defined enrollment path and a role model that matches the organization's separation of duties. The client certificate is the front door. The role graph and the issuing authorities determine what passing through that door allows.