Microsoft.web.sites.config.delete

​

Event Information

• The microsoft.web.sites.config.delete event in Azure for Azure Web Service indicates that a configuration file associated with the web application has been deleted.
• This event typically occurs when a user or an automated process removes a configuration file from the Azure Web Service.
• It is important to note that deleting a configuration file can have significant impact on the behavior and functionality of the web application, so it is crucial to ensure that the deletion is intentional and necessary.

​

Examples

1. Unauthorized deletion of Azure Web App configuration: If security is impacted with microsoft.web.sites.config.delete in Azure for AzureWebService, it could potentially allow an unauthorized user to delete the configuration settings of an Azure Web App. This could lead to service disruption or unauthorized access to sensitive information stored within the web app.
2. Exposure of sensitive information: If security is impacted with microsoft.web.sites.config.delete, an attacker could potentially gain access to sensitive information such as connection strings, API keys, or other configuration settings stored within the Azure Web App. This could result in data breaches or unauthorized access to backend systems.
3. Service disruption or downtime: If an unauthorized user gains access to the microsoft.web.sites.config.delete operation, they could potentially delete critical configuration settings required for the proper functioning of the Azure Web App. This could lead to service disruption or downtime, impacting the availability and reliability of the web application.

​

Remediation

​

Using Console

1. Enable Azure Security Center:
   • Go to the Azure portal and search for “Security Center” in the search bar.
   • Select “Security Center” from the results and click on it.
   • In the Security Center dashboard, click on “Pricing & settings” in the left menu.
   • Choose the subscription and resource group where your AzureWebService is located.
   • Click on “Apply to all resources” to enable Security Center for all resources in the selected resource group.
   • Review the pricing tier options and select the appropriate tier for your needs.
   • Click on “Save” to enable Security Center.
2. Implement Network Security Groups (NSGs):
   • Go to the Azure portal and search for “Virtual machines” in the search bar.
   • Select “Virtual machines” from the results and click on it.
   • Find the virtual machine(s) associated with your AzureWebService.
   • Select the virtual machine and click on “Networking” in the left menu.
   • Under “Inbound port rules”, click on “Add inbound port rule” to add a new rule.
   • Configure the rule to allow only the necessary inbound traffic for your AzureWebService.
   • Repeat the above steps for all virtual machines associated with your AzureWebService.
3. Implement Azure Key Vault for secrets management:
   • Go to the Azure portal and search for “Key vaults” in the search bar.
   • Select “Key vaults” from the results and click on it.
   • Click on “Add” to create a new key vault.
   • Provide the necessary details like name, subscription, resource group, and region.
   • Configure access policies to grant necessary permissions to your AzureWebService.
   • Click on “Review + create” and then “Create” to create the key vault.
   • Once the key vault is created, you can store and manage secrets securely.

​

Using CLI

1. Enable diagnostic logs:
   • Use the az webapp log config command to enable diagnostic logs for the Azure Web Service.
   • Specify the desired log level and retention days using the --web-server-logging and --detailed-error-messages parameters respectively.
2. Enable HTTPS Only:
   • Use the az webapp update command to enable HTTPS Only for the Azure Web Service.
   • Set the --https-only parameter to true to enforce HTTPS communication.
3. Enable Managed Service Identity (MSI):
   • Use the az webapp identity assign command to enable Managed Service Identity for the Azure Web Service.
   • This will provide an identity for the service, which can be used for authentication and authorization purposes.

​

Using Python

1. Monitoring and Alerting:
   • Use the Azure Monitor service to set up monitoring and alerting for your Azure Web Service.
   • Create a metric alert to trigger an action when a specific condition is met, such as high CPU usage or low memory availability.
   • Use the Azure SDK for Python to programmatically create and manage alerts. Here’s an example script:
   Copy

   Ask AI

   from azure.mgmt.monitor import MonitorManagementClient
   from azure.identity import DefaultAzureCredential
   
   # Authenticate using DefaultAzureCredential
   credential = DefaultAzureCredential()
   
   # Create a MonitorManagementClient
   monitor_client = MonitorManagementClient(credential, subscription_id)
   
   # Define the alert rule parameters
   alert_rule_params = {
       'location': 'eastus',
       'name': 'High CPU Alert',
       'description': 'Alert triggered when CPU usage exceeds 80%',
       'severity': 2,
       'enabled': True,
       'condition': {
           'odata.type': 'Microsoft.Azure.Management.Monitor.Models.ThresholdRuleCondition',
           'dataSource': {
               'odata.type': 'Microsoft.Azure.Management.Monitor.Models.RuleMetricDataSource',
               'resourceUri': '/subscriptions/{subscription_id}/resourceGroups/{resource_group}/providers/Microsoft.Web/sites/{web_service_name}',
               'metricName': 'CpuPercentage',
               'operator': 'GreaterThan',
               'threshold': 80
           }
       },
       'actions': [
           {
               'odata.type': 'Microsoft.Azure.Management.Monitor.Models.RuleEmailAction',
               'sendToServiceOwners': True
           }
       ]
   }
   
   # Create the alert rule
   monitor_client.alert_rules.create_or_update(
       resource_group_name,
       web_service_name,
       alert_rule_name,
       alert_rule_params
   )
   

2. Security and Compliance:
   • Implement Azure Security Center to continuously monitor the security posture of your Azure Web Service.
   • Enable Azure Security Center’s Just-In-Time (JIT) VM Access feature to restrict access to your virtual machines.
   • Use the Azure SDK for Python to programmatically enable JIT VM Access. Here’s an example script:
   Copy

   Ask AI

   from azure.mgmt.security import SecurityCenterManagementClient
   from azure.identity import DefaultAzureCredential
   
   # Authenticate using DefaultAzureCredential
   credential = DefaultAzureCredential()
   
   # Create a SecurityCenterManagementClient
   security_center_client = SecurityCenterManagementClient(credential, subscription_id)
   
   # Enable JIT VM Access for the web service's virtual machines
   security_center_client.jit_network_access_policies.create_or_update(
       resource_group_name,
       web_service_name,
       'default',
       {
           'location': 'eastus',
           'virtualMachines': [
               {
                   'id': '/subscriptions/{subscription_id}/resourceGroups/{resource_group}/providers/Microsoft.Compute/virtualMachines/{vm_name}',
                   'ports': [
                       {
                           'number': 22,
                           'protocol': 'Tcp',
                           'allowedSourceAddressPrefixes': ['0.0.0.0/0']
                       }
                   ]
               }
           ]
       }
   )
   

3. Cost Optimization:
   • Utilize Azure Cost Management and Billing to monitor and optimize the costs of your Azure Web Service.
   • Enable cost alerts to receive notifications when your spending exceeds a certain threshold.
   • Use the Azure SDK for Python to programmatically create cost alerts. Here’s an example script:
   Copy

   Ask AI

   from azure.mgmt.costmanagement import CostManagementClient
   from azure.identity import DefaultAzureCredential
   
   # Authenticate using DefaultAzureCredential
   credential = DefaultAzureCredential()
   
   # Create a CostManagementClient
   cost_management_client = CostManagementClient(credential, subscription_id)
   
   # Define the cost alert parameters
   cost_alert_params = {
       'name': 'High Cost Alert',
       'description': 'Alert triggered when monthly spending exceeds $1000',
       'enabled': True,
       'threshold': 1000,
       'time_grain': 'Monthly',
       'time_window': 'PT1H',
       'query': "cost > 1000"
   }
   
   # Create the cost alert
   cost_management_client.alerts.create_or_update(
       resource_group_name,
       'default',
       cost_alert_params
   )