Skip to main content
Release Notes 1.1.6

In one of the largest releases yet, Seculyze 1.1.6 introduces new functionality and improves existing ones across the board.

Updated over 10 months ago

With version 1.1.6, we're focusing on streamlining interactions and ensure consistent functionality across Seculyze components. With many new elements and components, and improvements based on your feedback, it's our ambition that user of 1.1.6 can feel the difference.

Patch highlights include direct access to Incident status from Tuning Rules, a new button for actions in your Incident view and a new improved look across all our tables - and so much more. Lets dive in.

πŸ—οΈ Added functionality:

  • A new button can now be found in the Action column in the Alerts table, displaying all action and providing a direct link to Sentinel

  • Introduced functionality to refresh current page by clicking sidebar.

  • Added new field in the Tuning Rule Popup's Response field for improved guidance.

  • Added Skeleton loaders in Tables and Banners to avoid misrepresentation of data while keeping elements from "jumping around".

  • Mapped Alert Rules in Log Sources can now be copied to clipboard with a single click.

  • "Copy" hover feature and updated feedback style for Alerts table Entity Chips.

  • Renamed the Tuning Rule confirm button.

  • Multiple ❓-symbols can now be found across Seculyze, leading to in-depth knowledge articles.

  • New tooltips when hovering elements can now be found in multiple places.

πŸ“Š Improved features:

  • Enhanced search in Alerts table to cover entity columns, enabling thorough data searches.

  • Updated SIEM Health Score-component style for visual consistency.

  • Standardized "+X more" chip behavior for consistent display across tables.

  • Standardized Attention and Action columns across all tables.

  • Made search bars sticky in main and minor tables for ease of access during navigation.

  • Renamed and adjusted Sentinel Severity Sorting Box colors for consistent severity representation.

  • Improved option panel in the Tuning Rule popup

  • Switched left/right of Tuning Rule popup details

  • Recolored multiple column data in Incident Table to not be as prominent.

  • Reduced transparency of tooltip background to increase readability

πŸ“¦ Removed: - until further notice

  • The "estimated savings" data from Log Source Spending Banner will not be displayed until the data is reliable established

  • Seculyze Statboard is temporarily disabled due to insufficient data

πŸ› οΈ Bug fixes:

  • πŸ”§ Fixed navigation issue in the New Top Incident Component; "View All" now respects the selected timespan.

  • πŸ”§ Corrected Value Change Component to display negative values in orange, aligning with our color coding.

  • πŸ”§ Adjusted Log Source Table column widths to allow for user interaction.

  • πŸ”§ Addressed pagination issues across all tables.

  • πŸ”§ Fixed multiple bugs pertaining Tuning Rules, including rounding errors and incorrectly tagging incidents.

  • πŸ”§ Alerts do not show as duplicates any more.

  • πŸ”§ Fixed an issue where Incidents sometimes didn't update properly.

🐞 Known issues: - what we're bringing with us to the next release

  • We're aware of an issue causing clicks to go through even when the user just highlights text in tables.

  • We're working on letting the users run a Sentinel query from our Tuning Rule popup, allowing thorough review on demand.

  • Tuning Rule Rework is in full motion. Our next release addresses multiple issues and alters the workflow of Tuning Rules.

Did this answer your question?