# tenant data protection

A security concept for protecting an organization's data within its tenant boundary in multi-tenant computing systems.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Best Tools for Multi-Tenant API Credentials

DevFeed: [Best Tools for Multi-Tenant API Credentials](<https://devfeed.tech/articles/best-tools-for-multi-tenant-api-credentials-146954.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/best-multi-tenant-credential-tools>)

Author: Swytchcode Team

Published: 2026-11-20T09:00:00Z

Content type: comparison

Language: en

Sources: [Swytchcode](<https://devfeed.tech/sources/swytchcode.md>)

Topics: [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [AI Context Management](<https://devfeed.tech/topics/ai-context-management.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [agents](<https://devfeed.tech/tags/agents.md>), [api](<https://devfeed.tech/tags/api.md>), [best](<https://devfeed.tech/tags/best.md>), [call](<https://devfeed.tech/tags/call.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [customer](<https://devfeed.tech/tags/customer.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [multi-tenant](<https://devfeed.tech/tags/multi-tenant.md>), [risk](<https://devfeed.tech/tags/risk.md>), [tenant](<https://devfeed.tech/tags/tenant.md>), [token](<https://devfeed.tech/tags/token.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

The key risk in multi-tenant agents is a valid API call using the wrong customer's token. Nango, WorkOS Pipes, and Auth0 Token Vault enforce tenant boundaries through storage or tenant context; Composio and Arcade require each call to identify the acting user, so isolation depends on the calling code or identity-provider check. Paragon/ActionKit ties pricing to connected users, while Arcade charges per auth event and tool call. Swytchcode selects credentials per tenant at execution time, runs on customer-controlled infrastructure, and adds policy checks, safe retries, validation, and audit records, but does not host an end-user OAuth connection screen. The excerpt frames Swytchcode as an execution layer that can complement a separate connection product.

### Source excerpt

The real risk in multi-tenant agents is a correct-looking call that runs against the wrong customer's token. Here's who actually stops that.

## CVE-2026-86061 - Teable: child-resource lookups permit cross-tenant data access and modification

DevFeed: [CVE-2026-86061 - Teable: child-resource lookups permit cross-tenant data access and modification](<https://devfeed.tech/articles/cve-2026-86061-teable-child-resource-lookups-permit-cross-tenant-data-access-and-modification-138225.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-86061>)

Author: CVEFEED.io; github.com

Published: 2026-11-17T18:17:59Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Authorization](<https://devfeed.tech/topics/authorization.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [enterprise data protection](<https://devfeed.tech/topics/enterprise-data-protection.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [base](<https://devfeed.tech/tags/base.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cve-2026-86061](<https://devfeed.tech/tags/cve-2026-86061.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [data](<https://devfeed.tech/tags/data.md>), [delete](<https://devfeed.tech/tags/delete.md>), [embedded](<https://devfeed.tech/tags/embedded.md>), [field](<https://devfeed.tech/tags/field.md>), [filter](<https://devfeed.tech/tags/filter.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [identifier](<https://devfeed.tech/tags/identifier.md>), [installation](<https://devfeed.tech/tags/installation.md>), [issue](<https://devfeed.tech/tags/issue.md>), [layout](<https://devfeed.tech/tags/layout.md>), [teable](<https://devfeed.tech/tags/teable.md>), [teableio](<https://devfeed.tech/tags/teableio.md>), [tenant](<https://devfeed.tech/tags/tenant.md>)

### AI overview

Before Teable release 2026-07-17T05-20-38Z.2264, authenticated users could target other plugins to rotate and disclose OAuth secrets or delete plugins, including system plugins, because the relevant methods lacked permission decorators and ownership checks. Separately, nested API authorization trusted a caller-supplied parent table, base, or space while services looked up child resources only by ID. This could expose another tenant's view configuration, filter values, field layout, and shareId, or let attackers overwrite plugin storage when installations were not tied back to the authorized resource. The issue is fixed in release 2026-07-17T05-20-38Z.2264.

### Source excerpt

CVE ID :CVE-2026-86061 Published : Nov. 17, 2026, 6:17 p.m. | 32 minutes ago Description :Teable is an AI spreadsheet for business. Prior to release.2026-07-17T05-20-38Z.2264, the routes for PluginService::regenerateSecret and PluginService::delete carry no @Permissions decorator, and the methods omit plugin ownership checks. An authenticated attacker can directly target another plugin's identifier to rotate and disclose its OAuth secret or delete the plugin, including system plugins. Separately, PermissionGuard authorizes several nested API requests using a caller-controlled parent tableId, baseId, or spaceId, while the services resolve the requested child object only by its globally unique identifier. An authenticated attacker can provide a parent resource the attacker owns together with a victim's child identifier. ViewService::getViewById can then disclose another tenant's view configuration, embedded filter values, field layout, and shareId. DashboardService::updatePluginStorage and the view-position updatePluginStorage path can overwrite another tenant's plugin storage because the plugin installation is not rebound to the authorized base, dashboard, table, or view. This issue is fixed in release.2026-07-17T05-20-38Z.2264. Severity: 8.8 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## How Duco transforms financial data automation with Amazon Bedrock AgentCore

DevFeed: [How Duco transforms financial data automation with Amazon Bedrock AgentCore](<https://devfeed.tech/articles/how-duco-transforms-financial-data-automation-with-amazon-bedrock-agentcore-136363.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/how-duco-transforms-financial-data-automation-with-amazon-bedrock-agentcore/>)

Author: Rob Gates

Published: 2026-11-16T22:06:08Z

Content type: article

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>)

Tags: [agentcore](<https://devfeed.tech/tags/agentcore.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-stack](<https://devfeed.tech/tags/ai-stack.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [automation](<https://devfeed.tech/tags/automation.md>), [banks](<https://devfeed.tech/tags/banks.md>), [bedrock](<https://devfeed.tech/tags/bedrock.md>), [bedrock-agentcore](<https://devfeed.tech/tags/bedrock-agentcore.md>), [context](<https://devfeed.tech/tags/context.md>), [costs](<https://devfeed.tech/tags/costs.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [data](<https://devfeed.tech/tags/data.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [financial](<https://devfeed.tech/tags/financial.md>), [financial-data](<https://devfeed.tech/tags/financial-data.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Duco rebuilt its financial operations agent stack on Amazon Bedrock and Amazon Bedrock AgentCore, pairing model choice by task with dedicated per-tenant runtimes, gateways, identity controls, and isolated data infrastructure. To address 300-400 tools generating about 200,000 tokens of context per tenant, it loads MCP skill descriptions on demand; this reduced main context to about 20,000 tokens while preserving prompt caching, with response quality improvements validated through evaluations. Agents support reconciliation onboarding and first-mile exception investigation, with analysts retaining final decisions and high-risk actions requiring authorization. Duco reports reconciliation deployments 10x faster; one global bank saw onboarding costs fall 70% and straight-through processing rise by over 20%.

### Source excerpt

Duco, a data automation platform for tier-one banks, rebuilt its agentic AI stack on Amazon Bedrock and Amazon Bedrock AgentCore. With strict per-tenant isolation, a multi-model strategy, and an MCP skills architecture that cut context overhead by 90%, Duco cut reconciliation deployment time 10x and onboarding costs 70%.

## Customize answers per tenant in Amazon Bedrock Managed Knowledge Base

DevFeed: [Customize answers per tenant in Amazon Bedrock Managed Knowledge Base](<https://devfeed.tech/articles/customize-answers-per-tenant-in-amazon-bedrock-managed-knowledge-base-136120.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/customize-answers-per-tenant-in-amazon-bedrock-managed-knowledge-base/>)

Author: Josh DeMuth

Published: 2026-11-16T15:46:28Z

Content type: tutorial

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [Amazon Bedrock Knowledge Bases](<https://devfeed.tech/topics/amazon-bedrock-knowledge-bases.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agentic-retrieval](<https://devfeed.tech/tags/agentic-retrieval.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [api](<https://devfeed.tech/tags/api.md>), [audit](<https://devfeed.tech/tags/audit.md>), [aws-cdk](<https://devfeed.tech/tags/aws-cdk.md>), [aws-cloudtrail](<https://devfeed.tech/tags/aws-cloudtrail.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [brand-voice](<https://devfeed.tech/tags/brand-voice.md>), [iam](<https://devfeed.tech/tags/iam.md>), [knowledge-base](<https://devfeed.tech/tags/knowledge-base.md>), [managed](<https://devfeed.tech/tags/managed.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [retrieval](<https://devfeed.tech/tags/retrieval.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

Amazon Bedrock Managed Knowledge Base retrieval instructions let each request apply tenant-specific voice, answer format, retrieval guidance, and answer policy through a managed, versioned resource. A backend can select an instruction version and metadata filter from the authenticated tenant, add a tenant-identifying line, and call AgenticRetrieveStream; one instruction can apply across as many as five knowledge bases. Instructions do not enforce data isolation or authorization, so use server-built metadata filters or separate knowledge bases, and scope IAM permissions when tenants use separate credentials. Filters require accurate document metadata; separate knowledge bases add resources to maintain and pay for. Policies are best effort, and output formats should be validated when code depends on them. Pin versions per tenant to canary, promote, or roll back changes; traces report the applied instruction ID and version, while CloudTrail can record calls when data events are enabled.

### Source excerpt

Retrieval instructions in Amazon Bedrock Managed Knowledge Base set the voice, format, retrieval guidance, and answer policy for each tenant on shared knowledge bases. This post shows how to give each tenant its own answers, keep tenant data apart with metadata filters, scope access with IAM tags, and roll out changes one tenant at a time.

## How to Build Multi-Tenant SaaS in Symfony Without Sacrificing Database Isolation

DevFeed: [How to Build Multi-Tenant SaaS in Symfony Without Sacrificing Database Isolation](<https://devfeed.tech/articles/how-to-build-multi-tenant-saas-in-symfony-without-sacrificing-database-isolation-135517.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-to-build-multi-tenant-saas-in-symfony-without-sacrificing-database-isolation?source=rss>)

Author: MattLeads

Published: 2026-11-16T04:40:39Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Per-user Database](<https://devfeed.tech/topics/per-user-database.md>), [Symfony](<https://devfeed.tech/topics/symfony.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [Database](<https://devfeed.tech/topics/database.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [cache](<https://devfeed.tech/tags/cache.md>), [database](<https://devfeed.tech/tags/database.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [free](<https://devfeed.tech/tags/free.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [messenger](<https://devfeed.tech/tags/messenger.md>), [multi-tenant](<https://devfeed.tech/tags/multi-tenant.md>), [multitenancy](<https://devfeed.tech/tags/multitenancy.md>), [php](<https://devfeed.tech/tags/php.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [redis](<https://devfeed.tech/tags/redis.md>), [saas](<https://devfeed.tech/tags/saas.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [symfony](<https://devfeed.tech/tags/symfony.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>), [workers](<https://devfeed.tech/tags/workers.md>)

### AI overview

The article's approach keeps a separate PostgreSQL database for each tenant while serving free tenants from shared Symfony processes; paying tenants can remain on dedicated deployments. A request path prefix sets the tenant, and a DBAL connection wrapper selects its database at query time, reconnecting on tenant switches and rejecting switches inside a transaction. A cache decorator namespaces tenant data, with tag-aware pools requiring tenant-prefixed tags. A custom Messenger transport polls each placed tenant's Redis stream, rotates tenants for fairness, and stamps messages from their stream; worker listeners set tenant context before retries or failures are stored and clear it afterward. An optional in-flight cap limits each tenant's concurrent jobs, though a worker crash can leave a slot occupied for up to three minutes. Placement is read from Redis, and migrations run in separate tenant-configured processes. The demo reports about 6.27 ms per database switch on a laptop; the article says this may matter for high-volume workers. It advises against the design when cross-tenant atomic transactions are needed, a tenant merits its own deployment, or services retain tenant-specific,

### Source excerpt

Run free tenants of a database-per-tenant Symfony 8.1 app on one shared deployment, with the DB connection, cache and Messenger workers following the tenant.

## As AI agents take control, Nvidia rethinks the security playbook

DevFeed: [As AI agents take control, Nvidia rethinks the security playbook](<https://devfeed.tech/articles/as-ai-agents-take-control-nvidia-rethinks-the-security-playbook-131019.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/11/12/ai-networking-nvidia-scalein-security-agentic-aifactoriesdatacenters/>)

Author: Mark Albertson

Published: 2026-11-12T22:46:33Z

Content type: news

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [Security](<https://devfeed.tech/topics/security.md>), [OpenShell](<https://devfeed.tech/topics/openshell.md>), [BlueField DPU](<https://devfeed.tech/topics/bluefield-dpu.md>), [DOCA](<https://devfeed.tech/topics/doca.md>), [observability](<https://devfeed.tech/topics/observability.md>), [NVIDIA Spectrum-X Ethernet](<https://devfeed.tech/topics/nvidia-spectrum-x-ethernet.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [NVIDIA Vera Rubin](<https://devfeed.tech/topics/nvidia-vera-rubin.md>), [Nvidia](<https://devfeed.tech/topics/nvidia.md>)

Tags: [agent-safety](<https://devfeed.tech/tags/agent-safety.md>), [agent-security](<https://devfeed.tech/tags/agent-security.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agentic-ai-security](<https://devfeed.tech/tags/agentic-ai-security.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-factories](<https://devfeed.tech/tags/ai-factories.md>), [ai-factory-roi-monetization-flywheels](<https://devfeed.tech/tags/ai-factory-roi-monetization-flywheels.md>), [ai-infrastructure-finance](<https://devfeed.tech/tags/ai-infrastructure-finance.md>), [ai-networking](<https://devfeed.tech/tags/ai-networking.md>), [aifactoriesdatacenters](<https://devfeed.tech/tags/aifactoriesdatacenters.md>), [aifactoriesdatacenters25eventpage](<https://devfeed.tech/tags/aifactoriesdatacenters25eventpage.md>), [bluefield-4](<https://devfeed.tech/tags/bluefield-4.md>), [capex-trends](<https://devfeed.tech/tags/capex-trends.md>), [cube-event-coverage](<https://devfeed.tech/tags/cube-event-coverage.md>), [data-centers-of-the-future](<https://devfeed.tech/tags/data-centers-of-the-future.md>), [doca](<https://devfeed.tech/tags/doca.md>), [dpu](<https://devfeed.tech/tags/dpu.md>), [gilad-shainer](<https://devfeed.tech/tags/gilad-shainer.md>), [gpu-access](<https://devfeed.tech/tags/gpu-access.md>), [hybrid-cloud-ecosystems](<https://devfeed.tech/tags/hybrid-cloud-ecosystems.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [nasdaq-nvda](<https://devfeed.tech/tags/nasdaq-nvda.md>), [news](<https://devfeed.tech/tags/news.md>), [nvidia](<https://devfeed.tech/tags/nvidia.md>), [openshell](<https://devfeed.tech/tags/openshell.md>), [orchestration-and-automation](<https://devfeed.tech/tags/orchestration-and-automation.md>), [scale-in](<https://devfeed.tech/tags/scale-in.md>), [secure-access](<https://devfeed.tech/tags/secure-access.md>), [security](<https://devfeed.tech/tags/security.md>), [thecube](<https://devfeed.tech/tags/thecube.md>), [thecube-plus-nyse-wired-ai-factories-data-centers-of-the-future-2025](<https://devfeed.tech/tags/thecube-plus-nyse-wired-ai-factories-data-centers-of-the-future-2025.md>), [unit-economics](<https://devfeed.tech/tags/unit-economics.md>)

### AI overview

Nvidia's Scale-In combines BlueField-4, DOCA and Spectrum-X Ethernet to secure and operate agentic AI factories. BlueField-4's in-silicon engines collect telemetry out of band from memory, storage, GPUs and CPUs, giving agents no control over that monitoring; DOCA APIs expose the DPU's security and storage acceleration capabilities. Nvidia's OpenShell runtime governs agent execution, access and inference routing. The later OpenShell Reference Architecture adds Sentry on BlueField-4, which Nvidia says continuously monitors agent behavior and can quarantine agents that cross defined software boundaries. The architecture pairs runtime controls with an independent monitoring and enforcement layer; the excerpt describes Nvidia's design and claims, not independent performance results.

### Source excerpt

Nvidia Corp. recently added a new pillar to its AI networking infrastructure with the unveiling of Scale-In. Scale-In brings purpose-built acceleration to secure, manage and operate agentic AI factories. It is designed to deliver secure access, high-performance data movement, tenant isolation, simpler operations and more predictable performance as agents assume increasingly larger roles within AI [...] The post As AI agents take control, Nvidia rethinks the security playbook appeared first on SiliconANGLE.

## How Hathr.AI delivers multi-tenant agentic RAG for regulated US government workloads with Amazon S3 Vectors

DevFeed: [How Hathr.AI delivers multi-tenant agentic RAG for regulated US government workloads with Amazon S3 Vectors](<https://devfeed.tech/articles/how-hathr-ai-delivers-multi-tenant-agentic-rag-for-regulated-us-government-workloads-with-amazon-s3-vectors-130617.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/storage/how-hathr-ai-delivers-multi-tenant-agentic-rag-for-regulated-us-government-workloads-with-amazon-s3-vectors/>)

Author: Sam Hart

Published: 2026-11-12T15:36:34Z

Content type: article

Language: en

Sources: [AWS Storage Blog](<https://devfeed.tech/sources/aws-storage-blog.md>)

Topics: [Multi-step AI processes](<https://devfeed.tech/topics/multi-step-ai-processes.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [vector embeddings in AI](<https://devfeed.tech/topics/vector-embeddings-in-ai.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-rag](<https://devfeed.tech/tags/agentic-rag.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon-documentdb](<https://devfeed.tech/tags/amazon-documentdb.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-simple-storage-service-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-s3.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-govcloud-us](<https://devfeed.tech/tags/aws-govcloud-us.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [government](<https://devfeed.tech/tags/government.md>), [hipaa](<https://devfeed.tech/tags/hipaa.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [rag](<https://devfeed.tech/tags/rag.md>), [step-functions](<https://devfeed.tech/tags/step-functions.md>), [strands-agents](<https://devfeed.tech/tags/strands-agents.md>), [tool](<https://devfeed.tech/tags/tool.md>), [us-government](<https://devfeed.tech/tags/us-government.md>), [vector](<https://devfeed.tech/tags/vector.md>), [vector-search](<https://devfeed.tech/tags/vector-search.md>), [vectors](<https://devfeed.tech/tags/vectors.md>)

### AI overview

Hathr.AI moved high-churn vector search from Amazon DocumentDB to Amazon S3 Vectors, using a separate index and ARN for each customer in AWS GovCloud (US). Step Functions and Lambda parse, chunk, and embed uploads; Amazon DocumentDB retains text and metadata, while S3 Vectors stores embeddings. Deletion removes vectors immediately in batches before deleting chunks. IAM scopes ingestion and agent access to customer indexes, and authenticated session context selects the index. Strands Agents on ECS Fargate can search, inspect results, and retry with revised queries; Hathr.AI caps searches per turn. The move addressed shared-cluster resource contention and reduced the DocumentDB cluster to one quarter of peak size. Hathr.AI reports zero failed vector requests, sub-100 ms average query latency, and upload-to-search readiness P99 below one-tenth of its prior time. S3 Vectors has per-index write limits, and index settings such as dimensions, distance metric, and encryption cannot be changed after creation. GovCloud deployments also need partition-specific ARNs and endpoint checks, model availability confirmation, and appropriate data-event logging where audit records are needed.

### Source excerpt

Hathr.AI runs a HIPAA-aligned, multi-tenant agentic RAG tool for regulated industries in AWS GovCloud (US). This post covers its architecture (a Step Functions ingestion pipeline, per-customer Amazon S3 Vectors indexes, and Strands Agents on ECS Fargate) and the results after moving vector search from Amazon DocumentDB to Amazon S3 Vectors.

## Building a multi-tenant CRM with Amazon Aurora DSQL

DevFeed: [Building a multi-tenant CRM with Amazon Aurora DSQL](<https://devfeed.tech/articles/building-a-multi-tenant-crm-with-amazon-aurora-dsql-129582.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/building-a-multi-tenant-crm-with-amazon-aurora-dsql/>)

Author: Aishwarya Sawant

Published: 2026-11-11T21:16:45Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [DSQL](<https://devfeed.tech/topics/dsql.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [crm](<https://devfeed.tech/tags/crm.md>), [dsql](<https://devfeed.tech/tags/dsql.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [proof-of-concept](<https://devfeed.tech/tags/proof-of-concept.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [tenancy](<https://devfeed.tech/tags/tenancy.md>), [tenant-isolation](<https://devfeed.tech/tags/tenant-isolation.md>)

### AI overview

The article's main security requirement is to derive tenant identity from a verified token claim and apply that tenant ID to every repository query. Its CRM proof of concept uses one shared schema with tenant_id on each tenant-scoped row; this is simple to onboard and scales with workload, but isolation depends on the application. Cluster-per-tenant offers stronger isolation at the cost of per-tenant endpoints, grants, and migrations; schema-per-tenant is limited by Aurora DSQL's current 10-schema maximum. The implementation uses UUID keys with tenant-leading indexes, application checks to ensure referenced accounts belong to the same tenant, and an IAM-authenticated connector with connections retired before the one-hour limit. Aurora DSQL requires separate transactions for DDL statements, while standalone indexes build asynchronously. Writes use optimistic concurrency control: transaction callbacks retry serialization conflicts and must be idempotent. Bulk writes should be batched to stay within the 3,000-row, 10 MiB, and five-minute transaction limits. The article also notes that Aurora DSQL does not support row-level security.

### Source excerpt

Learn how to design and implement a multi-tenant CRM on Amazon Aurora DSQL using the pooled tenancy model. Tenant isolation is enforced in a centralized data-access layer, with Aurora DSQL-specific design considerations, and a working proof of concept you can deploy on Amazon ECS Express Mode.

## Building Uscreen's remote, multi-tenant MCP server inside a Rails app

DevFeed: [Building Uscreen's remote, multi-tenant MCP server inside a Rails app](<https://devfeed.tech/articles/building-uscreen-s-remote-multi-tenant-mcp-server-inside-a-rails-app-130783.md>)

Original publisher: [Read original article](<https://evilmartians.com/chronicles/building-uscreens-remote-multi-tenant-mcp-server-inside-a-rails-app>)

Author: Travis Turner (richardturner@evilmartians.com)

Published: 2026-11-11T00:00:00Z

Content type: article

Language: en

Sources: [Evil Martians](<https://devfeed.tech/sources/evil-martians.md>)

Topics: [Ruby on Rails](<https://devfeed.tech/topics/ruby-on-rails.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [dry-run](<https://devfeed.tech/topics/dry-run.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [active-record](<https://devfeed.tech/tags/active-record.md>), [activerecord](<https://devfeed.tech/tags/activerecord.md>), [admin](<https://devfeed.tech/tags/admin.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [annotations](<https://devfeed.tech/tags/annotations.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [case-study](<https://devfeed.tech/tags/case-study.md>), [dry-run](<https://devfeed.tech/tags/dry-run.md>), [llms](<https://devfeed.tech/tags/llms.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [operations](<https://devfeed.tech/tags/operations.md>), [rails](<https://devfeed.tech/tags/rails.md>), [remote](<https://devfeed.tech/tags/remote.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [server](<https://devfeed.tech/tags/server.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

Uscreen moved its MCP server from a locally installed package into its Rails app, letting creators connect by URL, sign in, and approve access. The article describes 57 tools that call existing Rails models and business logic and ship with normal deploys. OAuth via Doorkeeper uses authorization-code and refresh-token grants with PKCE; tokens carry an Account and endpoint audience, and each request checks token validity, active Account, current admin membership, and tool scopes. The official `mcp` gem was chosen over fast-mcp for Streamable HTTP stateless transport, per-request context, and maintenance. Tool descriptions guide model selection, while scope checks enforce permissions at listing and execution. Destructive tools default to dry-run previews, though these are not approval gates and can become stale. The account invitation tool reuses existing admin-panel logic and quota, with the creator reviewing recipients before sending.

### Source excerpt

How Evil Martians moved Uscreen's MCP server into its Rails app as a remote, multi-tenant service: Doorkeeper OAuth, tenant-scoped tools, and dry-run previews for destructive operations.

## Lava Security's Yakir Kadkoda on the AI Data Center Boom: Growth, Security, and the Risks in Between

DevFeed: [Lava Security's Yakir Kadkoda on the AI Data Center Boom: Growth, Security, and the Risks in Between](<https://devfeed.tech/articles/lava-security-s-yakir-kadkoda-on-the-ai-data-center-boom-growth-security-and-the-risks-in-between-125756.md>)

Original publisher: [Read original article](<https://hackernoon.com/lava-securitys-yakir-kadkoda-on-the-ai-data-center-boom-growth-security-and-the-risks-in-between?source=rss>)

Author: Kevin John

Published: 2026-11-10T11:00:45Z

Content type: news

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [ai security](<https://devfeed.tech/topics/ai-security.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Shared Responsibility Model](<https://devfeed.tech/topics/shared-responsibility-model.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [network security](<https://devfeed.tech/topics/network-security.md>)

Tags: [accountability](<https://devfeed.tech/tags/accountability.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-data-center](<https://devfeed.tech/tags/ai-data-center.md>), [ai-data-center-expansion](<https://devfeed.tech/tags/ai-data-center-expansion.md>), [ai-data-center-security](<https://devfeed.tech/tags/ai-data-center-security.md>), [ai-infrastructure-policy](<https://devfeed.tech/tags/ai-infrastructure-policy.md>), [bmc-vulnerabilities](<https://devfeed.tech/tags/bmc-vulnerabilities.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cto](<https://devfeed.tech/tags/cto.md>), [data-center-moratorium](<https://devfeed.tech/tags/data-center-moratorium.md>), [exposed](<https://devfeed.tech/tags/exposed.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [gpu-cloud](<https://devfeed.tech/tags/gpu-cloud.md>), [gpu-cloud-security](<https://devfeed.tech/tags/gpu-cloud-security.md>), [gpu-utilization](<https://devfeed.tech/tags/gpu-utilization.md>), [growth](<https://devfeed.tech/tags/growth.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [neocloud-security](<https://devfeed.tech/tags/neocloud-security.md>), [risks](<https://devfeed.tech/tags/risks.md>), [security](<https://devfeed.tech/tags/security.md>), [tenant-isolation](<https://devfeed.tech/tags/tenant-isolation.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

Kadkoda argues that AI capacity should expand alongside enforceable resource commitments and independently verified infrastructure security. He says smaller companies and researchers would feel a construction pause first through higher prices and less availability. Lava's March-May 2026 snapshot found over 2,100 servers exposing monitoring data for more than 12,000 NVIDIA GPUs; nearly 60% reported zero utilization at observation time, a limited snapshot that does not establish permanent idleness. For rented GPUs, customers should seek technical evidence of tenant isolation, hardware and firmware integrity, and secure handover; Kadkoda says a SOC 2 certificate alone is insufficient. He describes risks below the OS and container layers, including exposed management systems and BMCs, and recommends sanitizing storage, credentials and keys and checking firmware and management controllers between tenants. He calls for measurable community commitments on power, water, costs and jobs, plus independent security verification across the infrastructure stack.

### Source excerpt

Lava Security CTO Yakir Kadkoda discusses AI data center expansion, GPU cloud vulnerabilities, tenant isolation, exposed infrastructure and accountability.

## MUSE: Multi-Tenant Model Serving With Seamless Model Updates

DevFeed: [MUSE: Multi-Tenant Model Serving With Seamless Model Updates](<https://devfeed.tech/articles/muse-multi-tenant-model-serving-with-seamless-model-updates-126681.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2602.11776>)

Author: Cl\\'audio Correia, Alberto E. A. Ferreira, Lucas Martins, Miguel P. Bento, Sofia Guerreiro, Ricardo Ribeiro Pereira, Ana Sofia Gomes, Jacopo Bono, Hugo Ferreira, Pedro Bizarro

Published: 2026-11-10T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Distributed Computing](<https://devfeed.tech/sources/arxiv-distributed-computing.md>), [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>)

Topics: [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [cost-optimization](<https://devfeed.tech/topics/cost-optimization.md>), [zero downtime deployment](<https://devfeed.tech/topics/zero-downtime-deployment.md>)

Tags: [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [fraud](<https://devfeed.tech/tags/fraud.md>), [high-availability](<https://devfeed.tech/tags/high-availability.md>), [lead-time](<https://devfeed.tech/tags/lead-time.md>), [low-latency](<https://devfeed.tech/tags/low-latency.md>), [model-serving](<https://devfeed.tech/tags/model-serving.md>), [multi-tenancy](<https://devfeed.tech/tags/multi-tenancy.md>), [muse](<https://devfeed.tech/tags/muse.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [routing](<https://devfeed.tech/tags/routing.md>), [sharing](<https://devfeed.tech/tags/sharing.md>), [stable](<https://devfeed.tech/tags/stable.md>), [transformation](<https://devfeed.tech/tags/transformation.md>)

### AI overview

MUSE addresses a multi-tenant serving bottleneck: retraining shifts model score distributions, making client-managed decision thresholds stale and costly to recalibrate. It shares models through dynamic intent-based routing and applies a two-level score transformation to map outputs to a stable reference distribution, decoupling serving updates from client decision boundaries. The abstract reports Feedzai deployment across several dozen tenants, processing over 1,000 events per second and more than 55 billion events in the last 12 months with high-availability and low-latency guarantees. It says model lead time fell from weeks to minutes; detailed implementation and evaluation methods are not included in the supplied excerpt.

### Source excerpt

arXiv:2602.11776v3 Announce Type: replace-cross Abstract: In binary classification systems, decision thresholds translate model scores into actions. Choosing suitable thresholds relies on the specific distribution of the underlying model scores but also on the specific business decisions of each client using that model. However, retraining models inevitably shifts score distributions, invalidating existing thresholds. In multi-tenant Score-as-a-Service environments, where decision boundaries reside in client-managed infrastructure, this creates a severe bottleneck: recalibration requires coordinating threshold updates across hundreds of clients, consuming excessive human hours and leading to model stagnation. We introduce MUSE, a model serving framework that enables seamless model updates by decoupling model scores from client decision boundaries. Designed for multi-tenancy, MUSE optimizes infrastructure re-use by sharing models via dynamic intent-based routing, combined with a two-level score transformation that maps model outputs to a stable, reference distribution. Deployed at scale by Feedzai, MUSE processes over a thousand events per second, and over 55 billion events in the last 12 months, across several dozens of tenants, while maintaining high-availability and low-latency guarantees. By reducing model lead time from weeks to minutes, MUSE promotes model resilience against shifting attacks, saving millions of dollars in fraud losses and operational costs.

## Aegis OS: A Transactional Multi-Tenant Operating System Runtime for Eliminating Authorization Fatigue in Autonomous Coding Agents

DevFeed: [Aegis OS: A Transactional Multi-Tenant Operating System Runtime for Eliminating Authorization Fatigue in Autonomous Coding Agents](<https://devfeed.tech/articles/aegis-os-a-transactional-multi-tenant-operating-system-runtime-for-eliminating-authorization-fatigue-in-autonomous-coding-agents-122783.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.08516>)

Author: Hui Zhao (Heurion Research)

Published: 2026-11-09T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Kernel](<https://devfeed.tech/topics/kernel.md>), [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>), [A2A protocol](<https://devfeed.tech/topics/a2a-protocol.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [google-antigravity](<https://devfeed.tech/topics/google-antigravity.md>)

Tags: [a2a](<https://devfeed.tech/tags/a2a.md>), [a2a-protocol](<https://devfeed.tech/tags/a2a-protocol.md>), [agent2agent](<https://devfeed.tech/tags/agent2agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [anthropic-claude](<https://devfeed.tech/tags/anthropic-claude.md>), [antigravity](<https://devfeed.tech/tags/antigravity.md>), [api](<https://devfeed.tech/tags/api.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [autonomous-coding](<https://devfeed.tech/tags/autonomous-coding.md>), [autonomy](<https://devfeed.tech/tags/autonomy.md>), [boundary](<https://devfeed.tech/tags/boundary.md>), [bridge](<https://devfeed.tech/tags/bridge.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-ma](<https://devfeed.tech/tags/cs-ma.md>), [cs-os](<https://devfeed.tech/tags/cs-os.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [operating-system](<https://devfeed.tech/tags/operating-system.md>), [os](<https://devfeed.tech/tags/os.md>), [runtime](<https://devfeed.tech/tags/runtime.md>)

### AI overview

Aegis OS moves authorization from individual tool calls to transactional workspace boundaries to reduce prompts while isolating autonomous coding agents. Its Rust runtime uses macOS Seatbelt or Linux Bubblewrap sandboxes, copy-on-write shadow workspaces, an identity-pinned HTTP egress proxy for scoped secret injection and outbound DLP, and an A2A bus with content-addressable storage. The abstract reports 94.19%-99.88% fewer prompts in 1,500 controlled calls and 90.7%-97.9% fewer across 28,087 calls in 52 sessions; attack success fell from 100% to 0% across 80 attacks on both platforms. It also reports 6.3 ms APFS and 15.6 ms btrfs cloning for a 1,000-file repository and detection of all 10 tested merge conflicts. These are claims from the supplied abstract; methods and broader limitations are not described.

### Source excerpt

arXiv:2611.08516v1 Announce Type: cross Abstract: Autonomous coding agents such as Google Antigravity (agy), Anthropic Claude Code (claude), and OpenAI Codex CLI (codex) execute multi-step software engineering workflows on workstations and cloud hosts. Existing agent environments face a Security-Autonomy Dilemma: operators must choose between per-action confirmation prompts, which interrupt workflows on 45%-57% of tool calls and induce authorization fatigue, or unconfined execution (--yolo / --dangerously-skip-permissions), which exposes host files, SSH/cloud credentials, and API tokens to prompt injection and hallucination risks. Furthermore, concurrent agents editing a shared working tree clobber one another's changes, while passing large artifacts inline through LLM context windows incurs high token overhead. We present Aegis OS (aegis-os), a transactional, multi-tenant Agent Operating System Runtime in Rust exposed via the Model Context Protocol (MCP) and Google Agent2Agent (A2A) protocol. Aegis OS shifts the authorization boundary from individual tool calls to transactional workspace boundaries. Each agent runs inside a kernel-enforced OS sandbox (macOS Seatbelt and Linux Bubblewrap with default-deny --tmpfs $HOME isolation and a Unix-socket egress bridge) backed by a Copy-on-Write (CoW) shadow workspace (APFS clonefile; single-open Linux FICLONE reflinks), an identity-pinned HTTP Egress Proxy with L7 method/path-scoped secret injection and outbound DLP, and an A2A IPC bus with Content-Addressable Storage (CAS). Across 1,500 controlled calls and 28,087 real calls across 52 coding-agent sessions, Aegis OS reduces prompts by 94.19%-99.88% (controlled) and 90.7%-97.9% (real sessions, 1.12% IPR), lowers attack success rate across 80 attacks in eight categories from 100.0% to 0.0% on macOS and Linux, clones 1,000-file (78.1 MB) repos in 6.3 ms on APFS and 15.6 ms on btrfs, and catches 10/10 syntactic and semantic merge conflicts.

## Smartbird Adds Supermicro DCBBS Racks to Its Managed Single-Tenant AI Clusters, Two Weeks After WEKA

DevFeed: [Smartbird Adds Supermicro DCBBS Racks to Its Managed Single-Tenant AI Clusters, Two Weeks After WEKA](<https://devfeed.tech/articles/smartbird-adds-supermicro-dcbbs-racks-to-its-managed-single-tenant-ai-clusters-two-weeks-after-weka-122668.md>)

Original publisher: [Read original article](<https://www.storagereview.com/news/smartbird-supermicro-dcbbs-managed-single-tenant-ai-clusters>)

Author: Harold Fritts

Published: 2026-11-08T19:07:39Z

Content type: news

Language: en

Sources: [StorageReview.com](<https://devfeed.tech/sources/storagereview-com.md>)

Topics: [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Managed Services](<https://devfeed.tech/topics/managed-services.md>), [digital sovereignty](<https://devfeed.tech/topics/digital-sovereignty.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>)

Tags: [added](<https://devfeed.tech/tags/added.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-clusters](<https://devfeed.tech/tags/ai-clusters.md>), [ai-data-centers](<https://devfeed.tech/tags/ai-data-centers.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [availability](<https://devfeed.tech/tags/availability.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [design](<https://devfeed.tech/tags/design.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [managed](<https://devfeed.tech/tags/managed.md>), [network](<https://devfeed.tech/tags/network.md>), [operations](<https://devfeed.tech/tags/operations.md>), [partner](<https://devfeed.tech/tags/partner.md>), [procurement](<https://devfeed.tech/tags/procurement.md>), [rack](<https://devfeed.tech/tags/rack.md>), [rack-scale](<https://devfeed.tech/tags/rack-scale.md>), [solutions](<https://devfeed.tech/tags/solutions.md>), [supermicro](<https://devfeed.tech/tags/supermicro.md>)

### AI overview

Smartbird and Supermicro will offer dedicated, single-tenant AI clusters built with Supermicro DCBBS and rack-scale systems. Smartbird is responsible for design, procurement, integration, deployment, and ongoing operations; customers can choose on-premises or colocation deployments tailored to their processor, capacity, performance, and workload needs, including training, fine-tuning, inference, agentic AI, and HPC. The arrangement combines Supermicro's compute, storage, networking, power, cooling, and supplier network with Smartbird's managed service, reducing vendors and handoffs. Single tenancy provides isolation and operational control, while deployment location can support data residency requirements; the announcement does not identify compliance certifications or establish that configurations meet specific regulations. It also gives no configurations, GPU platforms, availability dates, customers, or regions.

### Source excerpt

Smartbird, the managed AI infrastructure company that launched in June and trades on Nasdaq as BIRD, has added Supermicro to its partner network. The two will deliver dedicated, single-tenant AI clusters built from Supermicro's Data Center Building Block Solutions and rack-scale systems, with Smartbird handling design, procurement, integration, deployment, and day-to-day operations as the single The post Smartbird Adds Supermicro DCBBS Racks to Its Managed Single-Tenant AI Clusters, Two Weeks After WEKA appeared first on StorageReview.com.

## Addressing protocol security gaps in multi-tenant Kubernetes

DevFeed: [Addressing protocol security gaps in multi-tenant Kubernetes](<https://devfeed.tech/articles/addressing-protocol-security-gaps-in-multi-tenant-kubernetes-122100.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/security/addressing-protocol-security-gaps-in-multi-tenant-kubernetes/>)

Author: Ajinkya Patil

Published: 2026-11-06T21:08:50Z

Content type: article

Language: en

Sources: [AWS Security Blog](<https://devfeed.tech/sources/aws-security-blog.md>)

Topics: [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [adb](<https://devfeed.tech/topics/adb.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [WebRTC](<https://devfeed.tech/topics/webrtc.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [container-networking](<https://devfeed.tech/topics/container-networking.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>)

Tags: [active-directory](<https://devfeed.tech/tags/active-directory.md>), [adb](<https://devfeed.tech/tags/adb.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [amazon-kinesis-video-streams](<https://devfeed.tech/tags/amazon-kinesis-video-streams.md>), [android](<https://devfeed.tech/tags/android.md>), [android-debug-bridge](<https://devfeed.tech/tags/android-debug-bridge.md>), [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [audit](<https://devfeed.tech/tags/audit.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [network](<https://devfeed.tech/tags/network.md>), [pods](<https://devfeed.tech/tags/pods.md>), [policies](<https://devfeed.tech/tags/policies.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [protocol-security](<https://devfeed.tech/tags/protocol-security.md>), [protocols](<https://devfeed.tech/tags/protocols.md>), [security](<https://devfeed.tech/tags/security.md>), [security-blog](<https://devfeed.tech/tags/security-blog.md>), [security-identity-compliance](<https://devfeed.tech/tags/security-identity-compliance.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [webrtc](<https://devfeed.tech/tags/webrtc.md>)

### AI overview

The article describes a multi-tenant EKS design that adds security to unauthenticated protocols using namespace-scoped Envoy Gateway mTLS, short-lived certificates issued and rotated through cert-manager and AWS Private CA, and Kinesis Video Streams as managed TURN infrastructure for WebRTC. A custom API validates enterprise IdP JWTs, authorizes namespace access, returns connection details, and records identity, namespace, and time. The design depends on default-deny NetworkPolicies and namespace isolation; ADB traffic between Envoy and the pod is not encrypted, and immediate certificate revocation requires CRL or OCSP infrastructure. Compared with bastion forwarding through the Kubernetes API server, the reported Envoy path adds under 50 ms gateway latency, with ADB commands under 100 ms and installs under 30 seconds. Managed TURN removes the custom token-exchange service and, according to the article, kept WebRTC stable during peak use and removed manual routing updates after Availability Zone migrations. The post focuses on architecture and lessons, assumes existing EKS, IdP, and AWS Private CA setup, and notes that the JWT identity chain requires deployment-specific custom work

### Source excerpt

Protocols like Android Debug Bridge (ADB) and Web Real-Time Communication (WebRTC), by default, use unencrypted channels for network communications and don't support enterprise authentication mechanisms like JSON Web Tokens (JWTs). In a multi-tenant Kubernetes cluster--including Amazon Elastic Kubernetes Service (Amazon EKS)--pods can reach other tenants' open ports by default unless you configure network policies to [...]

## How OrderServ achieved up to 64% cost savings with multi-tenant ECS

DevFeed: [How OrderServ achieved up to 64% cost savings with multi-tenant ECS](<https://devfeed.tech/articles/how-orderserv-achieved-up-to-64-cost-savings-with-multi-tenant-ecs-119789.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/architecture/how-orderserv-achieved-up-to-64-cost-savings-with-multi-tenant-ecs/>)

Author: Chetan Yewale

Published: 2026-11-06T00:09:41Z

Content type: article

Language: en

Sources: [AWS Architecture Blog](<https://devfeed.tech/sources/aws-architecture-blog.md>)

Topics: [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [Use Cases for Every Cloud Service Model](<https://devfeed.tech/topics/use-cases-for-every-cloud-service-model.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch-logs](<https://devfeed.tech/tags/amazon-cloudwatch-logs.md>), [amazon-cognito](<https://devfeed.tech/tags/amazon-cognito.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-block-store-amazon-ebs](<https://devfeed.tech/tags/amazon-elastic-block-store-amazon-ebs.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-professional-services](<https://devfeed.tech/tags/aws-professional-services.md>), [compute-costs](<https://devfeed.tech/tags/compute-costs.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cost-savings](<https://devfeed.tech/tags/cost-savings.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [saas](<https://devfeed.tech/tags/saas.md>), [scaling](<https://devfeed.tech/tags/scaling.md>)

### AI overview

OrderServ moved from a separate 21-service ECS cluster per brand to a shared cluster, using a .NET tenancy library to route and validate tenant data access while per-tenant stores, scoped credentials, and Valkey access controls support isolation. The shared setup reduces duplicated services and sidecars; high-volume brands can still use dedicated clusters. For faster surge response, EC2 Auto Scaling warm pools with Bottlerocket and 80% target utilization bring capacity online in 30-60 seconds, compared with 5-7 minutes for Fargate cold starts. The article reports 47-64% lower compute costs and 80% lower authentication costs, alongside FireLens-based logging, persistent crash diagnostics, and Cognito passkeys. These patterns add application-level isolation and EC2 capacity management responsibilities; Savings Plan commitments are also part of the cost tradeoff.

### Source excerpt

See how Cognizant and AWS Professional Services transformed the OrderServ food-ordering platform into a multi-tenant SaaS offering on shared Amazon ECS, cutting compute costs up to 64%, reducing scaling time from minutes to seconds, and lowering authentication costs by 80%.

## Deliver multi-tenant AI analytics at scale with AgentCore and Lake Formation

DevFeed: [Deliver multi-tenant AI analytics at scale with AgentCore and Lake Formation](<https://devfeed.tech/articles/deliver-multi-tenant-ai-analytics-at-scale-with-agentcore-and-lake-formation-119231.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/deliver-multi-tenant-ai-analytics-at-scale-with-agentcore-and-lake-formation/>)

Author: Fortune Hui

Published: 2026-11-05T15:04:59Z

Content type: article

Language: en

Sources: [AWS Big Data Blog](<https://devfeed.tech/sources/aws-big-data-blog.md>)

Topics: [AWS Lake Formation](<https://devfeed.tech/topics/aws-lake-formation.md>), [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [Amazon Cognito](<https://devfeed.tech/topics/amazon-cognito.md>), [data lake](<https://devfeed.tech/topics/data-lake.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-analytics](<https://devfeed.tech/tags/ai-analytics.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-cognito](<https://devfeed.tech/tags/amazon-cognito.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lake-formation](<https://devfeed.tech/tags/aws-lake-formation.md>), [broker](<https://devfeed.tech/tags/broker.md>), [credential-broker](<https://devfeed.tech/tags/credential-broker.md>), [external](<https://devfeed.tech/tags/external.md>), [lambda](<https://devfeed.tech/tags/lambda.md>), [multi-tenant-data](<https://devfeed.tech/tags/multi-tenant-data.md>), [saas](<https://devfeed.tech/tags/saas.md>), [scale](<https://devfeed.tech/tags/scale.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The article describes a pattern for isolating external users' data access in an Amazon Bedrock AgentCore analytics agent. Cognito User Pool ID-token claims such as `custom:team` map through an Identity Pool to team-specific IAM roles. AgentCore Gateway validates the access token and forwards the ID token to a minimally privileged Lambda, which brokers temporary user-scoped credentials; Athena queries then run under those credentials, with Lake Formation LF-Tag permissions and data cell filters enforcing table and row access. The Lambda has no Athena, S3, or Glue data permissions. The article contrasts this external-user Cognito model with IAM Identity Center and Trusted Identity Propagation, which it describes as suited to workforce federation. It also outlines CDK deployment prerequisites and a walkthrough that changes Lake Formation grants and filters to extend Team A's access, noting that permission changes may take several minutes to propagate.

### Source excerpt

Governed, multi-tenant data access is a key requirement for SaaS and B2C products that embed AI-powered analytics. This post shows how to combine Amazon Cognito and AWS Lake Formation on Amazon Bedrock AgentCore to enforce row- and column-level data access for external users, with a minimal-privilege Lambda acting as a credential broker.

## Multi-Tenant CDC: Database-per-Tenant SaaS Architecture Guide

DevFeed: [Multi-Tenant CDC: Database-per-Tenant SaaS Architecture Guide](<https://devfeed.tech/articles/multi-tenant-cdc-database-per-tenant-saas-architecture-guide-116277.md>)

Original publisher: [Read original article](<https://estuary.dev/blog/multi-tenant-cdc>)

Author: Brian Sheehan

Published: 2026-11-03T08:35:50Z

Content type: tutorial

Language: en

Sources: [Estuary](<https://devfeed.tech/sources/estuary.md>)

Topics: [Per-user Database](<https://devfeed.tech/topics/per-user-database.md>), [Analytics Pipeline](<https://devfeed.tech/topics/analytics-pipeline.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [rdbms](<https://devfeed.tech/topics/rdbms.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [cdc](<https://devfeed.tech/tags/cdc.md>), [change-data-capture](<https://devfeed.tech/tags/change-data-capture.md>), [database](<https://devfeed.tech/tags/database.md>), [estuary](<https://devfeed.tech/tags/estuary.md>), [guide](<https://devfeed.tech/tags/guide.md>), [keys](<https://devfeed.tech/tags/keys.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [practical](<https://devfeed.tech/tags/practical.md>), [saas](<https://devfeed.tech/tags/saas.md>)

### AI overview

For database-per-tenant PostgreSQL SaaS, log-based CDC consolidates tenant data downstream by running one capture and replication slot per database, tagging each row with a stable tenant ID, and keying shared destination tables on tenant ID plus the source primary key. The guide's three-tenant test found that captures fail and recover independently, while shared materializations and PostgreSQL server resources can affect all tenants. Practical setup includes unique slot names, explicit table mappings, careful discovery and schema rollout, and monitoring each capture and slot; shared-server slot limits and stalled-slot WAL retention constrain scale. Schema drift can pause shared delivery or reject incompatible changes, and resets may rebuild data for every tenant. The test used sample data and does not establish production-scale behavior. Estuary supplies capture, tagging, grouping, and status features, with per-tenant connector-instance costs; self-managed connectors, ordinary CDC on already-shared tables, or scheduled ETL for workloads that tolerate it are noted alternatives.

### Source excerpt

A practical guide to multi-tenant CDC with PostgreSQL, tenant-aware keys, and shared analytics tables using Estuary.

## Never Let the Model Choose the tenant\_id

DevFeed: [Never Let the Model Choose the tenant\_id](<https://devfeed.tech/articles/never-let-the-model-choose-the-tenant-id-110004.md>)

Original publisher: [Read original article](<https://newsletter.systemdesignclassroom.com/p/never-let-the-model-choose-the-tenant-id>)

Author: Raul Junco

Published: 2026-10-31T11:45:45Z

Content type: opinion

Language: en

Sources: [System Design Classroom](<https://devfeed.tech/sources/system-design-classroom.md>)

Topics: [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [Per-user Database](<https://devfeed.tech/topics/per-user-database.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [prompt injection](<https://devfeed.tech/topics/prompt-injection.md>)

Tags: [2023](<https://devfeed.tech/tags/2023.md>), [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [access-control](<https://devfeed.tech/tags/access-control.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-memory](<https://devfeed.tech/tags/agent-memory.md>), [agent-tools](<https://devfeed.tech/tags/agent-tools.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-generated-code](<https://devfeed.tech/tags/ai-generated-code.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [black-hat](<https://devfeed.tech/tags/black-hat.md>), [blast-radius](<https://devfeed.tech/tags/blast-radius.md>), [cache](<https://devfeed.tech/tags/cache.md>), [chatgpt](<https://devfeed.tech/tags/chatgpt.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [rag](<https://devfeed.tech/tags/rag.md>)

### AI overview

The article's central rule is to keep tenant authorization outside the model: the model may choose what to search, but trusted application code must decide whose data it can access. It recommends tiered isolation--shared row-level storage for smaller tenants, separate schemas or logical databases for growing customers, and dedicated instances or clusters for high-risk or high-value customers--with `tenant_id` retained on every tenant-owned row to support moves. For shared storage, enforce boundaries below application code using database row-level security, least-privileged roles, transaction-scoped tenant context, non-null composite keys and foreign keys, and authorization bound to the authenticated caller. Test cross-tenant access in CI and add checks for AI-generated code. Apply the same boundary to caches, queues, search, logs, vector stores, and agent tools. RLS can affect query plans and complicate debugging; cross-tenant administration needs separately controlled access. Tiering also adds operational complexity, and database separation may still share infrastructure.

### Source excerpt

Tenant isolation was hard before AI. Agents, RAG, and AI-written code just made the blast radius bigger.

## CVE-2026-61708 - SOCFortress CoPilot: Cross-Tenant Arbitrary Object-Store Write via the Data-Store Upload Endpoint (customer\_user)

DevFeed: [CVE-2026-61708 - SOCFortress CoPilot: Cross-Tenant Arbitrary Object-Store Write via the Data-Store Upload Endpoint (customer\_user)](<https://devfeed.tech/articles/cve-2026-61708-socfortress-copilot-cross-tenant-arbitrary-object-store-write-via-the-data-store-upload-endpoint-customer-user-108965.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-61708>)

Author: CVEFEED.io; github.com

Published: 2026-10-30T15:16:52Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [CRUD](<https://devfeed.tech/topics/crud.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [admin](<https://devfeed.tech/tags/admin.md>), [analyst](<https://devfeed.tech/tags/analyst.md>), [artifacts](<https://devfeed.tech/tags/artifacts.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [content](<https://devfeed.tech/tags/content.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-61708](<https://devfeed.tech/tags/cve-2026-61708.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [data](<https://devfeed.tech/tags/data.md>), [delete](<https://devfeed.tech/tags/delete.md>), [download](<https://devfeed.tech/tags/download.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [object](<https://devfeed.tech/tags/object.md>), [store](<https://devfeed.tech/tags/store.md>), [upload](<https://devfeed.tech/tags/upload.md>), [user](<https://devfeed.tech/tags/user.md>), [write](<https://devfeed.tech/tags/write.md>)

### AI overview

Before version 0.1.76, SOCFortress CoPilot's upload endpoint lets `customer_user` callers choose object-store bucket and object names without tenant or ownership checks; the upload only requires a nonempty filename. Backend operations create missing buckets and upsert objects, enabling cross-tenant overwrites. The excerpt identifies possible targets including Windows endpoint Sysmon configurations, server-rendered report templates, case evidence, and forensic artifacts, with risks such as altered evidence, disrupted telemetry, later code execution through poisoned templates, and storage exhaustion. Sibling list, download, and delete routes remain restricted to admins and analysts. The issue is fixed in version 0.1.76.

### Source excerpt

CVE ID :CVE-2026-61708 Published : Oct. 30, 2026, 3:16 p.m. | 1 hour, 11 minutes ago Description :SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs. Prior to 0.1.76, `POST /api/agent_data_store/upload` in `backend/app/data_store/data_store_routes.py` permits `customer_user` callers to choose `bucket_name` and `object_name` without an allowlist, tenant prefix, ownership check or content restriction. The only file check requires a nonempty filename. The operations in `backend/app/data_store/data_store_operations.py` create missing buckets and upsert objects, allowing existing objects belonging to any tenant to be overwritten. Targets include `sysmon-configs//sysmon_config.xml` distributed to managed Windows endpoints, `copilot-case-report-templates/` rendered server-side, and case evidence or forensic artifacts under `copilot-cases//` and `velociraptor-artifacts///`. A lowest-privilege user can tamper with cross-tenant evidence, blind endpoint telemetry, poison report templates for later code execution, plant data or exhaust storage. Sibling list, download and delete routes remain restricted to admin/analyst; the exposed operation is the upload write path. This issue is fixed in version 0.1.76. Severity: 8.5 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CacheSolidarity: Preventing Prefix Caching Side Channels in Multi-Tenant LLM Serving Systems

DevFeed: [CacheSolidarity: Preventing Prefix Caching Side Channels in Multi-Tenant LLM Serving Systems](<https://devfeed.tech/articles/cachesolidarity-preventing-prefix-caching-side-channels-in-multi-tenant-llm-serving-systems-107551.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2603.10726>)

Author: Panagiotis Georgios Pennas, Konstantinos Papaioannou, Marco Guarnieri, Thaleia Dimitra Doudali

Published: 2026-10-30T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>), [arXiv: Distributed Computing](<https://devfeed.tech/sources/arxiv-distributed-computing.md>)

Topics: [LLM security](<https://devfeed.tech/topics/llm-security.md>), [LLM optimization](<https://devfeed.tech/topics/llm-optimization.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>)

Tags: [caching](<https://devfeed.tech/tags/caching.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [inference](<https://devfeed.tech/tags/inference.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [latency](<https://devfeed.tech/tags/latency.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-serving](<https://devfeed.tech/tags/llm-serving.md>), [prefix-caching](<https://devfeed.tech/tags/prefix-caching.md>), [reuse](<https://devfeed.tech/tags/reuse.md>), [side-channels](<https://devfeed.tech/tags/side-channels.md>), [systems](<https://devfeed.tech/tags/systems.md>)

### AI overview

Automatic Prefix Caching speeds inference by reusing previously computed request prefixes, but different latencies for cache hits and misses can let one tenant infer another's request from hit/miss patterns. CacheSolidarity monitors cross-user cache reuse, flags suspicious sharing, and selectively isolates prefixes when needed, aiming to retain ordinary cache benefits while limiting this side channel. The abstract reports up to 70% higher cache reuse and 30% lower inference latency than existing user-isolation defenses. These figures are reported for the paper's evaluation; the supplied excerpt does not provide its setup or additional results.

### Source excerpt

arXiv:2603.10726v3 Announce Type: replace-cross Abstract: Large Language Models (LLMs) rely on optimizations like Automatic Prefix Caching (APC) to accelerate inference. APC works by reusing previously computed states for the beginning part of a request (prefix), when another request starts with the same text. While APC improves throughput, it introduces timing side channels: cache hits are faster than misses, creating observable latency differences. In multi-tenant systems, attackers can exploit these differences to infer sensitive information, e.g., by incrementally reconstructing another user's request by observing hit/miss patterns. Current defenses take a sledgehammer approach: they disable APC and cache sharing, isolating users, and sacrificing efficiency for regular users. This paper presents CacheSolidarity, a system that secures multi-tenant LLM serving systems against APC side channels without sacrificing performance and efficiency. CacheSolidarity monitors cache reuse across users, flags suspicious sharing, and selectively isolates prefixes, restricting their reuse only when necessary. Evaluation shows that CacheSolidarity enables up to 70% higher cache reuse and 30% lower inference latency compared to existing user-isolation defenses. CacheSolidarity's lightweight design demonstrates how LLM serving can be secured without sacrificing performance or incurring unbearable overheads.

## The Illusion of Local Privacy: Confidentiality Boundary Failures in Consumer LLM Serving Systems

DevFeed: [The Illusion of Local Privacy: Confidentiality Boundary Failures in Consumer LLM Serving Systems](<https://devfeed.tech/articles/the-illusion-of-local-privacy-confidentiality-boundary-failures-in-consumer-llm-serving-systems-108999.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2609.18526>)

Author: Youssef Hamdi Zafan Ibrahim, Muhammad Ikram, Mohammed Khalaf Salama

Published: 2026-10-30T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [LLM security](<https://devfeed.tech/topics/llm-security.md>), [llama.cpp](<https://devfeed.tech/topics/llama-cpp.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [Local AI](<https://devfeed.tech/topics/local-ai.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Persistence](<https://devfeed.tech/topics/persistence.md>), [LLM Techniques](<https://devfeed.tech/topics/llm-techniques.md>), [interface](<https://devfeed.tech/topics/interface.md>)

Tags: [authorization](<https://devfeed.tech/tags/authorization.md>), [boundary](<https://devfeed.tech/tags/boundary.md>), [consumer](<https://devfeed.tech/tags/consumer.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-serving](<https://devfeed.tech/tags/llm-serving.md>), [local](<https://devfeed.tech/tags/local.md>), [memory](<https://devfeed.tech/tags/memory.md>), [oracle](<https://devfeed.tech/tags/oracle.md>), [persistence](<https://devfeed.tech/tags/persistence.md>), [prefix-caching](<https://devfeed.tech/tags/prefix-caching.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [prompt](<https://devfeed.tech/tags/prompt.md>), [storage](<https://devfeed.tech/tags/storage.md>)

### AI overview

Keeping LLM inference on-device does not by itself ensure prompt confidentiality: serving software can expose prompts at several stages. The authors use LLAnalyzer to examine model loading, runtime memory, wrapper persistence, and serving interfaces across four open-weight model families and two consumer platforms. In a 24-hour AFL++ campaign exceeding 12 million executions, they found no parser crashes or successful malformed GGUF loads within the explored state space. By contrast, plaintext prompt remnants persisted in allocator-managed memory after inference; sanitisation reduced but did not remove them, and wrappers could prolong prompt lifetime through plaintext storage. They also report a llama.cpp authorization flaw that let one authenticated client restore another tenant's saved conversation in 200/200 controlled trials, plus a shared-prefix-cache timing oracle distinguishable over WAN. The authors call for explicit guarantees on prompt lifetime, persistent storage, and tenant isolation.

### Source excerpt

arXiv:2609.18526v3 Announce Type: replace Abstract: Running large language models (LLMs) locally is often considered more private than cloud-hosted inference because user prompts remain on the device. We ask whether keeping inference local is, by itself, sufficient to keep those prompts confidential. Our results show that it is not: prompt confidentiality also depends on how the surrounding serving software handles prompt data before, during, and after inference. We examine four boundaries at which prompt confidentiality can fail in consumer local-LLM serving systems: model loading, runtime memory, wrapper-level persistence, and the serving interface. To study these boundaries, we develop LLAnalyzer, a measurement framework that tests each boundary separately and traces observed failures to the responsible software component. Applying LLAnalyzer to four open-weight model families and two consumer deployment platforms, we find markedly different behaviour across boundaries. In a 24-hour AFL++ campaign with more than 12 million executions, we observe no parser crashes or successful malformed GGUF loads within the explored state space. Runtime memory tells a different story: we recover prompts after inference because multiple plaintext representations survive in allocator-managed memory, and sanitisation reduces this residue without eliminating it. We also find that consumer wrappers can extend prompt lifetime through plaintext persistence. At the serving boundary, we uncover a previously undocumented authorization flaw in llama.cpp that allows one authenticated client to restore another tenant's saved conversation state; the attack succeeds in 200/200 controlled trials. Separately, shared prompt-prefix caching exposes a remote timing oracle that remains distinguishable under WAN conditions. We argue that local LLM systems need explicit guarantees for prompt lifetime, persistent storage, and tenant isolation.

## New Whitepaper: Architecting a Governed, Multi-Tenant Private AI Cloud with VCF 9

DevFeed: [New Whitepaper: Architecting a Governed, Multi-Tenant Private AI Cloud with VCF 9](<https://devfeed.tech/articles/new-whitepaper-architecting-a-governed-multi-tenant-private-ai-cloud-with-vcf-9-105701.md>)

Original publisher: [Read original article](<https://blogs.vmware.com/cloud-foundation/2026/10/28/new-whitepaper-architecting-a-governed-multi-tenant-private-ai-cloud-with-vcf-9/>)

Author: taka uenishi

Published: 2026-10-28T13:00:00Z

Content type: article

Language: en

Sources: [VMware](<https://devfeed.tech/sources/vmware-blogs.md>)

Topics: [VMware Cloud Foundation](<https://devfeed.tech/topics/vcf-9-1.md>), [vcf automation](<https://devfeed.tech/topics/vcf-automation.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [vcf networking](<https://devfeed.tech/topics/vcf-networking.md>), [vcf operations](<https://devfeed.tech/topics/vcf-operations.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-cloud](<https://devfeed.tech/tags/ai-cloud.md>), [business](<https://devfeed.tech/tags/business.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [containers](<https://devfeed.tech/tags/containers.md>), [developers](<https://devfeed.tech/tags/developers.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-it](<https://devfeed.tech/tags/enterprise-it.md>), [home-page](<https://devfeed.tech/tags/home-page.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [multi-tenancy](<https://devfeed.tech/tags/multi-tenancy.md>), [private-ai](<https://devfeed.tech/tags/private-ai.md>), [private-cloud](<https://devfeed.tech/tags/private-cloud.md>), [vcf](<https://devfeed.tech/tags/vcf.md>), [vcf-9](<https://devfeed.tech/tags/vcf-9.md>), [vcf-automation](<https://devfeed.tech/tags/vcf-automation.md>), [virtual](<https://devfeed.tech/tags/virtual.md>), [virtual-machines](<https://devfeed.tech/tags/virtual-machines.md>), [vmware](<https://devfeed.tech/tags/vmware.md>), [whitepaper](<https://devfeed.tech/tags/whitepaper.md>)

### AI overview

The excerpt presents VCF 9 as a way to provide self-service private cloud across AI, Kubernetes and VMs while enforcing tenant isolation and enterprise governance. Its Kubernetes-based vSphere Supervisor exposes infrastructure and services through Kubernetes APIs and CRDs. In VCF Automation's provider/consumer model, IT allocates resources and sets global guardrails while business tenants manage isolated projects, including VPCs, subnets, firewall policies and NAT; VMware vDefend enforces security rules hierarchically. VCF Private AI Services supports sharing pooled GPUs and models across isolated namespaces to avoid redundant deployments while preserving data privacy. Other described capabilities include tenant-level VM disaster recovery, YAML-based policy controls, reusable application-stack blueprints, and namespace-level cost accountability with pricing, lease and reclamation policies. The excerpt outlines these claims but does not provide implementation details or evidence quantifying outcomes.

### Source excerpt

Multi-Tenancy Is the Engine of the Modern Private AI Cloud The private cloud is undergoing a profound transformation. Today's enterprise IT organizations are tasked with supporting diverse, resource-intensive workloads, spanning AI, Kubernetes / containers, and virtual machines, on shared infrastructure. Simultaneously, they must enforce strict isolation between business divisions, developers, or external clients. When isolation ... Continued The post New Whitepaper: Architecting a Governed, Multi-Tenant Private AI Cloud with VCF 9 appeared first on VMware Blogs.

## Cross-User Poisoning: User-Task Boundary Failures in Multi-User Collaborative Language Agents

DevFeed: [Cross-User Poisoning: User-Task Boundary Failures in Multi-User Collaborative Language Agents](<https://devfeed.tech/articles/cross-user-poisoning-user-task-boundary-failures-in-multi-user-collaborative-language-agents-102921.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2511.17671>)

Author: Atharv Singh Patlan, Peiyao Sheng, S. Ashwin Hebbar, Prateek Mittal, Pramod Viswanath

Published: 2026-10-28T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [AI Context Management](<https://devfeed.tech/topics/ai-context-management.md>), [Multi-step AI processes](<https://devfeed.tech/topics/multi-step-ai-processes.md>)

Tags: [adversary](<https://devfeed.tech/tags/adversary.md>), [agents](<https://devfeed.tech/tags/agents.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [context](<https://devfeed.tech/tags/context.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-cl](<https://devfeed.tech/tags/cs-cl.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cup](<https://devfeed.tech/tags/cup.md>), [domains](<https://devfeed.tech/tags/domains.md>), [framework](<https://devfeed.tech/tags/framework.md>), [language](<https://devfeed.tech/tags/language.md>), [slack](<https://devfeed.tech/tags/slack.md>), [tool](<https://devfeed.tech/tags/tool.md>), [user](<https://devfeed.tech/tags/user.md>)

### AI overview

Cross-user poisoning (CUP) occurs when an adversary's message in shared context is later applied while an agent serves another user, leading to actions or responses beyond the message's intended scope. The study validates CUP on Continua and ElizaOS and evaluates it with MURMUR across Slack, Workspace, and Airline domains. The abstract reports high attack success, persistence across later interactions, and greater effectiveness than matched prompt-injection attacks. Context summarization alone was insufficient; task clustering and provenance prompting substantially reduced non-adaptive propagation. The findings point to explicit user and task scoping as a requirement for shared agents, though the abstract does not quantify results or establish defense performance against adaptive attacks.

### Source excerpt

arXiv:2511.17671v2 Announce Type: replace-cross Abstract: Language agents are moving from single-user assistants to shared collaborators in workspaces, forums, and group chats. A shared agent observes interleaved messages from multiple users, maintains persistent context, and executes tool actions, creating a boundary problem absent from standard single-user agents: the agent must decide not only whether an instruction is safe, but which user or task it is allowed to govern. We identify cross-user poisoning (CUP), where an adversary injects a message into shared context that is later applied while the agent serves a benign user, causing unauthorized actions or responses outside the instruction's intended scope. We validate CUP on two deployed multi-user agents, Continua and ElizaOS, and introduce MURMUR, a framework for evaluating shared-context agents under concurrent multi-user interactions. Across Slack, Workspace, and Airline domains, CUP achieves high attack success, persists across later interactions, and remains substantially more effective than matched prompt-injection attacks. We evaluate boundary-scoping defenses and find that context summarization alone is insufficient, while task clustering and provenance prompting substantially reduce non-adaptive propagation. These results show that robust multi-user agents require explicit user/task scoping rather than generic input filtering or context compression.

## Readyon Builds Four Layer Tenant Isolation for Multi Tenant Amazon EKS

DevFeed: [Readyon Builds Four Layer Tenant Isolation for Multi Tenant Amazon EKS](<https://devfeed.tech/articles/readyon-builds-four-layer-tenant-isolation-for-multi-tenant-amazon-eks-100607.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/10/readyon-four-layer-isolation/>)

Author: Leela Kumili

Published: 2026-10-26T14:07:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [Per-user Database](<https://devfeed.tech/topics/per-user-database.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>)

Tags: [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [argo-cd](<https://devfeed.tech/tags/argo-cd.md>), [cloud-security](<https://devfeed.tech/tags/cloud-security.md>), [development](<https://devfeed.tech/tags/development.md>), [devops](<https://devfeed.tech/tags/devops.md>), [eks](<https://devfeed.tech/tags/eks.md>), [gitops](<https://devfeed.tech/tags/gitops.md>), [isolates](<https://devfeed.tech/tags/isolates.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [layer](<https://devfeed.tech/tags/layer.md>), [multi-tenancy](<https://devfeed.tech/tags/multi-tenancy.md>), [multi-tenant-data](<https://devfeed.tech/tags/multi-tenant-data.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [news](<https://devfeed.tech/tags/news.md>), [observability](<https://devfeed.tech/tags/observability.md>), [policy](<https://devfeed.tech/tags/policy.md>), [readyon-four-layer-isolation](<https://devfeed.tech/tags/readyon-four-layer-isolation.md>), [security](<https://devfeed.tech/tags/security.md>), [tenant-isolation](<https://devfeed.tech/tags/tenant-isolation.md>), [threat-modeling](<https://devfeed.tech/tags/threat-modeling.md>), [virtual-pc](<https://devfeed.tech/tags/virtual-pc.md>)

### AI overview

ReadyOn describes four overlapping isolation layers for its Harmony platform on Amazon EKS: per-tenant Kubernetes namespaces with RBAC and default-deny policies; dedicated Karpenter node pools guarded by tenant and workload taints plus admission checks; VPC security groups that restrict database access to each tenant's node pool; and dedicated Aurora clusters instead of row-level filtering in a shared database. It also uses tenant-scoped Secrets Manager paths, short-lived IAM Roles for Service Accounts credentials, and dedicated observability backends. The excerpt says Kubernetes controls alone do not separate workloads on underlying nodes, and notes that observability should connect workload identity to database and network enforcement to reveal gaps. ReadyOn reports that adversarial exercises have not found a successful cross-tenant path to date; the excerpt does not provide independent verification.

### Source excerpt

ReadyOn has detailed a four-layer tenant isolation architecture for its Harmony platform on Amazon EKS. The design combines Kubernetes namespaces, dedicated Karpenter node pools, VPC security groups, and per-tenant Aurora databases, with controls evaluated against a 10-stage multi-tenant threat model focused on cross-tenant access and lateral movement. By Leela Kumili

[Next page](<https://devfeed.tech/topics/tenant-data-protection.md?cursor=WyIyMDI2LTEwLTI2VDE0OjA3OjAwKzAwOjAwIiwgIjA5OWZmNzNkLTZkZmEtNDIzMS05ZDM1LTZmZDFjMTMyODVkZSJd>)