Merge pull request #108344 from jameshkramer/1598649-meta-title-fixes

US 1698649 meta titles and misc cleanup

Author: GitHubber17

articles/asc-for-iot/TOC.yml

@@ -66,7 +66,7 @@
     - name: Local configuration C
       href: azure-iot-security-local-configuration-c.md
     - name: Local configuration C#
-      href: azure-iot-security-local-configuration-csharp.md 
+      href: azure-iot-security-local-configuration-csharp.md
   - name: Deploy Edge security module
     href: how-to-deploy-edge.md
   - name: Configure security agents

articles/asc-for-iot/architecture.md

@@ -1,5 +1,5 @@
 ---
-title: Understanding Azure Security Center for IoT solution architecture| Microsoft Docs
+title: Solution architecture
 description: Learn about the flow of information in the Azure Security Center for IoT service.
 services: asc-for-iot
 ms.service: asc-for-iot
@@ -16,41 +16,44 @@ ms.tgt_pltfrm: na
 ms.workload: na
 ms.date: 07/23/2019
 ms.author: mlottner
-
 ---
+
 # Azure Security Center for IoT architecture
 
-This article explains the functional system architecture of the Azure Security Center for IoT solution. 
+This article explains the functional system architecture of the Azure Security Center for IoT solution.
 
 ## Azure Security Center for IoT components
 
 Azure Security Center for IoT is composed of the following components:
+
 - IoT Hub integration
 - Device agents (optional)
 - Send security message SDK
 - Analytics pipeline
- 
+
 ### Azure Security Center for IoT workflows
 
-Azure Security Center for IoT works in one of two feature workflows: Built-in and Enhanced  
+Azure Security Center for IoT works in one of two feature workflows: Built-in and Enhanced
 
 ### Built-in
-In **Built-in** mode, Azure Security Center for IoT is enabled when you elect to turn on the **Security** option in your IoT Hub. Offering real-time monitoring, recommendations and alerts, Built-in mode offers single-step device visibility and unmatched security. Build-in mode does not require agent installation on any devices and uses advanced analytics on logged activities to analyze and protect your field device. 
 
-### Enhanced 
+In **Built-in** mode, Azure Security Center for IoT is enabled when you elect to turn on the **Security** option in your IoT Hub. Offering real-time monitoring, recommendations and alerts, Built-in mode offers single-step device visibility and unmatched security. Build-in mode does not require agent installation on any devices and uses advanced analytics on logged activities to analyze and protect your field device.
+
+### Enhanced
+
 In **Enhanced** mode, after turning on the **Security** option in your IoT Hub and installing Azure Security Center for IoT device agents on your devices, the agents collect, aggregate and analyze raw security events from your devices. Raw security events can include IP connections, process creation, user logins, and other security-relevant information. Azure Security Center for IoT device agents also handle event aggregation to help avoid high network throughput. The agents are highly customizable, allowing you to use them for specific tasks, such as sending only important information at the fastest SLA, or for aggregating extensive security information and context into larger segments, avoiding higher service costs.
 
 ![Azure Security Center for IoT architecture](./media/architecture/azure-iot-security-architecture.png)
- 
+
 Device agents, and other applications use the **Azure send security message SDK** to send security information into Azure IoT Hub. IoT Hub picks up this information and forwards it to the Azure Security Center for IoT service.
 
 Once the Azure Security Center for IoT service is enabled, in addition to the forwarded data, IoT Hub also sends out all of its internal data for analysis by Azure Security Center for IoT. This data includes device-cloud operation logs, device identities, and Hub configuration. All of this information helps to create the Azure Security Center for IoT analytics pipeline.
- 
+
 Azure Security Center for IoT analytics pipeline also receives additional threat intelligence streams from various sources within Microsoft and Microsoft partners. The Azure Security Center for IoT entire analytics pipeline works with every customer configuration made on the service (such as custom alerts and use of the send security message SDK).
- 
+
 Using the analytics pipeline, Azure Security Center for IoT combines all of the streams of information to generate actionable recommendations and alerts. The pipeline contains both custom rules created by security researchers and experts as well as   machine learning models searching for deviation from standard device behavior and risk analysis.
- 
-Azure Security Center for IoT recommendations and alerts (analytics pipeline output) is written to the Log Analytics workspace of each customer. Including the raw events in the workspace as well as the alerts and recommendations enables deep dive investigations and queries using the exact details of the suspicious activities detected.  
+
+Azure Security Center for IoT recommendations and alerts (analytics pipeline output) is written to the Log Analytics workspace of each customer. Including the raw events in the workspace as well as the alerts and recommendations enables deep dive investigations and queries using the exact details of the suspicious activities detected.
 
 ## Next steps
 

articles/asc-for-iot/azure-iot-security-local-configuration-c.md

@@ -1,5 +1,5 @@
 ---
-title: Understanding Azure Security Center for agent local configurations for C | Microsoft Docs
+title: Security agent local configuration (C)
 description: Learn about Azure Security Center for agent local configurations for C.
 services: asc-for-iot
 ms.service: asc-for-iot
@@ -16,22 +16,22 @@ ms.tgt_pltfrm: na
 ms.workload: na
 ms.date: 07/26/2019
 ms.author: mlottner
-
 ---
 
 # Understanding the LocalConfiguration.json file - C agent
 
 The Azure Security Center for IoT security agent uses configurations from a local configuration file.
 The security agent reads the configuration once,  at agent start-up.
 The configuration found in the local configuration file contains authentication configuration and other agent related configurations.
-The file contains configurations in "Key-Value" pairs in JSON notation and the configurations get populated when the agent is installed. 
+The file contains configurations in "Key-Value" pairs in JSON notation and the configurations get populated when the agent is installed.
 
 By default, the file is located at: /var/ASCIoTAgent/LocalConfiguration.json
 
-Changes to the configuration file take place when the agent is restarted. 
+Changes to the configuration file take place when the agent is restarted.
 
 ## Security agent configurations for C
-| Configuration Name | Possible values | Details | 
+
+| Configuration Name | Possible values | Details |
 |:-----------|:---------------|:--------|
 | AgentId | GUID | The agent Unique identifier |
 | TriggerdEventsInterval | ISO8601 string | Scheduler interval for triggered events collection |
@@ -50,6 +50,7 @@ Changes to the configuration file take place when the agent is restarted.
 | DiagnosticEventMinimumSeverity | 0 <= number <= 4 | log messages equal and above this severity will be sent as diagnostic events (0 is the lowest severity) |
 
 ## Security agent configurations code example
+
 ```JSON
 {
     "Configuration" : {
@@ -76,10 +77,11 @@ Changes to the configuration file take place when the agent is restarted.
 ```
 
 ## Next steps
+
 - Read the Azure Security Center for IoT service [Overview](overview.md)
 - Learn more about Azure Security Center for IoT [Architecture](architecture.md)
 - Enable the Azure Security Center for IoT [service](quickstart-onboard-iot-hub.md)
 - Read the Azure Security Center for IoT service [FAQ](resources-frequently-asked-questions.md)
 - Learn how to access [raw security data](how-to-security-data-access.md)
 - Understand [recommendations](concept-recommendations.md)
-- Understand security [alerts](concept-security-alerts.md)
+- Understand security [alerts](concept-security-alerts.md)

articles/asc-for-iot/azure-iot-security-local-configuration-csharp.md

@@ -1,5 +1,5 @@
 ---
-title: Understanding Azure Security Center for IoT security agent local configuration file for C# | Microsoft Docs
+title: Security agent local configuration (C#)
 description: Learn more about the Azure Security Center for IoT security service, security agent local configuration file for C#.
 services: asc-for-iot
 ms.service: asc-for-iot
@@ -16,12 +16,10 @@ ms.tgt_pltfrm: na
 ms.workload: na
 ms.date: 07/26/2019
 ms.author: mlottner
-
 ---
 
 # Understanding the local configuration file (C# agent)
 
-
 The Azure Security Center for IoT security agent uses configurations from a local configuration file.
 
 The security agent reads the configuration file once when the agent starts up. Configurations found in the local configuration file contains both authentication configuration and other agent related configurations.
@@ -32,18 +30,21 @@ The C# security agent uses multiple configuration files:
 - **Authentication.config** - Authentication related configuration (including authentication details).
 - **SecurityIotInterface.config** - IoT related configurations.
 
-The configuration files contain the default configuration. Authentication configuration is populated during agent installation and changes to the configuration file are made when the agent is restarted. 
+The configuration files contain the default configuration. Authentication configuration is populated during agent installation and changes to the configuration file are made when the agent is restarted.
 
 ## Configuration file location
+
 For Linux:
+
 - Operating system configuration files are located in `/var/ASCIoTAgent`.
 
 For Windows:
-- Operating system configuration files are located within the directory of the security agent. 
+
+- Operating system configuration files are located within the directory of the security agent.
 
 ### General.config configurations
 
-| Configuration Name | Possible values | Details | 
+| Configuration Name | Possible values | Details |
 |:-----------|:---------------|:--------|
 | agentId | GUID | Agent unique identifier |
 | readRemoteConfigurationTimeout | TimeSpan | Time period for fetching remote configuration from IoT Hub. If the agent can't fetch the configuration within the specified time, the operation will time out.|
@@ -58,6 +59,7 @@ For Windows:
 | defaultEventPriority | "High", "Low", "Off" | Default event priority. |
 
 ### General.config example
+
 ```XML
 <?xml version="1.0" encoding="utf-8"?>
 <General>
@@ -77,7 +79,7 @@ For Windows:
 
 ### Authentication.config
 
-| Configuration name | Possible values | Details | 
+| Configuration name | Possible values | Details |
 |:-----------|:---------------|:--------|
 | moduleName | string | Name of the security module identity. This name must correspond to the module identity name in the device. |
 | deviceId | string | ID of the device (as registered in Azure IoT Hub). || schedulerInterval | TimeSpan string | Internal scheduler interval. |
@@ -91,6 +93,7 @@ For Windows:
 |
 
 ### Authentication.config example
+
 ```XML
 <?xml version="1.0" encoding="utf-8"?>
 <Authentication>
@@ -105,14 +108,16 @@ For Windows:
   <add key="registrationId" value="d1"/>
 </Authentication>
 ```
+
 ### SecurityIotInterface.config
 
-| Configuration Name | Possible values | Details | 
+| Configuration Name | Possible values | Details |
 |:-----------|:---------------|:--------|
 | transportType | "Ampq" "Mqtt" | IoT Hub transport type. |
 |
 
 ### SecurityIotInterface.config example
+
 ```XML
 <ExternalInterface>
   <add key="facadeType"  value="Microsoft.Azure.Security.IoT.Agent.Common.SecurityIoTHubInterface, Security.Common" />
@@ -121,10 +126,11 @@ For Windows:
 ```
 
 ## Next steps
+
 - Read the Azure Security Center for IoT service [Overview](overview.md)
 - Learn more about Azure Security Center for IoT [Architecture](architecture.md)
 - Enable the Azure Security Center for IoT [service](quickstart-onboard-iot-hub.md)
 - Read the Azure Security Center for IoT service [FAQ](resources-frequently-asked-questions.md)
 - Learn how to access [raw security data](how-to-security-data-access.md)
 - Understand [recommendations](concept-recommendations.md)
-- Understand security [alerts](concept-security-alerts.md)
+- Understand security [alerts](concept-security-alerts.md)

articles/asc-for-iot/concept-baseline.md

@@ -1,7 +1,6 @@
 ---
-
-title: Understand Azure Security Center for IoT baseline| Microsoft Docs
-description: Learn about the concept of Azure Security Center for IoT baseline. 
+title: Baseline and custom checks
+description: Learn about the concept of Azure Security Center for IoT baseline.
 services: asc-for-iot
 ms.service: asc-for-iot
 documentationcenter: na
@@ -17,19 +16,19 @@ ms.tgt_pltfrm: na
 ms.workload: na
 ms.date: 10/07/2019
 ms.author: mlottner
-
 ---
+
 # Azure Security Center for IoT baseline and custom checks
 
 This article explains Azure Security Center for IoT baseline, and summarizes all associated properties of baseline custom checks.
 
 ## Baseline
 
-A baseline establishes standard behavior for each device and makes it easier to establish unusual behavior or deviation from expected norms.  
+A baseline establishes standard behavior for each device and makes it easier to establish unusual behavior or deviation from expected norms.
 
 ## Baseline custom checks
 
-Baseline custom checks establish a custom list of checks for each device baseline using the **Module identity twin** of the device. 
+Baseline custom checks establish a custom list of checks for each device baseline using the **Module identity twin** of the device.
 
 ## Setting baseline properties
 

articles/asc-for-iot/concept-customizable-security-alerts.md

@@ -1,5 +1,5 @@
 ---
-title: Customizable security alert guide for Azure Security Center for IoT| Microsoft Docs
+title: Customizable security alerts
 description: Learn about customizable security alerts and recommended remediation using Azure Security Center for IoT features and service.
 services: asc-for-iot
 ms.service: asc-for-iot
@@ -15,19 +15,17 @@ ms.tgt_pltfrm: na
 ms.workload: na
 ms.date: 03/04/2020
 ms.author: mlottner
-
 ---
+
 # Azure Security Center for IoT security alerts
 
 Azure Security Center for IoT continuously analyzes your IoT solution using advanced analytics and threat intelligence to alert you to malicious activity.
 
-We encourage you to create custom alerts based on your knowledge of expected device behavior to ensure alerts act as the most efficient indicators of potential compromise in your unique organizational deployment and landscape. 
+We encourage you to create custom alerts based on your knowledge of expected device behavior to ensure alerts act as the most efficient indicators of potential compromise in your unique organizational deployment and landscape.
 
 The following list of Azure Security Center for IoT alerts are definable by you based on your expected IoT Hub and/or device behavior. For more details about how to customize each alert, see [create custom alerts](quickstart-create-custom-alerts.md).
 
-## IoT Hub alerts available for customization 
-
-
+## IoT Hub alerts available for customization
 
 | Severity | Alert name | Data source | Description | Suggested remediation|
 |---|---|---|---|---|
@@ -47,7 +45,7 @@ The following list of Azure Security Center for IoT alerts are definable by you
 | Low      | Custom alert - number of unauthorized operations is outside the allowed range  | IoT Hub     | The amount of unauthorized operations within a specific time window is outside the currently configured and allowable range.|
 |
 
-## Agent alerts available for customization 
+## Agent alerts available for customization
 
 | Severity | Alert name | Data source | Description | Suggested remediation|
 |---|---|---|---|---|
@@ -63,4 +61,4 @@ The following list of Azure Security Center for IoT alerts are definable by you
 - Learn how to [customize an alert](quickstart-create-custom-alerts.md)
 - Azure Security Center for IoT service [Overview](overview.md)
 - Learn how to [Access your security data](how-to-security-data-access.md)
-- Learn more about [Investigating a device](how-to-investigate-device.md)
+- Learn more about [Investigating a device](how-to-investigate-device.md)

articles/asc-for-iot/concept-pricing.md

@@ -1,7 +1,6 @@
 ---
-
-title: Understand Azure Security Center for IoT costs| Microsoft Docs
-description: Learn about the costs associated with Azure Security Center for IoT, and how to  control them. 
+title: Pricing and associated costs
+description: Learn about the costs associated with Azure Security Center for IoT, and how to control them.
 services: asc-for-iot
 ms.service: asc-for-iot
 documentationcenter: na
@@ -17,8 +16,8 @@ ms.tgt_pltfrm: na
 ms.workload: na
 ms.date: 09/27/2019
 ms.author: mlottner
-
 ---
+
 # Pricing and associated costs
 
 This article explains Azure Security Center for IoT pricing model, summarizes all associated costs and explains how to manage them.
@@ -31,14 +30,12 @@ The Azure Security Center for IoT pricing model is comprised of two parts, and i
 
 - Cost by message - enhanced security capabilities based on security messages from IoT Edge or leaf devices.
 
-
 For more information, see [Security Center pricing](https://azure.microsoft.com/pricing/details/security-center/).
 
 ## Associated costs
 
 Azure Security Center for IoT has associated costs, which are not part of the direct pricing:
 
-
 - Log Analytics storage costs
 
 You can reduce associated costs by opting out of certain solution features. Opt out by changing your settings.
@@ -47,9 +44,9 @@ To change your settings:
 
 1. Open IoT Hub.
 
-2. Under **Security**, click **Overview**.
+1. Under **Security**, click **Overview**.
 
-3. Click **Settings**.
+1. Click **Settings**.
 
 The following table provides a summary of associated costs and implications of each option.
 
@@ -61,8 +58,8 @@ The following table provides a summary of associated costs and implications of e
 |
 
 >[!Important]
-> Opting out has severe implications to Azure Security Center for IoT security feature availability. 
-  
+> Opting out has severe implications to Azure Security Center for IoT security feature availability.
+
 | Opt out | Implications |
 | --- | --- |
 | _Twin metadata collection_ | Disable [custom alerts](quickstart-create-custom-alerts.md) |
@@ -72,7 +69,6 @@ The following table provides a summary of associated costs and implications of e
 | | Details on [alert](concept-security-alerts.md) and [recommendation](concept-recommendations.md) investigations are not available |
 |
 
-
 ## See also
 
 - Access your [raw security data](how-to-security-data-access.md)