prowler-cloud/prowler

[New Check]: Bedrock agent execution roles follow least privilege

已關閉

#11,011 建立於 2026年5月5日

 (2 則留言) (0 個反應) (1 位負責人)Python (1,322 個分叉)batch import
feature-requestgood first issuenew-checkprovider/aws

倉庫指標

星標
 (8,957 顆星)
PR 合併指標
 (平均合併 9天 17小時) (30 天內合併 314 個 PR)

描述

Existing check search

  • I have searched existing issues, Prowler Hub, and the public roadmap, and this check does not already exist.

Provider

AWS

New provider name

No response

Service or product area

bedrock

Suggested check name

bedrock_agent_role_least_privilege

Context and goal

  • Security condition to validate: Bedrock Agent execution roles (agentResourceRoleArn) follow least privilege — no full-access managed policies, no Resource: "*" wildcards, a permissions boundary set, and VPC condition keys when applicable.
  • Why it matters: A permissive agent execution role turns prompt injection into privilege escalation — the agent can be steered into any action the role allows.
  • Resource involved: Bedrock Agent → IAM execution role (attached/inline policies, permissions boundary, condition keys).

Expected behavior

  • Resource or scope to evaluate: Each Bedrock Agent's execution role.
  • PASS when: no full-access managed policy, no Allow + Resource: "*" with broad actions, a permissions boundary is set, and VPC conditions are present when the role acts on VPC resources.
  • FAIL when: any of the above is violated.

References

Suggested severity

High

Additional implementation notes

No response

貢獻者指南