✳flâneur — a map of the web's best reading

Why did we need to build our own SIEM? | Rippling

rippling.com · 3,389 words · saved by 1 readers

This blog is the first in a series of posts covering how we built an engineering-first security information and event management (SIEM) system at Rippling. Indeed, you read that right—Rippling consciously chose to develop its own SIEM rather than opting for an off-the-shelf solution. In this series, we’ll explore the rationale behind this decision and gain insights into the strategic choices that led us down this (quite) unique path, where we prioritize engineering practices, principles, and methodologies in the design and development process. You might be wondering what exactly “engineering-first” means for us at Rippling. It's about a commitment to integrating the best engineering practices in our work. This encompasses robust data engineering for effective information management, the use of reliable software development methodologies, and embedding security right from the start. We believe this approach helps us lay a solid foundation for our SIEM system while acknowledging that we’

Why did we need to build our own SIEM? Blog Engineering a SIEM part 1: Why did we need to build our own SIEM? Author Piotr Szwajkowski Read time 15 MIN Updated Apr 11, 2024 In this article The importance of SIEM and efficient log management Our journey to a custom SIEM solution Coming up in part 2: Our solution — security data lakehouse and modular design In this article The importance of SIEM and efficient log management Our journey to a custom SIEM solution Coming up in part 2: Our solution — security data lakehouse and modular design This blog is the first in a series of posts covering how

Explore this link on the map →

related reading