Feb 18, 202525.2.18

Release Summary

InsightCloudSec is pleased to announce release version 25.2.18. This release includes a new Resources interface, Insights, and Query Filters.

Azure deprecation announcements

Azure deprecating virtual network injection for Azure Data Explorer (ADX)/Kusto clusters

Beginning February 1, 2025, Azure will restrict an event hub's system-assigned identity from entering an ADX cluster's virtual network. This means if you are currently using the Azure Least-Privileged Access feature and have deployed it using a virtual network, you will need to migrate to using managed virtual private endpoints instead. We recommend following Azure's detailed migration guide.

Azure Database for MySQL Single Server deprecation announcement

Azure announced the deprecation of Database for MySQL Single Server and retired the service on September, 16, 2024. After March 10, 2025, Azure Database for MySQL Single Server instances will no longer receive security updates or fixes. Non-responsive MySQL Single Server instances that have not migrated to another service will be deleted. Azure recommends migrating to a MySQL Flexible Server instance and will attempt to automatically migrate any non-responsive MySQL Single Server instances. For more information, review the Azure documentation: https://learn.microsoft.com/en-us/azure/mysql/migrate/whats-happening-to-mysql-single-server

To assist with identifying affected resources, InsightCloudSec has added a new Insight available with this version that will flag any MySQL Single Server instances: Azure Database Instance Single Server Migration (MySQL)

After March 10, 2025, the following Insights will be removed:

  • Database Instance without Connection Log Auditing Events (MySQL Single Server)
  • Database Instance not Enforcing Transit Encryption (MySQL Single Server)
  • Database Instance without Log Auditing Enabled (MySQL Single Server)

After March 10, 2025, the following Query Filter will be removed:

  • Database Instance Server Type

Azure Database for PostgreSQL Single Server deprecation announcement

Azure announced the deprecation of Database for PostgreSQL Single Server and retired the service on September, 16, 2024. After March 28, 2025, Azure Database for PostgreSQL Single Server instances will no longer receive security updates or fixes. Non-responsive PostgreSQL Single Server instances that have not migrated to another service will be deleted. Azure recommends migrating to a PostgreSQL Flexible Server instance and will attempt to automatically migrate any non-responsive PostgreSQL Single Server instances. For more information, review the Azure documentation: https://learn.microsoft.com/en-us/azure/postgresql/migrate/whats-happening-to-postgresql-single-server

To assist with identifying affected resources, InsightCloudSec has added a new Insight available with this version that will flag any PostgreSQL Single Server instances: Azure Database Instance Single Server Migration (PostgreSQL)

After March 28, 2025, the following Insights will be removed:

  • Database Instance Allowing Access from Cloud Resources (PostgreSQL Single Server)
  • Database Instance without Infrastructure Encryption Enabled (PostgreSQL Single Server)
  • Database Instance Not Configured to Log Connections (PostgreSQL Single Server)
  • Database Instance Not Configured to Log Disconnections (PostgreSQL Single Server)
  • Database Instance Not Configured to Throttle Connections (PostgreSQL Single Server)
  • Database Instance Log Retention Below Threshold (PostgreSQL Single Server)
  • Database Instance not Enforcing Transit Encryption (PostgreSQL - Single Server)
  • Database Instance not configured to Log Checkpoints (PostgreSQL Single Server)

After March 28, 2025, the following Query Filter will be removed:

  • Database Instance Server Type
Details for self-hosted customers

New

  • Added the following Insights:
    • Web App With Remote Debugging Enabled
    • Azure Database Instance Single Server Migration (PostgreSQL)
  • Added the following Query Filters:
    • Web App With or Without Remote Debugging Enabled
  • Added a toggle to turn on the new interface for the Resource Inventory, which includes improved usability and navigation.

Improved

  • Kubernetes services and network policies are now listed under related resources for top-level Pod resources, including Deployments and Jobs.
  • Updated the Instance Resource Agent, Instance Metadata Service, Instance Status, and Instance User Data harvesters to trigger Bot modification hookpoints on creation and deletion events.
  • To provide a consistent navigation experience and align with the Command Platform, we have moved the Settings menu to the main navigation menu.
  • Added a new remove_whitespace parameter to the resource.get_tag_value Jinja2 function so tag values can be rendered without whitespaces.

Fixed

  • Fixed an issue with the Rapid7 InsightVM health check that would report an incorrect error.
  • Fixed an issue causing the Instance Resource Agent harvester to trigger Bot delete hookpoints on parent instances.