dynatrace/dynatrace-for-ai

dt-sec-semantic-mapping

Suggest and validate semantic dictionary (SD) mappings for new security integrations using vendor API samples or live events.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/dynatrace/dynatrace-for-ai --skill dt-sec-semantic-mapping

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

dt-sec-semantic-mapping

Build and validate semantic-dictionary-aligned mappings for new security integrations.

Purpose

Use this skill when a user wants to:

  • Suggest a mapping from vendor API output to Dynatrace security.events fields (Workflow A).
  • Validate an existing mapping for completeness and quality against:
  • Local baseline samples and semantic dictionary (Workflow B1 — static, offline validation), or
  • Live tenant data via live tenant access (Workflow B2 — runtime validation)
  • Highlight discrepancies vs. the Semantic Dictionary and local references.
  • Get actionable mapping improvements.

Semantic Dictionary

The Semantic Dictionary (SD) defines the canonical field set for security.events. See references/semantic-reference.md for the canonical reference: local-vs-live sources, queryable Grail tables, when-to-query decision matrix, and the authority rule (live SD wins on disagreement).

Required Inputs

Always run the intake checklist in references/intake-and-constraints.md before generating or validating a mapping. If inputs are incomplete, continue with a partial draft but explicitly list missing evidence and confidence limits.

Baseline Sources (self-contained)

All baseline material lives inside this skill:

  • samples/ — real integration payloads covering all finding types and providers. Consulted as a fallback when primary references (SD, data-model-notes, known-discrepancies, validation-rules, object-type-expectations) leave a specific question unresolved — not as a routine step on every workflow run.
  • references/semantic-reference.md — SD reference, field taxonomy, event types, provider taxonomy, and entity scoping
  • references/validation-policy-and-reporting.md — validation rules, acceptable discrepancies, and report templates
  • references/intake-and-constraints.md — intake checklist, output contract, object.type expectations, and OpenPipeline constraints

Event-Type Coverage Requirements

The mapping MUST address the correct set of event.type values per finding class. Detection integrations are push-based and do not use scan cycles — never require scan events for detection.

See validation-policy-and-reporting.md § Event-Type Coverage for the full table, severity rules, and the alternative-classification path when a detection-class mapping incorrectly emits *_SCAN events.

Workflows

This skill operates in three modes. Detect the mode from context:

ModeInputProcedural source
Workflow A — Suggest a new mappingRaw vendor API payloads onlyreferences/mapping-workflow.md § Workflow A (Phase 1 mapping table → user approval → Phase 2 sample JSON)
Workflow B1 — Static validationExisting mapping + vendor API samplesreferences/mapping-workflow.md § Workflow B — classify input mode (final ingested / theoretical), apply rules, produce diff-highlighted table
Workflow B2 — Runtime validationExisting mapping + live tenant accessreferences/runtime-validation.md — load the security (AppSec) events supporting skill first (REQUIRED Step 0), then run the query pack, produce a Validation Summary table

All workflows follow the output contracts in references/intake-and-constraints.md and the report templates in references/validation-policy-and-reporting.md. Validation rules (event-type coverage, required fields, scan references, namespace requirements, value/type checks, vendor-namespace duplication) live in references/validation-policy-and-reporting.md.

Acceptable Discrepancy Policy

See references/validation-policy-and-reporting.md for the canonical list of acceptable SD deviations and vendor-namespace patterns. Do NOT raise critical/major issues for fields on that list. Genuinely unknown fields (not in local refs AND not in the live SD — see references/semantic-reference.md) must be questioned per references/validation-policy-and-reporting.md.

Scope

This skill covers:

  • Mapping suggestion and refinement (Workflow A).
  • Static validation against local baseline examples and semantic dictionary (Workflow B1).
  • Runtime validation via live tenant access against live tenant data (Workflow B2).
  • Semantic-dictionary conformance checks.
  • Gap analysis and improvement recommendations.

This skill does not cover:

  • Live ingestion pipeline deployment.
  • Runtime DQL performance benchmarking.
  • Tenant-side ingestion troubleshooting.

References

  • references/semantic-reference.md — SD reference plus data-model notes: local sources, live (queryable) sources, DQL patterns, when-to-query decision matrix, authority rule, field taxonomy
  • A skill covering full SD access patterns and Grail-table documentation — for DQL query patterns against security.events and Grail tables
  • Semantic Dictionary (public docs)
  • references/intake-and-constraints.md — intake checklist, output contract, OpenPipeline constraints, and object.type namespace expectations
  • references/mapping-workflow.md — how to build and refine a mapping candidate
  • references/validation-policy-and-reporting.md — full validation rule set, known discrepancies, and discrepancy report templates
  • references/runtime-validation.md — optional real-environment query validation pack

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
dynatrace
コミュニティ

dt-obs-frontends

Real User Monitoring (RUM) on Dynatrace — web and mobile frontends. Core Web Vitals, user sessions, page performance, mobile crashes, frontend errors, and frontend-backend linking. Query via user.events, user.sessions, and dt.frontend. metrics. Does NOT cover synthetic monitoring (HTTP/browser/network checks) — that's a separate domain.

1時間の導入数
1
GitHub Stars
181
更新日
11月9日
dynatrace
コミュニティ

dt-obs-logs

Log querying, filtering, pattern analysis, and error rate calculation. Use when searching application or infrastructure logs, analyzing error patterns, or correlating log data. Trigger: "show error logs", "search logs for keyword", "log error rate", "recent errors", "logs from last hour", "find log entries", "top error messages", "log patterns", "parse JSON logs", "logs by process group", "log trends over time", "log entry counts per minute". Do NOT use for explaining existing queries, product d

1時間の導入数
1
GitHub Stars
181
更新日
11月9日
dynatrace
コミュニティ

dt-sec-contextualization

Resolve security signals, IoC matches, or Smartscape nodes to runtime entities, connect findings across entity levels, verify external findings against RVA on the same entity, and measure scan coverage against a Smartscape denominator. Covers identity mapping, RVA id resolution, K8s pod vs. node CVE topology, AI-service vulnerabilities, coverage counts. Trigger: "map these findings to workloads/hosts", "which workload does this image run as", "is this scanner finding also detected by RVA on a ru

1時間の導入数
1
GitHub Stars
181
更新日
11月9日
dynatrace
コミュニティ

dt-setup-openinference-migration

Migrate a GenAI/LLM app off Traceloop/OpenLLMetry onto OpenInference with its OTel genai. semconv option enabled (enablegenaisemconv / OPENINFERENCEENABLEGENAISEMCONV). Covers detecting the existing Traceloop setup, swapping the instrumentor per SDK, and the ingestion-shape question that decides what's fixable afterward — an app-owned OTel trace exporter vs. instrumentation-only with OneAgent picking up the spans. Flags that the semconv option is additive, not a replacement — legacy llm./openinf

1時間の導入数
1
GitHub Stars
181
更新日
11月9日