Cloud Security Podcast by Google

EP267 AI SOC or AI in a SOC? Cutting Through Hype, Pricing Models, and SIEM Detection Efficacy with Raffy Marty

· Summarized

Share this episode
Anyone with this link can open it.
Share Link
Start at 0:00

Key takeaways

  • Traditional SIEMs remain relevant and can evolve to address existing gaps, contrary to some marketing claims.
  • Locality and real-time detection are crucial; fully federated architectures struggle to match centralized SIEM fidelity.
  • AI has potential in detection engineering but cannot yet fully overcome core challenges such as environment variability and customization needs.
  • Pricing models based solely on data volume are flawed; more nuanced models considering compute, storage, and enrichment costs are preferable.
  • Detection content creation can benefit from AI but still requires understanding of environment-specific variability. Automated verification and recommendation systems are promising.
  • NDR remains an important telemetry source offering visibility and response capabilities, especially in environments with strict data governance or cloud migrations.

Summary

The State of SIEM and Industry Evolution

The hosts discuss the ongoing relevance of traditional Security Information and Event Management (SIEM) systems, emphasizing that claims of their obsolescence are more marketing hype than fact. Rafi Marty highlights that SIEMs have some gaps, but these are often temporary and can be addressed by the incumbents through fixing existing issues. The conversation emphasizes the importance of locality for correlation, stateful, real-time detection, which challenges the idea of fully federated or decoupled architectures delivering the same fidelity. The rise of data pipelines is seen as creating a 'Trojan horse', making SIEM components potentially swappable, and vendors should have adapted earlier to these shifts.

AI and the Future of Detection Engineering

The podcast explores whether AI can truly revolutionize detection engineering (DE) in security. Marty notes that despite historical efforts—from rules and heuristics to ML and now AI/agent-based approaches—the core issues of environment variability and customization remain. He stresses the importance of context graphs for entity monitoring and risk assessment, seeing this as a potential 'holy grail.' The discussion also touches on how detection rules could become more intelligent by verifying the presence of relevant data, thus reducing false positives and improving effectiveness. The influence of AI in automating and improving DE, but with the caveat that fundamental challenges still exist, is a key point.

Pricing Models and Vendor Strategies in the SIEM Market

The hosts delve into the flaws of volume-based pricing for SIEM products, noting that it often penalizes good security hygiene, as organizations that send more data pay more. Marty advocates for pricing models that fairly account for compute, enrichment, and retention, rather than volume alone. The discussion covers how vendors encouraging customers to bring their own compute and storage could reduce costs but shift responsibilities. The importance of providing effective management tools for different customer sizes, especially SMBs, is also emphasized. The conversation highlights that pricing strategies influence market adoption and vendor sustainability.

Detection Content Creation and Evaluation Metrics

The episode considers whether modern detection engineering can be automated or significantly improved through AI. Marty recalls the history of detection rule creation—from manual rule writing to ML—and emphasizes the need for systems that verify whether data will trigger specific detections, potentially providing recommendations for optimization. The challenge of environment variability remains, and advanced concepts like context graphs for entity and risk management are proposed as future directions. The discussion underscores that better metrics beyond coverage, such as quality and relevance of detection engineering output, are needed for evaluating vendors. AI's role in automating detection content remains promising but not yet fully realized.

Network Detection and Response (NDR) in Modern Security

The hosts discuss the resurgence of Network Detection and Response (NDR) technologies, emphasizing their importance as telemetry sources rather than standalone solutions. Marty explains that network data remains valuable for visibility, especially in environments where endpoint data is unreliable or inaccessible, such as cloud migrations or sensitive regions with strict data laws. The conversation clarifies that NDR is not likely to replace other security telemetry sources but complements them, offering critical insights into network activity and potential threats. The idea of response capabilities at the network level is also acknowledged as an important aspect.

Sponsors

  • Google · Thanks for joining us today on the Cloud Security Podcast by Google.

Show notes

Guest:

Topics:

  • You argue that declaring existing SIEM being obsolete is a "marketing slogan" rather than a true thesis. What is the real pain point and the actual gap in traditional SIEMs as opposed to the more sensational claims?
  • You highlight that "correlation, state, timelines, and real-time detection require locality," making centralization a necessary trade-off. Can a truly federated or decoupled SIEM architecture achieve the same fidelity and real-time performance for complex, stateful detections as a centralized one?
  • You call the rise of independent security data pipelines the "SIEM Trojan Horse." How quickly is this abstraction layer turning SIEM into a "swappable" component, and what should SIEM vendors have done differently years ago to prevent this market from existing?
  • This "AI SOC" thing, is this even real? Is AI in a SOC a better label? Do you think major SIEM vendors will own this very soon, like they did with UEBA and SOAR?
  • If volume-based pricing is flawed because it penalizes good security hygiene, what is a better SIEM pricing model that fairly addresses compute, enrichment, and retention costs without just shifting the volume cost to unpredictable query charges?
  • You question the idea that startups can find a better way to release detection rules than large vendors with significant content teams. What metrics should security leaders use to evaluate the quality of a vendor's detection engineering (DE) output beyond just coverage numbers? Can AI fix DE?

 

Resources:

Follow this show on AudioBrevity and new episodes get summarized for you. Create a free account

Couldn't load the audio. A blocker may be stopping the show's tracking links. Open the file