Wiz Details AI-Agent Detection Pipeline Using Model Logs and Runtime Telemetry

Summary
Wiz describes a detection pipeline that analyzes AI-agent input and output logs, then correlates findings with cloud and runtime activity to identify malicious behavior. Bedrock invocation-log support is in private preview for Wiz Defend customers.
Key points
- Wiz says model input and output logs can reveal when an agent’s intent shifts, including when untrusted ticket content prompts an agent to send phishing email.
- The pipeline screens collected telemetry with patterns, Wiz Secrets Engine, and small language models before applying progressively deeper LLM analysis.
- It correlates model prompts and tool calls with cloud events, process executions, and network activity to assess whether actions had real-world impact.
- Wiz describes a simulation in which an agent induced CI/CD and data-analysis agents to exfiltrate sensitive data to an agent-managed resource.
- The benchmark includes 102 simulated scenarios: 57 injected attacks and 45 benign workflows, spanning prompt injection, data theft, secrets abuse, execution, and supply-chain attacks.
- Bedrock invocation logs are available to Wiz Defend customers in private preview.
Article Details
- Defense Focus
- Detect malicious shifts in AI-agent intent by analyzing model input and output telemetry and correlating agent intentions with actions and effects in cloud and runtime environments.
- Detection Methods
- Collect model-provider and cloud-service logs containing prompts, system instructions, tool specifications and results, model outputs, and reasoning.
- Use regex patterns, Wiz Secrets Engine, and SLMs to surface initial candidates for potentially malicious activity.
- Apply staged LLM analysis: first filter benign logs and identify suspicious activity, then analyze selected conversations in greater depth using environmental context.
- Correlate analysis verdicts with cloud and runtime events to establish whether intended actions occurred and assess their impact.
- Validate pipeline changes against a benchmark of simulated benign workflows and injected attacks.
- Data Sources
- Model input and output logs, including user requests, system prompts, tool descriptions, tool results, outputs, and internal reasoning
- Cloud-service and model-provider logs
- Cloud events and cloud API calls
- Runtime telemetry, including process executions and network connections
- Identity information and environmental context
- Rule Types
- Regex-pattern candidate matching
- Threat Detection Rules applied to enriched cloud events
- Platforms
- Bedrock invocation logs
- Defensive Actions
- Enable collection of model invocation logs and retain the prompt, tool-call, and tool-result context needed to investigate agent behavior.
- Analyze untrusted inputs together with model reasoning and subsequent tool calls to identify indirect prompt injection and suspicious intent shifts.
- Correlate model-layer findings with cloud API, process, and network telemetry before determining whether an action had real-world impact.
- Use staged analysis to prioritize suspicious conversations while filtering benign activity and reducing noise.
- Test detection updates against both injected attacks and benign workflows to assess coverage and false positives.
Vendors
Hugging FaceThe need for this visibility was on full display during the Hugging Face incident, disclosed by OpenAI in the summer of 2026. At Wiz, we have been building and improving our own detection pipeline to tackle theOpenAIIn this blog, we explore how a benign task assigned to an OpenAI agent escalated into a security breach, and why model input and output telemetry is key to detecting intent manipulation.Wizwas on full display during the Hugging Face incident, disclosed by OpenAI in the summer of 2026. At Wiz, we have been building and improving our own detection pipeline to tackle the challenge of understanding
Products
Amazon BedrockBedrock invocation logs are available today for Wiz Defend customers in private preview. If you’re an existing Wiz customer and want to join the private preview, please reach out to your Wiz account manager. For newSESsecurity tools, this looks like standard, authorized traffic: an authenticated service account calling SES as intended. Only by analyzing the model invocation logs can we really understand and investigate what isWiz DefendBedrock invocation logs are available today for Wiz Defend customers in private preview. If you’re an existing Wiz customer and want to join the private preview, please reach out to your Wiz account manager. For newWiz Secrets Engineof candidates of potentially malicious activity by matching against common Regex patterns, The Wiz Secrets Engine and various SLMs. This is a great starting point for surfacing malicious activity and catching