Skip to content

Commit 33672a5

Browse files
committed
Tweaks of metadata titles to reduce length
Received an analysis that the titles of these docs were all too long (over 65 chars). They averaged at 88 characters. Now their average is 57. Where relevant I also removed redundant spaces.
1 parent d3d4619 commit 33672a5

20 files changed

+44
-45
lines changed

articles/security-center/quick-onboard-azure-stack.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Azure Security Center Quickstart - Onboard your Azure Stack virtual machines to Security Center | Microsoft Docs
2+
title: Onboard Azure Stack virtual machines to Azure Security Center
33
description: This quickstart shows you how to provision the Azure Monitor, Update and Configuration Management virtual machine extension on a Azure Stack virtual machines.
44
services: security-center
55
documentationcenter: na
@@ -17,7 +17,7 @@ ms.date: 04/02/2019
1717
ms.author: fiseraci
1818

1919
---
20-
# Quickstart: Onboard your Azure Stack virtual machines to Security Center
20+
# Quickstart: Onboard your Azure Stack virtual machines to Security Center
2121
After you onboard your Azure subscription, you can enable Security Center to protect your virtual machines running on Azure Stack by adding the **Azure Monitor, Update and Configuration Management** virtual machine extension from the Azure Stack marketplace.
2222

2323
This quickstart shows you how to add the **Azure Monitor, Update and Configuration Management** virtual machine extension on a virtual machine (Linux and Windows are both supported) running on Azure Stack.
@@ -65,7 +65,7 @@ You must now add the **Azure Monitor, Update and Configuration Management** virt
6565
> If you do not see the **Azure Monitor, Update and Configuration Management** extension listed in your marketplace, please reach out to your Azure Stack operator to make it available.
6666
6767
6. On the **Install extension** configuration blade, paste the **Workspace ID** and **Workspace Key (Primary Key)** that you copied into Notepad in the previous procedure.
68-
7. When you are done providing the necessary configuration settings, click **OK**.
68+
7. When you are done providing the necessary configuration settings, click **OK**.
6969
8. Once the extension installation completes, its status will show as **Provisioning Succeeded**. It might take up to one hour for the virtual machine to appear in the Security Center portal.
7070

7171
For further information on installing and configuring the agent for Windows, see [Connect Windows computers](../azure-monitor/platform/agent-windows.md#install-the-agent-using-setup-wizard).

articles/security-center/quick-onboard-windows-computer.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Azure Security Center Quickstart - Onboard your Windows computers to Security Center | Microsoft Docs
2+
title: Onboard Windows computers to Azure Security Center
33
description: This quickstart shows you how to provision the Microsoft Monitoring Agent on a Windows computer.
44
services: security-center
55
documentationcenter: na
@@ -60,7 +60,7 @@ You must now install the downloaded file on the target computer.
6060
4. On the **Destination Folder** page, change or keep the default installation folder and then select **Next**.
6161
5. On the **Agent Setup Options** page, choose to connect the agent to Azure Log Analytics and then select **Next**.
6262
6. On the **Azure Log Analytics** page, paste the **Workspace ID** and **Workspace Key (Primary Key)** that you copied into Notepad in the previous procedure.
63-
7. If the computer should report to a Log Analytics workspace in Azure Government cloud, select **Azure US Government** form the **Azure Cloud** dropdown list. If the computer needs to communicate through a proxy server to the Log Analytics service, select **Advanced** and provide the URL and port number of the proxy server.
63+
7. If the computer should report to a Log Analytics workspace in Azure Government cloud, select **Azure US Government** form the **Azure Cloud** dropdown list. If the computer needs to communicate through a proxy server to the Log Analytics service, select **Advanced** and provide the URL and port number of the proxy server.
6464
8. Select **Next** once you have completed providing the necessary configuration settings.
6565

6666
![Install the agent][5]

articles/security-center/security-center-alerts-cloud-smart.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Azure Security Center incidents - correlated alerts | Microsoft Docs
2+
title: Azure Security Center incidents - smart correlations of alerts
33
description: This topic explains how fusion uses cloud smart alert correlation to generate security incidents in Azure Security Center.
44
services: security-center
55
documentationcenter: na
@@ -25,7 +25,7 @@ Fusion analytics is the technology and analytic back end that powers Security Ce
2525

2626
Fusion analytics combines security domain knowledge with AI to analyze alerts, discovering new attack patterns as they occur.
2727

28-
Security Center leverages MITRE Attack Matrix to associate alerts with their perceived intent, helping formalize security domain knowledge. In addition, by using the information gathered for each step of an attack, Security Center can rule out activity that appears to be steps of an attack, but actually isn't.
28+
Security Center leverages MITRE Attack Matrix to associate alerts with their perceived intent, helping formalize security domain knowledge. In addition, by using the information gathered for each step of an attack, Security Center can rule out activity that appears to be steps of an attack, but actually isn't.
2929

3030
Because attacks often occur across different tenants, Security Center can combine AI algorithms to analyze attack sequences that are reported on each subscription. This technique identifies the attack sequences as prevalent alert patterns, instead of just being incidentally associated with each other.
3131

articles/security-center/security-center-alerts-integration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Integration of Azure security products in Azure Security Center| Microsoft Docs
2+
title: Integration of Azure security products with Azure Security Center
33
description: This topic presents Azure security products that have been integrated with Azure Security Center.
44
services: security-center
55
documentationcenter: na

articles/security-center/security-center-alerts-service-layer.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Threat detection for Azure service layer in Azure Security Center | Microsoft Docs
2+
title: Azure service layer threat detection - Azure Security Center
33
description: This topic presents the Azure service layer alerts available in Azure Security Center.
44
services: security-center
55
documentationcenter: na

articles/security-center/security-center-compliance-dashboard.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Improve your regulatory compliance using Azure Security Center | Microsoft Docs
2+
title: Regulatory compliance checks - Azure Security Center
33
description: "Tutorial: Learn how to Improve your regulatory compliance using Azure Security Center."
44
services: security-center
55
documentationcenter: na

articles/security-center/security-center-endpoint-protection.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Endpoint protection solutions discovery and health assessment in Azure Security Center | Microsoft Docs
2+
title: Endpoint protection recommendations in Azure Security Centers
33
description: How the endpoint protection solutions are discovered and identified as healthy.
44
services: security-center
55
documentationcenter: na
@@ -98,7 +98,7 @@ Or
9898

9999
Security Center recommends you **"Resolve endpoint protection health issues on your machines"** when any of the following checks aren't met:
100100

101-
* Check Symantec Version >= 12: Registry location: **HKLM:\Software\Symantec\Symantec Endpoint Protection\CurrentVersion" -Value "PRODUCTVERSION"**
101+
* Check Symantec Version >= 12: Registry location: **HKLM:\Software\Symantec\Symantec Endpoint Protection\CurrentVersion" -Value "PRODUCTVERSION"**
102102

103103
* Check Real Time Protection status: **HKLM:\Software\Wow6432Node\Symantec\Symantec Endpoint Protection\AV\Storages\Filesystem\RealTimeScan\OnOff == 1**
104104

@@ -159,21 +159,21 @@ Security Center recommends you **"Install endpoint protection solutions on virtu
159159

160160
Security Center recommends you **"Resolve endpoint protection health issues on your machines"** when any of the following checks aren't met:
161161

162-
- **"/opt/sophos-av/bin/savlog --maxage=7 | grep -i "Scheduled scan .\* completed" | tail -1"**, returns a value
162+
- **"/opt/sophos-av/bin/savlog --maxage=7 | grep -i "Scheduled scan .\* completed" | tail -1"**, returns a value
163163

164-
- **"/opt/sophos-av/bin/savlog --maxage=7 | grep "scan finished"** | tail -1", returns a value
164+
- **"/opt/sophos-av/bin/savlog --maxage=7 | grep "scan finished"** | tail -1", returns a value
165165

166166
- **"/opt/sophos-av/bin/savdstatus --lastupdate"** returns lastUpdate, which should be <= 7 days
167167

168168
- **"/opt/sophos-av/bin/savdstatus -v"** is equal to **"On-access scanning is running"**
169169

170-
- **"/opt/sophos-av/bin/savconfig get LiveProtection"** returns enabled
170+
- **"/opt/sophos-av/bin/savconfig get LiveProtection"** returns enabled
171171

172172
## Troubleshoot and support
173173

174174
### Troubleshoot
175175

176-
Microsoft Antimalware extension logs are available at:
176+
Microsoft Antimalware extension logs are available at:
177177
**%Systemdrive%\WindowsAzure\Logs\Plugins\Microsoft.Azure.Security.IaaSAntimalware(Or PaaSAntimalware)\1.5.5.x(version#)\CommandExecution.log**
178178

179179
### Support

articles/security-center/security-center-file-integrity-monitoring-baselines.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Compare baselines with File Integrity Monitoring in Azure Security Center | Microsoft Docs
2+
title: File Integrity Monitoring in Azure Security Center
33
description: Learn how to compare baselines with File Integrity Monitoring in Azure Security Center.
44
services: security-center
55
documentationcenter: na

articles/security-center/security-center-get-started.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Azure Security Center Quickstart - Onboard your Azure subscription to Security Center Standard | Microsoft Docs
2+
title: Upgrade to Standard tier - Azure Security Center
33
description: This quickstart shows you how to upgrade to Security Center's Standard pricing tier for additional security.
44
services: security-center
55
documentationcenter: na

articles/security-center/security-center-info-protection-policy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Customizing the SQL information protection policy in Azure Security Center | Microsoft Docs
2+
title: Customize SQL information protection - Azure Security Center
33
description: Learn how to customize information protection policies in Azure Security Center.
44
services: security-center
55
documentationcenter: na

0 commit comments

Comments
 (0)