Skip to content

Commit 6b25085

Browse files
authored
Merge pull request #294705 from Albertyang0/2025_02-Monthly-broken-links-fix-cwatson-cat
2025_02 - Fix monthly broken links - cwatson-cat
2 parents 109570f + bac894c commit 6b25085

8 files changed

+16
-18
lines changed

articles/sentinel/data-connectors/netskope-data-connector.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -271,4 +271,4 @@ Using the ARM template deploy the function apps for ingestion of Netskope events
271271

272272
## Next steps
273273

274-
For more information, go to the [related solution](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/netskope.netskope_mss?tab=Overview) in the Azure Marketplace.
274+
For more information, go to the [related solution](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/netskope.netskope-for-azure?tab=Overview) in the Azure Marketplace.

articles/sentinel/data-connectors/netskope-web-transactions-data-connector.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -153,4 +153,4 @@ Use the following step-by-step instructions to deploy the docker based data conn
153153

154154
## Next steps
155155

156-
For more information, go to the [related solution](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/netskope.netskope_mss?tab=Overview) in the Azure Marketplace.
156+
For more information, go to the [related solution](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/netskope.netskope-for-azure?tab=Overview) in the Azure Marketplace.

articles/sentinel/data-connectors/netskope.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -148,4 +148,4 @@ This method provides the step-by-step instructions to deploy the Netskope connec
148148

149149
## Next steps
150150

151-
For more information, go to the [related solution](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/netskope.netskope_mss?tab=Overview) in the Azure Marketplace.
151+
For more information, go to the [related solution](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/netskope.netskope-for-azure?tab=Overview) in the Azure Marketplace.

articles/sentinel/data-connectors/qualys-vm-knowledgebase.md

Lines changed: 9 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -58,13 +58,10 @@ To integrate with Qualys VM KnowledgeBase (using Azure Functions) make sure you
5858
## Vendor installation instructions
5959

6060

61-
**NOTE:** This data connector depends on a parser based on a Kusto Function to work as expected which is deployed as part of the solution. To view the function code in Log Analytics, open Log Analytics/Microsoft Sentinel Logs blade, click Functions and search for the alias QualysVM Knowledgebase and load the function code or click [here](https://aka.ms/sentinel-crowdstrikefalconendpointprotection-parser), on the second line of the query, enter the hostname(s) of your QualysVM Knowledgebase device(s) and any other unique identifiers for the logstream. The function usually takes 10-15 minutes to activate after solution installation/update.
62-
63-
64-
>This data connector depends on a parser based on a Kusto Function to work as expected. [Follow the steps](https://aka.ms/sentinel-qualyskb-parser) to use the Kusto function alias, **QualysKB**
65-
66-
67-
>**(Optional Step)** Securely store workspace and API authorization key(s) or token(s) in Azure Key Vault. Azure Key Vault provides a secure mechanism to store and retrieve key values. [Follow these instructions](/azure/app-service/app-service-key-vault-references) to use Azure Key Vault with an Azure Function App.
61+
> [!NOTE]
62+
> This data connector depends on a parser based on a Kusto Function to work as expected which is deployed as part of the solution. To view the function code in Log Analytics, open Log Analytics/Microsoft Sentinel Logs blade, click Functions and search for the alias QualysVM Knowledgebase and load the function code, on the second line of the query, enter the hostname(s) of your QualysVM Knowledgebase device(s) and any other unique identifiers for the logstream. The function usually takes 10-15 minutes to activate after solution installation/update.
63+
> This data connector depends on a parser based on a Kusto Function to work as expected. [Follow the steps](https://aka.ms/sentinel-qualyskb-parser) to use the Kusto function alias, **QualysKB**
64+
> **(Optional Step)** Securely store workspace and API authorization key(s) or token(s) in Azure Key Vault. Azure Key Vault provides a secure mechanism to store and retrieve key values. [Follow these instructions](/azure/app-service/app-service-key-vault-references) to use Azure Key Vault with an Azure Function App.
6865
6966

7067
**STEP 1 - Configuration steps for the Qualys API**
@@ -73,14 +70,15 @@ To integrate with Qualys VM KnowledgeBase (using Azure Functions) make sure you
7370
2. Click on the **New** drop-down menu and select **Users**.
7471
3. Create a username and password for the API account.
7572
4. In the **User Roles** tab, ensure the account role is set to **Manager** and access is allowed to **GUI** and **API**
76-
4. Log out of the administrator account and log into the console with the new API credentials for validation, then log out of the API account.
77-
5. Log back into the console using an administrator account and modify the API accounts User Roles, removing access to **GUI**.
78-
6. Save all changes.
73+
5. Log out of the administrator account and log into the console with the new API credentials for validation, then log out of the API account.
74+
6. Log back into the console using an administrator account and modify the API accounts User Roles, removing access to **GUI**.
75+
7. Save all changes.
7976

8077

8178
**STEP 2 - Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function**
8279

83-
>**IMPORTANT:** Before deploying the Qualys KB connector, have the Workspace ID and Workspace Primary Key (can be copied from the following), as well as the Qualys API username and password, readily available.
80+
> [!IMPORTANT]
81+
> Before deploying the Qualys KB connector, have the Workspace ID and Workspace Primary Key (can be copied from the following), as well as the Qualys API username and password, readily available.
8482
8583

8684

articles/sentinel/data-connectors/senservapro.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -220,7 +220,7 @@ let timeframe = 14d;
220220

221221
1. Setup the data connection
222222

223-
Visit [Senserva Setup](https://blog.senserva.com/senserva-and-microsoft-sentinel-overview/) for information on setting up the Senserva data connection, support, or any other questions. The Senserva installation will configure a Log Analytics Workspace for output. Deploy Microsoft Sentinel onto the configured Log Analytics Workspace to finish the data connection setup by following [this onboarding guide.](/azure/sentinel/quickstart-onboard)
223+
Visit [Senserva Setup](https://www.microsoft.com/en-us/americas-partner-blog/2024/07/30/bulletproof-partners-with-senserva-to-innovate-security-solutions-for-microsoft-customers/) for information on setting up the Senserva data connection, support, or any other questions. The Senserva installation will configure a Log Analytics Workspace for output. Deploy Microsoft Sentinel onto the configured Log Analytics Workspace to finish the data connection setup by following [this onboarding guide.](/azure/sentinel/quickstart-onboard)
224224

225225

226226

articles/sentinel/data-connectors/sophos-cloud-optix.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.collection: sentinel-data-connector
1111

1212
# Sophos Cloud Optix connector for Microsoft Sentinel
1313

14-
The [Sophos Cloud Optix](https://www.sophos.com/products/cloud-optix.aspx) connector allows you to easily connect your Sophos Cloud Optix logs with Microsoft Sentinel, to view dashboards, create custom alerts, and improve investigation. This gives you more insight into your organization's cloud security and compliance posture and improves your cloud security operation capabilities.
14+
The [Sophos Cloud Optix](https://www.sophos.com/products/cloud-optix) connector allows you to easily connect your Sophos Cloud Optix logs with Microsoft Sentinel, to view dashboards, create custom alerts, and improve investigation. This gives you more insight into your organization's cloud security and compliance posture and improves your cloud security operation capabilities.
1515

1616
This is autogenerated content. For changes, contact the solution provider.
1717

articles/sentinel/unified-connector-cef-device.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -380,7 +380,7 @@ Configure Palo Alto Networks to forward syslog messages in CEF format to your Mi
380380

381381
## PingFederate
382382

383-
[Follow these steps](https://docs.pingidentity.com/bundle/pingfederate-102/page/gsn1564002980953.html) to configure PingFederate sending audit log via syslog in CEF format.
383+
[Follow these steps](https://docs.pingidentity.com/) to configure PingFederate sending audit log via syslog in CEF format.
384384

385385
## RidgeSecurity
386386

articles/sentinel/unified-connector-syslog-device.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ This data connector was developed using Cisco ACI Release 1.x.
3737

3838
## Cisco Identity Services Engine (ISE)
3939

40-
[Follow these instructions](https://www.cisco.com/c/en/us/td/docs/security/ise/2-7/admin_guide/b_ise_27_admin_guide/b_ISE_admin_27_maintain_monitor.html#ID58) to configure remote syslog collection locations in your Cisco ISE deployment.
40+
[Follow these instructions](https://www.cisco.com/c/en/us/td/docs/security/ise/3-1/admin_guide/b_ise_admin_3_1.html#ID58) to configure remote syslog collection locations in your Cisco ISE deployment.
4141

4242
## Cisco Stealthwatch
4343

0 commit comments

Comments
 (0)