Toc Consulting’s 2026 AWS Security Report Examines IAM and Agentic AI Risks
Report discovered via Awesome Annual Security Reports.

Summary
Toc Consulting’s 2026 AWS security whitepaper examines identity misconfigurations, S3 ransomware, and agentic AI risks, with practical controls, audit checklists, and a 90-day hardening roadmap.
Key points
- The whitepaper prioritizes MFA, temporary credentials, least-privilege roles, and organizational guardrails to reduce risks from stolen credentials and excessive permissions.
- It describes Codefinger operators using compromised AWS credentials to re-encrypt S3 objects with attacker-controlled SSE-C keys, underscoring the need for protected, independent backups.
- Existing AmazonGuardDutyFullAccess v1 policy attachments require manual migration to v2, which restricts delegated-administrator registration to specified GuardDuty services.
- For monitoring and response, the guide recommends centralized, tamper-protected CloudTrail logs, selective data-event logging, and EventBridge-triggered remediation of high-confidence findings.
- The report explains how prompt injection can turn an AI agent into a confused deputy, exercising permissions broader than those of the requesting user.
- It distinguishes Bedrock Guardrails’ content filtering from AgentCore’s external Cedar-based tool-call authorization; AgentCore Policy Controls remained in preview as of February 2026.
- Its action plan sequences 30-day baseline improvements before broader 90-day hardening, with agent-specific incident playbooks, MCP tool validation, and human approval for high-risk actions.
Article Details
- Publisher
- Toc Consulting
- Report Period
- 2026 edition, published February 2026; primarily discusses 2025–2026 developments
- Scope
- AWS security architecture, identity, data protection, networking, detection, agentic AI security, and compliance.
- Key Statistics
- The cited Verizon 2025 DBIR examined 22,052 incidents and 12,195 confirmed breaches; compromised credentials were the initial access vector in 22% of breaches.
- According to the cited Verizon 2025 DBIR, third-party involvement in breaches increased from 15% to 30% year over year.
- The cited IBM 2025 report found that 13% of organizations experienced breaches of AI models or applications; 97% of those organizations lacked proper AI access controls.
- According to the cited Akto 2025 report, only 21% of enterprises had full visibility into agent actions, MCP tool invocations, or data access.
- The cited Cisco State of AI Security 2026 report found that 83% of organizations planned to deploy agentic AI capabilities, while 29% felt ready to do so securely.
- Recommendations
- Replace long-lived human access credentials with temporary role-based access, enforce MFA, delete root access keys, and review unused or overly permissive permissions.
- Block unnecessary SSE-C encryption and public S3 access; protect critical data with versioning, immutable storage, and independent cross-region backups.
- Enable centralized, multi-region CloudTrail logging with integrity validation, sensitive-resource data events, threat detection, and automated remediation for high-confidence findings.
- Constrain AI agents with unique identities, least-privilege execution roles, external action policies, content guardrails, and human approval for high-risk operations.
- Pin and verify MCP tool versions, treat tool responses as untrusted data, enable model invocation logging, and test agent containment procedures quarterly.
MITRE ATT&CK
T1078.004 · Cloud AccountsReported AWS intrusions used compromised cloud credentials, including exposed access keys, to access customer environments.T1098.003 · Additional Cloud RolesJavaGhost created IAM roles with trust policies granting cross-account access to attacker-controlled AWS accounts.T1136.003 · Cloud AccountThe intrusion documented by Sysdig created a backdoor administrative AWS user; JavaGhost also created cloud users for phishing operations.T1485 · Data DestructionCodefinger attackers configured S3 lifecycle management to automatically delete affected files within seven days.T1486 · Data Encrypted for ImpactThe Codefinger operation overwrote S3 objects using SSE-C encryption with attacker-controlled keys and demanded ransom.T1496 · Resource HijackingThe Sysdig-documented attacker invoked foundation models at the victim's expense and provisioned a GPU instance for persistent compute access.T1552.001 · Credentials In FilesThe Sysdig-documented intrusion began with valid AWS credentials exposed in publicly accessible S3 buckets containing RAG data.T1648 · Serverless ExecutionThe Sysdig-documented attacker modified existing Lambda function code and configuration to escalate privileges.
CVE
CVE-2025-32711documented incidents in 2025. EchoLeak (CVE-2025-32711), a zero‑click prompt injectionCVE-2025-53773Copilot (CVE-2025-53773) and Cursor IDE (CVE-2025-59944) both had remote code executionCVE-2025-59944Copilot (CVE-2025-53773) and Cursor IDE (CVE-2025-59944) both had remote code execution
People
Threat Actors
Vendors
Products
Amazon GuardDuty| GuardDuty | SecurityHub | | CloudTrail | Inspector | | Detective | Macie | Config |Amazon S3| Amazon S3 | | | November 2024 (launch) | | |AWS Audit ManagerAWS Audit Manager provides a prebuilt framework for ISO/IEC 27001:2013 Annex A (not theAWS Configconfiguration assessment (AWS Config), behavioral threat detection (GuardDuty), correlated riskAWS LambdaLangChain deployments on Lambda, and enterprise‑built agent frameworks grant AI systemsBedrock GuardrailsAmazon Bedrock Guardrails: Content‑Level ProtectionCloudTrail| GuardDuty | SecurityHub | | CloudTrail | Inspector | | Detective | Macie | Config |CursorCopilot (CVE-2025-53773) and Cursor IDE (CVE-2025-59944) both had remote code executionDevin AIweaknesses in Devin AI, an autonomous coding agent, that allowed attackers to expose ports,GitHub CopilotGitHub Copilot RCE Prompt injection in GitHub Copilot manipulated VS Code ASI05IAM Access AnalyzerIAM Access Analyzer's unused access findings.IAM Identity CenterThe fix: Use IAM Identity Center with temporary credentials for human access. Use IAM roles forMicrosoft 365 Copilotvulnerability in Microsoft 365 Copilot, allowed remote data exfiltration through craftedSecurity Hub CSPMaggregation, and Security Hub CSPM for compliance standards and security checks. This