Cloud Security Podcast by Google

EP264 Measuring Your (Agentic) SOC: Two Security Leaders Walk into a Podcast

· Summarized

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

Key takeaways

  • Metrics must evolve alongside technology; traditional measures like MTTD and MTTR may become less relevant with AI handling incident response at machine speed.
  • Focus on metrics that capture quality, context, and risk reduction, such as 'Time to Context' and automation impact, rather than speed alone.
  • AI-driven security operations are about augmentation, improving analyst efficiency and decision quality, not just replacing human workers.
  • High-level success should be communicated through risk-based metrics to the board, such as overall risk reduction and incident impact, rather than detailed operational metrics.
  • Explaining AI decisions and justifying security outcomes to regulators requires transparency, documentation, and trust-building, especially as systems become less deterministic.
  • The economic model for SOCs is shifting towards 'doing more with less,' with a focus on automation, productivity, and risk mitigation, rather than solely reducing headcount.
  • The future of security teams involves a transformation where humans focus on complex investigations and strategic tasks, supported by automation and AI tools.

Summary

Evolving Metrics in the Age of AI: From Legacy to Modern Indicators

The discussion begins with an analysis of traditional SOC metrics like Mean Time to Detect (MTTD) and Mean Time to Respond (MTTR). The speakers argue that these metrics are becoming less relevant as AI handles incident triage and resolution at machine speed. Instead of focusing solely on metrics like speed, the conversation shifts toward the importance of metrics that measure quality and context, such as 'Time to Context,' which accounts for understanding and action rather than just detection speed. The speakers emphasize that metrics need to evolve with technological advancements, highlighting that some traditional indicators could even be considered 'vanity metrics' if they no longer reflect true security health.

The Maturity Triangle and the Impact of AI on Security Measurements

The podcast explores the 'Maturity Triangle' framework, which assesses security maturity across infrastructure, operating system, applications, and data layers. The integration of AI is expected to shift this triangle, possibly moving organizations from a 'people-heavy' model to a more 'engineering-led' approach. The discussion highlights that as automation and AI expand, the metrics tracking the effectiveness of detection, response, and automation need to adapt. How organizations measure success, such as toil reduction, is also debated, with an emphasis on metrics that show the actual impact of AI—like time saved or threat complexity reduced—rather than just speed.

Google’s Approach to Measuring Success in D&R and Toil Reduction

Google's internal security strategy prioritizes quantifying 'Toil Reduction'—the reduction of repetitive manual tasks—by tracking how many incidents are handled automatically versus manually. The metrics also include the quality of incident handling, such as the accuracy of AI-assisted triage and the time saved for security analysts. Google measures success by assessing operational efficiencies, risk reduction, and the risk exposure within the organization's appetite. For the board, high-level metrics focus on risk mitigation and incident reduction rather than raw detection counts, emphasizing 'risk exposure' within a company's risk appetite.

Quantifying the Unit Economics of AI in SOCs and Managing Risks

The panel discusses the economic implications of integrating AI into security operations. AI is viewed more as an augmentation tool that increases analyst productivity and decision accuracy, rather than a direct replacement for humans. Metrics such as the ratio of AI-handled to human-handled incidents are considered crucial, but there is caution about over-reliance on automation, which could introduce new risks if AI handles instances improperly. The conversation underlines that as AI advances, organizations will need to redefine success metrics—moving toward measures that reflect risk mitigation, efficiency gains, and operational maturity—while understanding that the economic landscape for security staffing and automation is constantly changing.

Regulatory Challenges and Trust in AI-Driven Security Metrics

The speakers acknowledge the challenges posed by regulations and audits when deploying non-deterministic AI systems in security. Explaining and justifying AI decisions to auditors and regulators is complex, especially regarding false negatives or missed detections. Trust and transparency are central themes, with a focus on maintaining auditable processes, comprehensive documentation, and proving risk reduction. Google emphasizes that while AI can assist significantly, human oversight remains critical, especially in regulated environments, and success will depend on how well organizations can communicate AI's role and effectiveness without relying solely on deterministic measures.

Board-Level Metrics and Strategic Communication of Security Success

The discussion on high-level metrics reveals that organizational and board metrics tend to focus on risk reduction and overall security posture rather than detailed operational data. For example, rather than sharing pipeline latency or detection speed, security leaders communicate in terms of risk exposure and incident impact, demonstrating how security investments reduce their overall risk within acceptable thresholds. This approach aligns security metrics with business and financial outcomes, making them more relatable and meaningful for executive decision-makers.

Future of SOC Economics and Workforce Implications with AI

The conversation concludes with insights into the economic and workforce implications of AI in security. AI is seen as a productivity enhancer—helping security teams do more with less and shifting their roles toward more strategic, complex tasks. Analysts' jobs are evolving rather than disappearing, focusing on deep investigation and decision-making. While automation may reduce some manual toil, the importance of human judgment remains. The panel emphasizes that success in the future will depend on organizations' ability to adapt their operational models, redefine what constitutes value, and measure improvements in risk, efficiency, and threat understanding.

Sponsors

  • Google · Thanks for joining us today. Your host here in a random office in Seattle this week are myself, Tim Peacock, the senior PM for, well, a bunch of stuff, and Google Psychops, and of course, Anton Srivacan, or foreign analyst and senior staff in Google Cloud's Office of the CISO. You can find and subscribe to this podcast wherever you get your podcasts, as well as our new video format on YouTube, youtube.com slash at CloudSek Podcast. If you enjoy our content and want it delivered to you, piping hot, don't forget to hit that subscribe button.

Show notes

Guests:

Topics:

  • We've spent decades obsessed with MTTD (Mean Time to Detect) and MTTR (Mean Time to Respond). As AI agents begin to handle the bulk of triage at machine speed, do these metrics become "vanity metrics"? If an AI resolves an alert in seconds, does measuring the "mean" still tell us anything about the health of our security program, or should we be looking at "Time to Context" instead?
  • You mentioned the Maturity Triangle. Can you walk us through that framework? Specifically, how does AI change the balance between the three points of that triangle—is it shifting us from a "People-heavy" model to something more "Engineering-led," and where does the "Measurement" piece sit?
  • Google is famous for its "Engineering-led" approach to D&R. How is Google currently measuring the success of its own internal D&R program? Specifically, how are you quantifying "Toil Reduction"? Are we measuring how many hours we saved, or are we measuring the complexity of the threats our humans are now free to hunt?
  • Toil reduction is a laudable goal for the team members, what are the metrics we track and report up to document the overall improvement in D&R for Google's board?
  • When you talk to your board about the success of AI in your security program, what are the 2 or 3 "Golden Metrics" that actually move the needle for them? How do you prove that an AI-driven SOC is actually better, not just faster?
  • We often talk about AI as an "assistant," but we're moving toward Agentic SOCs. How should organizations measure the "unit economics" of their SOC? Should we be tracking the ratio of AI-handled vs. Human-handled incidents, and at what point does a high AI-handle rate become a risk rather than a success?

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