We proudly announce the latest release of NXLog Enterprise Edition, version 6.1. This release adds new features to our Google Chronicle and Kafka output modules to provide more flexible configuration, introduces support for certificates with TPM-attested keys, and implements enhancements to our HTTP input module.
Read on to find out more about these new features.
More flexibility for your Google Chronicle integration
We continue to build up our Google Chronicle output module with new functionality to give you more flexibility and control over your data. You can now set the Chronicle schema dynamically for each log record based on an event field or variable. Additionally, you can now use OAuth authentication to send logs to the Chronicle Ingestion API v2. You can also use our newly updated and more accurate default unified data model (UDM) schema.
Check our Google Chronicle (om_chronicle) reference for configuration details.
Simplify your Kafka output configuration
Our Apache Kafka output module now supports setting the Kafka topic dynamically. The ability to dynamically set the topic means you’re no longer restricted to sending logs to a single Kafka topic or creating complex configurations because you can specify the topic per log record based on an event field or variable.
See the Kafka (om_kafka) reference documentation for more information.
Ensure secure log transfer with hardware-based encryption
NXLog Enterprise Edition on Windows now supports certificates with TPM-generated keys. Trusted Platform Module (TPM) chips provide tamper-resistant security functions, making it the most secure way of encrypting data. You only need to specify the CA and server certificate thumbprints in the NXLog configuration—no need for a private key file or password.
See the im_ssl module directives, for example.
Gain more visibility into your HTTP log sources
Refine your log processing when receiving data over HTTP with access to the HTTP request headers. Parse request header fields and use the data to detect web crawlers, filter and enrich your logs, or correlate events from different devices by the same user.
Find more details and examples in our HTTP(S) (im_http) reference documentation.
Streamline your configuration with unified log forwarding settings
We implemented a new OutputRequestSize directive to supersede the module-specific batch size directive for Amazon S3 (om_amazons3), Google Chronicle (om_chronicle), Google Cloud Logging (om_googlelogging), Google Cloud Pub/Sub (om_googlepubsub), and Microsoft Azure Log Ingestion (om_azuremonitor).
However, the module-specific directives remain supported for backward compatibility.
Our valued customers can access the new NXLog Enterprise Edition 6.1 directly from their account or opt for a trial version to evaluate our solution.
Find out more
You can check out all of the new features and fixes in our release notes and view our changelog for a complete list of changes. Check out our comprehensive documentation, and get in touch with us below if you need help upgrading, have a feature request, or have any other questions.
