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 .
- aws.amazon.com Agent memory & RAG architectures
AI best practices for AWS network operations with AI ...
AWS published a technical pattern for network-operations agents using Amazon Bedrock AgentCore Memory. The approach persists context across sessions, allowing an agent to learn from prior investigations, while AgentCore Observability records traces, logs, and metrics and the Agen
- github.com Agent memory & RAG architectures
NousResearch/hermes-agent: The agent that grows with you
AWS published a technical pattern for network-operations agents using Amazon Bedrock AgentCore Memory. The approach persists context across sessions, allowing an agent to learn from prior investigations, while AgentCore Observability records traces, logs, and metrics and the Agen
- idc.com Agent memory & RAG architectures
Snapdragon Summit 2026: Qualcomm's Agentic AI Push
AWS published a technical pattern for network-operations agents using Amazon Bedrock AgentCore Memory. The approach persists context across sessions, allowing an agent to learn from prior investigations, while AgentCore Observability records traces, logs, and metrics and the Agen
- aiagentstore.ai high confidence Enterprise AI agent deployments
AI Agents News — Week of July 28, 2026 (Daily Updates)
A McKinsey report indicates that 45% of Fortune 500 companies are now operating AI agents in production environments, a significant increase from 8% in 2024.
- github.blog high confidence Autonomous coding agents
Agentic autofix now uses Copilot Memory - GitHub Changelog
GitHub’s agentic autofix now uses Copilot Memory for customers who enable it. The security-fix agent can use existing repository memories for context and save successful fix patterns for future alerts. These memories can also inform Copilot code review and Copilot cloud agent. Bo
External links matched to this session via topic relevance. The KB does not endorse third-party content; verify before citing.