Bedrock agent IAM role has broad permissions

Severity: Critical
Service: Bedrock
Check ID: BEDROCK_AGENT_OVERPERMISSIONED

What this check finds

A Bedrock agent's execution IAM role includes admin-level or wildcard action permissions. Agents with overpermissioned roles can be abused via prompt injection.

Passing looks like: Bedrock agent role least-privileged.

How to fix it

Scope the agent role to minimum required actions. Remove wildcard (*) from Action in the role policy. Review with IAM Access Analyzer.

Compliance controls it is evidence for

A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works

Compliance controls mapped to Bedrock agent IAM role has broad permissions
Framework	Controls
PCI-DSS v4.0.1	7.2 Access to system components and data is appropriately defined and assigned
HIPAA Security Rule	164.312(a)(1) Access Control — Unique User Identification
SOC 2 — Trust Services Criteria	CC6.2 Role-Based Access Control
NIST SP 800-53 Rev5 (Moderate)	AC-6 Least Privilege
NIST Cybersecurity Framework 2.0	PR.AA-05 Access permissions and authorizations are enforced with least privilege
ISO/IEC 27001:2022 Annex A	A.8.2 Privileged access rights

AI risk mappings

AI risk taxonomies mapped to Bedrock agent IAM role has broad permissions
Framework	Controls
OWASP Top 10 for LLM Applications (2025)	LLM06 Excessive Agency
MITRE ATLAS (Adversarial Threat Landscape for AI Systems)	AML.T0012 Valid Accounts AML.T0053 LLM Plugin Compromise

Checked on every scan

KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs

More Bedrock checks

All Bedrock checks