Skip to content

Amazon Bedrock configuration hardening security checks

Vendor-recommended secure defaults, patch levels and housekeeping settings that drift as tenants grow and admins change.

On Amazon Bedrock, Black Cat runs 12 checks in this area on every scan. Each one below lists its severity, how to fix it, and the compliance controls it satisfies where a control applies. See what access the Amazon Bedrock connector needs.

Checks (12)

severity: medium Bedrock Guardrail Weak Content Filters fix difficulty: easy #

Strengthen the guardrail's content filter strength and prompt-attack coverage

  1. Open AWS Bedrock Console > Guardrails
  2. Edit the guardrail's content filters
  3. Set input filter strength to MEDIUM or HIGH and enable a PROMPT_ATTACK filter

Vendor docs ↗

Satisfies: NIS2 Directive NIS2-21.e.4 DORA (SaaS Security) DORA-9.10

severity: high Bedrock No Guardrails Configured fix difficulty: medium #

Create at least one Bedrock Guardrail for this account/region

  1. Open AWS Bedrock Console > Guardrails
  2. Create a guardrail with content filters, denied topics, and PII redaction
  3. Attach it to models, agents, and flows as appropriate

Vendor docs ↗

Satisfies: NIS2 Directive NIS2-21.e.4 DORA (SaaS Security) DORA-9.10

severity: medium Bedrock Flow References Draft Prompt fix difficulty: easy #

Publish a versioned prompt and update the flow to reference it

  1. Open AWS Bedrock Console > Prompt management
  2. Create a version of the draft prompt used by the flow
  3. Update the flow's prompt node to reference the published version

Vendor docs ↗

Satisfies: NIS2 Directive NIS2-21.e.4 DORA (SaaS Security) DORA-9.10

severity: low Bedrock Orphaned Knowledge Base fix difficulty: easy #

Attach the knowledge base to an agent or delete it if unused

  1. Open AWS Bedrock Console > Knowledge bases
  2. Confirm whether the knowledge base is still needed
  3. Attach it to an agent, or delete it to reduce unmanaged data exposure

Vendor docs ↗

Satisfies: NIS2 Directive NIS2-21.e.4 DORA (SaaS Security) DORA-9.10

severity: high Bedrock Guardrail Filters Disabled fix difficulty: easy #

Re-enable input and output enforcement on every configured content filter

  1. Open AWS Bedrock Console > Guardrails and select the guardrail
  2. Under Content filters, turn input and output enforcement back on for each filter, or remove filters you do not intend to enforce
  3. Create a new guardrail version and confirm every filter shows enforcement enabled on both input and output

Vendor docs ↗

Satisfies: NIS2 Directive NIS2-21.e.4 DORA (SaaS Security) DORA-9.10

severity: low Bedrock Guardrail Without Contextual Grounding fix difficulty: easy #

Add a contextual grounding policy with grounding and relevance thresholds

  1. Open AWS Bedrock Console > Guardrails and select the guardrail
  2. Enable the contextual grounding check and set grounding and relevance thresholds (for example 0.7)
  3. Create a new guardrail version and test it against a RAG answer that is not supported by its source

Vendor docs ↗

Satisfies: NIS2 Directive NIS2-21.e.4 DORA (SaaS Security) DORA-9.10

severity: medium Bedrock AgentCore Gateway Without Policy Engine fix difficulty: medium #

Attach a policy engine so tool calls are checked against Cedar policies

  1. Open AWS Bedrock AgentCore Console > Policy and create a policy engine with Cedar policies for the gateway's tools
  2. Open Gateways, select the gateway and attach the policy engine
  3. Set the policy engine mode to ENFORCE after validating the policies in LOG_ONLY mode

Vendor docs ↗

Satisfies: NIS2 Directive NIS2-21.e.4 DORA (SaaS Security) DORA-9.10

severity: low Bedrock AgentCore Gateway Without WAF fix difficulty: easy #

Protect the gateway endpoint with an AWS WAF web ACL

  1. Open AWS WAF Console and create or choose a regional web ACL with the managed rule groups you need
  2. Associate the web ACL with the AgentCore gateway
  3. Confirm the gateway detail page in AWS Bedrock AgentCore Console > Gateways shows the web ACL ARN

Vendor docs ↗

Satisfies: NIS2 Directive NIS2-21.e.4 DORA (SaaS Security) DORA-9.10

severity: low Bedrock AgentCore Gateway Without Rate Limits fix difficulty: easy #

Configure rate limits on the gateway

  1. Open AWS Bedrock AgentCore Console > Gateways and select the gateway
  2. Add a rate limit sized to the expected request volume of the agents that call the gateway
  3. Save the gateway and confirm the rate limit appears in the gateway configuration

Vendor docs ↗

Satisfies: NIS2 Directive NIS2-21.e.4 DORA (SaaS Security) DORA-9.10

severity: low Bedrock AgentCore Runtime Public Network fix difficulty: medium #

Run the agent runtime in VPC network mode

  1. Open AWS Bedrock AgentCore Console > Runtimes and select the runtime
  2. Update the runtime's network configuration to VPC mode with private subnets and security groups
  3. Confirm the agent reaches only the endpoints it needs through the VPC

Vendor docs ↗

Satisfies: NIS2 Directive NIS2-21.e.4 DORA (SaaS Security) DORA-9.10

severity: medium Bedrock AgentCore Policy Engine Log-Only Policies fix difficulty: medium #

Enforce policies that are only logging violations

  1. Open AWS Bedrock AgentCore Console > Policy and select the policy engine
  2. Review the LOG_ONLY policies' logged decisions to confirm they would not block legitimate tool calls
  3. Switch each validated policy to ENFORCE

Vendor docs ↗

Satisfies: NIS2 Directive NIS2-21.e.4 DORA (SaaS Security) DORA-9.10

severity: medium Bedrock AgentCore Sandbox Public Network fix difficulty: medium #

Restrict the sandbox's network access

  1. Open AWS Bedrock AgentCore Console > Built-in tools and select the browser or code interpreter
  2. Create a replacement in VPC mode (or SANDBOX mode for a code interpreter) with the same settings
  3. Point the agents at the replacement and delete the public-network sandbox

Vendor docs ↗

Satisfies: NIS2 Directive NIS2-21.e.4 DORA (SaaS Security) DORA-9.10

More Amazon Bedrock checks

The information on this page is provided for general informational purposes and is believed to be accurate as of its most recent update. Product names, logos, and trademarks are the property of their respective owners and are used for identification purposes only; their use does not imply any affiliation with or endorsement by those owners. Descriptions of third-party applications and of compliance frameworks are based on publicly available documentation and may change over time.

See these checks run on your stack

Start a free 14-day trial — no credit card required.

Start Free Trial