HYAS Protect (using Azure Functions) connector for Microsoft Sentinel
HYAS Protect provide logs based on reputation values - Blocked, Malicious, Permitted, Suspicious.
This is autogenerated content. For changes, contact the solution provider.
Connector attributes
| Connector attribute | Description |
|---|---|
| Azure function app code | https://aka.ms/sentinel-HYASProtect-functionapp |
| Log Analytics table(s) | HYASProtectDnsSecurityLogs_CL |
| Data collection rules support | Not currently supported |
| Supported by | HYAS |
Query samples
All Logs
HYASProtectDnsSecurityLogs_CL
Prerequisites
To integrate with HYAS Protect (using Azure Functions) make sure you have:
- Microsoft.Web/sites permissions: Read and write permissions to Azure Functions to create a Function App is required. See the documentation to learn more about Azure Functions.
- REST API Credentials/permissions: HYAS API Key is required for making API calls.
Vendor installation instructions
Note
This connector uses Azure Functions to connect to the HYAS API to pull Logs into Microsoft Sentinel. This might result in additional costs for data ingestion and for storing data in Azure Blob Storage costs. Check the Azure Functions pricing page and Azure Blob Storage pricing page for details.
(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 to use Azure Key Vault with an Azure Function App.
Option 1 - Azure Resource Manager (ARM) Template
Use this method for automated deployment of the HYAS Protect data connector using an ARM Tempate.
Click the Deploy to Azure button below.
Select the preferred Subscription, Resource Group and Location.
Enter the Function Name, Table Name, Workspace ID, Workspace Key, API Key, TimeInterval, FetchBlockedDomains, FetchMaliciousDomains, FetchSuspiciousDomains, FetchPermittedDomains and deploy.
Mark the checkbox labeled I agree to the terms and conditions stated above.
Click Purchase to deploy.
Option 2 - Manual Deployment of Azure Functions
Use the following step-by-step instructions to deploy the HYAS Protect Logs data connector manually with Azure Functions (Deployment via Visual Studio Code).
1. Deploy a Function App
NOTE:You will need to prepare VS code for Azure function development.
Download the Azure Function App file. Extract archive to your local development computer.
Start VS Code. Choose File in the main menu and select Open Folder.
Select the top level folder from extracted files.
Choose the Azure icon in the Activity bar, then in the Azure: Functions area, choose the Deploy to function app button. 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 If you're already signed in, go to the next step.
Provide the following information at the prompts:
a. Select folder: Choose a folder from your workspace or browse to one that contains your function app.
b. Select Subscription: Choose the subscription to use.
c. Select Create new Function App in Azure (Don't choose the Advanced option)
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. HyasProtectLogsXXX).
e. Select a runtime: Choose Python 3.8.
f. Select a location for new resources. For better performance and lower costs choose the same region where Microsoft sentinel is located.
Deployment will begin. A notification is displayed after your function app is created and the deployment package is applied.
Go to Azure Portal for the Function App configuration.
2. Configure the Function App
- In the Function App, select the Function App Name and select Configuration.
- In the Application settings tab, select + New application setting.
- Add each of the following application settings individually, with their respective string values (case-sensitive): APIKey Polling WorkspaceID WorkspaceKey . Once all application settings have been entered, click Save.
Next steps
For more information, go to the related solution in the Azure Marketplace.