Skip to main content
Release notes 2.0.0

Improving tuning rule recommendation interface

Updated over a week ago

BIG news: we've rolled out version 2.0.0. It's all about making your life easier with our cybersecurity tool. This isn't about reinventing the wheel; it's about greasing it to spin smoother and faster, especially when it comes to tuning recommendations.

Release Highlights:

πŸ’‘ Frontend: Dive into our new tuning interface designed through plenty of customer feedback. Enjoy more value based recommendations with features like recency, similarity, and enhanced search capabilities. Entity grouping has been revamped too, making it a breeze to distinguish between tuning rules that bring you value and do not bring value, also focusing on what is and what is "not".

🧠 Backend: We've upgraded our sorting and filtering API to handle enriched metadata for tuning suggestions more efficiently. Now, tuning suggestions update their recency and value automatically, ensuring you're always ahead of the game. Plus, we've expanded our health check capabilities with new log sources and made significant optimizations across all services for smoother operations.

πŸ› οΈ Internal: Behind the scenes, we've been busy! We've ensured database calls are optimized for better performance, and squashed bugs affecting health checks. We've also improved our Health feature by updating identifiers and adding new recommendations.

Release Notes:

πŸ—οΈ Added Functionality:

  • Enriched Metadata for Tuning Suggestions: Enhanced sorting/filtering API for more precise tuning.

  • Automatic Updates for Tuning Suggestions: Value is calculated based on recency and similarity and now update on their own, keeping you in the loop with minimal effort.

  • Expanded Health Check Log Sources: More log sources mean broader oversight and better security.

πŸ“Š Improved Features:

  • New Tuning Interface: An all-new UI focuses on ease of use and clarity, making tuning a snap.

  • Optimized Entity Grouping: Quickly identify relevant entities in incidents, thanks to improved grouping.

  • Backend and Frontend Optimization: From database calls to UI tweaks, we've made extensive improvements..

πŸ› οΈ Bug Fixes:

  • Health Data Accuracy: Fixed issues where log sources showed incorrect statuses, ensuring reliable health assessments.

  • Enhanced Health Configuration: Updated configurations to be more inclusive and accurate.

  • Streamlined Azure Log Analytics Queries: Improved data retrieval from Azure.

🐞 Known Issues:

  • While we're proud of the progress made in this version, we're always striving to do better. We recognize there are areas needing more attention, particularly around the tuning recommendation UI's user interaction. Rest assured, we're already working on these for future updates, along with a comprehensive overhaul of tuning rules to better serve your needs.

Did this answer your question?