Skip to main content

Send security telemetry from GravityZone to Splunk Enterprise


GravityZone provides security telemetry (also called “raw” or OS events) so that administrators can analyze it, save it, filter it, and build custom correlations using the Splunk Enterprise console.

This topic describes how you can forward such information from GravityZone to Splunk Enterprise v8. It provides the requirements and the configuration steps to enable the Bitdefender security telemetry to the SIEM.

The topic is intended for a technical audience, with knowledge of Window/Linux CLI and of security certificates.

GravityZone forwards security telemetry events to the SIEM through the Bitdefender Endpoint Security Tools (BEST) agent that is installed on the Windows endpoints. BitdefenderGravityZone only controls the activation, configuration, and validation of the event submission.

Security Telemetry architecture

BEST can send the following security telemetry event types:

  • Process (create, terminate)

  • File (create, read, modify, move, delete)

  • Registry (create, delete key; modify, delete value)

  • User (logon, logout)

  • Network connection


You can choose which types of events to send by configuring the policies in GravityZone Control Center.


For Bitdefender GravityZone:

  • The Security Telemetry option is available with the following product suites:

    • Bitdefender Cloud MSP Security with ATS and EDR add-ons

    • GravityZone Business Security Enterprise


    For GravityZone on-premises, version 6.21.1-1 or newer is needed.

  • BEST for Windows security agent, version or newer

  • GravityZone user privileges: Company Administrator or Custom user with Manage Network and Manage Company rights

For Splunk Enterprise:

  • Splunk Enterprise 8.1.3 or newer

  • Splunk user privileges: Admin account

  • Access to management console

  • Access to HTTP Event Collector (default port: 8088, but you can also use port 443)


To receive endpoint security telemetry events from GravityZone to Splunk Enterprise, you must ensure a trusted connection between the managed endpoint and Splunk. Through this channel, events are forwarded in real-time, and you can query the raw data.

For this purpose, you can use security certificates issued by a public Certificate Authority (CA), or you can use self-signed certificates. If using certificates issued by a CA for Splunk, skip to the Configure GravityZonesection in this topic. If using self-signed certificates, follow the entire configuration procedure.

Configure Splunk

You can use an existing Splunk HTTP Event Collector or create a new dedicated collector responsible for receiving the Bitdefender security telemetry data from agents.

The HTTP Event Collector must have the following configuration:

  • Sourcetype: _json

  • Index: main

  • Global Settings: enableSSL=1

Splunk configuration

By default, BEST will send the security telemetry data to Splunk HTTP Collector via port 8088.

  1. Use the following guide to generate the self-signed certificates needed to secure your Splunk installation: How to Self Sign Certificates for Splunk Enterprise.

    The output consists of the following files:

    • myServerCertificate.pem

    • myServerPrivateKey.key

    • myCACertificate.pem

  2. Concatenate all files previously obtained into a single cert file.

    Command for Windows:

    type myServerCertificate.pem myServerPrivateKey.key myCACertificate.pem > myNewServerCertificate.pem

    Command for Linux:

    cat myServerCertificate.pem myServerPrivateKey.key myCACertificate.pem > myNewServerCertificate.pem

    Once created, the contents of the myNewServerCertificate.pem file should contain, in the following order:

    • The server certificate: myServerCertificate.pem

    • The private key: myServerPrivateKey.key

    • The certificate authority public key: myCACertificate.pem

  3. Instruct Splunk to use new certificate schema:

    1. Move all the certs obtained in the above process to a new Splunk folder.

      For example: $SPLUNK_HOME/etc/auth/mycerts/

    2. Instruct Splunk about securing the HTTP collector section with the new certs by editing $SPLUNK_HOME/etc/apps/splunk_httpinput/local/inputs.conf.

      The inputs.conf file should contain the following items:

      enableSSL = 1
      serverCert = $SPLUNK_HOME/etc/auth/mycerts/myNewServerCertificate.pem
      sslPassword = password_used_when_creating_the_certificate


      You can write the password in clear when first editing inputs.conf. Splunk will automatically encode this field after you restart it.

    3. Restart Splunk from GUI.


      Alternatively, you can restart only the splunkd service: $SPLUNK_HOME/bin/splunk restart splunkd

    4. Extract myCACertificate.pem from Splunk directory ($SPLUNK_HOME/etc/auth/mycerts/) and import it into the endpoints that will submit security telemetry.

      The certificate must be converted to a format in which it can be imported by Windows endpoints in Certificates (Local computer) > Trusted Root Certification Authorities > Certificates.

    5. Verify that the imported certificate is valid:

      1. Access https://:8088/services/collector with a browser from the endpoint that already have it in their certificate store.


        If you have trouble with this link, there other variations available in the Send data to HTTP Event Collector on Splunk Cloud Platform section of this article.

      2. Click the lock icon to check the state of the certificate.

Configure GravityZone

  1. Using the token value for the new HTTP Event Collector, connect to GravityZone Control Center.

  2. Click the policy applied to the managed endpoints to edit it.

  3. Navigate to General > Security Telemetry.

  4. Select the Security Telemetry option.

  5. Under the SIEM Connection Settings section, enter the SIEM server URL and the Splunk token from the newly generated HTTP Event Collector.

    The Splunk server URL should have this format: https://:8088/services/collector

    Security Telemetry settings
  6. If using self-signed certificates, select Bypass validation of the SSL certificate on HTTP collector.

    By default, Control Center checks the server URL and validates the certificates on the server against a public CA. With self-signed certificates, Control Center will return an error and communication between Control Center and the HTTP collector will not be established unless you select this option.


    This option applies only to the communication between the HTTP collector and GravityZone console, not the endpoints.

    Control Center is responsible for policy enforcement, collector settings and event selection.

  7. Click Save.

Test the configuration

To validate the configuration:

  1. Log in to GravityZone Control Center.

  2. Go to the Network page from the left side menu.

  3. Select an endpoint that was set to send security telemetry data.

    The endpoint details page opens.

  4. Check the Security Telemetry Status section under the Protection tab. Communication status should be Established.

    Established status

The Security Telemetry events will be forwarded from the managed endpoint where BEST is installed directly to Splunk Enterprise 8. You can review and investigate alerts by searching the raw data and aggregating different fields.