Homeโ€บ๐Ÿ” Playbooksโ€บModule 51 min read ยท 6/8

Security Incident

Hands-on

Security Incident Investigation

When Dynatrace detects a vulnerability or attack, follow this structured investigation pattern.

Step 1: Assess the Situation

// What's open right now? Summary by risk level
fetch security.events, from:now()-30d
| filter event.type == "VULNERABILITY_STATE_REPORT_EVENT" AND event.level == "ENTITY"
| dedup {vulnerability.display_id, affected_entity.id}, sort:{timestamp desc}
| filter vulnerability.resolution.status == "OPEN"
| summarize count=count(), by:{vulnerability.risk.level}
| sort count desc

Step 2: Identify Affected Entities

// Which processes are vulnerable?
fetch security.events, from:now()-30d
| filter event.type == "VULNERABILITY_STATE_REPORT_EVENT" AND event.level == "ENTITY"
| dedup {vulnerability.display_id, affected_entity.id}, sort:{timestamp desc}
| filter vulnerability.resolution.status == "OPEN" AND vulnerability.risk.level == "HIGH"
| summarize vulns=count(), by:{affected_entity.name}
| sort vulns desc

Step 3: Check for Active Attacks

// Any attack attempts in the last 24h?
fetch security.events, from:now()-24h
| filter event.type == "ATTACK_EVENT"
| fields timestamp, attack.type, attack.source.ip, affected_entity.name
| sort timestamp desc

Step 4: Determine Exposure

Dynatrace automatically assesses exposure using Smartscape topology:

  • Public exposure: incoming requests from public IPs
  • Reachable data assets: traces service dependencies to find databases
  • Affected services: which services run the vulnerable library

Step 5: Remediate

Vulnerability Type          Remediation
โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€  โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€
Third-party library (TPV)   Upgrade the dependency (npm/pip/maven)
Runtime component           Upgrade Node.js/Java/.NET runtime
Code-level (CLV)            Fix the code pattern

After patching, vulnerabilities auto-close when the vulnerable library is no longer loaded for 2+ hours. State reports refresh every 30-60 minutes.

Attack Protection Modes

Mode      What It Does
โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€  โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€
MONITOR   Detect + alert, don't block (safe to start)
BLOCK     Detect + block + alert (production protection)
OFF       Disabled

Attack types detected: SQL injection, JNDI injection (Log4Shell), command injection, SSRF.

โ–ถ Knowledge Check

Q: How long after patching do vulnerabilities auto-close?

  • โŒ Immediately
  • โŒ After 30 minutes
  • โœ… After 2+ hours (when library is no longer loaded)