- Site Collector Features
- Site Collector Features Introduced in 2024
- Site Collectors 2.4 (November 2024)
- Site Collectors 2.3 (October 2024)
- Site Collectors 2.2 (September 2024)
- Site Collectors 2.1 (August 2024)
- Site Collectors 2.0 (July 2024)
- Site Collectors 1.20.0 (June 2024)
- Site Collectors 1.19.0 (May 2024)
- Site Collectors 1.18.0 (April 2024)
- Site Collectors 1.17.0 (March 2024)
- Site Collectors 1.16.0 (February 2024)
- Site Collectors 1.15.0 (January 2024)
- Site Collector Features Introduced in 2023
- Site Collectors 1.14.0 (November 2023)
- Site Collectors 1.13.0 (October 2023)
- Site Collectors 1.12.0 (September 2023)
- Site Collectors 1.11.0 (August 2023)
- Site Collectors 1.10.0 (July 2023)
- Site Collectors 1.9.4 (June 2023)
- Site Collectors 1.8.0 (May 2023)
- Site Collectors 1.7.0 (April 2023)
- Site Collectors 1.6.0 (March 2023)
- Site Collectors 1.5.0 (January 2023)
- Site Collector Features Introduced in 2022
- Site Collector Features Introduced in 2024
- Site Collector Known Issues
- Addressed Issues in Site Collector
- Site Collector 2.4: Addressed Issues
- Site Collector 2.3: Addressed Issues
- Site Collector 2.2: Addressed Issues
- Site Collector 2.1: Addressed Issues
- Site Collector 2.0: Addressed Issues
- Site Collector 1.20: Addressed Issues
- Site Collector 1.19: Addressed Issues
- Site Collector 1.18: Addressed Issues
- Site Collector 1.17: Addressed Issues
- Site Collector 1.16: Addressed Issues
- Site Collector 1.15: Addressed Issues
- Site Collector 1.14: Addressed Issues
- Site Collector 1.13: Issues Addressed in October 2023
- Site Collector 1.11: Issues Addressed in August 2023
- Site Collector 1.9.4: Issues Addressed in June 2023
- Site Collector 1.8: Issues Addressed in May 2023
- Site Collector 1.6: Issues Addressed in March 2023
- Site Collector 1.5: Issues Addressed in January 2023
- Site Collector Issues Addressed in December 2022
- Vulnerability Remediation Policy
Addressed Issues in Site Collector
2024:
2023:
Site Collector 2.4: Addressed Issues
The Site Collectors 2.4 (November 2024) Addressed Issues section includes details about fixed issues and remediated security vulnerabilities in this release.
Site Collector 2.4: Security Vulnerabilities Remediated in November 2024
Site Collector 2.4: Security Vulnerabilities Remediated in November 2024
The Site Collectors 2.4 (November 2024) release includes remediated security vulnerabilities. For more information about Exabeam’s commitment to remediating vulnerabilities for Site Collector, see the Vulnerability Remediation Policy.
There are no open known CVEs in any container image (Nifi). Toolkit has been deprecated and is no longer in use hence no security vulnerabilities update is available for that.
The following table lists the CVEs remediated for the Nifi container and their severity.
CVEs for NiFi
Critical | High | Medium | Low |
|---|---|---|---|
Total: 0 | Total: 0 | Total: 195 | Total: 4 |
– | – |
|
|
Site Collector 2.3: Addressed Issues
The Site Collectors 2.3 (October 2024) Addressed Issues section includes details about fixed issues and remediated security vulnerabilities in this release.
Hotfixes in Site Collector 2.3 Release
The following table provides details about the hotfixes and enhancements implemented after the October 2024 release.
Release Number | Description |
|---|---|
2.3.1 | Resolved an issue that prevented deletion of Windows Event Log Collector instance via the user interface. |
2.3.2 | Resolved an issue pertaining to Windows Event Log Collector that displayed incorrect data metrics that includes volume and status details. |
Site Collector 2.3: Security Vulnerabilities Remediated in October 2024
The Site Collectors 2.3 (October 2024) release includes remediated security vulnerabilities. For more information about Exabeam’s commitment to remediating vulnerabilities for Site Collector, see the Vulnerability Remediation Policy.
There are no open known CVEs in any container image (Nifi). Toolkit has been deprecated and is no longer in use hence no security vulnerabilities update is available for that.
The following table lists the CVEs remediated for the Nifi container and their severity.
CVEs for NiFi
Critical | High | Medium | Low |
|---|---|---|---|
Total: 0 | Total: 0 | Total: 9 | Total: 1 |
– | – |
|
|
Site Collector 2.2: Addressed Issues
The Site Collectors 2.2 (September 2024) Addressed Issues section includes details about fixed issues and remediated security vulnerabilities in this release.
Site Collector 2.2: Addressed Issues
The following table provides details about the issues fixed during or after the September 2024 release.
Release Number and Issue ID | Description |
|---|---|
NGSCL-3674 | Fixed an issue in which the Windows Event Log agent collector pulled duplicate logs when historic log fetch is enabled, after upgrading the collector to it’s latest version. |
Hotfixes in Site Collector 2.2 Release
The following table provides details about the hotfixes and enhancements implemented after the September 2024 release.
Release Number | Description |
|---|---|
2.2.1 | Enhanced the monitoring functionality for the Splunk collector to increase reliability. Additionally, resolved Splunk collector specific issue that caused data processing interruptions. |
2.2.2 | Resolved issues pertaining to operations such as start and stop, performed on Site Collector. |
2.2.3 | Resolved issues pertaining to operations such as start and stop, performed on Site Collector. |
2.2.4 | Resolved an issue with paths containing regular expression characters for the File collector. |
Site Collector 2.2: Security Vulnerabilities Remediated in September 2024
The Site Collectors 2.2 (September 2024) release includes remediated security vulnerabilities. For more information about Exabeam’s commitment to remediating vulnerabilities for Site Collector, see the Vulnerability Remediation Policy.
There are no open known CVEs in any container image (Nifi). Toolkit has been deprecated and is no longer in use hence no security vulnerabilities update is available for that.
The following table lists the CVEs remediated for the Nifi container and their severity.
CVEs for NiFi
Critical | High | Medium | Low |
|---|---|---|---|
Total: 0 | Total: 1 | Total: 117 | Total: 1 |
– | CVE-2024-27398 – |
|
|
Site Collector 2.1: Addressed Issues
The Site Collectors 2.1 (August 2024) Addressed Issues section includes details about fixed issues and remediated security vulnerabilities in this release.
Site Collector 2.1: Addressed Issues
The following table provides details about the issues fixed after the August 2024 release.
Release Number and Issue ID | Description |
|---|---|
NGSCL-3696 | Fixed an issue in which the Splunk Fetch Timestamp value and the collector name for a Splunk collector instance could not be updated and the associated logs could not be searched by the Search functionality. |
Hotfixes in Site Collector 2.1 Release
The following table provides details about the hotfixes and enhancements implemented after the August 2024 release.
Release Number | Description |
|---|---|
2.1.1 | 0.5.1 – Fixed an issue which caused disruption in docker compose installation. |
2.1.2 | 0.5.1 – Fixed an issue that caused timestamp failure. |
2.1.3 | 0.5.1 – Fixed an issue in which the Windows Event Log Collector caused a heartbeat error for the Site Collector instance. |
2.1.3 | 0.5.2 – Updated the precheck log to check and resolve docker compose v2 installation errors. |
2.1.3 | 0.5.3 – Fixed an issue that caused docker compose v2 installation errors. |
Site Collector 2.1: Security Vulnerabilities Remediated in August 2024
The Site Collectors 2.1 (August 2024) release includes remediated security vulnerabilities. For more information about Exabeam’s commitment to remediating vulnerabilities for Site Collector, see the Vulnerability Remediation Policy.
There are no open known CVEs in any container image (Nifi and toolkit) and no CVEs are found for NiFi as of the day release image was built.
The following tables list the CVEs by container and severity:
CVEs for Toolkit
Critical | High | Medium | Low |
|---|---|---|---|
Total: 0 | Total: 0 | Total: 3 | Total: 5 |
– | – |
|
|
Site Collector 2.0: Addressed Issues
The Site Collectors 2.0 (July 2024) Addressed Issues section includes details about hotfixes and remediated security vulnerabilities in this release.
Hotfixes in Site Collector 2.0 Release
The following table provides details about the hotfixes and enhancements implemented after the July 2024 release.
Release Number | Description |
|---|---|
2.0.1 | 0.4.9 – Enhanced the versioning system for NiFi custom libraries. |
2.0.1 | 0.4.8 – Fixed issues that caused Site Collector installation failure when custom installation path is specified. |
2.0.1 | 0.4.7 – Set backward compatibility by populating default extraction path. |
2.0.1 | 0.4.6 – Increased the timeout duration for downloading Site Collector configuration files. |
2.0.1 | 0.4.5 – Migrated the bash script to Go for retrieving certificate expiration details. |
2.0.1 | 0.4.4 – Added debugging details to identify upgrade issues related to cert script. |
2.0.1 | 0.4.3 – Fixed an issue for support packages functionality for fetching specific NiFi API information. |
2.0.0 | Hotfix for Windows Event Log Collector, Windows File Collector, Windows Archive Collector, Linux File Collector, and Linux Archive Collector – Enhanced management functionality to operate independently without the minifi-c2 server dependency. |
Site Collector 2.0: Security Vulnerabilities Remediated in July 2024
The Site Collectors 2.0 (July 2024) release includes remediated security vulnerabilities. For more information about Exabeam’s commitment to remediating vulnerabilities for Site Collector, see the Vulnerability Remediation Policy.
The following tables list the CVEs by container and severity:
CVEs for NiFi
Critical | High | Medium | Low |
|---|---|---|---|
Total: 1 | Total: 8 | Total: 155 | Total: 2 |
CVE-2016-1000027 |
|
|
|
CVEs for Toolkit
Critical | High | Medium | Low |
|---|---|---|---|
Total: 0 | Total: 0 | Total: 10 | Total: 1 |
– | – |
| CVE-2024-2511 – |
Note
MiNiFi has been deprecated and is no longer in use hence no security vulnerabilities update is available for that.
Site Collector 1.20: Addressed Issues
The Site Collectors 1.20.0 (June 2024) addressed issues section includes details about hotfixes and enhancements, and remediated security vulnerabilities in this release.
Hotfixes in Site Collector 1.20 Release
The following table provides details about the hotfixes and enhancements implemented after the June 2024 release.
Release Number | Description |
|---|---|
1.20.0 | Ngsccli version 0.3.1 – Resolved issues related to the upgrade process to ensure retention and implementation of necessary configurations during the upgrade process. |
1.20.0 | Ngsccli version 0.3.2 – Included detailed debugging information for identifying and recording missing property values during the upgrade process. |
1.20.0 | Ngsccli version 0.3.3 – Elaborated the debugging information for resolving the issue of missing NiFi property values after the upgrade process. Added additional logging to capture and identify missing property values during the upgrade process. |
1.20.0 | Ngsccli version 0.3.4 – Removed the self-extract directory in the /tmp folder that gets created during the upgrade process to prevent potential conflicts with existing files. |
1.20.0 | Ngsccli version 0.3.5 – Set backward compatibility in case of absence of the extract and install paths. |
1.20.0 | Ngsccli version 0.3.6 – Removed the debugging information that was added in patch 0.3.2 after resolving the associated issue to streamline the codebase and eliminate redundant logging. |
1.20.0 | Ngsccli version 0.3.7 – Enhanced the pre-check to support IPv6 loopback in /etc/hosts. |
1.20.0 | Ngsccli version 0.3.8 – Increased the download timeout interval to accommodate networks with slower download speeds and ensure successful completion of downloads in environments with higher latency. |
1.20.0 | Ngsccli version 0.3.9 – Optimized performance of Ngsccli to ensure stability, seamless and reliable state changes, and prevention of potential race conditions. |
1.20.0 | Ngsccli version 0.3.10 – Enhanced the pre-check to support IPv6 loopback in /etc/hosts. |
1.20.0 | Ngsccli version 0.3.11 – Set backward compatibility by populating default extract and install paths. |
Site Collector 1.20: Security Vulnerabilities Remediated in June 2024
The Site Collectors 1.20.0 (June 2024) release includes remediated security vulnerabilities. For more information about Exabeam’s commitment to remediating vulnerabilities for Site Collector, see the Vulnerability Remediation Policy.
The following tables list the CVEs by container and severity:
CVEs for NiFi
Critical | High | Medium | Low |
|---|---|---|---|
Total: 0 | Total: 4 | Total: 142 | Total: 7 |
|
|
|
CVEs for MiniFi
Critical | High | Medium | Low |
|---|---|---|---|
Total: 0 | Total: 0 | Total: 4 | Total: 0 |
|
CVEs for Toolkit
Critical | High | Medium | Low |
|---|---|---|---|
Total: 0 | Total: 0 | Total: 4 | Total: 0 |
– | – |
| – |
Site Collector 1.19: Addressed Issues
Release Number | Description |
|---|---|
1.19.4 | Fixed minor issues pertaining to File collector configuration attributes. |
1.19.3 | Fixed an issue related to Windows File Collector GCS filename for ECP bucket support. |
1.19.2 | Enhanced security certificates for Linux File Collector, and Linux Archive Collector for optimized data integrity, authentication, and encryption. |
1.19.1 | Updated security certificates for Windows Event Log Collector, and Windows File Collector for optimized data integrity, authentication, and encryption. |
1.19 | Following are the hotfixes for Windows File Collector.
Following are the hotfixes for Linux File Collector.
Hotfix for Linux Archive Collector: 1.1.0 – Updated version of the collectors for General Availability (GA) release. Hotfix for Windows Event Log Collector: 1.1.0 – Updated version of the collectors for General Availability (GA) release. |
Site Collector 1.18: Addressed Issues
Release Number | Description |
|---|---|
1.18.3 | Fixed issues related to collector updates at collector level. |
1.18.2 | Fixed issues pertaining to installation of prechecks binary file. |
1.18.1 | Enhanced the precheck feature to support multiple operating systems. |
Site Collector 1.17: Addressed Issues
Release Number | Description |
|---|---|
1.17.2 | Improved monitoring at collector level to optimize performance with multiple collector instances. |
1.17.1 | Enhanced and extended monitoring capabilities for Site Collector to support a wider range of collectors. |
Site Collector 1.16: Addressed Issues
Release Number | Description |
|---|---|
1.16.2 | Updated some minor prechecks. |
1.16.1 | Fixed a communication failure with service related issue at collector level. |
Site Collector 1.15: Addressed Issues
Release Number and Issue ID | Description |
|---|---|
1.15 | Following are the hotfixes for Windows Event Log Collector.
Hotfix for Windows Archive Collector and Windows File Collector – 0.1.0 – Resolved the version mismatch issue for agent management functionality that enables management operations such as add, update, and stop, and the collector service that enables log collection. |
1.15.4 | Fixed an issue in which Site Collector upgrade failed if the IP address of the VM host on which Site Collector is being installed did not match the IP address you entered while installing a Site Collector instance via the user interface. The installation precheck script verifies the IP address and prevents installation and upgrade failure. |
1.15.3 | Enhanced performance of Splunk collector that now lets you update the fetch interval in Splunk collector without resetting the data fetch clock for the next data pull. |
1.15.2 | Fixed an issue in which a collector instance could not be renamed via collector configuration page while editing configuration for a collector instance. |
1.15.1 – NGSCL-2620 | Enhanced configuration for the Syslog receiver of Site Collectors service to handle UDP packets and eliminate UDP packet drops within Syslog. |
1.15.1 | Fixed an issue in which a Site Collector instance did not apply changes that you initiated via user interface such as start, stop, delete, and update. |
Site Collector 1.14: Addressed Issues
Release Number and Issue ID | Description |
|---|---|
1.14.1 – NGSCL-2560 | Fixed an issue in which memory leak was observed for the Fortinet Collector after running the collector for more than eight hours. |
1.14 | 0.0.1 – Initial release of Windows Archive Collector, Linux File Collector, Linux Archive Collector, and Windows File Collector. |
Site Collector 1.13: Issues Addressed in October 2023
Release Number and Issue ID | Description |
|---|---|
1.13.5 | Installation optimization. |
1.13.4 | Installation optimization. |
1.13.3 – NGSCL-2414 | Fixed an issue in which Site Collector displayed connectivity and certificate errors. |
1.13.2 – NGSCL-2443 | Updated the precheck script to remove the ports 9090, 9100 and 9092 for Prometheus that are no longer required. |
1.13.1 | Updated the precheck script to check available space for the /tmp folder. |
Site Collector 1.11: Issues Addressed in August 2023
Issue ID | Description |
|---|---|
NGSCL-1305 | Fixed an issue in which Splunk collector stopped working intermittently and showed the |
NGSCL-1802 | Fixed an issue in which the Windows Event Log Collector instance collected very few logs affecting the log volume because of incorrect template configuration. |
NGSCL-1821 | Fixed an issue in which deleting a Windows Active Directory Collector instance caused an error 'Stop Failed'. |
NGSCL-2029 | Fixed an issue in which installation of a Windows Event Log Collector instance by running PowerShell script failed. Windows Defender was treating Windows Event Log Collector installer as a virus or malware. |
Site Collector 1.9.4: Issues Addressed in June 2023
Issue ID | Description |
|---|---|
NGSCL-1435 | Fixed an issue in which upon searching for specific keywords from the collector name, for Site Collector instances, the search results do not display the associated collectors. Site Collectors now support partial keyword search and display all the relevant instances for partial keywords that you may search for. |
NGSCL-1610 | Fixed an issue in which the Syslog Collector installed on Site Collector version 1.9, shows performance degradation with maximum 7k EPS on the VMs with CPU frequency lower than 2.4GHz. |
NGSCL-1678 | Fixed issues for Syslog Collector instances that run on User Datagram Protocol (UDP), for the collector to work appropriately with up to 5K EPS rate without any data loss. |
Site Collector 1.8: Issues Addressed in May 2023
Issue ID | Description |
|---|---|
NGSCL-1205 | Fixed an issue in which the Syslog Collector instance stopped working and displayed |
NGSCL-1424 | Fixed an issue in which the Syslog Collector displayed the Run Failed error continually for the region US-East1, because of large message frame size. |
NGSCL-1510 | Fixed an issue in which after deleting a stopped collector instance, the collector instance appears disabled on the Collectors app. |
Site Collector 1.6: Issues Addressed in March 2023
Issue ID | Description |
|---|---|
NGSCL-1164 | Fixed an issue in the service file configuration, in which Site Collector upgrade process did not delete daemon on RH8/9 with SElinux versions earlier than 1.5.3. |
Site Collector 1.5: Issues Addressed in January 2023
Issue ID | Description |
|---|---|
NGSCL-992 | Fixed an issue associated with CVE-2022-42889 vulnerability by updating the configuration. |
NGSCL-1059 | Implemented a scheduler to move Site Collector instances with 'Installation_Error' status to 'DELETED' status after 24 hours of installation failure. |
Site Collector Issues Addressed in December 2022
Issue ID | Description |
|---|---|
NGSCL-747 | Fixed an issue in which the Last Day Volume/Count column on the user interface displayed inconsistent volume for the ingested data. |
NGSCL-1030 | Fixed an issue in which regardless of the uninterrupted log flow, the Last Day Volume/Count column on the user interface displayed the status ‘0MB’ after Site Collector installation. |
NGSCL-1057 | Fixed an issue in which the Collector list showed no aggregated data on the user interface. |
NGSCL-1065 | Updated the formula to calculate the trend for the ingested data. The Trend column on the Site Collectors user interface now displays the accurate count for the ingested data. |