Microsoft.sql.instancepools.delete

​

Event Information

• The Microsoft.Sql.instancePools.delete event in Azure for AzureDatabaseService refers to the deletion of an instance pool in the Azure SQL Database service.
• This event indicates that an administrator or user has initiated the deletion of an instance pool, which is a resource that allows for the management and scaling of multiple databases within a single pool.
• The event signifies the removal of the instance pool and all associated databases, including any data and configurations stored within them.

​

Examples

1. Unauthorized deletion: If security is impacted with Microsoft.Sql.instancePools.delete in Azure for AzureDatabaseService, it could potentially allow unauthorized individuals to delete instance pools. This could lead to the loss of critical data and disrupt the availability of databases hosted within those instance pools.
2. Data exposure: In some cases, the deletion of instance pools may not immediately remove all associated data. If security is impacted, it could result in the exposure of sensitive information stored within the instance pools, even after they have been deleted. This could lead to data breaches and compromise the confidentiality of the data.
3. Access control bypass: If security is impacted, it may allow unauthorized users to bypass access controls and delete instance pools that they should not have permissions to modify. This could result in unauthorized changes to the database infrastructure and potentially disrupt the availability and integrity of the databases hosted within those instance pools.

​

Remediation

​

Using Console

1. Enable auditing for Azure SQL Database:
   • Go to the Azure portal and navigate to the Azure SQL Database service.
   • Select the specific database you want to enable auditing for.
   • In the left-hand menu, under the Security section, click on “Auditing”.
   • Click on “Enable” to enable auditing for the database.
   • Configure the desired audit settings, such as storage account, retention period, and events to audit.
   • Click on “Save” to apply the changes.
2. Enable encryption for Azure Storage:
   • Go to the Azure portal and navigate to the Azure Storage account.
   • Select the specific storage account you want to enable encryption for.
   • In the left-hand menu, under the Settings section, click on “Encryption”.
   • Enable the “Encryption at rest” option.
   • Choose the desired encryption type, such as Microsoft-managed keys or customer-managed keys.
   • Click on “Save” to apply the changes.
3. Enable logging and monitoring for Azure Virtual Machines:
   • Go to the Azure portal and navigate to the Azure Virtual Machine.
   • Select the specific virtual machine you want to enable logging and monitoring for.
   • In the left-hand menu, under the Monitoring section, click on “Diagnostic settings”.
   • Click on “Add diagnostic setting” to create a new diagnostic setting.
   • Configure the desired diagnostic settings, such as enabling boot diagnostics, guest OS diagnostics, and performance counters.
   • Choose the desired destination for the logs, such as Azure Storage or Azure Event Hubs.
   • Click on “Save” to apply the changes.

​

Using CLI

1. Enable auditing for Azure SQL Database:
   • Use the az sql server update-auditing command to enable auditing for the Azure SQL Server.
   • Specify the necessary parameters such as --state Enabled and --storage-account-resource-id to configure auditing settings.
   • Example command: az sql server update-auditing --resource-group <resource-group-name> --server <server-name> --state Enabled --storage-account-resource-id <storage-account-resource-id>
2. Enable diagnostic settings for Azure SQL Database:
   • Use the az monitor diagnostic-settings create command to enable diagnostic settings for the Azure SQL Database.
   • Specify the necessary parameters such as --name, --resource-id, and --workspace to configure diagnostic settings.
   • Example command: az monitor diagnostic-settings create --name <diagnostic-settings-name> --resource <database-resource-id> --workspace <workspace-id>
3. Enable threat detection for Azure SQL Database:
   • Use the az sql db threat-policy update command to enable threat detection for the Azure SQL Database.
   • Specify the necessary parameters such as --name, --resource-group, --server, and --state to configure threat detection settings.
   • Example command: az sql db threat-policy update --name <database-name> --resource-group <resource-group-name> --server <server-name> --state Enabled

​

Using Python

1. Monitor and alert on database service events:
   • Use the Azure Monitor service to set up alerts for specific events or metrics related to the Azure Database Service.
   • Create a Log Analytics workspace and configure it to collect and analyze logs from the database service.
   • Use the Azure Monitor Python SDK to programmatically create and manage alerts and log analytics queries.
2. Implement automated backups and retention policies:
   • Use the Azure Backup service to schedule automated backups for your Azure Database Service.
   • Configure the retention policies to retain backups for a specific duration.
   • Utilize the Azure Python SDK to programmatically create and manage backup policies and retention settings.
3. Implement security best practices:
   • Enable firewall rules to restrict access to your Azure Database Service.
   • Implement Azure Active Directory authentication for better security.
   • Utilize the Azure Key Vault service to securely store and manage database connection strings and credentials.
   • Use the Azure Python SDK to automate the configuration of firewall rules, enable Azure AD authentication, and interact with Azure Key Vault.