Skip to content

Commit ea64478

Browse files
authored
Merge pull request #229817 from cwatson-cat/3-7-23-gen-data-connectors-fix-warnings
Sentinel auto-gen data connectors: Fix warnings on data connector files
2 parents 94c2599 + 02792ab commit ea64478

5 files changed

+35
-35
lines changed

articles/sentinel/data-connectors/cohesity-using-azure-function.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ To integrate with Cohesity (using Azure Function) make sure you have:
5252
**STEP 1 - Get a Cohesity DataHawk API key (see troubleshooting [instruction 1](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/CohesitySecurity/Data%20Connectors/Helios2Sentinel/IncidentProducer))**
5353

5454

55-
**STEP 2 - Register Azure app ([link](https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/RegisteredApps)) and save Application (client) ID, Directory (tenant) ID, and Secret Value ([instructions](https://learn.microsoft.com/en-us/azure/healthcare-apis/register-application)). Grant it Azure Storage (user_impersonation) permission. Also, assign the 'Microsoft Sentinel Contributor' role to the application in the appropriate subscription.**
55+
**STEP 2 - Register Azure app ([link](https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/RegisteredApps)) and save Application (client) ID, Directory (tenant) ID, and Secret Value ([instructions](https://learn.microsoft.com/azure/healthcare-apis/register-application)). Grant it Azure Storage (user_impersonation) permission. Also, assign the 'Microsoft Sentinel Contributor' role to the application in the appropriate subscription.**
5656

5757

5858
**STEP 3 - Deploy the connector and the associated Azure Functions**.

articles/sentinel/data-connectors/digital-shadows-searchlight-using-azure-function.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ Use this method for automated deployment of the 'Digital Shadows Searchlight' co
9595
2. Select **Timer Trigger**.
9696
3. Enter a unique Function **Name** in the New Function field and leave the default cron schedule of every 5 minutes, then click **Create Function**.
9797
4. Click on the function name and click **Code + Test** from the left pane.
98-
5. Copy the [Function App Code](<Add GitHub link to Function App code>) and paste into the Function App `run.ps1` editor.
98+
5. Copy the Function App Code and paste into the Function App `run.ps1` editor.
9999
6. Click **Save**.
100100

101101
3. Configure the Function App

articles/sentinel/data-connectors/lookout-cloud-security-for-microsoft-sentinel-using-azure-function.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,7 @@ This connector uses a Agari REST API connection to push data into Microsoft Sent
2424
## Query samples
2525

2626
**All Lookout Cloud Security logs**
27+
2728
```kusto
2829
LookoutCloudSecurity_CL
2930
@@ -67,17 +68,17 @@ To integrate with Lookout Cloud Security for Microsoft Sentinel (using Azure Fun
6768

6869
**To add a new API client:**
6970

70-
1. Go to Administration > Enterprise Integration > API Clients and click New.
71+
1. Go to Administration > Enterprise Integration > API Clients and click New.
7172

72-
2. Enter a Name (required) and a Description (optional).
73+
1. Enter a Name (required) and a Description (optional).
7374

74-
3. Enter the Client ID that was provided to you.
75+
1. Enter the Client ID that was provided to you.
7576

76-
4. Select one or more Permissions from the dropdown list.
77+
1. Select one or more Permissions from the dropdown list.
7778

78-
5. Enter one or more Authorized IP addresses for this client. Separate each address with a comma.
79+
1. Enter one or more Authorized IP addresses for this client. Separate each address with a comma.
7980

80-
6. Click Save.
81+
1. Click Save.
8182

8283
When prompted, copy the string for the client's secret. You will need this information (along with the client ID) to authenticate to the API gateway.
8384

articles/sentinel/data-connectors/rapid7-insight-platform-vulnerability-management-reports-using-azure-function.md

Lines changed: 12 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -94,27 +94,22 @@ Use the following step-by-step instructions to deploy the Rapid7 Insight Vulnera
9494
**1. Deploy a Function App**
9595

9696
> **NOTE:** You will need to [prepare VS code](https://aka.ms/sentinel-InsightVMCloudAPI-functionapp) file. Extract archive to your local development computer.
97-
2. Start VS Code. Choose File in the main menu and select Open Folder.
98-
3. Select the top level folder from extracted files.
99-
4. Choose the Azure icon in the Activity bar, then in the **Azure: Functions** area, choose the **Deploy to function app** button.
97+
1. Start VS Code. Choose File in the main menu and select Open Folder.
98+
1. Select the top level folder from extracted files.
99+
1. Choose the Azure icon in the Activity bar, then in the **Azure: Functions** area, choose the **Deploy to function app** button.
100100
If you aren't already signed in, choose the Azure icon in the Activity bar, then in the **Azure: Functions** area, choose **Sign in to Azure**
101101
If you're already signed in, go to the next step.
102-
5. Provide the following information at the prompts:
102+
1. Provide the following information at the prompts:
103103

104-
a. **Select folder:** Choose a folder from your workspace or browse to one that contains your function app.
104+
1. **Select folder:** Choose a folder from your workspace or browse to one that contains your function app.
105+
1. **Select Subscription:** Choose the subscription to use.
106+
1. Select **Create new Function App in Azure** (Don't choose the Advanced option)
107+
1. **Enter a globally unique name for the function app:** Type a name that is valid in a URL path. The name you type is validated to make sure that it's unique in Azure Functions. (e.g. InsightVMXXXXX).
108+
1. **Select a runtime:** Choose Python 3.8.
109+
1. Select a location for new resources. For better performance and lower costs choose the same [region](https://azure.microsoft.com/regions/) where Microsoft Sentinel is located.
105110

106-
b. **Select Subscription:** Choose the subscription to use.
107-
108-
c. Select **Create new Function App in Azure** (Don't choose the Advanced option)
109-
110-
d. **Enter a globally unique name for the function app:** Type a name that is valid in a URL path. The name you type is validated to make sure that it's unique in Azure Functions. (e.g. InsightVMXXXXX).
111-
112-
e. **Select a runtime:** Choose Python 3.8.
113-
114-
f. Select a location for new resources. For better performance and lower costs choose the same [region](https://azure.microsoft.com/regions/) where Microsoft Sentinel is located.
115-
116-
6. Deployment will begin. A notification is displayed after your function app is created and the deployment package is applied.
117-
7. Go to Azure Portal for the Function App configuration.
111+
1. Deployment will begin. A notification is displayed after your function app is created and the deployment package is applied.
112+
1. Go to Azure Portal for the Function App configuration.
118113

119114

120115
**2. Configure the Function App**

articles/sentinel/data-connectors/snowflake-using-azure-function.md

Lines changed: 14 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -60,34 +60,38 @@ To query data from Snowflake you need a user that is assigned to a role with suf
6060

6161
1. Enter the Snowflake console.
6262
2. Switch role to SECURITYADMIN and [create a new role](https://docs.snowflake.com/en/sql-reference/sql/create-role.html):
63-
```
63+
6464
USE ROLE SECURITYADMIN;
65-
CREATE OR REPLACE ROLE EXAMPLE_ROLE_NAME;```
65+
CREATE OR REPLACE ROLE EXAMPLE_ROLE_NAME;
66+
6667
3. Switch role to SYSADMIN and [create warehouse](https://docs.snowflake.com/en/sql-reference/sql/create-warehouse.html) and [grand access](https://docs.snowflake.com/en/sql-reference/sql/grant-privilege.html) to it:
67-
```
68+
6869
USE ROLE SYSADMIN;
6970
CREATE OR REPLACE WAREHOUSE EXAMPLE_WAREHOUSE_NAME
7071
WAREHOUSE_SIZE = 'SMALL'
7172
AUTO_SUSPEND = 5
7273
AUTO_RESUME = true
7374
INITIALLY_SUSPENDED = true;
74-
GRANT USAGE, OPERATE ON WAREHOUSE EXAMPLE_WAREHOUSE_NAME TO ROLE EXAMPLE_ROLE_NAME;```
75+
GRANT USAGE, OPERATE ON WAREHOUSE EXAMPLE_WAREHOUSE_NAME TO ROLE EXAMPLE_ROLE_NAME;
76+
7577
4. Switch role to SECURITYADMIN and [create a new user](https://docs.snowflake.com/en/sql-reference/sql/create-user.html):
76-
```
78+
7779
USE ROLE SECURITYADMIN;
7880
CREATE OR REPLACE USER EXAMPLE_USER_NAME
7981
PASSWORD = 'example_password'
8082
DEFAULT_ROLE = EXAMPLE_ROLE_NAME
8183
DEFAULT_WAREHOUSE = EXAMPLE_WAREHOUSE_NAME
82-
;```
84+
;
85+
8386
5. Switch role to ACCOUNTADMIN and [grant access to snowflake database](https://docs.snowflake.com/en/sql-reference/account-usage.html#enabling-account-usage-for-other-roles) for role.
84-
```
87+
8588
USE ROLE ACCOUNTADMIN;
86-
GRANT IMPORTED PRIVILEGES ON DATABASE SNOWFLAKE TO ROLE EXAMPLE_ROLE_NAME;```
89+
GRANT IMPORTED PRIVILEGES ON DATABASE SNOWFLAKE TO ROLE EXAMPLE_ROLE_NAME;
90+
8791
6. Switch role to SECURITYADMIN and [assign role](https://docs.snowflake.com/en/sql-reference/sql/grant-role.html) to user:
88-
```
92+
8993
USE ROLE SECURITYADMIN;
90-
GRANT ROLE EXAMPLE_ROLE_NAME TO USER EXAMPLE_USER_NAME;```
94+
GRANT ROLE EXAMPLE_ROLE_NAME TO USER EXAMPLE_USER_NAME;
9195

9296
>**IMPORTANT:** Save user and API password created during this step as they will be used during deployment step.
9397

0 commit comments

Comments
 (0)