Skip to content

Releases: utmstack/UTMStack

v10.5.20-202502241617

24 Feb 14:22
417c480

Choose a tag to compare

UTMStack 10.5.20 Release Notes

This release incorporates several enhancements and bug fixes. Here is a list of featured changes:

  • The IP geolocation component has been corrected to reliably distinguish between public and private IP addresses.
  • Agent communication protocols have been updated to use current TLS versions and configurations.
  • New features include the implementation of enhanced compliance reporting, featuring updated standards, sections, dashboards, and visualizations.
  • Agent IP address management has also been improved.

v10.5.19-202502062035

06 Feb 18:35
c46d9e2

Choose a tag to compare

UTMStack Version 10.5.19 Release Notes

Bug Fixes

  • Resolved an issue where log field data in the table didn't align with applied filters.
  • Corrected a problem where time filter updates were not correctly reflected in the filter string.
  • Addressed an issue where index pattern modifications did not update the browser URL.
  • Fixed container memory resource allocation.
  • Resolved an empty column status issue in CSV exports.

New Features

  • Limited the time filter to a maximum range of 30 days.
  • Mandated the timestamp field and introduced a summary view for selections lacking fields.
  • Relocated the "Add Filter" button to the left and enhanced the filter UI with improved icons.
  • Removed redundant header space to improve table visibility.
  • Added "contains one of" and "does not contain one of" operators to filter options.

v10.5.18-202412161725

16 Dec 15:25
92870ec

Choose a tag to compare

UTMStack 10.5.18 Release Notes

Bug Fixes

  • Resolved: Inability to mark as complete when observations contain French characters.
  • Resolved: Log Explorer's elastic filter incorrectly appends '/d' to time intervals.
  • Resolved: Improper handling of special characters in password query parameters.
  • Resolved: Duplicate filters in Log Explorer upon filter removal.
  • Resolved: Filtering issues with Cisco ASA and Cisco Firepower data lacking syslog dates or host information.

v10.5.17-202412022339

02 Dec 21:40
734bbef

Choose a tag to compare

UTMStack Version 10.5.17 Release Notes

Changes

  • Resolved a problem hindering incident status updates when inputting extensive solutions.
  • Corrected a problem obstructing incident creation from the Alerts dashboard.
  • Integrated the Asia/Jakarta timezone into the TIMEZONES directory.
  • Addressed an issue where timezone modifications on an instance weren't reflected when accessed via the Federation Server.
  • Resolved a display issue where the Last log was not visible for a generated alert

v10.5.16-202411201215

20 Nov 17:16
5aebb0b

Choose a tag to compare

UTMStack 10.5.16 Release Notes

Bugfix

  • False positive alerts displayed in Dashboard Overview
  • Correct query parsing for filterType conditions with special characters

v10.5.15-202411101625

11 Nov 14:25
7d4a656

Choose a tag to compare

UTMStack 10.5.15 Release Notes

Bugfix

  • Sorting not working on any column in index management view

v10.5.14-202411051556

05 Nov 13:57
fc0bb28

Choose a tag to compare

UTMStack 10.5.14 Release Notes

Bugfix

  • Remove memory usage indicator

v10.5.13-202410291952

29 Oct 17:52
6e581f1

Choose a tag to compare

UTMStack 10.5.13 Release Notes

Bugfix

  • Error on server when sorting by severity column in threat Management/Alerts view.

v10.5.12-202410221638

22 Oct 13:38
0098c87

Choose a tag to compare

UTMStack 10.5.12 Release Notes

Bugfix

  • Implemented validation checks during the user deletion process to prevent the deletion of the last admin user. This ensures that at least one admin user remains in the system, maintaining the integrity of the authentication process.

v10.5.11-202410211009

21 Oct 14:10
0b92be6

Choose a tag to compare

UTMStack 10.5.11 Release Notes

Bugfix

  • Implemented validation checks during the user deletion process to prevent the deletion of the last admin user. This ensures that at least one admin user remains in the system, maintaining the integrity of the authentication process.