SIEM Integration
Last updated
Last updated
It is possible to integrate your dope.swg with whichever SIEM tool your organization is using. We provide two methods for integration using an AWS S3 bucket or HTTP Integration.
Simply provide dope.security with the location of your organization's AWS S3 Bucket where we can send all web transactions from each dope. endpoint.
Each dope.endpoint sends all web transactions for that endpoint to the dope.cloud every 15 mins. Once SIEM Integration is enabled the dope.cloud will ensure all of this log data is sent to your organization's AWS S3 bucket as it is received from the dope.endpoint.
The data is sent to the AWS S3 Bucket in a compressed GZIP format. This data can then be ingested into whichever SIEM product your organization is using.
The first step to configure SIEM integration is to navigate to the Settings ➔ SIEM page. From here, you must provide the name of the AWS S3 Bucket to which you want the dope.cloud to send the log data.
Your AWS S3 Bucket must be in the AWS region noted on the right-hand side of the SIEM integration page on the right-hand side (above).
e.g. US-EAST-2 should have a US-EAST-2 S3 Bucket location
The AWS S3 bucket that you want to log data to be sent to must be configured to give the dope.cloud write access.
Within the SIEM integration page on the right-hand panel, dope.security has provided the policy that the AWS S3 Bucket needs to be configured with. You need to copy and paste this policy and use it to configure the organization’s AWS S3 Bucket.
When everything has been configured correctly a successful synchronization will be clearly indicated on the SIEM page.
A green tick will appear next to the AWS S3 Bucket name and the last synchronization time will appear on the top right of the page.
Where the synchronization fails it will be because of one of the following errors:
AWS S3 bucket not found
AWS S3 Bucket needs to be in Data Residency Region
AWS S3 access policy is not set
AWS S3 access policy is incorrect.
The synchronization failure will be clearly indicated on the SIEM page.
It is possible that the connection to the AWS S3 Bucket could get lost. This will result in log data not getting sent to the organization’s AWS S3 Bucket. The reasons for a lost connection be because of one of the following errors:
AWS S3 bucket not found
AWS S3 Bucket needs to be in Data Residency Region
AWS S3 access policy is not set
AWS S3 access policy is incorrect.
The SIEM Integration page will clearly indicate that the connection is lost and will indicate the possible reasons.
The Audit Log will have an event posted that shows the number of files that have not been sent to the organization's AWS S3 Bucket.
When connection to the AWS S3 Bucket is restored then the SIEM page will again indicate that the synchronization was successful. There will also be a connection returned event added to the Audit Log.
The data is sent in JSONL format below you can find the JSON Schema and an example JSONL file.
Below is a description of each parameter in the JSONL file:
Timestamp (ISO 8601 time format)
The timestamp of when the web transaction was requested
Duration
The duration that the connection was open for, this is in milliseconds
Matched Destination
The domain that the dope category was matched against
Destination IP
The destination IP address for the requested URL
Tenant ID
The customers dope.cloud unique tenant ID
Agent ID
The unique agent ID for the dope.endpoint where the data is being sent from
User
The logged in user on the dope.endpoint
OIDC User
The email address for the authenicated user on the dope.endpoint. Only shown when OIDC authentication is enabled
Categories
Verdict
The policy verdict for the requested URL. This can be Allow (0), Block (1), Warning (2) or Bypass (3) where the URL is part of a policies bypass list.
Data Sent
The amount of data sent in the connection
Data Received
The amount of data received in the connection
Policy Type
The type of policy that was applied to the URL.This can be either Web, Cloud Application Control (CAC), Custom Category or Malware.
Block Detail
Populated for a block verdict. It will be either a dope category, a custom category, Cloud Application or a malware type.
Filename
The name any file downloaded.
File Hash
The file hash for the downloaded file
Process Name
The name of the process making the URL request.
URL
The complete requested URL
Policy Name
The name of the policy applied
Protocol
Protocol used, e.g.: HTTP/2, HTTP/1.1
Hostname
Device hostname
HTTP Request Method
HTTP Request Method e.g. Put
Process Call Tree
Shows the parent-child relationships established via process spawn operations, also includes the command arguments
Currently DOPE HTTP Integration supports the following SIEM tools:
Splunk
QRadar
Taegis
MS Sentinel
In the dope.console, navigate to Settings ➔ SIEM ➔ SIEM Integration Settings ➔ HTTP. From here select "Splunk" as the SIEM type and update the HEC URI and the HEC token in the following SIEM HTTP settings page of the dope.console and sync.
In order to confirm that the sync is successful, you should see a couple of sample records in your SIEM as a validation test.
In the dope.console navigate to Settings ➔ SIEM ➔ SIEM Integration Settings ➔ HTTP. From here select “QRadar” as the SIEM type and update the integration URL and the integration key and sync.
In order to confirm that the sync is successful, you should see a couple of sample records in your SIEM as a validation test.
In the dope.console navigate to Settings ➔ SIEM ➔ SIEM Integration Settings ➔ HTTP. From here select “Taegis” as the SIEM type and update the integration URL and the integration key and sync.
In order to confirm that the sync is successful, you should see a couple of sample records in your SIEM as a validation test.
Microsoft Entra Application (Client ID, Tenant ID, Client Secret)
Data Collection Endpoint (DCE)
Custom Log Analytics Table
Data Collection Rule (DCR)
Assign your Microsoft Entra Application the Monitoring Metrics Publisher role on your DCR.
In the dope.console navigate to Settings ➔ SIEM ➔ SIEM Integration Settings ➔ HTTP. From here select “MS Sentinel” as the SIEM type. Provide all the necessary information in the form below.
In order to confirm that the sync is successful, you should see a couple of sample records in your SIEM as a validation test.
To configure Crowdstrike, you must create a HEC Connector within your Crowdstrike console. First login to your Crowdstrike console and go to Data Onboarding. Then add a HEC Connector and add the dopesecurity-swg parser. Once this is saved you will be provided with an API key and an API URL, copy these so you can add them to the SIEM configuration in the dope console.
In the dope.console, navigate to Settings ➔ SIEM ➔ SIEM Integration Settings ➔ HTTP. From here select "Crowdstrike" as the SIEM type and update the API Token and the API URL token in the following SIEM HTTP settings page and sync.
In order to confirm that the sync is successful, you should see a couple of sample records in your SIEM as a validation test.
Once the AWS S3 Bucket is configured correctly return to the Settings ➔ SIEM Page and simply click the Sync Button
The matched for the requested URL
To configure Splunk, you must have the HTTP Event Collector (HEC) URI and the token. The steps to obtain these can be found in .
To configure Taegis, you must have the Taegis integration URL and the integration key. The steps to obtain these can be found in .
To configure Taegis, you must have the Taegis integration URL and the integration key. The steps to obtain these can be found in .
To integrate with Microsoft Sentinel using HTTP, you'll need to utilize the Azure Monitor Logs Ingestion API. The steps to configure this can be found in
