A message bus provides a scalable, event-driven mechanism for distributing high-volume security telemetry to multiple consumers independently. With endpoint telemetry reaching 15 TB daily, Sophia requires a solution that supports continuous ingestion, low-latency delivery, and parallel consumption without introducing unnecessary processing overhead into the SIEM.
A message bus enables endpoint telemetry to be published to a common messaging infrastructure. The SIEM and data science platform can subscribe to the relevant data streams and process events according to their operational requirements. This architecture decouples data producers from consumers, allowing independent scaling, buffering, and failure recovery.
Technologies such as Apache Kafka provide capabilities for partitioned event streams, durable message retention, and consumer groups. These capabilities support security analytics workloads while preserving flexibility for additional downstream systems.
Options A and C involve historical exports and do not address the requirement for continuous delivery of newly generated events. Option D introduces batch-processing delays and is unsuitable for real-time analysis.
The architecture also requires appropriate throughput planning, access controls, delivery guarantees, and retention policies.
Official reference / study topic: Splunk Cybersecurity Defense Architect blueprint, Security Data Management Objectives 2.1 and 2.8: message buses and scalable integration architectures.
===============
Submit