Terminal
Terminal/Skill
Links security findings and IoC matches to the workloads, hosts and containers they run on in Dynatrace, for analysts checking exposure.
By Dynatrace
Works with
npx skills add dynatrace/dynatrace-for-ai --skill dt-sec-contextualizationResolve security signals and entity attribute sets to runtime Dynatrace
Smartscape entities, summarize findings across entity levels, and connect
signals that land on different levels (e.g. a detection on a K8S_POD vs.
a CVE on a KUBERNETES_NODE) via a shared runtime entity.
dt.smartscape_source.id, container_image.digest, container_image.id,
host.ip, dt.entity.*, or k8s.* fields, resolve it to a Smartscape
entity at any requested level (CONTAINER / K8S_POD / workload /
K8S_NODE / HOST / cloud / GENAI_SERVICE — AI/GenAI workloads).container_image.digest →
smartscapeNodes CONTAINER → is_part_of.* → parent workload or
runs_on.host → HOST. Works without pre-enriched dt.smartscape_source.id.K8S_POD to its K8S_NODE via
k8s.node.name (co-projected field) or Smartscape edge traversal. Enables
"detection hit pod X — does that pod run on a vulnerable node?"THREAT_REPORT events whose observable arrays contain that IoC.| Intent / trigger | Reference |
|---|---|
| Map findings / IoC matches to workloads, hosts, or cloud entities | identity-mapping.md -> entity-enrichment.md |
| Which Smartscape entity does this container image / digest run as? | identity-mapping.md § Mapping Primitive (Path 2 - container digest) |
| Do this detection and this CVE relate via a shared entity? | correlation-and-coverage.md § Correlation |
| Pod X fired - does it run on a vulnerable node? | correlation-and-coverage.md § Correlation (Pod->Node Topology) |
| Per-entity risk summary (Critical/High/Medium/Low) | entity-enrichment.md |
| Coverage match recipe - which workloads are covered by product Y? | correlation-and-coverage.md § Coverage |
| Which entity-identity fields are relevant to a finding type? | identity-mapping.md § Data Model |
| Enrich a matched IoC (IP/domain/hash/CVE/...) with threat-report adversary context | ioc-enrichment.md |
| Scope findings to AI/GenAI workloads; which processes belong to an AI service; resolve a process to its AI service | identity-mapping.md § Mapping Primitive (Path 4 - GENAI_SERVICE -> SERVICE -> PROCESS) |
THREAT_REPORT events and
surface adversary context (actor / malware / MITRE / targeting). Single and
batch (per-IoC) templates; supported-IoC taxonomy.dt-dql-essentials first — DQL syntax and function names
differ from SQL. Confirm all functions before generating queries.dt.smartscape_source.type before trusting Path 1 — a non-null
dt.smartscape_source.id is not proof of workload-level resolution; the
field may point to a namespace, cluster, or cloud resource. Only K8s workload
types (K8S_DEPLOYMENT, K8S_DAEMONSET, K8S_STATEFULSET, K8S_CRONJOB,
K8S_JOB, K8S_REPLICASET) are eligible for workload enrichment via Path 1.append — dedup before joins to collapse
re-ingested duplicates; dedup again after append because the same finding
can match multiple paths.dt-obs-kubernetes — pod→node placement and
Smartscape edge traversal patterns live in
dt-obs-kubernetes/references/pod-node-placement.md. Do not re-author
them here; reference them and apply the output in correlation-and-coverage.md.dt.system.bucket filters — security event data may live in any
bucket; filtering by bucket risks hiding findings.security.events query allowed here — reverse
lookup only. ioc-enrichment.md attributes a matched IoC to reports
(IoC → report). Broad THREAT_REPORT overviews, IOC rollups, and forward
report → environment correlation stay in dt-sec-insights
(threat-intelligence.md). Never author finding/posture queries here.| Skill | Role |
|---|---|
dt-dql-essentials | Load first. Core DQL syntax, functions, Smartscape patterns. |
dt-sec-insights | Consumer of mapping primitive; owns finding-schema queries and coverage counting logic. Owns forward threat-intel (report → environment correlation, overviews, IOC rollups) in threat-intelligence.md; this skill owns only the reverse IoC → report enrichment (ioc-enrichment.md). |
dt-sec-ioc-hunting | Routes cross-evidence correlation and entity enrichment to this skill. |
dt-obs-kubernetes | Pod→node topology; K8s entity placement patterns. |
dt-obs-hosts | Host inventory; process-level context for HOST/PROCESS_GROUP findings. |
dt-obs-aws / dt-obs-azure / dt-obs-gcp | Cloud Smartscape topology for cloud-entity enrichment. |