Description
This connector uses the Dynatrace Attacks REST API to ingest detected attacks into Microsoft Sentinel Log Analytics
- Declared status
- 1
- Declared author / publisher
- Dynatrace
Declared sources
Metadata from the source file. No dependencies inferred from KQL.
Data types
Declared permissions
read and write permissions are required.
Workspace
Workspace
Dynatrace tenant (ex. xyz.dynatrace.com)
You need a valid Dynatrace tenant with [Application Security](https://www.dynatrace.com/platform/application-security/) enabled, learn more about the [Dynatrace platform](https://www.dynatrace.com/).
Dynatrace Access Token
You need a Dynatrace Access Token, the token should have ***Read attacks*** (attacks.read) scope.
Connector instructions
Content published in the repository. Refer to the original file for all parameters.
Dynatrace Attack Events to Microsoft Sentinel
Configure and Enable Dynatrace [Application Security](https://www.dynatrace.com/platform/application-security/).
Follow [these instructions](https://docs.dynatrace.com/docs/shortlink/token#create-api-token) to generate an access token.
Dynatrace tenant (ex. xyz.dynatrace.com)
Dynatrace Access Token
Related content
Links established from declared identifiers and solution manifests.
Source provenance
GitHubDisplayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.
- File
- Solutions/Dynatrace/Data Connectors/DynatraceAttacksV2/Connector_Dynatrace_Attacks_Definition.json ↗
- Commit
9800e51↗- Source identifier
DynatraceAttacksCCPDefinition
GSTEP / CATALOG TRACKING
Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC