Merge pull request #125157 from ArieHein/Spelling-Wave-37

Court72 · web-flow · commit 630720024d39 · 2024-12-16T10:27:59.000-07:00
Spelling Fixes
diff --git a/articles/sentinel/data-connectors/microsoft-exchange-message-tracking-logs.md b/articles/sentinel/data-connectors/microsoft-exchange-message-tracking-logs.md
@@ -39,14 +39,14 @@ MessageTrackingLog_CL
 To integrate with Microsoft Exchange Message Tracking Logs make sure you have: 
 
 - **Azure Log Analytics will be deprecated**: Azure Log Analytics will be deprecated, to collect data from non-Azure VMs, Azure Arc is recommended. [Learn more](/azure/azure-monitor/agents/azure-monitor-agent-install?tabs=ARMAgentPowerShell,PowerShellWindows,PowerShellWindowsArc,CLIWindows,CLIWindowsArc)
-- **Detailled documentation**: >**NOTE:** Detailled documentation on Installation procedure and usage can be found [here](https://aka.ms/MicrosoftExchangeSecurityGithub)
+- **Detailed documentation**: >**NOTE:** Detailed documentation on Installation procedure and usage can be found [here](https://aka.ms/MicrosoftExchangeSecurityGithub)
 
 
 ## Vendor installation instructions
 
 
 > [!NOTE]
-   >  This solution is based on options. This allows you to choose which data will be ingest as some options can generate a very high volume of data. Depending on what you want to collect, track in your Workbooks, Analytics Rules, Hunting capabilities you will choose the option(s) you will deploy. Each options are independant for one from the other. To learn more about each option: ['Microsoft Exchange Security' wiki](https://aka.ms/ESI_DataConnectorOptions)
+   >  This solution is based on options. This allows you to choose which data will be ingest as some options can generate a very high volume of data. Depending on what you want to collect, track in your Workbooks, Analytics Rules, Hunting capabilities you will choose the option(s) you will deploy. Each options are independent for one from the other. To learn more about each option: ['Microsoft Exchange Security' wiki](https://aka.ms/ESI_DataConnectorOptions)
 
 >This Data Connector is the **option 6** of the wiki.
 
diff --git a/articles/sentinel/data-connectors/mimecast-audit-authentication.md b/articles/sentinel/data-connectors/mimecast-audit-authentication.md
@@ -96,7 +96,7 @@ Deploy the Mimecast Audit & Authentication Data Connector:
  - appName: Unique string that will be used as id for the app in Azure platform
  - objectId: Azure portal ---> Azure Active Directory ---> more info ---> Profile -----> Object ID
  - appInsightsLocation(default): westeurope
- - mimecastEmail: Email address of dedicated user for this integraion
+ - mimecastEmail: Email address of dedicated user for this integration
  - mimecastPassword: Password for dedicated user
  - mimecastAppId: Application Id from the Microsoft Sentinel app registered with Mimecast
  - mimecastAppKey: Application Key from the Microsoft Sentinel app registered with Mimecast
diff --git a/articles/sentinel/data-connectors/mimecast-intelligence-for-microsoft-microsoft-sentinel.md b/articles/sentinel/data-connectors/mimecast-intelligence-for-microsoft-microsoft-sentinel.md
@@ -97,7 +97,7 @@ Enable Mimecast Intelligence for Microsoft - Microsoft Sentinel Connector:
  - appName: Unique string that will be used as id for the app in Azure platform
  - objectId: Azure portal ---> Azure Active Directory ---> more info ---> Profile -----> Object ID
  - appInsightsLocation(default): westeurope
- - mimecastEmail: Email address of dedicated user for this integraion
+ - mimecastEmail: Email address of dedicated user for this integration
  - mimecastPassword: Password for dedicated user
  - mimecastAppId: Application Id from the Microsoft Sentinel app registered with Mimecast
  - mimecastAppKey: Application Key from the Microsoft Sentinel app registered with Mimecast
diff --git a/articles/sentinel/data-connectors/mimecast-secure-email-gateway.md b/articles/sentinel/data-connectors/mimecast-secure-email-gateway.md
@@ -104,7 +104,7 @@ Deploy the Mimecast Secure Email Gateway Data Connector:
  - appName: Unique string that will be used as id for the app in Azure platform
  - objectId: Azure portal ---> Azure Active Directory ---> more info ---> Profile -----> Object ID
  - appInsightsLocation(default): westeurope
- - mimecastEmail: Email address of dedicated user for this integraion
+ - mimecastEmail: Email address of dedicated user for this integration
  - mimecastPassword: Password for dedicated user
  - mimecastAppId: Application Id from the Microsoft Sentinel app registered with Mimecast
  - mimecastAppKey: Application Key from the Microsoft Sentinel app registered with Mimecast
diff --git a/articles/sentinel/data-connectors/mimecast-targeted-threat-protection.md b/articles/sentinel/data-connectors/mimecast-targeted-threat-protection.md
@@ -120,7 +120,7 @@ Deploy the Mimecast Targeted Threat Protection Data Connector:
  - appName: Unique string that will be used as id for the app in Azure platform
  - objectId: Azure portal ---> Azure Active Directory ---> more info ---> Profile -----> Object ID
  - appInsightsLocation(default): westeurope
- - mimecastEmail: Email address of dedicated user for this integraion
+ - mimecastEmail: Email address of dedicated user for this integration
  - mimecastPassword: Password for dedicated user
  - mimecastAppId: Application Id from the Microsoft Sentinel app registered with Mimecast
  - mimecastAppKey: Application Key from the Microsoft Sentinel app registered with Mimecast
diff --git a/articles/sentinel/data-connectors/mulesoft-cloudhub.md b/articles/sentinel/data-connectors/mulesoft-cloudhub.md
@@ -79,7 +79,7 @@ To integrate with MuleSoft Cloudhub (using Azure Functions) make sure you have:
 
 **Option 1 - Azure Resource Manager (ARM) Template**
 
-Use this method for automated deployment of the MuleSoft Cloudhub data connector using an ARM Tempate.
+Use this method for automated deployment of the MuleSoft Cloudhub data connector using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
diff --git a/articles/sentinel/data-connectors/netclean-proactive-incidents.md b/articles/sentinel/data-connectors/netclean-proactive-incidents.md
@@ -51,7 +51,7 @@ Netclean_Incidents_CL
   In your Logic app designer, click +New Step and search for “Azure Log Analytics Data Collector” click it and select “Send Data”  
  Enter the Custom Log Name: Netclean_Incidents and a dummy value in the Json request body and click save 
  Go to code view on the top ribbon and scroll down to line ~100  it should start with "Body"  
- replace the line entirly with: 
+ replace the line entirely with: 
  
  "body": "{\n\"Hostname\":\"@{variables('machineName')}\",\n\"agentType\":\"@{triggerBody()['value']['agent']['type']}\",\n\"Identifier\":\"@{triggerBody()?['key']?['identifier']}\",\n\"type\":\"@{triggerBody()?['key']?['type']}\",\n\"version\":\"@{triggerBody()?['value']?['incidentVersion']}\",\n\"foundTime\":\"@{triggerBody()?['value']?['foundTime']}\",\n\"detectionMethod\":\"@{triggerBody()?['value']?['detectionHashType']}\",\n\"agentInformatonIdentifier\":\"@{triggerBody()?['value']?['device']?['identifier']}\",\n\"osVersion\":\"@{triggerBody()?['value']?['device']?['operatingSystemVersion']}\",\n\"machineName\":\"@{variables('machineName')}\",\n\"microsoftCultureId\":\"@{triggerBody()?['value']?['device']?['microsoftCultureId']}\",\n\"timeZoneId\":\"@{triggerBody()?['value']?['device']?['timeZoneName']}\",\n\"microsoftGeoId\":\"@{triggerBody()?['value']?['device']?['microsoftGeoId']}\",\n\"domainname\":\"@{variables('domain')}\",\n\"Agentversion\":\"@{triggerBody()['value']['agent']['version']}\",\n\"Agentidentifier\":\"@{triggerBody()['value']['identifier']}\",\n\"loggedOnUsers\":\"@{variables('Usernames')}\",\n\"size\":\"@{triggerBody()?['value']?['file']?['size']}\",\n\"creationTime\":\"@{triggerBody()?['value']?['file']?['creationTime']}\",\n\"lastAccessTime\":\"@{triggerBody()?['value']?['file']?['lastAccessTime']}\",\n\"lastWriteTime\":\"@{triggerBody()?['value']?['file']?['lastModifiedTime']}\",\n\"sha1\":\"@{triggerBody()?['value']?['file']?['calculatedHashes']?['sha1']}\",\n\"nearbyFiles_sha1\":\"@{variables('nearbyFiles_sha1s')}\",\n\"externalIP\":\"@{triggerBody()?['value']?['device']?['resolvedExternalIp']}\",\n\"domain\":\"@{variables('domain')}\",\n\"hasCollectedNearbyFiles\":\"@{variables('hasCollectedNearbyFiles')}\",\n\"filePath\":\"@{replace(triggerBody()['value']['file']['path'], '\\', '\\\\')}\",\n\"m365WebUrl\":\"@{triggerBody()?['value']?['file']?['microsoft365']?['webUrl']}\",\n\"m365CreatedBymail\":\"@{triggerBody()?['value']?['file']?['createdBy']?['graphIdentity']?['user']?['mail']}\",\n\"m365LastModifiedByMail\":\"@{triggerBody()?['value']?['file']?['lastModifiedBy']?['graphIdentity']?['user']?['mail']}\",\n\"m365LibraryId\":\"@{triggerBody()?['value']?['file']?['microsoft365']?['library']?['id']}\",\n\"m365LibraryDisplayName\":\"@{triggerBody()?['value']?['file']?['microsoft365']?['library']?['displayName']}\",\n\"m365Librarytype\":\"@{triggerBody()?['value']?['file']?['microsoft365']?['library']?['type']}\",\n\"m365siteid\":\"@{triggerBody()?['value']?['file']?['microsoft365']?['site']?['id']}\",\n\"m365sitedisplayName\":\"@{triggerBody()?['value']?['file']?['microsoft365']?['site']?['displayName']}\",\n\"m365sitename\":\"@{triggerBody()?['value']?['file']?['microsoft365']?['parent']?['name']}\",\n\"countOfAllNearByFiles\":\"@{variables('countOfAllNearByFiles')}\",\n\n}",  
  click save   
@@ -64,7 +64,7 @@ Netclean_Incidents_CL
 Ingest data using a api function. please use the script found on [Send log data to Azure Monitor by using the HTTP Data Collector API](/azure/azure-monitor/logs/data-collector-api?tabs=powershell)  
 Replace the CustomerId and SharedKey values with your values
 Replace the content in $json variable to the sample data.
-Set the LogType varible to **Netclean_Incidents_CL**
+Set the LogType variable to **Netclean_Incidents_CL**
 Run the script
 
 
diff --git a/articles/sentinel/data-connectors/netskope.md b/articles/sentinel/data-connectors/netskope.md
@@ -86,7 +86,7 @@ To integrate with Netskope (using Azure Functions) make sure you have:
 
 Option 1 - Azure Resource Manager (ARM) Template
 
-This method provides an automated deployment of the Netskope connector using an ARM Tempate.
+This method provides an automated deployment of the Netskope connector using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
@@ -111,7 +111,7 @@ This method provides the step-by-step instructions to deploy the Netskope connec
 1.  From the Azure Portal, navigate to [Function App](https://portal.azure.com/#blade/HubsExtension/BrowseResource/resourceType/Microsoft.Web%2Fsites/kind/functionapp), and select **+ Add**.
 2. In the **Basics** tab, ensure Runtime stack is set to **Powershell Core**. 
 3. In the **Hosting** tab, ensure the **Consumption (Serverless)** plan type is selected.
-4. Make other preferrable configuration changes, if needed, then click **Create**.
+4. Make other preferable configuration changes, if needed, then click **Create**.
 
 
 **2. Import Function App Code**
@@ -136,9 +136,9 @@ This method provides the step-by-step instructions to deploy the Netskope connec
 		timeInterval
 		logTypes
 		logAnalyticsUri (optional)
-> - Enter the URI that corresponds to your region. The `uri` value must follow the following schema: `https://<Tenant Name>.goskope.com` - There is no need to add subsquent parameters to the Uri, the Function App will dynamically append the parameteres in the proper format.
+> - Enter the URI that corresponds to your region. The `uri` value must follow the following schema: `https://<Tenant Name>.goskope.com` - There is no need to add subsequent parameters to the Uri, the Function App will dynamically append the parameters in the proper format.
 > - Set the `timeInterval` (in minutes) to the default value of `5` to correspond to the default Timer Trigger of every `5` minutes. If the time interval needs to be modified, it is recommended to change the Function App Timer Trigger accordingly to prevent overlapping data ingestion. 
-> - Set the `logTypes` to `alert, page, application, audit, infrastructure, network` - This list represents all the avaliable log types. Select the log types based on logging requirements, seperating each by a single comma.
+> - Set the `logTypes` to `alert, page, application, audit, infrastructure, network` - This list represents all the available log types. Select the log types based on logging requirements, separating each by a single comma.
 > - Note: If using Azure Key Vault, use the`@Microsoft.KeyVault(SecretUri={Security Identifier})`schema in place of the string values. Refer to [Key Vault references documentation](/azure/app-service/app-service-key-vault-references) for further details. 
 > - Use logAnalyticsUri to override the log analytics API endpoint for dedicated cloud. For example, for public cloud, leave the value empty; for Azure GovUS cloud environment, specify the value in the following format: `https://<CustomerId>.ods.opinsights.azure.us`.
 4. Once all application settings have been entered, click **Save**.
diff --git a/articles/sentinel/data-connectors/nxlog-aix-audit.md b/articles/sentinel/data-connectors/nxlog-aix-audit.md
@@ -32,7 +32,7 @@ NXLog_parsed_AIX_Audit_view
 
    | summarize count() by EventType
 
-   | render piechart title="AIX Audit event type distributon"
+   | render piechart title="AIX Audit event type distribution"
    ```
 
 **Highest event per second (EPS) AIX Audit event types**
diff --git a/articles/sentinel/data-connectors/oracle-cloud-infrastructure.md b/articles/sentinel/data-connectors/oracle-cloud-infrastructure.md
@@ -69,7 +69,7 @@ To integrate with Oracle Cloud Infrastructure (using Azure Functions) make sure
 7. Select Source: Logging
 8. Select Target: Streaming
 9. (Optional) Configure *Log Group*, *Filters* or use custom search query to stream only logs that you need.
-10. Configure Target - select the strem created before.
+10. Configure Target - select the stream created before.
 11. Click *Create*
 
 Check the documentation to get more information about [Streaming](https://docs.oracle.com/en-us/iaas/Content/Streaming/home.htm) and [Service Connectors](https://docs.oracle.com/en-us/iaas/Content/service-connector-hub/home.htm).
diff --git a/articles/sentinel/data-connectors/proofpoint-on-demand-email-security.md b/articles/sentinel/data-connectors/proofpoint-on-demand-email-security.md
@@ -85,7 +85,7 @@ To integrate with Proofpoint On Demand Email Security (using Azure Functions) ma
 
 Option 1 - Azure Resource Manager (ARM) Template
 
-Use this method for automated deployment of the Proofpoint On Demand Email Security data connector using an ARM Tempate.
+Use this method for automated deployment of the Proofpoint On Demand Email Security data connector using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
diff --git a/articles/sentinel/data-connectors/qualys-vulnerability-management.md b/articles/sentinel/data-connectors/qualys-vulnerability-management.md
@@ -11,7 +11,7 @@ ms.collection: sentinel-data-connector
 
 # Qualys Vulnerability Management (using Azure Functions) connector for Microsoft Sentinel
 
-The [Qualys Vulnerability Management (VM)](https://www.qualys.com/apps/vulnerability-management/) data connector provides the capability to ingest vulnerability host detection data into Microsoft Sentinel through the Qualys API. The connector provides visibility into host detection data from vulerability scans. This connector provides Microsoft Sentinel the capability to view dashboards, create custom alerts, and improve investigation 
+The [Qualys Vulnerability Management (VM)](https://www.qualys.com/apps/vulnerability-management/) data connector provides the capability to ingest vulnerability host detection data into Microsoft Sentinel through the Qualys API. The connector provides visibility into host detection data from vulnerability scans. This connector provides Microsoft Sentinel the capability to view dashboards, create custom alerts, and improve investigation 
 
 This is autogenerated content. For changes, contact the solution provider.
 
@@ -27,7 +27,7 @@ This is autogenerated content. For changes, contact the solution provider.
 
 ## Query samples
 
-**Top 10 Qualys V2 Vulerabilities detected**
+**Top 10 Qualys V2 Vulnerabilities detected**
 
    ```kusto
 QualysHostDetectionV2_CL
@@ -39,7 +39,7 @@ QualysHostDetectionV2_CL
    | top 10 by count_
    ```
 
-**Top 10 Vulerabilities detected**
+**Top 10 Vulnerabilities detected**
 
    ```kusto
 QualysHostDetection_CL
@@ -96,7 +96,7 @@ To integrate with Qualys Vulnerability Management (using Azure Functions) make s
 
 Option 1 - Azure Resource Manager (ARM) Template
 
-Use this method for automated deployment of the Qualys VM connector using an ARM Tempate.
+Use this method for automated deployment of the Qualys VM connector using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
@@ -119,7 +119,7 @@ Use the following step-by-step instructions to deploy the Quayls VM connector ma
 1.  From the Azure Portal, navigate to [Function App](https://portal.azure.com/#blade/HubsExtension/BrowseResource/resourceType/Microsoft.Web%2Fsites/kind/functionapp), and select **+ Add**.
 2. In the **Basics** tab, ensure Runtime stack is set to **Powershell Core**. 
 3. In the **Hosting** tab, ensure the **Consumption (Serverless)** plan type is selected.
-4. Make other preferrable configuration changes, if needed, then click **Create**.
+4. Make other preferable configuration changes, if needed, then click **Create**.
 
 
 **2. Import Function App Code**
@@ -146,7 +146,7 @@ Use the following step-by-step instructions to deploy the Quayls VM connector ma
 		timeInterval
 		logAnalyticsUri (optional)
 > - Enter the URI that corresponds to your region. The complete list of API Server URLs can be [found here](https://www.qualys.com/docs/qualys-api-vmpc-user-guide.pdf#G4.735348). The `uri` value must follow the following schema: `https://<API Server>/api/2.0/fo/asset/host/vm/detection/?action=list&vm_processed_after=` -- There is no need to add a time suffix to the URI, the Function App will dynamically append the Time Value to the URI in the proper format.
-> - Add any additional filter parameters, for the `filterParameters` variable, that need to be appended to the URI. Each parameter should be seperated by an "&" symbol and should not include any spaces.
+> - Add any additional filter parameters, for the `filterParameters` variable, that need to be appended to the URI. Each parameter should be separated by an "&" symbol and should not include any spaces.
 > - Set the `timeInterval` (in minutes) to the value of `5` to correspond to the Timer Trigger of every `5` minutes. If the time interval needs to be modified, it is recommended to change the Function App Timer Trigger accordingly to prevent overlapping data ingestion.
 > - Note: If using Azure Key Vault, use the`@Microsoft.KeyVault(SecretUri={Security Identifier})`schema in place of the string values. Refer to [Key Vault references documentation](/azure/app-service/app-service-key-vault-references) for further details.
 > - Use logAnalyticsUri to override the log analytics API endpoint for dedicated cloud. For example, for public cloud, leave the value empty; for Azure GovUS cloud environment, specify the value in the following format: `https://<CustomerId>.ods.opinsights.azure.us`.
@@ -159,7 +159,7 @@ Due to the potentially large amount of Qualys host detection data being ingested
 
 1. In the Function App, select the Function App Name and select the **App Service Editor** blade.
 2. Click **Go** to open the editor, then select the **host.json** file under the **wwwroot** directory.
-3. Add the line `"functionTimeout": "00:10:00",` above the `managedDependancy` line 
+3. Add the line `"functionTimeout": "00:10:00",` above the `managedDependency` line 
 4. Ensure **SAVED** appears on the top right corner of the editor, then exit the editor.
 
 > NOTE: If a longer timeout duration is required, consider upgrading to an [App Service Plan](/azure/azure-functions/functions-scale#timeout)
diff --git a/articles/sentinel/data-connectors/sentinelone.md b/articles/sentinel/data-connectors/sentinelone.md
@@ -84,7 +84,7 @@ To integrate with SentinelOne (using Azure Functions) make sure you have:
 
 Option 1 - Azure Resource Manager (ARM) Template
 
-Use this method for automated deployment of the SentinelOne Audit data connector using an ARM Tempate.
+Use this method for automated deployment of the SentinelOne Audit data connector using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
diff --git a/articles/sentinel/data-connectors/slack-audit.md b/articles/sentinel/data-connectors/slack-audit.md
@@ -67,7 +67,7 @@ To integrate with Slack Audit (using Azure Functions) make sure you have:
 
 Option 1 - Azure Resource Manager (ARM) Template
 
-Use this method for automated deployment of the Slack Audit data connector using an ARM Tempate.
+Use this method for automated deployment of the Slack Audit data connector using an ARM Template.
 
 1. Select the **Deploy to Azure** button below. 
 
diff --git a/articles/sentinel/data-connectors/thehive-project-thehive.md b/articles/sentinel/data-connectors/thehive-project-thehive.md
@@ -61,7 +61,7 @@ To integrate with TheHive Project - TheHive (using Azure Functions) make sure yo
 
  Follow the [instructions](https://docs.thehive-project.org/thehive/installation-and-configuration/configuration/webhooks/) to configure Webhooks.
 
-1. Authentication method is *Beared Auth*.
+1. Authentication method is *Bearer Auth*.
 2. Generate the **TheHiveBearerToken** according to your password policy.
 3. Setup Webhook notifications in the *application.conf* file including **TheHiveBearerToken** parameter.
 
diff --git a/articles/sentinel/data-connectors/transmit-security-connector.md b/articles/sentinel/data-connectors/transmit-security-connector.md
@@ -79,7 +79,7 @@ Before deploying the Transmit Security data connector, have the Workspace ID and
 
 Option 1 - Azure Resource Manager (ARM) Template
 
-Use this method for automated deployment of the Transmit Security Audit data connector using an ARM Tempate.
+Use this method for automated deployment of the Transmit Security Audit data connector using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
diff --git a/articles/sentinel/data-connectors/trend-vision-one.md b/articles/sentinel/data-connectors/trend-vision-one.md
diff --git a/articles/sentinel/data-connectors/vmware-carbon-black-cloud.md b/articles/sentinel/data-connectors/vmware-carbon-black-cloud.md
diff --git a/articles/sentinel/data-connectors/wiz.md b/articles/sentinel/data-connectors/wiz.md
diff --git a/articles/sentinel/data-connectors/workplace-from-facebook.md b/articles/sentinel/data-connectors/workplace-from-facebook.md
