Published event
CloudInfrastructure
SecurityIncident
1 source(s)
How Benchling secured multi-tenant AI agents with Amazon Bedrock AgentCore
Summary
How Benchling secured multi-tenant AI agents with Amazon Bedrock AgentCore How Benchling secured multi-tenant AI agents with Amazon Bedrock AgentCore When Benchling needed to run AI agent-generated scientific code across thousands of life sciences tenants, their security team found that traditional sandboxing wasn’t enough. Today, this architecture processes more than 600 code execution sessions per day across more than 250 tenants per week with zero security incidents.
Why it matters
This SecurityIncident is relevant to the technology intelligence record because it involves Amazon, Amazon Web Services, Intel, Amazon Bedrock. The source article should remain the factual reference for follow-up coverage.
Key facts
- How Benchling secured multi-tenant AI agents with Amazon Bedrock AgentCore When Benchling needed to run AI agent-generated scientific code across thousands of life sciences tenants, their security team found that traditional sandboxing wasn’t enough.
- Today, this architecture processes more than 600 code execution sessions per day across more than 250 tenants per week with zero security incidents.
- Standard network controls block HTTP, restrict egress ports, and limit outbound connections.
- However, DNS resolution is often still permitted, and even when system defaults restrict it, you may not have visibility into or control over those restrictions.
- This is the challenge Benchling faced when deploying AI agents across thousands of life sciences tenants.
- Their security team needed full control over network isolation beyond the system defaults to meet their threat model for executing untrusted code at scale.
Entities in this story
Related events