Amazon Bedrock data sharing & exposure security checks
External sharing, public links, guest access, retention and data-protection settings that quietly push company data outside the tenant.
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 Agent Multiple Knowledge Bases fix difficulty: medium #
Review data exposure from multiple knowledge bases
- Open AWS Bedrock Console > Agents
- Review each knowledge base and its data source
- Remove unnecessary knowledge base associations
Satisfies: NIS2 Directive NIS2-21.a.3 DORA (SaaS Security) DORA-9.12
severity: medium Bedrock Agent No Customer-Managed Encryption fix difficulty: medium #
Configure a customer-managed KMS key for the agent
- Open AWS KMS Console and create or select a key
- Open AWS Bedrock Console > Agents
- Update the agent to use the customer-managed key
Satisfies: NIS2 Directive NIS2-21.a.3 DORA (SaaS Security) DORA-9.12
severity: low Bedrock Agent Session Memory Enabled fix difficulty: easy #
Review if session memory is appropriate for this agent's data sensitivity
- Assess what data the agent processes
- If handling sensitive data, disable session memory
Satisfies: NIS2 Directive NIS2-21.a.3 DORA (SaaS Security) DORA-9.12
severity: medium Bedrock Agent Long Session TTL fix difficulty: easy #
Reduce idle session TTL to 30 minutes or less
- Open AWS Bedrock Console > Agents
- Update the agent idle session timeout to 1800 seconds or less
Satisfies: NIS2 Directive NIS2-21.a.3 DORA (SaaS Security) DORA-9.12
severity: medium Bedrock Guardrail Without Customer-Managed Key fix difficulty: easy #
Encrypt the guardrail with a customer-managed KMS key
- Open AWS Bedrock Console > Guardrails and select the guardrail
- Edit the guardrail and choose a customer-managed KMS key under encryption, then create a new version
- Confirm the guardrail detail page shows the KMS key ARN and update agents to the new version
Satisfies: NIS2 Directive NIS2-21.a.3 DORA (SaaS Security) DORA-9.12
severity: medium Bedrock Guardrail PII Detect-Only fix difficulty: easy #
Set every PII entity action to BLOCK or ANONYMIZE
- Open AWS Bedrock Console > Guardrails and select the guardrail
- Under Sensitive information filters, change each PII entity set to Detect (NONE) to Block or Mask (ANONYMIZE)
- Create a new guardrail version and confirm no PII entity remains in detect-only mode
Satisfies: NIS2 Directive NIS2-21.a.3 DORA (SaaS Security) DORA-9.12
severity: high Bedrock Knowledge Base On Third-Party Vector Store fix difficulty: medium #
Review the third-party vector store contract, network path and encryption, or migrate to an AWS-managed store
- Open AWS Bedrock Console > Knowledge bases and note the vector store configured for the knowledge base
- Confirm the vendor's data processing agreement, network path (private endpoint) and encryption at rest, or recreate the knowledge base on an AWS-managed store such as OpenSearch Serverless, Aurora or S3 Vectors
- Re-sync the data source and confirm the knowledge base detail page shows the approved storage type
Satisfies: NIS2 Directive NIS2-21.a.3 DORA (SaaS Security) DORA-9.12
severity: low Bedrock Flow Without Customer-Managed Key fix difficulty: easy #
Encrypt the flow with a customer-managed KMS key
- Open AWS Bedrock Console > Flows and select the flow
- Edit the flow details and choose a customer-managed KMS key for encryption
- Save and prepare the flow, then confirm the flow detail page shows the KMS key ARN
Satisfies: NIS2 Directive NIS2-21.a.3 DORA (SaaS Security) DORA-9.12
severity: medium Bedrock Agent Relays History To Collaborators fix difficulty: easy #
Disable conversation-history relay or clear every collaborator for the shared data
- Open AWS Bedrock Console > Agents, select the supervisor agent and open Multi-agent collaboration
- For each collaborator, set conversation history relay to Disabled unless the collaborator is cleared for the data users share
- Prepare the agent and confirm each collaborator shows relay disabled or is documented as approved
Satisfies: NIS2 Directive NIS2-21.a.3 DORA (SaaS Security) DORA-9.12
severity: medium Bedrock AgentCore Gateway Without Customer-Managed Key fix difficulty: easy #
Encrypt the gateway with a customer-managed KMS key
- Open AWS KMS Console and create or choose a customer-managed key whose key policy allows AgentCore to use it
- Open AWS Bedrock AgentCore Console > Gateways, select the gateway and set the KMS key
- Confirm the gateway detail page shows the KMS key ARN
Satisfies: NIS2 Directive NIS2-21.a.3 DORA (SaaS Security) DORA-9.12
severity: medium Bedrock AgentCore Memory Without Customer-Managed Key fix difficulty: easy #
Encrypt agent memory with a customer-managed KMS key
- Open AWS KMS Console and create or choose a customer-managed key whose key policy allows AgentCore to use it
- Create a new memory in AWS Bedrock AgentCore Console > Memory with that KMS key
- Point the agents at the new memory and delete the unencrypted one
Satisfies: NIS2 Directive NIS2-21.a.3 DORA (SaaS Security) DORA-9.12
severity: low Bedrock AgentCore Memory Long Retention fix difficulty: easy #
Shorten the memory's event retention to 90 days or less
- Open AWS Bedrock AgentCore Console > Memory and select the memory
- Set the event expiry to 90 days or less
- Save the memory and confirm the new expiry on its detail page
Satisfies: NIS2 Directive NIS2-21.a.3 DORA (SaaS Security) DORA-9.12