Hello,
I’m currently working on a multi-tenant Wazuh implementation where we manage multiple clients (environments like Environment A and Environment B) from our central MSSP console. Each client has their own Wazuh indexer and server, which allows for isolated environments. While this works well, I have concerns about the scalability and data retention on the client side.
Specifically, I’m seeking guidance on two key architectural points:
1. Centralized Data Storage - Moving Client Data to Our MSSP Cloud:Our goal is to implement an architecture where client data (logs, security events, etc.) is not stored locally on the client's Wazuh infrastructure. Instead, we want to offload this data directly into our cloud, so the client doesn’t have to handle the growing storage needs. Additionally, this would allow us to avoid any inbound connections into the client’s environment, as it’s more secure and comfortable for clients to only have outbound data transfers.
We want to minimize the need for inbound connections from our MSSP console into the client's environment. The idea is to set up a flow where the client’s Wazuh agents and indexers push data out to our cloud or MSSP console, rather than us accessing their systems directly.
Is it possible to implement a fully cloud-based solution where all client data is stored centrally in our cloud, and the client does not need to manage or store any Wazuh data on-premises? I’m particularly interested in understanding if there are ways to handle the following:
I would greatly appreciate insights from anyone who has implemented something similar or has experience working with cloud-centric Wazuh deployments. Any implementation details, best practices, or potential challenges would be extremely helpful.
Thank you in advance for your support and suggestions!