A security company is developing a new cloud-based log analytics platform. Its purpose is to allow: - Customers to upload their log files to the "big data" platform - Customers to perform remote log…

API keys serve as authentication credentials for third-party integrations; if they are not securely stored and transmitted, a customer or attacker could obtain another customer's key and access their log data through the API. Protecting these credentials is essential to maintaining tenant isolation at the integration layer.

Secure protocols such as TLS encrypt log files and search results during transmission between customers and the platform, preventing interception or man-in-the-middle attacks that could expose one customer's data to another. Without transport encryption, data traversing shared network infrastructure could be read by other tenants.

Log retention policies address compliance and e-discovery requirements, not the prevention of cross-tenant data disclosure.

Multi-tenancy with RBAC is the foundational architectural control that ensures each customer can only access their own data within the shared platform. RBAC policies enforce authorization boundaries between tenants so that authenticated users are limited strictly to their own organization's resources.

Sanitizing uploaded log content prevents sensitive data from entering the platform but does not control whether one authenticated tenant can access another tenant's already-stored data.

Encrypted storage protects data at rest from infrastructure-level unauthorized access but does not enforce tenant isolation or prevent an authenticated user from reaching another customer's data if access controls are misconfigured.