Azure Database SQL Server Server Vulnerability Assessment
This page shows how to write Terraform and Azure Resource Manager for Database SQL Server Server Vulnerability Assessment and write them securely.
azurerm_mssql_server_vulnerability_assessment (Terraform)
The SQL Server Server Vulnerability Assessment in Database can be configured in Terraform with the resource name azurerm_mssql_server_vulnerability_assessment
. The following sections describe 8 examples of how to use the resource and its parameters.
Example Usage from GitHub
resource "azurerm_mssql_server_vulnerability_assessment" "mssqlvulnassessment" {
server_security_alert_policy_id = var.sql_vuln_alert_policy_id
storage_container_path = var.sql_vuln_container_path
storage_account_access_key = var.sql_vuln_access_key
recurring_scans {
resource "azurerm_mssql_server_vulnerability_assessment" "mssql" {
count = try(var.settings.security_alert_policy.vulnerability_assessment, null) == null ? 0 : 1
server_security_alert_policy_id = azurerm_mssql_server_security_alert_policy.mssql.0.id
storage_container_path = format("%s%s/", data.azurerm_storage_account.mssql_va.0.primary_blob_endpoint, try(var.settings.security_alert_policy.vulnerability_assessment.storage_account.container_path, "vascans"))
storage_account_access_key = data.azurerm_storage_account.mssql_va.0.primary_access_key
resource "azurerm_mssql_server_vulnerability_assessment" "mssql" {
count = try(var.settings.security_alert_policy.vulnerability_assessment, null) == null ? 0 : 1
server_security_alert_policy_id = azurerm_mssql_server_security_alert_policy.mssql.0.id
storage_container_path = format("%s%s/", data.azurerm_storage_account.mssql_va.0.primary_blob_endpoint, try(var.settings.security_alert_policy.vulnerability_assessment.storage_account.container_path, "vascans"))
storage_account_access_key = data.azurerm_storage_account.mssql_va.0.primary_access_key
resource "azurerm_mssql_server_vulnerability_assessment" "this" {
server_security_alert_policy_id = var.server_security_alert_policy_id
storage_account_access_key = var.storage_account_access_key
storage_container_path = var.storage_container_path
storage_container_sas_key = var.storage_container_sas_key
resource "azurerm_mssql_server_vulnerability_assessment" "this" {
server_security_alert_policy_id = var.server_security_alert_policy_id
storage_account_access_key = var.storage_account_access_key
storage_container_path = var.storage_container_path
storage_container_sas_key = var.storage_container_sas_key
resource "azurerm_mssql_server_vulnerability_assessment" "mssql" {
count = try(var.settings.security_alert_policy.vulnerability_assessment, null) == null ? 0 : 1
server_security_alert_policy_id = azurerm_mssql_server_security_alert_policy.mssql.0.id
storage_container_path = format("%s%s/", data.azurerm_storage_account.mssql_va.0.primary_blob_endpoint, try(var.settings.security_alert_policy.vulnerability_assessment.storage_account.container_path, "vascans"))
storage_account_access_key = data.azurerm_storage_account.mssql_va.0.primary_access_key
resource "azurerm_mssql_server_vulnerability_assessment" "mssql" {
count = try(var.settings.security_alert_policy.vulnerability_assessment, null) == null ? 0 : 1
server_security_alert_policy_id = azurerm_mssql_server_security_alert_policy.mssql.0.id
storage_container_path = format("%s%s/", data.azurerm_storage_account.mssql_va.0.primary_blob_endpoint, try(var.settings.security_alert_policy.vulnerability_assessment.storage_account.container_path, "vascans"))
storage_account_access_key = data.azurerm_storage_account.mssql_va.0.primary_access_key
resource "azurerm_mssql_server_vulnerability_assessment" "mssql" {
count = try(var.settings.security_alert_policy.vulnerability_assessment, null) == null ? 0 : 1
server_security_alert_policy_id = azurerm_mssql_server_security_alert_policy.mssql.0.id
storage_container_path = format("%s%s/", data.azurerm_storage_account.mssql_va.0.primary_blob_endpoint, try(var.settings.security_alert_policy.vulnerability_assessment.storage_account.container_path, "vascans"))
storage_account_access_key = data.azurerm_storage_account.mssql_va.0.primary_access_key
Parameters
-
id
optional computed - string -
server_security_alert_policy_id
required - string -
storage_account_access_key
optional - string -
storage_container_path
required - string -
storage_container_sas_key
optional - string -
recurring_scans
list block-
email_subscription_admins
optional - bool -
emails
optional - list of string -
enabled
optional - bool
-
-
timeouts
single block
Explanation in Terraform Registry
Manages the Vulnerability Assessment for a MS SQL Server. -> NOTE Vulnerability Assessment is currently only available for MS SQL databases.
Tips: Best Practices for The Other Azure Database Resources
In addition to the azurerm_mariadb_firewall_rule, Azure Database has the other resources that should be configured for security reasons. Please check some examples of those resources and precautions.
azurerm_mariadb_firewall_rule
Ensure database firewalls do not permit public access
It is better to restrict IP address ranges that can access the database by firewall rules. If both start_ip_address and end_ip_address are set to 0.0.0.0, it blocks connections from the Internet and accepts connections from all Azure datacenter IP addresses.
azurerm_mariadb_server
Ensure that access to Azure SQL Database is restricted
It is better to disable public access to the database to avoid unwilling communications with unknown services if not required.
azurerm_mssql_database_extended_auditing_policy
Ensure to configure retention periods of database auditing to enough duration
It is better to configure retention periods of database auditing to enough duration. It would be better to set greater than at least 90 days.
azurerm_mssql_server
Ensure to enable auditing on Azure SQL databases
It is better to enable auditing on Azure SQL databases. It helps you maintain regulatory compliance, monitor the activities indicating unexpected incidents or suspected security violations.
azurerm_mssql_server_security_alert_policy
Ensure to configure at least one email address for threat alerts
It is better to configure at least one email address for threat alerts. SQL Server is able to send alerts for threat detection via emails and it could support us to notice the incident on time.
azurerm_mysql_firewall_rule
Ensure database firewalls do not permit public access
It is better to restrict IP address ranges that can access the database by firewall rules. If both start_ip_address and end_ip_address are set to 0.0.0.0, it blocks connections from the Internet and accepts connections from all Azure datacenter IP addresses.
azurerm_mysql_server
Ensure to disable public access to database
It is better to disable public access to the database to avoid unwilling communications with unknown services if not required.
azurerm_postgresql_firewall_rule
Ensure database firewalls do not permit public access
It is better to restrict IP address ranges that can access the database by firewall rules. If both start_ip_address and end_ip_address are set to 0.0.0.0, it blocks connections from the Internet and accepts connections from all Azure datacenter IP addresses.
azurerm_postgresql_server
Ensure to disable public access to database
It is better to disable public access to the database to avoid unwilling communications with unknown services if not required.
azurerm_sql_firewall_rule
Ensure database firewalls do not permit public access
It is better to restrict IP address ranges that can access the database by firewall rules. If both start_ip_address and end_ip_address are set to 0.0.0.0, it blocks connections from the Internet and accepts connections from all Azure datacenter IP addresses.
azurerm_sql_server
Ensure to enable auditing on Azure SQL databases
It is better to enable auditing on Azure SQL databases. It helps you maintain regulatory compliance, monitor the activities indicating unexpected incidents or suspected security violations.
Microsoft.Sql/servers/databases/vulnerabilityAssessments (Azure Resource Manager)
The servers/databases/vulnerabilityAssessments in Microsoft.Sql can be configured in Azure Resource Manager with the resource name Microsoft.Sql/servers/databases/vulnerabilityAssessments
. The following sections describe how to use the resource and its parameters.
Example Usage from GitHub
{
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"serverName": {
"type": "Microsoft.Sql/servers/databases/vulnerabilityAssessments",
"existenceCondition": {
"allOf": [
{
"field": "Microsoft.Sql/servers/databases/vulnerabilityAssessments/recurringScans.emails",
"equals": "[parameters('vulnerabilityAssessmentsEmail')]"
"type": "Microsoft.Sql/servers/databases/vulnerabilityAssessments",
"existenceCondition": {
"allOf": [
{
"field": "Microsoft.Sql/servers/databases/vulnerabilityAssessments/recurringScans.emails",
"equals": "[parameters('vulnerabilityAssessmentsEmail')]"
"type": "Microsoft.Sql/servers/databases/vulnerabilityAssessments",
"existenceCondition": {
"allOf": [
{
"field": "Microsoft.Sql/servers/databases/vulnerabilityAssessments/recurringScans.emails",
"equals": "[parameters('vulnerabilityAssessmentsEmail')]"
"type": "Microsoft.Sql/servers/databases/vulnerabilityAssessments",
"existenceCondition": {
"allOf": [
{
"field": "Microsoft.Sql/servers/databases/vulnerabilityAssessments/recurringScans.emails",
"equals": "[parameters('vulnerabilityAssessmentsEmail')]"
"type": "Microsoft.Sql/servers/databases/vulnerabilityAssessments",
"existenceCondition": {
"allOf": [
{
"field": "Microsoft.Sql/servers/databases/vulnerabilityAssessments/recurringScans.emails",
"equals": "[parameters('vulnerabilityAssessmentsEmail')]"
"type": "Microsoft.Sql/servers/databases/vulnerabilityAssessments",
"existenceCondition": {
"allOf": [
{
"field": "Microsoft.Sql/servers/databases/vulnerabilityAssessments/recurringScans.emails",
"equals": "[parameters('vulnerabilityAssessmentsEmail')]"
"type": "Microsoft.Sql/servers/databases/vulnerabilityAssessments",
"existenceCondition": {
"allOf": [
{
"field": "Microsoft.Sql/servers/databases/vulnerabilityAssessments/recurringScans.emails",
"equals": "[parameters('vulnerabilityAssessmentsEmail')]"
"type": "Microsoft.Sql/servers/databases/vulnerabilityAssessments",
"existenceCondition": {
"allOf": [
{
"field": "Microsoft.Sql/servers/databases/vulnerabilityAssessments/recurringScans.emails",
"equals": "[parameters('vulnerabilityAssessmentsEmail')]"
"type": "Microsoft.Sql/servers/databases/vulnerabilityAssessments",
"existenceCondition": {
"allOf": [
{
"field": "Microsoft.Sql/servers/databases/vulnerabilityAssessments/recurringScans.emails",
"equals": "[parameters('vulnerabilityAssessmentsEmail')]"
Frequently asked questions
What is Azure Database SQL Server Server Vulnerability Assessment?
Azure Database SQL Server Server Vulnerability Assessment is a resource for Database of Microsoft Azure. Settings can be wrote in Terraform.
Where can I find the example code for the Azure Database SQL Server Server Vulnerability Assessment?
For Terraform, the prancer-io/prancer-terramerra, davesee/terraform-caf-rover-breakout and anmoltoppo/Terraform source code examples are useful. See the Terraform Example section for further details.
For Azure Resource Manager, the pfiadeiro/blog-content, tschwarz01/tf-caf-data-management-zone and samrande/Enterprise-scale- source code examples are useful. See the Azure Resource Manager Example section for further details.