Explore a practical framework to think about and build secure AI agents on Amazon Bedrock AgentCore. This session covers threat modeling specific to agentic workloads, including how agents interact with tools, memory, and external systems, and what you need to watch out for. You'll learn how to apply AWS security best practices across AgentCore services, and walk away with actionable patterns. Suitable for developers and architects building AI agents who want to move from prototype to production with confidence.
What this session is about
Playbook
Editorial commentary · what to actually do about this on Monday
The concept
Threat-modeling agentic workloads specifically — tool surface, memory, external system interactions. Apply AWS security best practices across AgentCore components.
Why it matters
Agent threat models differ meaningfully from API threat models. Your existing security playbook misses tool injection, memory poisoning, and prompt-via-data attacks.
The hard parts
Tool injection (an agent tricked into calling a tool with malicious args). Memory poisoning (an agent's long-term memory corrupted by an attacker). Prompt-via-data (instructions embedded in retrieved content).
Playbook moves
(1) Run STRIDE per agent component (memory, tool registry, planner, executor). (2) Specifically check: who can mutate memory, who can register new tools, who validates tool outputs before they're trusted. (3) Sandbox every tool execution that touches external systems.
The surprise
The most common agent vulnerability in real deployments is *over-broad tool scopes*. Engineers grant tools more permission than needed because it's faster. Audit tool permissions like you audit IAM. Most don't, and it shows up as blast radius when things go wrong.
---
Independent editorial perspective — not an official AWS or speaker statement. Designed for executives evaluating what to brief their teams on next.
Live updates related to this session LIVE
Sourced via Parallel AI Monitor — continuous web watch on 21 topical streams. Updated .
- newsroom.workday.com high confidence Agent dev tools & observability
Workday Launches New Tools for Developers to Build, ...
AWS launched several Bedrock AgentCore updates on June 17, 2026, including the Optimization Loop for monitoring production traces (failure, intent, and trajectory insights) and the general availability of the AgentCore harness for building and orchestrating agents. Pricing is int
- tarka.ai high confidence Agent dev tools & observability
The Center of AI Moved Away from OpenAI
AWS launched several Bedrock AgentCore updates on June 17, 2026, including the Optimization Loop for monitoring production traces (failure, intent, and trajectory insights) and the general availability of the AgentCore harness for building and orchestrating agents. Pricing is int
- aboutamazon.com high confidence Agent dev tools & observability
AWS Summit New York 2026: New AI agent innovations
AWS launched several Bedrock AgentCore updates on June 17, 2026, including the Optimization Loop for monitoring production traces (failure, intent, and trajectory insights) and the general availability of the AgentCore harness for building and orchestrating agents. Pricing is int
- itecsonline.com high confidence Agent benchmarks & evals
Agentic AI Governance Framework 2026 | Shadow AI Guide | ITECS
mem0.ai released the 'State of AI Agent Memory 2026', featuring a new benchmark that evaluates 10 different AI agent memory architectures across 21 integrations to determine the most effective patterns for production agent memory.
- blog.cloudflare.com high confidence Agent frameworks (LangGraph, CrewAI, AutoGen)
Building the agentic cloud: everything we launched during Agents ...
Microsoft Agent Framework released dotnet-1.11.1 on June 25, 2026. This update includes a breaking change where all AgentSkillsProvider tools now require approval by default. It also introduces DeclarativeWorkflowJsonOptions for AOT-safe checkpointing and fixes for resuming check
External links matched to this session via topic relevance. The KB does not endorse third-party content; verify before citing.