Framework/Configurations/SVT/Services/DBForMySql.json
|
{
"FeatureName": "DBForMySql", "Reference": "aka.ms/azsktcp/DBForMySql", "IsMaintenanceMode": false, "Controls": [ { "ControlID": "Azure_DBforMySQL_AuthZ_Review_AzureServices_Access", "Description": "Use the 'Allow access to Azure services' flag or IP range only if required", "Id": "DBforMySql100", "ControlSeverity": "High", "Automated": "Yes", "MethodName": "CheckMySQLFirewallAccessAzureService", "Rationale": "The 'Allow access to Azure services' setting configures a very broad range of IP addresses from Azure as permitted to access the MySQL Server. Please make sure your scenario really requires this setting before enabling it. Turning it ON exposes your MySQL Server to risk of attacks from resources (IPs) owned by others in the Azure region.", "Recommendation": "1. Turn 'OFF' the 'Allow access to Azure services' setting. 2. Remove IP range from firewall rules. Refer: https://docs.microsoft.com/en-us/azure/mysql/concepts-firewall-rules#connecting-from-azure", "Tags": [ "SDL", "TCP", "AuthZ", "Automated", "NetSec" ], "Enabled": true }, { "ControlID": "Azure_DBforMySQL_AuthZ_Verify_IP_Range", "Description": "Configure only the required IP addresses on MySQL server. Do not use 'Any-to-Any' IP range.", "Id": "DBforMySql110", "ControlSeverity": "High", "Automated": "Yes", "MethodName": "CheckMySQLFirewallIpRange", "Rationale": "Using the firewall feature ensures that access to the data or the service is restricted to a specific set/group of clients. NOTE: While this control does provide an extra layer of access control protection, it may not always be feasible to implement in all scenarios.", "Recommendation": "Do not configure 'Any to Any' firewall IP address. Refer: https://docs.microsoft.com/en-us/azure/mysql/concepts-firewall-rules.", "Tags": [ "SDL", "TCP", "AuthZ", "Automated", "NetSec" ], "Enabled": true }, { "ControlID": "Azure_DBforMySQL_Authz_Enable_SSL_Connection", "Description": "SSL connection must be enabled for Azure Database for MySQL", "Id": "DBforMySQL120", "ControlSeverity": "High", "Automated": "Yes", "MethodName": "CheckMySQLSSLConnection", "Rationale": "Enforcing SSL connections between your database server and your client applications helps protect against 'man in the middle' attacks by encrypting the data stream between the server and your application.", "Recommendation": "To enable SSL connection for Azure Database for MySQL server, refer https://docs.microsoft.com/en-us/azure/mysql/concepts-ssl-connection-security.", "Tags":[ "SDL", "TCP", "Authz", "Automated" ], "Enabled": true }, { "ControlID": "Azure_DBforMySQL_NetSec_Configure_VNet_Rules", "Description": "Consider using virtual network rules for improved isolation", "Id": "DBforMySQL130", "ControlSeverity": "Medium", "Automated": "Yes", "MethodName": "CheckMySQLServerVnetRules", "Rationale": "Virtual network rules provides isolation for your Azure Database for MySQL by permitting only the specified virtual networks to access the database server.", "Recommendation": "Refer: https://docs.microsoft.com/en-us/azure/mysql/concepts-data-access-and-security-vnet", "Tags": [ "SDL", "TCP", "NetSec", "Automated" ], "Enabled": true }, { "ControlID": "Azure_DBforMySQL_BCDR_Plan", "Description": "Backup and Disaster Recovery must be planned at the time of creation of Azure Database for MySql service", "Id": "DBforMySQL140", "ControlSeverity": "Medium", "Automated": "Yes", "MethodName": "CheckMySQLBCDRStatus", "Rationale": "Azure Database for MySQL offers default backup/disaster recovery for 7 days that can be extended up to 35 days. You can choose between locally redundant or geo-redundant backup storage. When processing critical workloads, a team must have adequate backups of the data.", "Recommendation": "Ensure back up settings for Azure Database for MySQL have been set correctly.", "Tags": [ "SDL", "TCP", "BCDR", "Automated" ], "Enabled": true }, { "ControlID": "Azure_DBforMySQL_Audit_Enable_ATP", "Description": "Advanced Threat Protection must be enabled for Azure Database for MySQL", "Id": "DBforMySQL150", "ControlSeverity": "High", "Automated": "Yes", "MethodName": "CheckMySQLServerATP", "Rationale": "Advanced Threat Protection for Azure Database for MySQL provides a layer of security, which enables customers to detect and respond to potential threats as they occur by providing security alerts on anomalous activities.", "Recommendation": "Refer: https://docs.microsoft.com/en-us/azure/mysql/concepts-data-access-and-security-threat-protection", "Tags": [ "SDL", "TCP", "Audit", "Automated" ], "Enabled": true }, { "ControlID": "Azure_DBforMySQL_Audit_Enable_Diagnostics_Log", "Description": "Diagnostics logs must be enabled with a retention period of at least365 days.", "Id": "DBforMySQL160", "ControlSeverity": "Medium", "Automated": "Yes", "MethodName": "CheckDiagnosticsSettings", "Rationale": "Logs should be retained for a long enough period so that activity trail can be recreated when investigations are required in the event of an incident or a compromise. A period of 1 year is typical for several compliance requirements as well.", "Recommendation": "You can change the diagnostic settings from the Azure Portal by following the steps given here: https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-archive-diagnostic-logs#archive-diagnostic-logs-using-the-portal", "Tags": [ "SDL", "TCP", "Audit", "Diagnostics", "DBforMySQL", "Automated" ], "Enabled": true }, { "ControlID": "Azure_DBforMySQL_Audit_Review_Logs", "Description": "Diagnostic and activity logs for Azure Database for MySQL should be reviewed periodically", "Id": "DBforMySQL170", "ControlSeverity": "Medium", "Automated": "No", "MethodName": "", "Rationale": "Periodic reviews of diagnostics, activity and audit logs ensures that anomalous activity can be identified early enough instead of after a major compromise.", "Recommendation": "Review diagnostic/activity logs to check activities on the resource. Refer: https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-overview-of-diagnostic-logs and https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-overview-activity-logs", "Tags": [ "SDL", "Best Practice", "Manual", "Audit", "DBforMySQL" ], "Enabled": true }, { "ControlID": "Azure_DBforMySQL_AuthZ_Grant_Min_Access", "Description": "Access to Azure Database for MySQL Servers must be granted in accordance with the principle of least privilege", "Id": "DBforMySQL180", "ControlSeverity": "High", "Automated": "No", "MethodName": "", "Rationale": "Granting minimum access ensures that users are granted just enough permissions to perform their tasks. This minimizes exposure of the resources in case of user/service account compromise.", "Recommendation": "Refer: https://docs.microsoft.com/en-us/azure/mysql/howto-create-users#how-to-create-database-users-in-azure-database-for-mysql", "Tags": [ "SDL", "TCP", "Manual", "AuthZ", "RBAC" ], "Enabled": true } ] } |