Explorez tous les épisodes du podcast Cloud Security Podcast by Google
Plongez dans la liste complète des épisodes de Cloud Security Podcast by Google. Chaque épisode est catalogué accompagné de descriptions détaillées, ce qui facilite la recherche et l'exploration de sujets spécifiques. Suivez tous les épisodes de votre podcast préféré et ne manquez aucun contenu pertinent.
Rows per page:
50
1–50 of 281
Titre
Date
Durée
EP239 Linux Security: The Detection and Response Disconnect and Where Is My Agentless EDR
When it comes to Linux environments – spanning on-prem, cloud, and even–gasp–hybrid setups – where are you seeing the most significant blind spots for security teams today?
There's sometimes a perception that Linux is inherently more secure or less of a malware target than Windows. Could you break down some of the fundamental differences in how malware behaves on Linux versus Windows, and why that matters for defenders in the cloud?
'Living off the Land' isn't a new concept, but on Linux, it feels like attackers have a particularly rich set of native tools at their disposal. What are some of the more subtly abused but legitimate Linux utilities you're seeing weaponized in cloud attacks, and how does that complicate detection?
When you weigh agent-based versus agentless monitoring in cloud and containerized Linux environments, what are the operational trade-offs and outcome trade-offs security teams really need to consider?
SSH keys are the de facto keys to the kingdom in many Linux environments. Beyond just 'use strong passphrases,' what are the critical, often overlooked, risks associated with SSH key management, credential theft, and subsequent lateral movement that you see plaguing organizations, especially at scale in the cloud?
What are the biggest operational hurdles teams face when trying to conduct incident response effectively and rapidly across such a distributed Linux environment, and what's key to overcoming them?
When introducing AI agents to security teams at Google, what was your initial strategy to build trust and overcome the natural skepticism? Can you walk us through the very first conversations and the key concerns that were raised?
With a vast array of applications, how did you identify and prioritize the initial use cases for AI agents within Google's enterprise security?
What specific criteria made a use case a good candidate for early evaluation? Were there any surprising 'no-go' areas you discovered?"
Beyond simple efficiency gains, what were the key metrics and qualitative feedback mechanisms you used to evaluate the success of the initial AI agent deployments?
What were the most significant hurdles you faced in transitioning from successful pilots to broader adoption of AI agents?
How do you manage the inherent risks of autonomous agents, such as potential for errors or adversarial manipulation, within a live and critical environment like Google's?
How has the introduction of AI agents changed the day-to-day responsibilities and skill requirements for Google's security engineers?
From your unique vantage point of deploying defensive AI agents, what are your biggest concerns about how threat actors will inevitably leverage similar technologies?
Security is part of your DNA. In your day to day at TikTok, what are some tips you’d share with users about staying safe online?
Many regulations were written with older technologies in mind. How do you bridge the gap between these legacy requirements and the realities of a modern, microservices-based tech stack like TikTok's, ensuring both compliance and agility?
You have a background in compliance and risk management. How do you approach demonstrating the effectiveness of security controls, not just their existence, especially given the rapid pace of change in both technology and regulations?
TikTok operates on a global scale, facing a complex web of varying regulations and user expectations. How do you balance the need for localized compliance with the desire for a consistent global security posture? How do you avoid creating a fragmented and overly complex system, and what role does automation play in this balancing act?
What strategies and metrics do you use to ensure auditability and provide confidence to stakeholders?
We understand you've used TikTok videos for security training. Can you elaborate on how you've fostered a strong security culture internally, especially in such a dynamic environment?
EP236 Accelerated SIEM Journey: A SOC Leader's Playbook for Modernization and AI
28 juil. 2025
00:27:15
Guest:
Manija Poulatova, Director of Security Engineering and Operations at Lloyd's Banking Group
Topics:
SIEM migration is hard, and it can take ages. Yours was - given the scale and the industry - on a relatively short side of 9 months. What’s been your experience so far with that and what could have gone faster?
Anton might be a “reformed” analyst but I can’t resist asking a three legged stool question: of the people/process/technology aspects, which are the hardest for this transformation? What helped the most in solving your big challenges?
Was there a process that people wanted to keep but it needed to go for the new tool?
One thing we talked about was the plan to adopt composite alerting techniques and what we’ve been calling the “funnel model” for detection in Google SecOps. Could you share what that means and how your team is adopting?
There are a lot of moving parts in a D&R journey from a process and tooling perspective, how did you structure your plan and why?
It wouldn’t be our show in 2025 if I didn’t ask at least one AI question! What lessons do you have for other security leaders preparing their teams for the AI in SOC transition?
Agentic AI and AI agents, with its promise of autonomous decision-making and learning capabilities, presents a unique set of risks across various domains. What are some of the key areas of concern for you?
What frameworks are most relevant to the deployment of agentic AI, and where are the potential gaps?
What are you seeing in terms of how regulatory frameworks may need to be adapted to address the unique challenges posed by agentic AI?
How about legal aspects - does traditional tort law or product liability apply?
How does the autonomous nature of agentic AI challenge established legal concepts of liability and responsibility?
The other related topic is knowing what agents “think” on the inside. So what are the key legal considerations for managing transparency and explainability in agentic AI decision-making?
Why do so many organizations still collect logs yet don’t detect threats? In other words, why is our industry spending more money than ever on SIEM tooling and still not “winning” against Tier 1 ... or even Tier 5 adversaries?
What are the hardest parts about getting the right context into a SOC analyst’s face when they’re triaging and investigating an alert? Is it integration? SOAR playbook development? Data enrichment? All of the above?
What are the organizational problems that keep organizations from getting the full benefit of the security operations tools they’re buying?
Top SIEM mistakes? Is it trying to migrate too fast? Is it accepting a too slow migration? In other words, where are expectations tyrannical for customers? Have they changed much since 2015?
Do you expect people to write their own detections? Detecting engineering seems popular with elite clients and nobody else, what can we do?
Do you think AI will change how we SOC (Tim: “SOC” is not a verb?) in the next 1- 3 -5 years?
Do you think that AI SOC tech is repeating the mistakes SOAR vendors made 10 years ago? Are we making the same mistakes all over again? Are we making new mistakes?
EP233 Product Security Engineering at Google: Resilience and Security
07 juil. 2025
00:25:44
Guest:
Cristina Vintila, Product Security Engineering Manager, Google Cloud
Topic:
Could you share insights into how Product Security Engineering approaches at Google have evolved, particularly in response to emerging threats (like Log4j in 2021)?
You mentioned applying SRE best practices in detection and response, and overall in securing the Google Cloud products. How does Google balance high reliability and operational excellence with the needs of detection and response (D&R)?
How does Google decide which data sources and tools are most critical for effective D&R?
You have had a fascinating career since we [Tim] graduated from college together – you mentioned before we met that you’ve consulted with a literal world leader on his personal digital security footprint. Maybe tell us how you got into this field of helping organizations treat sensitive information securely and how that led to helping keep targeted individuals secure?
You also work as a privacy engineer on Fuschia, Google’s new operating system kernel. How did you go from human rights and privacy to that?
What are the key privacy considerations when designing an operating system for “ambient computing”? How do you design privacy into something like that?
More importantly, not only “how do you do it”, but how do you convince people that you did do it?
When we talk about "higher risk" individuals, the definition can be broad. How can an average person or someone working in a seemingly less sensitive role better assess if they might be a higher-risk target? What are the subtle indicators?
Thinking about the advice you give for personal security beyond passwords and multi-factor auth, how much of effective personal digital hygiene comes down to behavioral changes versus purely technical solutions?
Given your deep understanding of both individual security needs and large-scale OS design, what's one thing you wish developers building cloud services or applications would fundamentally prioritize about user privacy?
EP231 Beyond the Buzzword: Practical Detection as Code in the Enterprise
23 juin 2025
00:30:40
Guest:
David French, Staff Adoption Engineer, Google Cloud
Topic:
Detection as code is one of those meme phrases I hear a lot, but I’m not sure everyone means the same thing when they say it. Could you tell us what you mean by it, and what upside it has for organizations in your model of it?
What gets better for security teams and security outcomes when you start managing in a DAC world? What is primary, actual code or using SWE-style process for detection work?
Not every SIEM has a good set of APIs for this, right? What’s a team to do in a world of no or low API support for this model?
If we’re talking about as-code models, one of the important parts of regular software development is testing. How should teams think about testing their detection corpus? Where do we even start? Smoke tests? Unit tests?
You talk about a rule schema–you might also think of it in code terms as a standard interface on the detection objects–how should organizations think about standardizing this, and why should they?
If we’re into a world of detection rules as code and detections as code, can we also think about alert handling via code? This is like SOAR but with more of a software engineering approach, right?
One more thing that stood out to me in your presentation was the call for sharing detection content. Is this between vendors, vendors and end users?
Your RSA talk highlights lessons learned from two years of AI red teaming at Google. Could you share one or two of the most surprising or counterintuitive findings you encountered during this process?
What are some of the key differences or unique challenges you've observed when testing AI-powered applications compared to traditional software systems?
Can you provide an example of a specific TTP that has proven effective against AI systems and discuss the implications for security teams looking to detect it?
What practical advice would you give to organizations that are starting to incorporate AI red teaming into their security development lifecycle?
What are some initial steps or resources you would recommend they explore to deepen their understanding of this evolving field?
Something about vuln exploitation vs credential abuse in today’s breaches–what’s driving the shifts we’re seeing? DBIR
Are we at peak ransomware? Will ransomware be here in 20 years? Will we be here in 20 years talking about it?
How is AI changing the breach report, other than putting in hilarious footnotes about how the report is for humans to read and and is written by actual humans?
SIEM is hard, and many vendors have discovered this over the years. You need to get storage, security and integration complexity just right. You also need to be better than incumbents. How would you approach this now?
Decoupled SIEM vs SIEM/EDR/XDR combo. These point in the opposite directions, which side do you think will win?
In a world where data volumes are exploding, especially in cloud environments, you're building a SIEM with ClickHouse as its backend, focusing on both parsed and raw logs. What's the core advantage of this approach, and how does it address the limitations of traditional SIEMs in handling scale?
Cribl, Bindplane and “security pipeline vendors” are all the rage. Won’t it be logical to just include this into a modern SIEM?
You're envisioning a 'Pipeline QL' that compiles to SQL, enabling 'detection in SQL.' This sounds like a significant shift, and perhaps not to the better? (Anton is horrified, for once) How does this approach affect detection engineering?
With Sigma HQ support out-of-the-box, and the ability to convert SPL to Sigma, you're clearly aiming for interoperability. How crucial is this approach in your vision, and how do you see it benefiting the security community?
What is SIEM in 2025 and beyond? What’s the endgame for security telemetry data? Is this truly SIEM 3.0, 4.0 or whatever-oh?
Why is your AI-powered MDR special? Why start an MDR from scratch using AI?
So why should users bet on an “AI-native” MDR instead of an MDR that has already got its act together and is now applying AI to an existing set of practices?
What’s the current breakdown in labor between your human SOC analysts vs your AI SOC agents? How do you expect this to evolve and how will that change your unit economics?
What tasks are humans uniquely good at today’s SOC? How do you expect that to change in the next 5 years?
We hear concerns about SOC AI missing things –but we know humans miss things all the time too. So how do you manage buyer concerns about the AI agents missing things?
Let’s talk about how you’re helping customers measure your efficacy overall. What metrics should organizations prioritize when evaluating MDR?
Can you describe the key components of an AI software supply chain, and how do they compare to those in a traditional software supply chain?
I hope folks listening have heard past episodes where we talked about poisoning training data. What are the other interesting and unexpected security challenges and threats associated with the AI software supply chain?
We like to say that history might not repeat itself but it does rhyme – what are the rhyming patterns in security practices people need to be aware of when it comes to securing their AI supply chains?
We’ve talked a lot about technology and process–what are the organizational pitfalls to avoid when developing AI software? What organizational "smells" are associated with irresponsible AI development?
We are all hearing about agentic security – so can we just ask the AI to secure itself?
Top 3 things to do to secure AI software supply chain for a typical org?
Can you explain the concept of "MLSecOps" as an analogy with DevSecOps, with 'Dev' replaced by 'ML'? This has nothing to do with SecOps, right?
What are the most critical steps a CISO should prioritize when implementing MLSecOps within their organization? What gets better when you do it?
How do we adapt traditional security testing, like vulnerability scanning, SAST, and DAST, to effectively assess the security of machine learning models? Can we?
In the context of AI supply chain security, what is the essential role of third-party assessments, particularly regarding data provenance?
How can organizations balance the need for security logging in AI systems with the imperative to protect privacy and sensitive data? Do we need to decouple security from safety or privacy?
What are the primary security risks associated with overprivileged AI agents, and how can organizations mitigate these risks?
Top differences between LLM/chatbot AI security vs AI agent security?
EP223 AI Addressable, Not AI Solvable: Reflections from RSA 2025
05 mai 2025
00:31:37
Guests:
no guests, just us in the studio
Topics:
At RSA 2025, did we see solid, measurably better outcomes from AI use in security, or mostly just "sizzle" and good ideas with potential?
Are the promises of an "AI SOC" repeating the mistakes seen with SOAR in previous years regarding fully automated security operations? Does "AI SOC" work according to RSA floor?
How realistic is the vision expressed by some [yes, really!] that AI progress could lead to technical teams, including IT and security, shrinking dramatically or even to zero in a few years?
Why do companies continue to rely on decades-old or “non-leading” security technologies, and what role does the concept of a "organizational change budget" play in this inertia?
Is being "AI Native" fundamentally better for security technologies compared to adding AI capabilities to existing platforms, or is the jury still out? Got "an AI-native SIEM"? Be ready to explain how is yours better!
What is the hardest thing about turning distinct incident reports into a fun to read and useful report like M-Trends?
How much are the lessons and recommendations skewed by the fact that they are all “post-IR” stories?
Are “IR-derived” security lessons the best way to improve security? Isn’t this a bit like learning how to build safely from fires vs learning safety engineering?
The report implies that F500 companies suffer from certain security issues despite their resources, does this automatically mean that smaller companies suffer from the same but more?
"Dwell time" metrics sound obvious, but is there magic behind how this is done? Sometimes “dwell tie going down” is not automatically the defender’s win, right?
What is the expected minimum dwell time? If “it depends”, then what does it depend on?
Impactful outliers vs general trends (“by the numbers”), what teaches us more about security?
Why do we seem to repeat the mistakes so much in security?
Do we think it is useful to give the same advice repeatedly if the data implies that it is correct advice but people clearly do not do it?
EP221 Special - Semi-Live from Google Cloud Next 2025: AI, Agents, Security ... Cloud?
23 avr. 2025
00:30:26
Guests:
No guests [Tim in Vegas and Anton remote]
Topics:
So, another Next is done. Beyond the usual Vegas chaos, what was the overarching security theme or vibe you [Tim] felt dominated the conference this year?
Thinking back to Next '24, what felt genuinely different this year versus just the next iteration of last year's trends?
Last year, we pondered the 'Cloud Island' vs. 'Cloud Peninsula'. Based on Next 2025, is cloud security becoming more integrated with general cyber security, or is it still its own distinct domain?
What wider trends did you observe, perhaps from the expo floor buzz or partner announcements, that security folks should be aware of?
What was the biggest surprise for you at Next 2025? Something you absolutely didn't see coming?
Putting on your prediction hats (however reluctantly): based on Next 2025, what do you foresee as the major cloud security focus or challenge for the industry in the next 12 months?
If a busy podcast listener listening could only take one key message or action item away from everything announced and discussed at Next 2025, what should it be?
Vulnerability response at cloud-scale sounds very hard! How do you triage vulnerability reports and make sure we’re addressing the right ones in the underlying cloud infrastructure?
How do you determine how much to pay for each vulnerability? What is the largest reward we paid? What was it for?
What products get the most submissions? Is this driven by the actual product security or by trends and fashions like AI?
What are the most likely rejection reasons?
What makes for a very good - and exceptional? - vulnerability report? We hear we pay more for “exceptional” reports, what does it mean?
In college Tim had a roommate who would take us out drinking on his Google web app vulnerability rewards. Do we have something similar for people reporting vulnerabilities in our cloud infrastructure? Are people making real money off this?
How do we actually uniquely identify vulnerabilities in the cloud? CVE does not work well, right?
What are the expected risk reduction benefits from Cloud VRP?
We've seen a shift in how boards engage with cybersecurity. From your perspective, what's the most significant misconception boards still hold about cyber risk, particularly in the Asia Pacific region, and how has that impacted their decision-making?
Cybersecurity is rife with jargon. If you could eliminate or redefine one overused term, which would it be and why? How does this overloaded language specifically hinder effective communication and action in the region?
The Mandiant Attack Lifecycle is a well-known model. How has your experience in the East Asia region challenged or refined this model? Are there unique attack patterns or actor behaviors that necessitate adjustments?
Two years post-acquisition, what's been the most surprising or unexpected benefit of the Google-Mandiant combination?
M-Trends data provides valuable insights, particularly regarding dwell time. Considering the Asia Pacific region, what are the most significant factors reducing dwell time, and how do these trends differ from global averages?
Given your expertise in Asia Pacific, can you share an observation about a threat actor's behavior that is often overlooked in broader cybersecurity discussions?
Looking ahead, what's the single biggest cybersecurity challenge you foresee for organizations in the Asia Pacific region over the next five years, and what proactive steps should they be taking now to prepare?
EP218 IAM in the Cloud & AI Era: Navigating Evolution, Challenges, and the Rise of ITDR/ISPM
07 avr. 2025
00:30:10
Guest:
Henrique Teixeira, Senior VP of Strategy, Saviynt, ex-Gartner analyst
Topics:
How have you seen IAM evolve over the years, especially with the shift to the cloud, and now AI? What are some of the biggest challenges and opportunities these two shifts present?
ITDR (Identity Threat Detection and Response) and ISPM (Identity Security Posture Management) are emerging areas in IAM. How do you see these fitting into the overall IAM landscape? Are they truly distinct categories or just extensions of existing IAM practices?
Shouldn’t ITDR just be part of your Cloud DR or maybe even your SecOps tool of choice? It seems goofy to try to stand ITDR on its own when the impact of an identity compromise is entirely a function of what that identity can access or do, no?
Regarding workload vs. human identity, could you elaborate on the unique security considerations for each? How does the rise of machine identities and APIs impact IAM approaches?
We had a whole episode around machine identity that involved turtles–what have you seen in the machine identity space and how have you seen users mess it up?
The cybersecurity world is full of acronyms. Any tips on how to create a memorable and impactful acronym?
Adversa AI is known for its focus on AI red teaming and adversarial attacks. Can you share a particularly memorable red teaming exercise that exposed a surprising vulnerability in an AI system? What was the key takeaway for your team and the client?
Beyond traditional adversarial attacks, what emerging threats in the AI security landscape are you most concerned about right now?
What trips most clients, classic security mistakes in AI systems or AI-specific mistakes?
Are there truly new mistakes in AI systems or are they old mistakes in new clothing?
I know it is not your job to fix it, but much of this is unfixable, right?
Can you walk us through Google's typical threat modeling process? What are the key steps involved?
Threat modeling can be applied to various areas. Where does Google utilize it the most? How do we apply this to huge and complex systems?
How does Google keep its threat models updated? What triggers a reassessment?
How does Google operationalize threat modeling information to prioritize security work and resource allocation? How does it influence your security posture?
What are the biggest challenges Google faces in scaling and improving its threat modeling practices? Any stories where we got this wrong?
How can LLMs like Gemini improve Google's threat modeling activities? Can you share examples of basic and more sophisticated techniques?
What advice would you give to organizations just starting with threat modeling?
You are responsible for building systems that need to comply with laws that are often mutually contradictory. It seems technically impossible to do, how do you do this?
Google is not alone in being a global company with local customers and local requirements. How are we building systems that provide local compliance with global consistency in their use for customers who are similar in scale to us?
Originally, Google had global systems synchronized around the entire planet–planet scale supercompute–with atomic clocks. How did we get to regionalized approach from there?
Engineering takes a long time. How do we bring enough agility to product definition and engineering design to give our users robust foundations in our systems that also let us keep up with changing and diverging regulatory goals?
What are some of the biggest challenges you face working in the trusted cloud space?
Is there something you would like to share about being a woman leader in technology? How did you overcome the related challenges?
Where do you see a gap between the “promise” of LLMs for security and how they are actually used in the field to solve customer pains?
I know you use LLMs for anomaly detection. Explain how that “trick” works? What is it good for? How effective do you think it will be?
Can you compare this to other anomaly detection methods? Also, won’t this be costly - how do you manage to keep inference costs under control at scale?
SOC teams often grapple with the tradeoff between “seeing everything” so that they never miss any attack, and handling too much noise. What are you seeing emerge in cloud D&R to address this challenge?
We hear from folks who developed an automated approach to handle a reviews queue previously handled by people. Inevitably even if precision and recall can be shown to be superior, executive or customer backlash comes hard with a false negative (or a flood of false positives). Have you seen this phenomenon, and if so, what have you learned about handling it?
What are other barriers that need to be overcome so that LLMs can push the envelope further for improving security?
So from your perspective, LLMs are going to tip the scale in whose favor - cybercriminals or defenders?
EP211 Decoding the Underground: Google's Dual-Lens Threat Intelligence Magic
17 févr. 2025
00:26:02
Guest:
Kimberly Goody, Head of Intel Analysis and Production, Google Cloud
Topics:
Google's Threat Intelligence Group (GTIG) has a unique position, accessing both underground forum data and incident response information. How does this dual perspective enhance your ability to identify and attribute cybercriminal campaigns?
Attributing cyberattacks with high confidence is important. Can you walk us through the process GTIG uses to connect an incident to specific threat actors, given the complexities of the threat landscape and the challenges of linking tools and actors?
There is a difficulty of correlating publicly known tool names with the aliases used by threat actors in underground forums. How does GTIG overcome this challenge to track the evolution and usage of malware and other tools? Can you give a specific example of how this "decoding" process works?
How does GTIG collaborate with other teams within Google, such as incident response or product security, to share threat intelligence and improve Google's overall security posture? How does this work make Google more secure?
What does Google (and specifically GTIG) do differently than other organizations focused on collecting and analyzing threat-intelligence? Is there AI involved?
EP210 Cloud Security Surprises: Real Stories, Real Lessons, Real "Oh No!" Moments
10 févr. 2025
00:26:58
Guest:
Or Brokman, Strategic Google Cloud Engineer, Security and Compliance, Google Cloud
Topics:
Can you tell us about one particular cloud consulting engagement that really sticks out in your memory? Maybe a time when you lifted the hood, so to speak, and were absolutely floored by what you found – good or bad!
In your experience, what's that one thing – that common mistake – that just keeps popping up? That thing that makes you say 'Oh no, not this again!'
'Tools over process' mistake is one of the 'oldies.' What do you still think drives people to it, and how to fix it?
If you could give just one piece of cloud security advice to every company out there, regardless of their size or industry, what would it be?
EP209 vCISO in the Cloud: Navigating the New Security Landscape (and Don’t Forget Resilience!)
03 févr. 2025
00:29:06
Guests:
Beth Cartier, former CISO, vCISO, founder of Initiative Security
Guest host of the CISO mini-series:
Marina Kaganovich, Executive Trust Lead, Office of the CISO @ Google Cloud
Topics:
How is that vCISO’ing going? What is special about vCISO and cloud? Is it easier or harder?
AI, cyber, resilience - all are hot topics these days. In the context of cloud security, how are you seeing organizations realistically address these trends? Are they being managed effectively (finally?) or is security always playing catch up?
Recent events reminded us that cybersecurity may sometimes interfere with resilience. How have you looked to build resilience into your security program?
The topic is perhaps 30+ years old, but security needs to have a seat at the table, and often still doesn’t - why do you think this is the case?
What approaches or tips have you found to work well in elevating security within organizations?
Any tips for how cyber professionals can stay up to date to keep up with the current threat landscape vs the threats that are around the corner?
Can you briefly walk us through your CISO career path?
What are some of the key (cloud or otherwise) trends that CISOs should be keeping an eye on? What is the time frame for them?
What are the biggest cloud security challenges CISOs are facing today, and how are those evolving?
Given the rapid change of pace in emerging tech, such as what we’ve seen in the last year or so with gen AI, how do you balance the need to address short-term or imminent issues vs those that are long-term or emergent risks?
What advice do you have for how CISOs can communicate the importance of anticipating threats to their boards and executives?
So, how to be a forward looking and strategic yet not veer into dreaming, paranoia and imaginary risks? How to be futuristic yet realistic?
The CISO role as an official title is a relatively new one, what steps have you taken to build credibility and position yourself for having a seat at the table?
Tell us about the ransomware problem - isn't this a bit of old news? Circa 2015, right?
What makes ransomware a unique security problem?
What's different about ransomware versus other kinds of malware? What do you make of the “RansomOps” take (aka “ransomware is not malware”)?
Are there new ways to solve it?
Is this really a problem that a startup is positioned to solve? Aren’t large infrastructure owners better positioned for this? In fact, why haven't existing solutions solved this?
Is this really a symptom of a bigger problem? What is that problem?
What made you personally want to get into this space, other than the potential upside of solving the problem?
EP206 Paying the Price: Ransomware's Rising Stakes in the Cloud
13 janv. 2025
00:33:01
Guest:
Allan Liska, CSIRT at Recorded Future, now part of Mastercard
Topics:
Ransomware has become a pervasive threat. Could you provide us with a brief overview of the current ransomware landscape?
It's often said that ransomware is driven by pure profit. Can you remind us of the business model of ransomware gangs, including how they operate, their organizational structures, and their financial motivations?
Ransomware gangs are becoming increasingly aggressive in their extortion tactics. Can you shed some light on these new tactics, such as data leaks, DDoS attacks, and threats to contact victims' customers or partners?
What specific challenges and considerations arise when dealing with ransomware in cloud environments, and how can organizations adapt their security strategies to mitigate these risks?
What are the key factors to consider when deciding whether or not to pay the ransom?
What is the single most important piece of advice you would give to organizations looking to bolster their defenses against ransomware?
We are getting a bit annoyed about the fear-mongering on “oh, but attackers will use AI.” You are a threat analyst, realistically, how afraid are you of this?
The report discusses the threat of compromised identities in hybrid environments (aka “no matter what you do, and where, you are hacked via AD”). What steps can organizations take to mitigate the risk of a single compromised identity leading to a significant security breach? Is this expected to continue?
Is zero-day actually growing? The report seems to imply that, but aren’t “oh-days” getting more expensive every day?
Many organizations still lag with detection, in your expertise, what approaches to detection actually work today? It is OK to say ”hire Managed Defense”, BTW :-)
We read the risk posed by the "Big Four" sections and they (to us) read like “hackers hack” and “APTs APT.” What is genuinely new and interesting here?
EP204 Beyond PCAST: Phil Venables on the Future of Resilience and Leading Indicators
23 déc. 2024
00:30:32
Guest:
Phil Venables, Vice President, Chief Information Security Officer (CISO) @ Google Cloud
Topics
Why is our industry suddenly obsessed with resilience? Is this ransomware’s doing?
How did the PCAST report come to be? Can you share the backstory and how it was created?
The PCAST report emphasizes the importance of leading indicators for security and resilience. How can organizations effectively shift their focus from lagging indicators to these leading indicators?
The report also emphasizes the importance of "Cyber-Physical Modularity" - this sounds mysterious to us, and probably our listeners! What is it and how does this concept contribute to enhancing the resilience of critical infrastructure?
The report advocates for regular and rigorous stress testing. How can organizations effectively implement such stress testing to identify vulnerabilities and improve their resilience?
In your opinion, what are the most critical takeaways from our PCAST-related paper for organizations looking to improve their security and resilience posture today?
What are some of the challenges organizations might face when implementing the PCAST recommendations, and how can they overcome these challenges?
Do organizations get resilience benefits “for free” by using Google Cloud?
Let’s talk about cloud security shared responsibility. How to separate the blame? Is there a good framework for apportioning blame?
You've introduced the Cloud Shared Irresponsibilities Model, stating cloud providers will be considered partially responsible for breaches even if due to customer misconfigurations. How do you see this impacting the relationship between cloud providers and their customers? Will it lead to more collaboration or more friction?
We both know the Jay Heiser 2015 classic “cloud is secure, but you not using it securely.” In your view, what does “use cloud securely” mean for various organizations today?
Here is a very painful question: how to decide what cloud security should be free with cloud and what security can be paid?
You dealt with cloud security for a long time, what is your #1 lesson so far on how to make the cloud more secure or use the cloud more securely?
What is the best way to learn how to cloud? What is this CloudSLAW thing?
EP201 Every CTO Should Be a CSTO (Or Else!) - Transformation Lessons from The Hoff
02 déc. 2024
00:36:57
Guest:
Chris Hoff, Chief Secure Technology Officer at Last Pass
Topics:
I learned that you have a really cool title that feels very “now” - Chief Secure Technology Officer? What’s the story here? Weirdly, I now feel that every CTO better be a CSTO or quit their job :-)
After, ahem, not-so-recent events you had a chance to rebuild a lot of your stack, and in the process improve security. Can you share how it went, and what security capabilities are now built in?
How much of a culture change did that require? Was it purely a technological transformation or you had to change what people do and how they do it?
Would you recommend this to others (not the “recent events experience”, but the rebuild approach)? What benefits come from doing this before an incident occurs? Are there any?
How are you handling telemetry collection and observability for security in the new stack? I am curious how this was modernized
Cloud is simple, yet also complex, I think you called it “simplex.” How does this concept work?
“How Google protects its production services” paper covers how Google's infrastructure balances several crucial aspects, including security, reliability, development speed, and maintainability. How do you prioritize these competing demands in a real-world setting?
What attack vectors do you consider most critical in the production environment, and how has Google’s defenses against these vectors improved over time?
Can you elaborate on the concept of Foundational services and their significance in Google's security posture?
How does your security approach adapt to this vast spectrum of sensitivity and purpose of our servers and services, actually?
How do you implement this principle of zero touch prod for both human and service accounts within our complex infrastructure?
Can you talk us through the broader approach you take through Workload Security Rings and how this helps?
What is your reaction to “in the cloud you are one IAM mistake away from a breach”? Do you like it or do you hate it? Or do you "it depends" it? :-)
Everyone's talking about how "identity is the new perimeter" in the cloud. Can you break that down in simple terms?
A lot of people say “in the cloud, you must do IAM ‘right’”. What do you think that means? What is the first or the main idea that comes to your mind when you hear it?
What’s this stuff about least-privilege and separation-of-duties being less relevant? Why do they matter in the cloud that changes rapidly?
EP197 SIEM (Decoupled or Not), and Security Data Lakes: A Google SecOps Perspective
04 nov. 2024
00:29:34
Guest:
Travis Lanham, Uber Tech Lead (UTL) for Security Operations Engineering, Google Cloud
Topics:
There’s been a ton of discussion in the wake of the three SIEM week about the future of SIEM-like products. We saw a lot of takes on how this augurs the future of disassembled or decoupled SIEMs. Can you explain what these disassembled SIEMs are all about?
What are the expected upsides of detaching your SIEM interface and security capabilities from your data backend?
Tell us about the early days of SecOps (nee Chronicle) and why we didn’t go with this approach?
What are the upsides of a tightly coupled datastore + security experience for a SIEM?
Are there more risks or negatives of the decoupled/decentralized approach? Complexity and the need to assemble “at home” are on the list, right?
One of the 50 things Google knew to be true back in the day was that product innovation comes from technical innovation, what’s the technical innovation driving decoupled SIEMs?
So what about those security data lakes? Any insights?
EP196 AI+TI: What Happens When Two Intelligences Meet?
28 oct. 2024
00:28:08
Guest:
Vijay Ganti, Director of Product Management, Google Cloud Security
Topics:
What have been the biggest pain points for organizations trying to use threat intelligence (TI)?
Why has it been so difficult to convert threat knowledge into effective security measures in the past?
In the realm of AI, there's often hype (and people who assume “it’s all hype”). What's genuinely different about AI now, particularly in the context of threat intelligence?
Can you explain the concept of "AI-driven operationalization" in Google TI? How does it work in practice?
What's the balance between human expertise and AI in the TI process? Are there specific areas where you see the balance between human and AI involvement shifting in a few years?
Google Threat Intelligence aims to be different. Why are we better from client PoV?
How would you approach answering the question ”what is more secure, container or a virtual machine (VM)?”
Could you elaborate on the real-world implications of this for security, and perhaps provide some examples of when one might be a more suitable choice than the other?
While containers boast a smaller attack surface (what about the orchestrator though?), VMs present a full operating system. How should organizations weigh these factors against each other?
The speed of patching and updates is a clear advantage of containers. How significant is this in the context of today's rapidly evolving threat landscape? Are there any strategies organizations can employ to mitigate the slower update cycles associated with VMs?
Both containers and VMs can be susceptible to misconfigurations, but container orchestration systems introduce another layer of complexity. How can organizations address this complexity and minimize the risk of misconfigurations leading to security vulnerabilities?
What about combining containers and VMs. Can you provide some concrete examples of how this might be implemented? What benefits can organizations expect from such an approach, and what challenges might they face?
How do you envision the security landscape for containers and VMs evolving in the coming years? Are there any emerging trends or technologies that could significantly impact the way we approach security for these two technologies?
Why do we need Application Detection and Response (ADR)? BTW, how do you define it?
Isn’t ADR a subset of CDR (for cloud)? What is the key difference that sets ADR apart from traditional EDR and CDR tools?
Why can’t I just send my application data - or eBPF traces - to my SIEM and achieve the goals of ADR that way?
We had RASP and it failed due to instrumentation complexities. How does an ADR solution address these challenges and make it easier for security teams to adopt and implement?
What are the key inputs into an ADR tool?
Can you explain how your ADR correlates cloud, container, and application contexts to provide a better view of threats? Could you share real-world examples of types of badness solved for users?
How would ADR work with other application security technologies like DAST/SAST, WAF and ASPM?
Upon hearing this, many experts suggest that “burn the environment with fire” or “nuke it from orbit” are the only feasible approaches? What is your take on that suggestion?
On the opposite side, what if business demands you don't touch anything but “make it secure” regardless?
Could you walk us through some of the first critical steps you do after “inheriting a cloud” and why they are prioritized in this way?
Why not just say “add MFA everywhere”? What may or will blow up?
We also say “address overly permissive users and roles” and this sounds valuable, but also tricky. How do we go about it?
What are the chances that the environment is in fact compromised already? When is Compromise Assessment the right call, it does cost money, right?
How do you balance your team’s current priorities when you’ve just adopted an insecure cloud environment. How do you make tradeoffs among your existing stack and this new one?
Nelly Porter, Director of PM, Cloud Security at Google Cloud
Topics:
Share your story and how you ended here doing confidential AI at Google?
What problem does confidential compute + AI solve and for what clients?
What are some specific real-world applications or use cases where you see the combination of AI and confidential computing making the most significant impact?
What about AI in confidential vs AI on prem? Should those people just do on-prem AI instead?
Which parts of the AI lifecycle need to be run in Confidential AI: Training? Data curation? Operational workloads?
What are the performance (and thus cost) implications of running AI workloads in a confidential computing environment?
Are there new risks that arise out of confidential AI?
EP191 Why Aren't More Defenders Winning? Defender’s Advantage and How to Gain it!
23 sept. 2024
00:23:36
Guest:
Dan Nutting, Manager - Cyber Defense, Google Cloud
Topics:
What is the Defender’s Advantage and why did Mandiant decide to put this out there?
This is the second edition. What is different about DA-II?
Why do so few defenders actually realize their Defender’s Advantage?
The book talks about the importance of being "intelligence-led" in cyber defense. Can you elaborate on what this means and how organizations can practically implement this approach?
Detection engineering is presented as a continuous cycle of adaptation. How can organizations ensure their detection capabilities remain effective and avoid fatigue in their SOC?
Many organizations don’t seem to want to make detections at all, what do we tell them?
What is this thing called “Mission Control”- it sounds really cool, can you explain it?