Detection finding events represent alerts or detections generated by security tools or Dynatrace detection rules. Detections are available for both Dynatrace-generated and third-party ingested data.
A detection finding refers to alerts or detections generated by security tools using correlation algorithms, detection rules, or other analytical methods. They're primarily consumed in the Threats & Exploits app.
Lists the most recent detection findings.
fetch security.events| filter event.type == "DETECTION_FINDING"| sort timestamp desc
Counts detection findings by normalized risk level.
fetch security.events| filter event.type == "DETECTION_FINDING"| summarize {findings = count()}, by: {dt.security.risk.level}| sort findings desc
Core event metadata. These fields identify the event record and are added automatically by Dynatrace during ingest.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | stableDisplay name: |
|
| string | stableDisplay name: |
|
| string | stableDisplay name: |
|
| timestamp | stableDisplay name: |
|
Information about the security finding.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | stableDisplay name: |
|
| timestamp | stableDisplay name: |
|
| string | stableDisplay name: |
|
| string | stableDisplay name: |
|
Information about the object in which the detection finding was raised.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | resource experimentalIdentifier of the affected object. Either this or |
|
| string | resource experimentalName of the affected object. Either this or |
|
| string | resource experimentalType of the affected object. |
|
Information about the product or tool that raised the detection finding.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | stableDisplay name: |
|
| string | resource experimentalProduct name. |
|
| string | resource experimentalProduct vendor. |
|
Optional fields for detection findings (their existence in an event does not influence if they're displayed in T&E or not).
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | stableDisplay name: |
|
| string | stableDisplay name: |
|
| string[] | experimentalMITRE ATT&CK sub-technique identifiers for this detection, in T{parent}.{sub} dotted format. Independent of threat.attack.technique.ids—no positional alignment is assumed or required. The parent technique is encoded in the sub-technique ID itself, for example, T1059.003 belongs to technique T1059). Omit when no sub-technique information is available; don't use empty string placeholders. Sub-technique names are derivable from IDs via the ATT&CK knowledge base. DQL filter example: array.contains(threat.attack.subtechnique.ids, "T1059.003") |
|
| string[] | experimentalHuman-readable names of the MITRE ATT&CK sub-techniques for this detection. Optional companion to threat.attack.subtechnique.ids. When populated, elements must correspond positionally to threat.attack.subtechnique.ids: names[i] is the display name for ids[i]. No specific ordering of the array is required. Omit when the producing source does not provide sub-technique names; don't use placeholder values. Names can be derived from IDs using the ATT&CK knowledge base. |
|
| string[] | experimentalMITRE ATT&CK tactic identifiers for this detection, in TA-prefixed format. A detection may map to zero or more tactics. Omit or set to an empty array when tactic information is unavailable from the producing source. Tactic names can be derived from IDs using the ATT&CK knowledge base. DQL filter example: array.contains(threat.attack.tactic.ids, "TA0002") |
|
| string[] | experimentalHuman-readable names of the MITRE ATT&CK tactics for this detection. Optional companion to threat.attack.tactic.ids. When populated, elements must correspond positionally to threat.attack.tactic.ids: names[i] is the display name for ids[i]. No specific ordering of the array is required. Omit when the producing source does not provide tactic names; don't use placeholder values. Names can be derived from IDs using the ATT&CK knowledge base. |
|
| string[] | experimentalMITRE ATT&CK technique identifiers for this detection, in T-prefixed format. A detection may map to zero or more techniques. The primary pivot field for ATT&CK heat maps and technique coverage dashboards. Technique names can be derived from IDs using the ATT&CK knowledge base. DQL filter example: array.contains(threat.attack.technique.ids, "T1059") |
|
| string[] | experimentalHuman-readable names of the MITRE ATT&CK techniques for this detection. Optional companion to threat.attack.technique.ids. When populated, elements must correspond positionally to threat.attack.technique.ids: names[i] is the display name for ids[i]. No specific ordering of the array is required. Omit when the producing source does not provide technique names; don't use placeholder values. Names can be derived from IDs using the ATT&CK knowledge base. |
|
| string | experimentalVersion of the MITRE ATT&CK framework used to classify this detection. Useful for audit and reproducibility, since tactic and technique IDs can be added or renumbered across major ATT&CK versions. Some producers don't embed the framework version in their event payloads; omit when version provenance can't be reliably determined. Use bare version numbers without a "v" prefix. |
|
Fields added by Dynatrace to normalize and enrich the finding with platform-level risk assessment and Smartscape entity resolution.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | stableDisplay name: |
|
| smartscapeId | resource stableDisplay name: |
|
| string | stableDisplay name: |
|
The value of this field will be based on the value of one of the dt.smartscape.<type> fields. That means that the dt.smartscape_source.id and dt.smartscape.<type> fields will both be set to the same ID.
A detection finding is an alert raised by a security tool or a Dynatrace detection rule when it observes suspicious or malicious activity—for example, an exploit attempt, a policy violation, or anomalous behavior. Detection findings are available for both Dynatrace-generated data and findings ingested from third-party security tools, and are primarily consumed in the Threats & Exploits app.
Unlike a vulnerability finding, which reports a known weakness in a scanned object, a detection finding reports activity that was observed.
A detection finding generated by Dynatrace Runtime Application Protection, reporting a blocked SQL injection attempt against a Node.js process. Dynatrace resolves the targeted process to a Smartscape entity and adds dt.smartscape_source.* during ingest.
{"event.kind": "SECURITY_EVENT","event.type": "DETECTION_FINDING","event.provider": "OneAgent","product.vendor": "Dynatrace","product.name": "Runtime Application Protection","finding.id": "A-35VEHCHS","finding.title": "Blocked SQL injection attempt at Query.ErrorPacket() (Query.js:83:17)","finding.type": "SQL injection","finding.time.created": "2026-07-14T18:07:39.274000000Z","dt.security.risk.level": "CRITICAL","object.id": "PROCESS-87234EE293F14F76","object.type": "PROCESS","object.name": "BloatedNodeJsSoftwareGroup-IG-1","dt.smartscape_source.id": "PROCESS-87234EE293F14F76","dt.smartscape_source.type": "PROCESS"}
A detection finding ingested from Akamai SIEM reporting a cross-site scripting attempt against a web endpoint, showing the finding metadata, the affected object (the targeted URL), and the normalized Dynatrace risk level.
{"event.kind": "SECURITY_EVENT","event.type": "DETECTION_FINDING","event.provider": "Akamai","product.vendor": "Akamai","product.name": "Akamai SIEM","finding.id": "1753176775716859162-86508-3000110-","finding.title": "Cross-site Scripting (XSS) Attack (SmartDetect)","finding.type": "Cross-site scripting","finding.time.created": "2026-04-24T13:19:00.959138000Z","dt.security.risk.level": "MEDIUM","object.id": "atlas-int-01-channel-api.sampledomain.com:443/authz/v2/token","object.type": "URL","object.name": "atlas-int-01-channel-api.sampledomain.com:443/authz/v2/token"}