Merge pull request #94962 from memildin/asc-melvyn-seofixes

PRMerger9 · web-flow · commit f41da97d48e9 · 2019-11-06T02:15:24.000-08:00
Shortened title lengths
diff --git a/articles/security-center/quick-onboard-linux-computer.md b/articles/security-center/quick-onboard-linux-computer.md
@@ -1,5 +1,5 @@
 ---
-title: Azure Security Center Quickstart - Onboard your Linux computers to Security Center | Microsoft Docs
+title: Onboard Linux computers to Azure Security Center | Microsoft Docs
 description: This quickstart shows you how to onboard your Linux computers to Security Center.
 services: security-center
 documentationcenter: na
diff --git a/articles/security-center/security-center-alerts-cloud-smart.md b/articles/security-center/security-center-alerts-cloud-smart.md
@@ -1,5 +1,5 @@
 ---
-title: Cloud smart alert correlation in Azure Security Center (incidents) | Microsoft Docs
+title: Azure Security Center incidents - correlated alerts | Microsoft Docs
 description: This topic explains how fusion uses cloud smart alert correlation to generate security incidents in Azure Security Center.
 services: security-center
 documentationcenter: na
diff --git a/articles/security-center/security-center-alerts-compute.md b/articles/security-center/security-center-alerts-compute.md
@@ -16,7 +16,7 @@ ms.author: memildin
 ---
 # Threat detection for cloud native computing in Azure Security Center
 
-As a native solution, Azure Security Center has unique visibility into  internal logs for attack methodology identification across multiple targets. This article presents the alerts available for the following Azure services:
+As a native solution, Azure Security Center has unique visibility into internal logs for attack methodology identification across multiple targets. This article presents the alerts available for the following Azure services:
 
 * [Azure App Service](#app-services)
 * [Azure Containers](#azure-containers) 
@@ -74,9 +74,9 @@ Also, our global team of security researchers constantly monitor the threat land
 
 |Alert|Description|
 |---|---|
-|**PREVIEW - Role binding to the cluster-admin role detected**|Kubernetes audit log analysis detected a new binding to the cluster-admin role resulting in administrator privileges. Unnecessarily providing administrator privileges might result in  privilege escalation issues in the cluster.|
+|**PREVIEW - Role binding to the cluster-admin role detected**|Kubernetes audit log analysis detected a new binding to the cluster-admin role resulting in administrator privileges. Unnecessarily providing administrator privileges might result in privilege escalation issues in the cluster.|
 |**PREVIEW - Exposed Kubernetes dashboard detected**|Kubernetes audit log analysis detected exposure of the Kubernetes Dashboard by a LoadBalancer service. Exposed dashboards allow unauthenticated access to the cluster management and pose a security threat.|
-|**PREVIEW - New high privileges role detected**|Kubernetes audit log analysis detected a new role with high privileges. A binding to a role with high privileges gives the user/group elevated privileges in the cluster. Unnecessarily providing elevated privileges might result in  privilege escalation issues in the cluster.|
+|**PREVIEW - New high privileges role detected**|Kubernetes audit log analysis detected a new role with high privileges. A binding to a role with high privileges gives the user/group elevated privileges in the cluster. Unnecessarily providing elevated privileges might result in privilege escalation issues in the cluster.|
 |**PREVIEW - New container in the kube-system namespace detected**|Kubernetes audit log analysis detected a new container in the kube-system namespace that isn’t among the containers that normally run in this namespace. The kube-system namespaces shouldn't contain user resources. Attackers can use this namespace to hide malicious components.|
 |**PREVIEW - Digital currency mining container detected**|Kubernetes audit log analysis detected a container that has an image associated with a digital currency mining tool.|
 |**PREVIEW - Privileged container detected**|Kubernetes audit log analysis detected a new privileged container. A privileged container has access to the node’s resources and breaks the isolation between containers. If compromised, an attacker can use the privileged container to gain access to the node.|
diff --git a/articles/security-center/security-center-endpoint-protection.md b/articles/security-center/security-center-endpoint-protection.md
@@ -31,23 +31,23 @@ Azure Security Center provides health assessments of [supported](https://docs.mi
 
   * Any of the following properties are false:
 
-     **AMServiceEnabled**
+    **AMServiceEnabled**
 
-     **AntispywareEnabled**
+    **AntispywareEnabled**
 
-     **RealTimeProtectionEnabled**
+    **RealTimeProtectionEnabled**
 
-     **BehaviorMonitorEnabled**
+    **BehaviorMonitorEnabled**
 
-     **IoavProtectionEnabled**
+    **IoavProtectionEnabled**
 
-     **OnAccessProtectionEnabled**
+    **OnAccessProtectionEnabled**
 
   * If one or both of the following properties are 7 or more.
 
-     **AntispywareSignatureAge**
+    **AntispywareSignatureAge**
 
-     **AntivirusSignatureAge**
+    **AntivirusSignatureAge**
 
 ## Microsoft System Center endpoint protection
 
@@ -57,23 +57,23 @@ Azure Security Center provides health assessments of [supported](https://docs.mi
 
     * At least one of the following properties is false:
 
-       **AMServiceEnabled**
-    
-       **AntispywareEnabled**
+            **AMServiceEnabled**
+
+            **AntispywareEnabled**
     
-       **RealTimeProtectionEnabled**
+            **RealTimeProtectionEnabled**
     
-       **BehaviorMonitorEnabled**
+            **BehaviorMonitorEnabled**
     
-       **IoavProtectionEnabled**
+            **IoavProtectionEnabled**
     
-       **OnAccessProtectionEnabled**
+            **OnAccessProtectionEnabled**
           
     * If one or both of the following Signature Updates is greater or equal to 7. 
 
-       **AntispywareSignatureAge**
+            **AntispywareSignatureAge**
     
-       **AntivirusSignatureAge**
+            **AntivirusSignatureAge**
 
 ## Trend Micro
 
diff --git a/articles/security-center/security-center-onboarding.md b/articles/security-center/security-center-onboarding.md
@@ -1,5 +1,5 @@
 ---
-title: Onboarding to Azure Security Center Standard for enhanced security | Microsoft Docs
+title: Standard tier's enhanced security - Azure Security Center | Microsoft Docs
 description: " Learn how to onboard to Azure Security Center Standard for enhanced security. "
 services: security-center
 documentationcenter: na
diff --git a/articles/security-center/security-center-pricing.md b/articles/security-center/security-center-pricing.md
@@ -1,5 +1,5 @@
 ---
-title: Upgrade to Security Center's Standard tier for enhanced security | Microsoft Docs
+title: Pricing of Azure Security Center tiers | Microsoft Docs
 description: This article provides information on pricing for Azure Security Center.
 services: security-center
 documentationcenter: na
diff --git a/articles/security-center/security-center-sql-service-recommendations.md b/articles/security-center/security-center-sql-service-recommendations.md
@@ -1,5 +1,5 @@
 ---
-title: Protect Azure data and storage services in Azure Security Center | Microsoft Docs
+title: Data & storage recommendations - Azure Security Center | Microsoft Docs
 description: This document addresses recommendations in Azure Security Center that help you protect your data and Azure SQL service and stay in compliance with security policies.
 services: security-center
 documentationcenter: na
@@ -22,16 +22,16 @@ This topic shows you how to view and implement security recommendations for data
 
 1. In the **Resource security hygiene** section, click **Data and storage resources**.
 
-   ![Data & storage resources](./media/security-center-monitoring/click-data.png)
+    ![Data & storage resources](./media/security-center-monitoring/click-data.png)
 
     The **Data security** page opens with recommendations for data resources.
 
-     ![Data Resources](./media/security-center-monitoring/sql-overview.png)
+    ![Data Resources](./media/security-center-monitoring/sql-overview.png)
 
-From this page, you can:
+    From this page, you can:
 
-* Click the **Overview** tab lists all the data resources recommendations to be remediated. 
-* Click each tab, and view the recommendations by resource type.
+    * Click the **Overview** tab lists all the data resources recommendations to be remediated. 
+    * Click each tab, and view the recommendations by resource type.
 
     > [!NOTE]
     > For more information about storage encryption, see [Azure Storage encryption for data at rest](../storage/common/storage-service-encryption.md).
@@ -60,7 +60,7 @@ From this page, you can:
 |Storage account|20|Secure transfer to storage accounts should be enabled|Secure transfer is an option that forces your storage account to accept requests only from secure connections (HTTPS). HTTPS ensures authentication between the server and the service and protects data in transit from network layer attacks such as man-in-the-middle, eavesdropping, and session-hijacking.|
 |Redis|20|Only secure connections to your Redis Cache should be enabled|Enable only connections via SSL to Azure Cache for Redis. Use of secure connections ensures authentication between the server and the service and protects data in transit from network layer attacks such as man-in-the-middle, eavesdropping, and session-hijacking.|
 |SQL|15|Transparent Data Encryption on SQL databases should be enabled|Enable transparent data encryption to protect data-at-rest and meet compliance requirements.|
-|SQL|15|SQL server auditing should be enabled|Enable auditing  for Azure SQL servers. (Azure SQL service only. Doesn't include SQL running on your virtual machines.)|
+|SQL|15|SQL server auditing should be enabled|Enable auditing for Azure SQL servers. (Azure SQL service only. Doesn't include SQL running on your virtual machines.)|
 |Data lake analytics|5|Diagnostics logs in Data Lake Analytics should be enabled|Enable logs and retain them up to a year. This enables you to recreate activity trails for investigation purposes when a security incident occurs or your network is compromised. |
 |Data lake store|5|Diagnostics logs in Azure Data Lake Store should be enabled|Enable logs and retain them up to a year. This enables you to recreate activity trails for investigation purposes when a security incident occurs or your network is compromised. |
 |SQL|30|Vulnerabilities on your SQL databases should be remediated|SQL Vulnerability Assessment scans your database for security vulnerabilities and exposes any deviations from best practices such as misconfigurations, excessive permissions, and unprotected sensitive data. Resolving the vulnerabilities found can greatly improve your database security stature.|
diff --git a/articles/security-center/tutorial-protect-resources.md b/articles/security-center/tutorial-protect-resources.md
@@ -1,5 +1,5 @@
 ---
-title: Azure Security Center Tutorial - Protect your resources with Azure Security Center | Microsoft Docs
+title: Access & application controls tutorial - Azure Security Center | Microsoft Docs
 description: This tutorial shows you how to configure a just-in-time VM access policy and an application control policy.
 services: security-center
 documentationcenter: na
@@ -25,8 +25,6 @@ In this tutorial you learn how to:
 > * Configure a just-in-time VM access policy
 > * Configure an application control policy
 
-If you don’t have an Azure subscription, create a  [free account](https://azure.microsoft.com/pricing/free-trial/) before you begin.
-
 ## Prerequisites
 To step through the features covered in this tutorial, you must be on Security Center’s Standard pricing tier. You can try Security Center Standard at no cost. To learn more, see the [pricing page](https://azure.microsoft.com/pricing/details/security-center/). The quickstart [Onboard your Azure subscription to Security Center Standard](security-center-get-started.md) walks you through how to upgrade to Standard.
 
@@ -91,7 +89,7 @@ Adaptive application controls help you define a set of applications that are all
 4. Once you finish your selections, select **Create**.
 
 ## Clean up resources
-Other quickstarts and tutorials in this collection build upon this quickstart. If you plan to continue on to work with subsequent quickstarts and tutorials, continue running the Standard tier and keep automatic provisioning enabled. If you do not plan to continue or wish to return to the Free tier:
+Other quickstarts and tutorials in this collection build upon this quickstart. If you plan to continue to work with subsequent quickstarts and tutorials, continue running the Standard tier and keep automatic provisioning enabled. If you do not plan to continue or wish to return to the Free tier:
 
 1. Return to the Security Center main menu and select **Security Policy**.
 2. Select the subscription or policy that you want to return to Free. **Security policy** opens.
diff --git a/articles/security-center/tutorial-security-incident.md b/articles/security-center/tutorial-security-incident.md
@@ -1,5 +1,5 @@
 ---
-title: Azure Security Center Tutorial - Respond to security incidents | Microsoft Docs
+title: Incident response tutorial - Azure Security Center | Microsoft Docs
 description: Azure Security Center Tutorial - Respond to security incidents
 services: security-center
 documentationcenter: na
@@ -61,7 +61,7 @@ Security Center provides a unified view of all security alerts. Security alerts
 
 1. On the Security Center main menu under **DETECTION**, select **Security alerts**:
 
-   ![Security alerts](./media/tutorial-security-incident/tutorial-security-incident-fig1.png)  
+   ![Security alerts](./media/tutorial-security-incident/tutorial-security-incident-fig1.png)
 
 2. In the list of alerts, click on a security incident, which is a collection of alerts, to learn more about this incident. **Security incident detected** opens.
 
