Add other dbs

Author: rachel-msft

articles/mariadb/TOC.yml

@@ -49,16 +49,18 @@
       href: concepts-limits.md
   - name: Data access & security
     items:
-    - name: Firewall rules
-      href: concepts-firewall-rules.md
+    - name: Security overview
+      href: concepts-security.md
     - name: Configuring SSL
       href: concepts-ssl-connection-security.md
-    - name: Advanced Threat Protection
-      href: concepts-data-access-and-security-threat-protection.md
-    - name: Virtual Network
-      href: concepts-data-access-security-vnet.md
     - name: Connectivity architecture
       href: concepts-connectivity-architecture.md
+    - name: Firewall rules
+      href: concepts-firewall-rules.md
+    - name: Virtual Network
+      href: concepts-data-access-security-vnet.md
+    - name: Advanced Threat Protection
+      href: concepts-data-access-and-security-threat-protection.md
   - name: Business continuity
     items:
     - name: Business continuity intro

articles/mariadb/concepts-security.md

@@ -0,0 +1,49 @@
+---
+title: Security in Azure Database for MariaDB - Single Server
+description: An overview of the security features in Azure Database for MariaDB - Single Server.
+author: ajlam
+ms.author: andrela
+ms.service: mariadb
+ms.topic: conceptual
+ms.date: 11/22/2019
+---
+
+# Security in Azure Database for MariaDB - Single Server
+
+There are multiple layers of security that are available to protect the data on your Azure Database for MariaDB server. This article outlines those security options.
+
+## Information protection and encryption
+
+### In-transit
+Azure Database for MariaDB secures your data by encrypting data in-transit with Transport Layer Security. Encryption (SSL/TLS) is enforced by default.
+
+### At-rest
+The Azure Database for MariaDB service uses the FIPS 140-2 validated cryptographic module for storage encryption of data at-rest. Data, including backups, are encrypted on disk, with the exception of temporary files created while running queries. The service uses the AES 256-bit cipher included in Azure storage encryption, and the keys are system managed. Storage encryption is always on and can't be disabled.
+
+
+## Network security
+Connections to an Azure Database for MariaDB server are first routed through a regional gateway. The gateway has a publicly accessible IP, while the server IP addresses are protected. For more information about the gateway, visit the [connectivity architecture article](concepts-connectivity-architecture.md).  
+
+A newly created Azure Database for MariaDB server has a firewall that blocks all external connections. Though they reach the gateway, they are not allowed to connect to the server. 
+
+### IP firewall rules
+IP firewall rules grant access to servers based on the originating IP address of each request. See the [firewall rules overview](concepts-firewall-rules.md) for more information.
+
+### Virtual network firewall rules
+Virtual network service endpoints extend your virtual network connectivity over the Azure backbone. Using virtual network rules you can enable your Azure Database for MariaDB server to allow connections from selected subnets in a virtual network. For more information, see the [virtual network service endpoint overview](concepts-data-access-security-vnet.md).
+
+
+## Access management
+
+While creating the Azure Database for MariaDB server, you provide credentials for an administrator user. This administrator can be used to create additional MariaDB users.
+
+
+## Threat protection
+
+You can opt in to [Advanced Threat Protection](concepts-data-access-and-security-threat-protection.md) which detects anomalous activities indicating unusual and potentially harmful attempts to access or exploit servers.
+
+[Audit logging](concepts-audit-logs.md) is available to track activity in your databases. 
+
+
+## Next steps
+- Enable firewall rules for [IPs](concepts-firewall-rules.md) or [virtual networks](concepts-data-access-and-security-vnet.md)

articles/mysql/TOC.yml

@@ -79,16 +79,18 @@
       href: concepts-limits.md
   - name: Data access & security
     items:
-    - name: Firewall rules
-      href: concepts-firewall-rules.md
+    - name: Security overview
+      href: concepts-security.md
     - name: Configuring SSL
       href: concepts-ssl-connection-security.md
-    - name: Advanced Threat Protection
-      href: concepts-data-access-and-security-threat-protection.md
-    - name: Virtual Network
-      href: concepts-data-access-and-security-vnet.md
     - name: Connectivity architecture
-      href: concepts-connectivity-architecture.md      
+      href: concepts-connectivity-architecture.md
+    - name: Firewall rules
+      href: concepts-firewall-rules.md
+    - name: Virtual Network
+      href: concepts-data-access-security-vnet.md
+    - name: Advanced Threat Protection
+      href: concepts-data-access-and-security-threat-protection.md   
   - name: Business continuity
     items:
     - name: Business continuity intro

articles/mysql/concepts-security.md

@@ -0,0 +1,49 @@
+---
+title: Security in Azure Database for MySQL - Single Server
+description: An overview of the security features in Azure Database for MySQL - Single Server.
+author: ajlam
+ms.author: andrela
+ms.service: mysql
+ms.topic: conceptual
+ms.date: 11/22/2019
+---
+
+# Security in Azure Database for MySQL - Single Server
+
+There are multiple layers of security that are available to protect the data on your Azure Database for MySQL server. This article outlines those security options.
+
+## Information protection and encryption
+
+### In-transit
+Azure Database for MySQL secures your data by encrypting data in-transit with Transport Layer Security. Encryption (SSL/TLS) is enforced by default.
+
+### At-rest
+The Azure Database for MySQL service uses the FIPS 140-2 validated cryptographic module for storage encryption of data at-rest. Data, including backups, are encrypted on disk, with the exception of temporary files created while running queries. The service uses the AES 256-bit cipher included in Azure storage encryption, and the keys are system managed. Storage encryption is always on and can't be disabled.
+
+
+## Network security
+Connections to an Azure Database for MySQL server are first routed through a regional gateway. The gateway has a publicly accessible IP, while the server IP addresses are protected. For more information about the gateway, visit the [connectivity architecture article](concepts-connectivity-architecture.md).  
+
+A newly created Azure Database for MySQL server has a firewall that blocks all external connections. Though they reach the gateway, they are not allowed to connect to the server. 
+
+### IP firewall rules
+IP firewall rules grant access to servers based on the originating IP address of each request. See the [firewall rules overview](concepts-firewall-rules.md) for more information.
+
+### Virtual network firewall rules
+Virtual network service endpoints extend your virtual network connectivity over the Azure backbone. Using virtual network rules you can enable your Azure Database for MySQL server to allow connections from selected subnets in a virtual network. For more information, see the [virtual network service endpoint overview](concepts-data-access-security-vnet.md).
+
+
+## Access management
+
+While creating the Azure Database for MySQL server, you provide credentials for an administrator user. This administrator can be used to create additional MySQL users.
+
+
+## Threat protection
+
+You can opt in to [Advanced Threat Protection](concepts-data-access-and-security-threat-protection.md) which detects anomalous activities indicating unusual and potentially harmful attempts to access or exploit servers.
+
+[Audit logging](concepts-audit-logs.md) is available to track activity in your databases. 
+
+
+## Next steps
+- Enable firewall rules for [IPs](concepts-firewall-rules.md) or [virtual networks](concepts-data-access-and-security-vnet.md)

articles/postgresql/concepts-security.md

@@ -5,7 +5,7 @@ author: rachel-msft
 ms.author: raagyema
 ms.service: postgresql
 ms.topic: conceptual
-ms.date: 11/20/2019
+ms.date: 11/22/2019
 ---
 
 # Security in Azure Database for PostgreSQL - Single Server
@@ -24,13 +24,13 @@ The Azure Database for PostgreSQL service uses the FIPS 140-2 validated cryptogr
 ## Network security
 Connections to an Azure Database for PostgreSQL server are first routed through a regional gateway. The gateway has a publicly accessible IP, while the server IP addresses are protected. For more information about the gateway, visit the [connectivity architecture article](concepts-connectivity-architecture.md).  
 
-A new Azure Database for PostgreSQL server has a firewall that blocks all external connections. Though they reach the gateway, they are not allowed to connect to the server. 
+A newly created Azure Database for PostgreSQL server has a firewall that blocks all external connections. Though they reach the gateway, they are not allowed to connect to the server. 
 
 ### IP firewall rules
 IP firewall rules grant access to servers based on the originating IP address of each request. See the [firewall rules overview](concepts-firewall-rules.md) for more information.
 
 ### Virtual network firewall rules
-Using virtual network service endpoints, you can enable your Azure Database for PostgreSQL server to allow connections from selected subnets in a virtual network. For more information, see the [virtual network service endpoint overview](concepts-data-access-and-security-vnet.md).
+Virtual network service endpoints extend your virtual network connectivity over the Azure backbone. Using virtual network rules you can enable your Azure Database for PostgreSQL server to allow connections from selected subnets in a virtual network. For more information, see the [virtual network service endpoint overview](concepts-data-access-and-security-vnet.md).
 
 
 ## Access management

articles/postgresql/overview.md

@@ -6,21 +6,22 @@ ms.author: jonels
 ms.custom: mvc
 ms.service: postgresql
 ms.topic: overview
-ms.date: 05/06/2019
+ms.date: 11/21/2019
 ---
 # What is Azure Database for PostgreSQL?
 Azure Database for PostgreSQL is a relational database service in the Microsoft cloud built for developers. It is based on the community version of open-source [PostgreSQL](https://www.postgresql.org/) database engine, and is available in two deployment options: Single Server and Hyperscale (Citus).
 
 ## Azure Database for PostgreSQL - Single Server
 The Single Server deployment option delivers:
 
-- Built-in high availability with no additional cost (99.99% SLA)
+- Built-in [high availability](concepts-high-availability.md) with no additional cost (99.99% SLA)
 - Predictable performance, using inclusive pay-as-you-go pricing
-- Vertical scale as needed within seconds
-- Monitoring and alerting to quickly assess the impact of scaling
-- Secured to protect sensitive data at-rest and in-motion
-- Automatic backups and point-in-time-restore for up to 35 days
+- [Vertical scale as needed](concepts-pricing-tiers.md) within seconds
+- [Monitoring and alerting](concepts-monitoring.md) to assess your server
 - Enterprise-grade security and compliance
+- [Secured to protect](concepts-security.md) sensitive data at-rest and in-motion
+- [Automatic backups and point-in-time-restore](concepts-business-continuity.md) for up to 35 days
+
 
 All those capabilities require almost no administration, and all are provided at no additional cost. They allow you to focus on rapid application development and accelerating your time to market, rather than spending precious time and resources to manage virtual machines and infrastructure. You can continue to develop your application with the open-source tools and platform of your choice, without having to learn new skills.