Product logo
DocsHubBlogPricing
← Back

azure-storage v5.19.0 - Enable Encryption at Rest and table logging for storage accounts

Jul 30, 2024
•
Mods

What's new?

  • Users can now enable/disable Table logging for Storage Accounts via Azure > Storage > Storage Account > Table > Logging control. To get started, set the Azure > Storage > Storage Account > Table > Logging policy.

Control Types

  • Azure > Storage > Storage Account > Encryption at Rest
  • Azure > Storage > Storage Account > Table
  • Azure > Storage > Storage Account > Table > Logging

Policy Types

  • Azure > Storage > Storage Account > Encryption at Rest
  • Azure > Storage > Storage Account > Encryption at Rest > Customer Managed Key
  • Azure > Storage > Storage Account > Table
  • Azure > Storage > Storage Account > Table > Logging
  • Azure > Storage > Storage Account > Table > Logging > Properties
  • Azure > Storage > Storage Account > Table > Logging > Retention Days

Action Types

  • Azure > Storage > Storage Account > Update Encryption at Rest

  • Azure > Storage > Storage Account > Update Storage Account Table Logging

  • The Storage Account CMDB data will now also include information about the account's table service properties.

  • We've removed the dependency on listKeys permission for Azure > Storage Account > Container > Discovery to run its course to completion. This release includes breaking changes in the CMDB data for containers. We recommend updating your existing policy settings to refer to the updated attributes as mentioned below.

Renamed: isImmutableStorageWithVersioningEnabled to isImmutableStorageWithVersioning.enabled

Removed: preventEncryptionScopeOverride

Bug fixes

  • The Azure > Storage > Storage Account > CMDB control would go into an error state while trying to fetch default Queue and Blob properties if Guardrails did not have permission to list the storage account keys. The control will now not attempt to fetch default Queue and Blob properties if Guardrails does not have the required access for listKeys, and will run its course to completion without going into an error state.