Skip to content

Releases: utmstack/UTMStack

v10.5.19-202502062035

Choose a tag to compare

@c3s4rfred c3s4rfred released this 06 Feb 18:35
c46d9e2

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

Choose a tag to compare

@c3s4rfred c3s4rfred released this 16 Dec 15:25
92870ec

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

Choose a tag to compare

@c3s4rfred c3s4rfred released this 02 Dec 21:40
734bbef

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

Choose a tag to compare

@Kbayero Kbayero released this 20 Nov 17:16
5aebb0b

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

Choose a tag to compare

@c3s4rfred c3s4rfred released this 11 Nov 14:25
7d4a656

UTMStack 10.5.15 Release Notes

Bugfix

  • Sorting not working on any column in index management view

v10.5.14-202411051556

Choose a tag to compare

@c3s4rfred c3s4rfred released this 05 Nov 13:57
fc0bb28

UTMStack 10.5.14 Release Notes

Bugfix

  • Remove memory usage indicator

v10.5.13-202410291952

Choose a tag to compare

@c3s4rfred c3s4rfred released this 29 Oct 17:52
6e581f1

UTMStack 10.5.13 Release Notes

Bugfix

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

v10.5.12-202410221638

Choose a tag to compare

@c3s4rfred c3s4rfred released this 22 Oct 13:38
0098c87

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

Choose a tag to compare

@Kbayero Kbayero released this 21 Oct 14:10
0b92be6

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.

v10.5.10-202410101810

Choose a tag to compare

@c3s4rfred c3s4rfred released this 10 Oct 15:10
d8b7904

UTMStack 10.5.10 Release Notes

Bugfix

  • Improved timezone handling for Data Source -> Last Input and Log Explorer views
  • Implemented a check to assign 'UNKNOWN' as the default key for buckets with empty keys to ensure data consistency.