A global conglomerate with operations in multiple geopolitical regions is onboarding XSIAM. Their existing data residency requirements dictate that certain types of security logs from specific regions must not leave those regions, even for cloud-based processing. How can XSIAM's architecture be adapted to meet these stringent data residency and compliance needs, while still providing a unified security posture view?
Correct Answer: C
For strict data residency requirements across geopolitical boundaries, deploying separate XSIAM tenants (instances) in the compliant cloud regions is the most robust and architecturally sound approach. Each tenant would store and process data within its designated region. XSIAM's platform design allows for querying and potentially federating insights across multiple tenants (e.g., through a 'parent' account or specific XSIAM features for multi-tenant management), providing a consolidated security view without violating data residency. Option B might work for some data, but not for raw security logs if the residency applies to raw data. A and E are not architectural options for XSIAM, and D introduces undue complexity.