How to Scale Cloud Security with Auto-Remediation | Samuel Burgos López & Andoni Alonso Fernández

How to Scale Cloud Security with Auto-Remediation | Samuel Burgos López & Andoni Alonso Fernández

Title history
  • How to Scale Cloud Security with Auto-Remediation | Samuel Burgos López & Andoni Alonso Fernández — observed on 20261113-0014 UTC (YouTube)
🎙 Cloud Security Podcast 👥 41K 📅 November 12, 2026 ⏱ 43 min 👁 10 📄 expert opinion 🧭 2026-11-13
Available in: English (current) Français

Keywords

auto-remediationcloud securityCSPMguardrailsmulti-cloud

Summary

In this podcast episode, Ashish Rajan interviews Andoni Alonso Fernández and Samuel Burgos López about their approach to scaling cloud security via auto-remediation. They explain why auto-remediation initially failed—due to lack of context and trust—and how they overcame this through a structured, infrastructure-as-code approach. They describe their architecture using Steampipe, SQS, and Lambda to automate fixes across AWS, GCP, and Azure. A central theme is building trust with engineering teams by offering bypass options, configuration locks, and thorough testing in isolated environments. They emphasize starting with low-risk, repetitive fixes like enabling default EBS encryption, which frees teams to focus on complex issues. They also discuss handling M&A integrations and the role of AI in accelerating script development for remediation. Key guardrails include configuration (enabled controls with exceptions), locks (preventing infinite loops), and bypasses (allowing teams to temporarily skip remediations). The episode concludes with practical advice on starting an auto-remediation program and the importance of human relationships.

156 words

Critical Evaluation

Value of the Information & Strength of the Argument

The video offers valuable, actionable insights for cloud security practitioners. The guests present a compelling case for auto-remediation when implemented with rigorous guardrails. Their argumentation is solid, grounded in real-world experience from multiple cloud environments and M&A scenarios. They acknowledge the initial failure of auto-remediation and provide a nuanced solution that balances automated enforcement with human oversight and trust. The step-by-step starting suggestions (e.g., remediating only new resources first) are practical and reduce risk. The emphasis on transparency and communication with engineering teams is a crucial point that is often overlooked. Overall, the information is high-value and the reasoning is persuasive, although it relies primarily on anecdotal evidence rather than quantitative data.

Scientific Rigor, Source Quality, Title Accuracy

The content demonstrates rigorous engineering discipline: they modeled their remediation pipeline after software release practices, including tests and staging environments. They used open-source tools like Steampipe, which are well-documented and widely adopted. However, the sources cited are limited to the podcast’s own website and promotional links (Newsletter, Bootcamp, LinkedIn), and they mention a talk at ForwardCloud EU without providing a direct URL. The title accurately represents the content, and the discussion stays on topic throughout. The technical details are credible, but the lack of external references reduces the ability to independently verify some claims. Nevertheless, the alignment between title and content is excellent.

230 words

Title / Content Match

The title accurately reflects the topic: discussing how to scale cloud security using auto-remediation, with the named guests as practitioners.

Quality & Reliability

7/10

The content is based on practical, first-hand experience from two cloud security engineers. They describe a concrete architecture for auto-remediation with guardrails (configuration, lock, bypass) and emphasize trust-building with engineering teams. While no academic sources are cited, the use of well-known open-source tools (Steampipe) and cloud services adds credibility. The reasoning is consistent and addresses common pitfalls.

Chapters

Cited Sources

Concurring Sources

  • Steampipe Documentation — Documentation for the tool used to query cloud APIs, supporting the multi-cloud visibility described.
  • AWS Config Remediation — AWS's native auto-remediation mechanism, which aligns with the general practice of automating fixes.

Contribution & Novelties

This episode contributes a pragmatic, trust-driven framework for auto-remediation, emphasizing guardrails (configuration, lock, bypass) and the importance of involving engineering teams. It details a specific architecture using Steampipe, SQS, and Lambda, which is not commonly covered in such depth. The discussion on scaling across multiple clouds and handling M&A complexities adds practical value.

Pour aller plus loin :

  • Steampipe — Official site for Steampipe, the open-source infrastructure-as-code tool used to query cloud assets and automate checks.
  • Cloud Security Posture Management (CSPM) — Definition and overview of CSPM, the category of tools that generate the alerts discussed.
  • AWS Config Remediation — Official documentation on AWS Config’s remediation capabilities, a service often used for automated fixes.
  • Infrastructure as Code (IaC) — Concept underlying the approach of managing cloud resources declaratively, enabling reproducible and testable remediations.
  • AWS Lambda — Serverless compute service used in the described remediation pipeline for executing actions.

148 words

Radar Profile

The radar profile shows a balanced high score across information quality, quantity, and technical level, with reliability slightly lower due to the anecdotal nature. This indicates a content that is rich in practical detail and well-argued but relies on personal experience rather than formal research.

Reliability 7/10