Enterprise-ready SIEM, SOAR and Compliance powered by real-time correlation and threat intelligence.
Repo utmstack/UTMStack, read from GitHub 1 min ago. utmstack has not joined Take My Repo.
This release improves the accuracy of statistics and resolves an installation issue.
Full Changelog: v12.0.2...v12.0.3
UTMStack v11.4.0 focuses on more reliable dashboards, stronger incident response controls, and important security and stability fixes.
What's New
Improved
Fixed
Full Changelog: v11.3.0...v11.4.0
This release fixes an update issue for macOS users.
Full Changelog: v11.3.0...v11.3.1
UTMStack v12.0.2 includes fixes that improve login reliability and correct the AWS integration experience.
Improved
Fixed
Full Changelog: v12.0.1...v12.0.2
This release improves installation and update reliability, especially on Debian and Ubuntu systems.
Fixed
Full Changelog: v12.0.0...v12.0.1
v11.3.0 is a reliability and data-model release. The headline change is a rename of the raw-event storage field (log → event) with a new utm.* namespace for charting, plus a set of fixes for disk protection, installer memory handling, and the alert/compliance UI. Upgrading does not reindex existing data, but customer-created filters, rules, and dashboards that use the old log.* bag must be updated (see Breaking).
log.* event bag must be migrated to event.* (or utm.* for charts). UTMStack v11.3.0 renames the raw per-vendor event bag from log to event. Every filter, rule, and dashboard shipped by UTMStack was migrated for you, and the Log Explorer / Alerts search UI still accepts legacy log.* filter values. Customer-created content is not migrated, and it stops working against new data:
where / afterEvents / groupBy expressions referencing log.* no longer match any new event.log.* sources) or write to (log.* targets) the old bag name no longer see the data.log.* fields return empty on new indices.log.<field> → event.<field>. For aggregations and charts, event.* is not aggregatable (it is stored as a flat field), so use the utm.* namespace or the promoted standard fields (action, severity, deviceTime, origin.*, target.*, tenantId), which are unchanged. Old pre-upgrade data keeps the log bag and is retained per its index lifecycle.utm.* aggregatable field namespace for charts. Raw per-vendor fields moved to event.*; promoted, aggregatable fields live under utm.* (e.g. utm.action, utm.severity).log.* → event.* in the schema. New events store under event; old events keep log and are read with a dual-read pass, so no reindex and no data loss. Custom dashboards or saved filters that hard-code log.* paths must be updated to event.* (see upgrade notes below).threatwinds.com in a new tab instead of embedding galaxy.threatwinds.com in an iframe./utmstack/updates/memory-allocation.json is now the single authority for per-service memory. Normal updates never re-balance it. Use utmstack_installer --recalculate-memory to recompute and rewrite it. Fresh installs seed the file once.delete state, so on fresh or high-volume installs it deleted nothing and the disk could still reach 100% and tip OpenSearch into flood-stage. Alerts, statistics, and system indices are never auto-deleted.EXECUTING the moment they're dispatched, so the scheduler can't re-select them, and any EXECUTING row left over from a backend restart is reset to PENDING once at boot.assetGroupId/assetGroupName from new alerts. Note and alias now use dedicated field-scoped endpoints that touch only that column./data/alert/view without ?alertType=... never triggered the initial search. Now it loads, defaulting to the Alerts view (Status column, status tabs, Datasource Group filter) exactly like the menu link.IS_ONE_OF filters with invalid (non-list) values, which the backend rejected with a 500; every later search on the page failed until a reload. Composite columns are now offered unchecked by default and every emitted value is normalized to a valid list; the backend additionally returns a 400 (not 500) for structurally invalid filters.v11-statistics-* with a tokenized match on dataType, so firewall-sonicwall matched firewall-pfsense and similar, and read only a single 10-minute document's count. It now reads exact dataType.keyword for all of the module's data types, sums count over the last 24 h, resets to 0 when empty, and stops picking an arbitrary data type for multi-filter modules.memory-allocation.json was missing/corrupt, overwriting the operator's distribution. A normal update now refuses to deploy a non-authoritative distribution instead of guessing; the file is written only on fresh install (one-time seed) or explicit --recalculate-memory.MaxRAMPercentage=75 so it stops OOMing on Log Explorer with large result sets. Run utmstack_installer --recalculate-memory on existing installs to apply.printPage at 16 GB hosts.technique field was blank and the backend rejects blank techniques on sync. Each is populated now; they load on boot.origin.ip.keyword, which doesn't exist on new (typed ip) indices, and the nginx CSP blocked the tile hosts. Maps now bucket on origin.ip (with a .keyword multi-field for old indices) and the CSP allows *.tile.openstreetmap.org / *.tile.thunderforest.com.22935 instead of the real port) and dataSource kept the :port suffix. The filter v3.2.0 + agent 11.1.5 decode correctly.2a00:8c40:* (Fastly) IPv6 ranges to the US centroid; new data resolves them to Madrid/Canary, eliminating a class of "impossible travel" false alarms.cel plugin's OpenSearch connection regression (silently killing every CEL-dependent rule) is fixed; text-search operators (contains, startsWith, regexMatch, …) now work on object/array fields by searching the raw JSON text.NoSuchMethodError in Spring Boot 3.1.5's YAML loader) is reverted; snakeyaml stays at 1.33.event.* sub-fields are selectable as columns and filters; the filter picker lists them; the sort control is hidden for flattened bag fields (sorting them was a 400).ORDER BY).v11-log-* indices keep their log field and are read alongside event by the backend; only new data uses event.log.* content: see Breaking above. Shipped content is migrated; customer-owned filters, rules, and dashboards using the old bag name are the operator's responsibility.docker service update --memory, that tuning is not persisted and the installer will re-apply memory-allocation.json on the next update. To make a custom distribution stick, edit /utmstack/updates/memory-allocation.json or run utmstack_installer --recalculate-memory.Full diff: v11.2.16...v11.3.0