January 2026

Prev Next

New Features

  • Riskflow chats can now be permanently deleted, with a confirmation prompt that clearly indicates the action is irreversible.

  • Riskflow can now answer questions directly from policy documentation, such as compliance ownership, calculation methods, and supported frameworks, making it easier to understand and act on compliance requirements.

Feature Enhancements

  • Alert generation logic is updated to better handle intermittent errors.

  • The entity feed tables are enhanced to improve historical data accuracy and queryability, including support for class-level identification and more consistent updates across feed versions and management status.

  • The multi-environment feed description is updated with improved line breaks to enhance readability.

  • Performance of the Cyber Vulnerability data table is improved, resulting in faster and more efficient query execution.

  • Advanced Queries now enforce user-level query limits to improve stability and overall query performance.

  • The source displayed for remediation actions is updated to show schema.table.

  • Workflow pages now load faster and more reliably due to optimizations that reduce unnecessary processing in the UI.

  • The Riskflow table export action is moved into a standardized location and streamlined.

  • Performance of the workflows table is improved, significantly reducing load times for workflow listings and related views.

  • The OCSF schema is updated to improve support for distinguishing between person and account users.

  • API ingest feeds that encounter rate-limit errors no longer display error alerts in the UI.

  • Owner Discovery returns unique device–employee associations, eliminating duplicates and providing clearer, more accurate results.

  • Riskflow’s Schema Explainer now leverages all available schemas when responding to a question.

Bug Fixes

  • An issue where API error alerts were not automatically closed in the DataBee Alerts UI after resolution is fixed.

  • An issue where ServiceNow CMDB CI events failed with Error 5404 (API_NotFoundError) due to a missing resource is fixed.

  • An issue where high ingestion latency was observed for a Splunk SOAR data feed is fixed.

  • An issue where duplicate records were created in the device feed table for the same device, feed, and class combination is fixed, ensuring a single record per unique key.

  • An issue where the total bytes ingested displayed as zero on the data page, despite ingestion metrics being available for individual data sources, is fixed.

  • An issue where the Cyber Vulnerability data displayed incorrect first seen and last seen timestamps is fixed.

  • An issue where column display names in the Application Devices view were unclear and caused confusion during searches is fixed.

  • An issue where organizational hierarchy data contained missing or incomplete management levels for some employees is fixed.

  • An issue where the Integrations page failed to load due to a service connectivity error is fixed.

  • An issue where configuration settings prevented forms from being submitted when optional fields were set to None is fixed.

  • An issue where tab navigation on the tenant user page followed an incorrect field order is fixed.

  • An issue where emails sent from Salesforce lost table formatting and spacing when displayed in the Customer Support Portal is fixed.

  • An issue where the Save button remained disabled after updating data lake settings is fixed.

  • An issue where the Workflow Listing page status column did not reflect the actual workflow status and always displayed an incorrect value is fixed.

  • An issue where increment buttons were incorrectly displayed in the UI search time picker is fixed.

  • An issue where navigating back after clearing file import errors caused a rendering failure in Collections is fixed.

  • An issue where certain records could not be properly closed due to incomplete field reassignment is fixed, improving accuracy when resolving duplicate entries.

  • An issue where user entity merges failed due to a missing column error is fixed.

  • An issue preventing the creation of person-account entities in Entity Management is fixed.

  • An issue causing raw data to appear in both unmapped and top-level fields, resulting in duplicate storage, is fixed.

  • An issue causing Qualys Vulnerability Management feed events to fail validation and appear in unprocessed events is fixed.

Deprecation

  • Support for the legacy api_ingest type is deprecated following the completion of migration to api_ingest_v2.

  • The non-embedded reports and dashboards experience is deprecated.

  • Fields from OCSF version 1.4 are deprecated.