This guide provides step-by-step procedure of installing WithSecure data connector for Azure Sentinel.
- Access to Azure account with installed Sentinel solution.
- Workstation with installed Azure CLI.
- Access to WithSecure Elements Security Center.
Connector installation has following steps:
- Get installation package.
- Create Elements API credentials
- Create Azure Entra application.
- Deploy Azure resources.
- Verify installation.
Log Analytics Workspace is not managed with provided deployment templates. It can be created
manually in Azure Portal or from command line. All resources that are mentioned in this
guide must be deployed in the same resource group where the Log Analytics Workspace is
created. For purpose of this guide in next paragraphs we will be using example resource
group called UserGuide. Initially it only contains Log Analytics Workspace called
UserGuideLogs and Sentinel solution.
Installation package provides ARM template
that deploys WithSecure Elements API connector in Azure portal. Download installation
package from github.com
and extract archive in preferred localization. Directory ws_connector/deploy contains two
files:
azuredeploy_connector_app.json- ARM template that deploys all required resources in given resource group. Deployment can be customized with temaplate's parameters. If non-required parameter is not specified during a default value will be used:workspaceName(required) - name of Log Analytics Workspace,elementsApiClientId(required) - Elements API client id,elementsApiClientSecret(required) - Elements API client secret,entraClientId(required) - Entra application client id,entraClientSecret(required) - Entra application client secret,entraTenantId(required) - Entra application tenant id,entraObjectId(required) - Entra application principal id,engine- list of Security Event engines as described in Elements API documentation, for exampledeepGuard,engineGroup- list of Security Event engines as described in Elements API documentation, for exampleedr. By default connector polls all supported Security Events
connector_app_paramters.json- deployment parameters used with Azure CLI.
Connector polls Security Events from WithSecure Elements backend therefore before installation administrator must create API credentials in Elements Security Center.
-
Go to Elements Security Center. Use direct link that will automatically open API credentials management page or open
Organization SettingsinManagementsection and go toAPI clientstab. Only administrators with full EPP permissions are permited to manage API credentials. -
Click button
Add newand enter description of new credentials pair. If you plan to use Elements API for managements (for example blocking devices or triggering remote operations) then uncheckRead-onlyfield. Click buttonAdd. -
After new credentials pair is added you can copy
Client IDandSecretto fileconnector_app_parameters.json. PutClient IDas value ofelementsApiClientIdandSecretas value ofelementsApiClientSecret.
Entra application is responsible for authentication and authorization in communication between Elements Connector and Azure Log Analytics Workspace. Azure administrator must create Entra application before deploying connector.
-
In Azure portal go to
Microsoft Entra IDand openApp registrationsfrom left menu. -
Click button
New registration. In fieldNameenter name of application, for exampleUserGuideAppand click buttonRegister. -
Click on application name in the list to open details of new Entra application.
-
Find row with label
Client credentials(red square with number1.on screenshot) and click linkAdd a certificate or secret. -
Click on button
New client secret. Enter client secret description, for exampleUserGuideSecretand click buttonAdd -
From secrets list copy value in column
Valueto parameterentraClientSecretin fileconnector_app_parameters.json. Secret value will be hidden after page refresh. -
Back to details of
UserGuideApp. Copy value from rowApplication (client) IDto parameterentraClientIdand value from rowDirectory (tenant) IDto parameterentraTenantIdin fileconnector_app_parameters.json. -
Find row with label
Managed application in local directory(red square with number4.on screenshot) and click link with application name. -
Copy value from field
Object IDto parameterentraObjectIdin fileconnector_app_parameters.json.
WithSecure Elements API connector is implemented as Azure Function App. Azure ARM template
from file azuredeploy_connector_app.json deploys all required resources:
- Function App with Application Insights,
- Data Collection Rule,
- Data Collection Endpoint,
- Storage Account.
ARM template can be deployed from command line. Before deployment check
connector_app_paramters.json and ensure that all parameters have values describe in
previous sections of this guide.
In command line go to directory ws_client/deploy, execute command
az deployment group create -n ConnectorApp -g UserGuide -f azuredeploy_connector_app.json -p connector_app_parameters.json
and wait until execution finish. Remember to replace UserGuide with name of resource
group with your Sentinel solution.
Go to resource group with Sentinel solution. After successful deployment it should contain items similar to ones from screenshot below.
After deployment connector starts polling Security Events from Elements backend. Every
minute reads most recent events and push to table WsSecurityEvents_CL in Log Analytics
Workspace. WARNING: Connector skip Security Events that were created BEFORE installation
To check table go to your Sentinel solution and open Logs view. Expand node Custom Logs.
If WsSecurityEvents_CL is visible then double click on table. Click button Run to fetch
ingested events.
Missing or empty WsSecurityEvents_CL might indicate that connector can't read Security
Events or ingest to Log Analytics workspace. Connector logs can be checked in Azure
Function App console.
-
Go to
UserGuideresource group. -
On list find item of type
Function Appand name with prefixConnector(red square on screenshot). Click on item to open details view. -
In details view in tab
Functionsfind row with nameupload_security_events. Click on linkInvocations and morein columnMonitor. -
Every row in table represents single connector executions. Exception in execution logs might indicate either communication errors, such as invalid credentials or other unexpected conditions. If you need help from WithSecure support remember to provide full exectution log.
-
To check last execution you can also run Application Insights query.
traces | where timestamp > ago(30d) | where operation_Name =~ 'upload_security_events' | where message contains "Found" or message contains "Error" | order by timestamp desc | take 200Message that starts with
Found 0 items since $DATEindicates that connector didn't found any new items since$DATE.
If you need more help with connector you can try contact WithSecure support.












