Microsoft.storage.storageaccounts.localusers.delete remediation

​

Event Information

1. The Microsoft.Storage.storageAccounts.localUsers.delete event in Azure for Azure Storage indicates that a local user account has been deleted from a storage account.
2. This event is triggered when a user account that was created specifically for accessing the storage account is removed.
3. It is important to monitor this event as it can help track any changes made to the access control of the storage account and ensure that only authorized users have access to the data.

​

Examples

1. Unauthorized deletion of local users: If security is impacted with Microsoft.Storage.storageAccounts.localUsers.delete in Azure for Azure Storage, it could potentially allow unauthorized individuals to delete local user accounts associated with the storage account. This could lead to a loss of access control and increase the risk of unauthorized access to the storage resources.
2. Data loss or corruption: Deleting local user accounts associated with Azure Storage can result in data loss or corruption if the deleted accounts had permissions or roles that were necessary for managing or accessing the storage resources. This can impact the availability and integrity of the stored data.
3. Compliance violations: Deleting local user accounts without proper authorization or documentation can lead to compliance violations, especially if the storage account is subject to specific regulatory requirements. It is important to ensure that all user account deletions are properly documented and authorized to maintain compliance with relevant standards and regulations.

​

Remediation

​

Using Console

1. Enable Storage Analytics Logging:
   • Go to the Azure portal and navigate to the Azure Storage account.
   • Select the “Monitoring” section from the left-hand menu.
   • Click on “Storage Analytics” and then select “Logging”.
   • Enable logging by toggling the switch to “On”.
   • Configure the desired retention period for the logs.
   • Save the changes.
2. Enable Storage Analytics Metrics:
   • In the same “Monitoring” section of the Azure Storage account, click on “Storage Analytics” and then select “Metrics”.
   • Enable metrics by toggling the switch to “On”.
   • Configure the desired retention period for the metrics.
   • Save the changes.
3. Enable Soft Delete for Blob Storage:
   • Navigate to the Azure Storage account and select the “Blob service” from the left-hand menu.
   • Click on “Data protection” and then select “Soft delete”.
   • Enable soft delete by toggling the switch to “On”.
   • Configure the desired retention period for the deleted blobs.
   • Save the changes.

​

Using CLI

1. Enable soft delete for Azure Blob Storage:
   • Use the following command to enable soft delete for a specific storage account:
     Copy

     Ask AI

     az storage account blob-service-properties update --account-name <storage_account_name> --enable-delete-retention true --delete-retention-days <retention_days>
     

     Replace <storage_account_name> with the name of your storage account and <retention_days> with the number of days you want to retain deleted blobs.
2. Enable logging for Azure Storage:
   • Use the following command to enable logging for a specific storage account:
     Copy

     Ask AI

     az storage logging update --account-name <storage_account_name> --log <log_settings>
     

     Replace <storage_account_name> with the name of your storage account and <log_settings> with the desired logging settings.
3. Enable firewall rules for Azure Storage:
   • Use the following command to add a firewall rule for a specific storage account:
     Copy

     Ask AI

     az storage account network-rule add --account-name <storage_account_name> --ip-address <ip_address>
     

     Replace <storage_account_name> with the name of your storage account and <ip_address> with the IP address you want to allow access to the storage account.

​

Using Python

1. Monitor and handle storage exceptions:
   • Implement exception handling in your Python code to catch and handle any storage-related exceptions that may occur.
   • Use the try-except block to catch specific exceptions like azure.core.exceptions.ResourceNotFoundError or azure.core.exceptions.ServiceRequestError.
   • Handle the exceptions appropriately, such as logging the error, retrying the operation, or taking any necessary corrective actions.
2. Implement access control and security measures:
   • Ensure that appropriate access controls are in place for your Azure Storage resources.
   • Use Azure Active Directory (Azure AD) to authenticate and authorize access to your storage accounts.
   • Implement role-based access control (RBAC) to grant specific permissions to users or groups.
   • Regularly review and update access policies to ensure least privilege access.
3. Enable logging and monitoring:
   • Enable diagnostic logging for your Azure Storage accounts to capture relevant logs and metrics.
   • Use Azure Monitor to collect and analyze the logs and metrics.
   • Set up alerts and notifications to proactively detect and respond to any storage-related issues.
   • Leverage Azure Application Insights or other monitoring tools to gain insights into the performance and health of your storage resources.