Skip to main content

Seculyze 3.8.5 Release Notes

Seculyze 3.8.5 introduces ITSM integration, notification configuration, and incident tagging for Microsoft Sentinel, enabling more automated and flexible security operations workflows.

Overview

Seculyze 3.8.5 introduces ITSM integration, notification configuration, and incident tagging for Microsoft Sentinel, enabling more automated and flexible security operations workflows.

This release also delivers improvements to Content Hub reliability, strengthening installation and update handling, and enhances platform stability through performance and enrichment optimizations.

Release Highlights

🔔 ITSM Integration & Notification Configuration — Introduced ITSM credential setup and notification management to support automated incident workflows and routing.

🧩 Content Hub Reliability Improvements — Improved installation, update handling, retry mechanisms, and recovery behavior for Content Hub deployments.

🏷️ Incident Tagging — Added configurable incident tagging's to Microsoft Sentinel based on the incidents' attention.

Changes

🏗️ Added Functionality

  • Added configurable incident tagging's to Microsoft Sentinel based on the incidents' attention.

  • Added ITSM credential configuration and management capabilities

  • Introduced validation of existing ITSM credentials before updates

  • Added notification endpoint configuration across services

  • Added configurable notification management capabilities

📊 Improved Features

  • Improved enrichment processing performance and scalability

  • Enhanced notification delivery and processing workflows

  • Content Hub installation logic now determines install, update, or skip actions automatically

  • Enhanced threat intelligence prioritization logic for improved incident relevance

  • Enhanced label handling for observables and URL reputation workflows

🛠️ Bug Fixes

  • Fixed threat intelligence entity handling issues

  • Fixed Content Hub installation failures and improved recovery behavior

  • Fixed enrichment failures caused by null or non-iterable values

  • Fixed notification configuration and delivery issues

  • Fixed Office Activity log source handling issues

  • Fixed file hash display to prioritize SHA-256 values

  • Fixed rule tuning issues caused by malformed rule names and search terms (URL encoding fix)

Did this answer your question?