📢 Read the latest Release Notes to learn what's new on Hunters! 💡

Keyfactor EJBCA Integration

Prev Next

TL;DR

Supported data types 3rd party detection Hunters detection IOC search Search Table name Log format Collection method
Keyfactor EJBCA Audit Logs ✅ ✅ ✅ keyfactor_ejbca_audit_logs Text S3, GCP Bucket List, Azure Block Storage List

Overview

Keyfactor EJBCA is an open-source Certificate Authority (CA) / PKI platform used to issue, manage, and revoke X.509 certificates and CRLs for enterprise and device PKI use cases. EJBCA emits detailed audit logs via its Log4j-based audit device (CESeCore audit log), recording every security-relevant action in the system including administrator logins/logouts, certificate requests/issuance/revocation, CRL creation and publishing, end-entity (identity) management, crypto token activation/deactivation, and access-control decisions. These logs are critical for security operations because they provide a tamper-evident record of PKI trust operations — who issued or revoked a certificate, who authenticated to the CA, and what access control checks succeeded or failed — which is essential for detecting misuse of certificate authorities, unauthorized certificate issuance, and insider threats against the PKI. The logs are typically collected as flat files from EJBCA application servers and shipped to cloud storage (S3, GCS, Azure Blob) for ingestion. Integrating these logs with Hunters enables correlation of PKI trust events with the rest of your security telemetry.

Supported data types

Keyfactor EJBCA Audit Logs

Table name: keyfactor_ejbca_audit_logs

This data type contains the CESeCore audit log entries emitted by EJBCA's Log4j-based audit device. It covers security-relevant PKI operations such as administrator authentication, certificate issuance and revocation, CRL storage, crypto token activation/deactivation, end-entity management, and access-control decisions.

Expected format

Logs are expected in text format.

2026-10-02 09:32:45,030+0000 INFO [org.cesecore.audit.impl.log4j.Log4jDevice] (EJB default - 4) 2026-10-02 09:32:45Z;ACCESS_CONTROL;SUCCESS;ACCESSCONTROL;CORE;ServiceSession;;;;resource0=/ca/-819549949

Send data to Hunters

Hunters supports the collection of Keyfactor EJBCA logs using S3 List, S3 Notifications, GCP Bucket List, or Azure Block Storage List.

To connect Keyfactor EJBCA logs:

Connect using S3 List or S3 Notifications

  1. Route Keyfactor EJBCA logs into an AWS S3 bucket.
  2. Once logs are in S3, follow the steps in this section.

Connect using Azure Block Storage List

  1. Route Keyfactor EJBCA logs into an Azure Storage container as block blobs.
  2. Once logs are in the container, follow the steps in this section.

Connect using GCP Bucket List

  1. Route Keyfactor EJBCA logs into a Google Cloud Storage bucket.
  2. Once logs are in the bucket, follow the steps in this section.