What is the nature and description of the request?

Enable Trustee to support multi-organization confidential computing scenarios through namespace-based multi-tenancy for service providers and multi-party collaboration workflows for cross-organization attestation. The request includes automated tenant onboarding with strong isolation boundaries, BYOK integration patterns maintaining customer control over key management, multi-endpoint client support enabling workflows where different Trustee instances serve different verification purposes, and independent verification patterns following IETF RATS architecture for organizational sovereignty over attestation policies.

Why does the customer need this? (Business requirements)

Service provider business model: Cloud providers (Azure, Ionos, KT, SKT) need multi-tenant attestation platforms to offer confidential computing as managed service

Customer data sovereignty: Service providers must demonstrate inability to access customer keys or attestation data through BYOK integration

Cross-organization collaboration: Industries need secure collaboration (healthcare + pharma, financial consortium) without exposing proprietary data or algorithms

Federated learning: AI companies require attestation frameworks supporting distributed model training across organizational boundaries

Regulatory compliance: Different customers have varying compliance requirements requiring isolation and independent management

Supply chain verification: Multi-party attestation for complex supply chains with independent organizational policies and verification workflows

Affected packages or components

• trustee-operator: Multi-tenancy support, namespace-based isolation
• attestation-agent: Multi-endpoint support for multiple Trustee instances
• image-rs: Multi-source key resolution and workflow coordination
• kbs: Multi-party verification support, tenant isolation
• OLM: Multi-tenant operator deployment patterns
• Kubernetes RBAC: Tenant isolation and security boundaries

Technical implementation details

Namespace-Based Multi-Tenancy: Dedicated operator instances per tenant namespace providing strong security isolation and independent lifecycle management

BYOK Integration Patterns: Customer-specific key management system integration ensuring service providers cannot access tenant keys or sensitive data

Multi-Endpoint Client Framework: Enhanced guest-components supporting multiple Trustee instances for different verification purposes (algorithm signing, environment validation, compliance checking)

Independent Verification Workflows: IETF RATS-compliant pattern where organizations maintain sovereignty over their attestation policies while enabling cross-organization collaboration

Reference: Technical Document 2 - Multi-Organization Confidential Computing Platform