Skip to main content

Enable AI-specific analytics rules for prompt injection detection

Implementation Effort: Medium – Requires identifying and enabling the relevant built-in analytics rule templates from the Content hub, mapping entity types to AI workload identities, and tuning thresholds to the organization's AI usage patterns.
User Impact: Low – Analytics rules run in the background; end users are not affected.

Overview

A Sentinel workspace with connected data sources collects AI workload telemetry, but raw data in a Log Analytics table does not generate alerts or incidents on its own. Analytics rules are the layer that converts collected data into actionable detections. For AI workloads, the built-in rule templates in the Content hub include detections for prompt injection patterns, suspicious token usage, and anomalous AI service access patterns. Without enabling these rules, the telemetry flows in but the SOC receives no signal — threat actors can execute prompt injection attacks, probe for jailbreak vulnerabilities, and exfiltrate data through AI interactions without triggering a single alert.

Enabling built-in analytics rules is the fastest path to detection coverage for known AI threat patterns. These templates are maintained by Microsoft's security research teams and updated as new attack techniques emerge. The organization should enable all templates relevant to its AI workload footprint and tune the scheduling intervals and alert thresholds to balance detection latency against false positive volume.

This supports Assume breach by ensuring that known AI attack patterns — prompt injection, jailbreak attempts, anomalous token consumption — generate alerts and incidents that the SOC can investigate and respond to. It supports Verify explicitly by subjecting AI workload activity to continuous rule-based evaluation rather than trusting that AI services will self-report security issues. Without these rules enabled, the Sentinel workspace is a passive data store with no detection capability, and AI threats go undetected regardless of how much telemetry is collected.

Reference