<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ed Legault on Medium]]></title>
        <description><![CDATA[Stories by Ed Legault on Medium]]></description>
        <link>https://medium.com/@ed.legault?source=rss-76724aa135d7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*My-yzwp7AGPIJbN-</url>
            <title>Stories by Ed Legault on Medium</title>
            <link>https://medium.com/@ed.legault?source=rss-76724aa135d7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 14:23:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ed.legault/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Chaos Engineering: Breaking Things On Purpose]]></title>
            <link>https://medium.com/leading-edje/chaos-engineering-breaking-things-on-purpose-4cd300693601?source=rss-76724aa135d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/4cd300693601</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[chaos-engineering]]></category>
            <dc:creator><![CDATA[Ed Legault]]></dc:creator>
            <pubDate>Tue, 03 Jun 2025 18:48:27 GMT</pubDate>
            <atom:updated>2025-06-03T18:48:27.259Z</atom:updated>
            <content:encoded><![CDATA[<h4>What chaos engineering is, how to get started and how to not get fired</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zDeSKAiPotVE2AuYCkM-JQ.png" /></figure><p>In today’s complex digital landscape, systems fail. This isn’t pessimism, it’s a fundamental truth that experienced technical professionals understand all too well. When (not if) failures occur, the difference between organizations that thrive and those that struggle often comes down to a single factor: preparation. Enter chaos engineering, a disciplined approach to identifying system vulnerabilities by proactively introducing controlled failures in production environments.</p><p>Chaos engineering is like a vaccine for your infrastructure. A little controlled pain now prevents a lot of uncontrolled pain later.</p><p>This article explores why chaos engineering deserves both budget allocation and prioritization within technical organizations seeking to build truly resilient systems.</p><h3>What Is Chaos Engineering?</h3><p>Chaos Engineering is the practice of deliberately injecting failures into a system to test its resilience and identify weaknesses before they manifest as customer-impacting incidents. Pioneered by Netflix with their <a href="https://netflix.github.io/chaosmonkey/">Chaos Monkey</a> tool, this methodology has evolved into a structured discipline focused on conducting controlled experiments that reveal how systems behave under stress.</p><p>At its core, chaos engineering follows a scientific process:</p><ol><li>Form a hypothesis about how the system should behave under adverse conditions</li><li>Design an experiment that introduces a specific failure or stressor</li><li>Execute the experiment in a controlled environment</li><li>Observe and measure the system’s response</li><li>Learn and improve by addressing identified weaknesses</li></ol><p>Unlike traditional testing which verifies known requirements, chaos engineering explores the unknown: how systems respond to unexpected conditions that weren’t explicitly designed for but will inevitably occur.</p><h3>Why Resilience Matters in Modern Systems</h3><p>Modern digital infrastructures have evolved into intricate ecosystems of microservices, distributed databases, and complex dependencies. This complexity introduces numerous potential failure points that can cascade in unexpected ways.</p><p>Resilience isn’t merely a technical consideration, it’s a business imperative. The ability to withstand unexpected conditions directly impacts revenue, reputation, and customer trust.</p><h3>Key Benefits of Chaos Engineering</h3><h3>Increased Reliability and Resiliency</h3><p>Chaos engineering fundamentally changes how teams approach system reliability. Rather than merely responding to failures, teams proactively identify weaknesses before they impact users. This approach helps identify hidden vulnerabilities that traditional testing misses, builds confidence in actual (not theoretical) fault tolerance capabilities, and validates that recovery mechanisms function as designed. If a team feels uncomfortable running a chaos experiment on a particular system, that discomfort often signals exactly where testing is most needed.</p><h3>Improved Incident Response</h3><p>When teams regularly practice responding to controlled failures, they develop muscle memory that proves invaluable during actual incidents. This regular practice leads to reduced mean time to resolution (MTTR) as teams become familiar with failure patterns and respond more efficiently. Engineers develop intuition about system behavior under stress, and the process often reveals gaps in runbooks and incident response procedures that can be addressed proactively.</p><h3>Reduced Downtime and Business Impact</h3><p>By discovering vulnerabilities proactively, organizations can address weaknesses before they result in customer-facing outages. This approach means fewer unexpected outages, as issues are discovered during controlled experiments rather than in production. Recovery times become shorter thanks to well-exercised recovery procedures, and customer impact is minimized as systems become more reliable.</p><h3>Improved Understanding of System Behavior</h3><p>Perhaps the most underrated benefit of chaos engineering is how it deepens engineers’ understanding of their systems. Teams gain clearer visualization of how components interact, understand how failures cascade through systems, and learn how systems behave under various forms of stress. This knowledge proves invaluable when designing new features or troubleshooting issues.</p><h3>Enhanced Confidence in Production Changes</h3><p>Organizations practicing chaos engineering report higher confidence when deploying new features and infrastructure changes. This confidence stems from validated resilience mechanisms, understood failure modes, and battle-tested monitoring systems that ensure observability during failures.</p><h3>How to Get Started with Chaos Engineering</h3><p>Implementing chaos engineering doesn’t require a massive organizational overhaul. Here are a few steps to help get started:</p><h3>Establish a Baseline</h3><p>Before conducting any chaos experiments, ensure you have comprehensive monitoring and observability tools in place. You’ll need clear metrics for what constitutes “normal” system behavior and defined service level objectives (SLOs) that matter to your business. This baseline allows you to measure the impact of your experiments objectively and determine whether your system is resilient enough to withstand the introduced failures.</p><h3>Start with Game Days</h3><p>Before implementing automated chaos, conduct manual “game days” — scheduled exercises where teams intentionally create failure scenarios and practice response procedures. These events build confidence, establish processes, and identify gaps in your incident response capabilities. A typical game day might involve manually stopping a non-critical service and documenting the recovery process, impact, and lessons learned.</p><h3>Choose Simple, Low-Risk Experiments</h3><p>Your first automated chaos experiments should target non-critical infrastructure components and run during business hours when engineers are available. Make sure to have well-defined abort conditions and communicate broadly to stakeholders. For example, start by terminating a single instance in a load-balanced pool of web servers during a low-traffic period, with the hypothesis that customers should experience no impact.</p><h3>Document and Share Results</h3><p>After each experiment, document findings, including unexpected behaviors, and share results with the broader engineering organization. Update runbooks and monitoring based on insights, and prioritize fixing any revealed weaknesses. This knowledge-sharing amplifies the value of each experiment across the organization.</p><h3>Gradually Expand Scope</h3><p>As confidence grows, incrementally increase both the complexity of experiments and their proximity to critical business functions. Progress from testing individual components to testing interactions between systems, and move from staging environments toward production. Expand from simple resource constraints to more complex failure modes, and consider implementing continuous chaos engineering with automated guardrails.</p><h3>Build a Culture of Resilience</h3><p>The most successful chaos engineering programs evolve beyond tools and processes to become cultural movements within organizations. Celebrate the discovery of weaknesses rather than punishing failures, and reward teams for building resilient systems that withstand chaos experiments. Include resilience as a first-class requirement in system design, and provide time and resources for fixing weaknesses discovered through experiments.</p><h3>Available Tools for Chaos Engineering</h3><p>The chaos engineering ecosystem has matured significantly, with options ranging from cloud provider offerings to open-source frameworks.</p><h3>Cloud Provider Tools</h3><p><a href="https://aws.amazon.com/fis/">AWS Fault Injection Service</a> offers native integration with AWS services, supporting EC2, ECS, EKS, and RDS experiments with safeguards and automatic rollbacks.</p><p><a href="https://azure.microsoft.com/en-us/products/chaos-studio">Azure Chaos Studio</a> targets Azure-specific resources with an experiment builder featuring managed fault types and integration with Azure monitoring for validation.</p><h3>Open-Source Options</h3><p>Here are a few open-source or free tools for chaos engineering you may want to investigate:</p><ul><li><a href="https://netflix.github.io/chaosmonkey/">Chaos Monkey</a>, Netflix’s original chaos engineering tool, randomly terminates instances in production. Though simple, it remains effective for basic resilience testing.</li><li><a href="https://litmuschaos.io/">Litmus</a> offers Kubernetes-native chaos engineering with an extensive experiment catalog for cloud-native systems and an active community.</li><li><a href="https://chaostoolkit.org/">Chaos Toolkit</a> provides a framework-agnostic approach with extensive API support for various platforms and declarative experiment definitions.</li><li><a href="https://www.gremlin.com/chaos-engineering">Gremlin</a>, while commercial, offers a free tier with a user-friendly interface, broad attack types, and built-in safety mechanisms.</li></ul><h3>Implementing Chaos Engineering Responsibly — Not getting fired</h3><p>While the benefits are substantial, chaos engineering requires thoughtful implementation. Start small with non-critical systems and simple experiments. Establish clear boundaries for potential impact and ensure comprehensive observability during experiments. Prepare mechanisms to quickly restore normal operations, and communicate plans to stakeholders before conducting chaos experiments.</p><h3>Conclusion</h3><p>Chaos engineering represents a paradigm shift from reactive to proactive reliability management. Rather than waiting for unexpected failures to reveal system weaknesses, forward-thinking organizations deliberately introduce controlled failure to build more resilient systems.</p><p>As systems grow more complex, the organizations that thrive will be those that embrace failure as an inevitable reality and engineer accordingly. Chaos engineering isn’t merely about breaking things, it’s about building confidence through evidence-based resilience.</p><p>You don’t run chaos experiments because you enjoy creating problems. You run them because problems are inevitable, and you would rather find them on your terms instead of your customers’.</p><p>When viewed through this lens, chaos engineering isn’t a luxury, it’s a necessity for modern system reliability that delivers measurable business value through improved uptime, faster incident response, and enhanced customer experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4cd300693601" width="1" height="1" alt=""><hr><p><a href="https://medium.com/leading-edje/chaos-engineering-breaking-things-on-purpose-4cd300693601">Chaos Engineering: Breaking Things On Purpose</a> was originally published in <a href="https://medium.com/leading-edje">Leading EDJE</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Critical Role of Automated Dependency Scanning]]></title>
            <link>https://medium.com/leading-edje/the-critical-role-of-automated-dependency-scanning-8c78870fccb0?source=rss-76724aa135d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c78870fccb0</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[dependency-management]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Ed Legault]]></dc:creator>
            <pubDate>Fri, 30 May 2025 13:09:11 GMT</pubDate>
            <atom:updated>2025-05-30T13:09:11.327Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why automated dependency scanning has emerged as a critical component in modern DevOps practices</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2MH_NNU6jGcAUesvVusCxQ.png" /></figure><p>In today’s rapidly evolving software development landscape, managing dependencies has become increasingly complex. Applications often rely on dozens, sometimes hundreds, of third-party libraries and packages, each with their own update cycles and security considerations. This article explores why automated dependency scanning has emerged as a critical component in modern DevOps practices.</p><h3>The Security Imperative</h3><p>Security vulnerabilities in dependencies represent one of the most significant risks to application security today. According to recent studies, over 80% of code-bases contain at least one vulnerability in their dependencies.</p><p>Automated dependency scanning addresses this challenge by:</p><ul><li><strong>Continuous vulnerability detection</strong>: Rather than point-in-time assessments, automated tools constantly monitor for newly discovered vulnerabilities in your dependencies</li><li><strong>Rapid response capability</strong>: When vulnerabilities are discovered, teams can be notified immediately, rather than during periodic manual reviews</li><li><strong>Comprehensive coverage</strong>: Scanning tools can analyze deep dependency trees that would be impractical to review manually</li></ul><p>Expecting developers to manually track CVEs is like expecting them to memorize pi to 100 digits. Although it is technically possible, there are much better uses of their brainpower.</p><h3>Reducing Friction in Development Workflows</h3><p>The most effective security measures are those that developers actually use. Traditional security reviews often create bottlenecks that frustrate development teams and slow delivery.</p><p>Automated dependency scanning helps by:</p><ul><li><strong>Integrating directly into existing workflows</strong>: Scans run automatically during commits, PRs, or builds</li><li><strong>Minimizing manual intervention</strong>: Only requiring developer attention when action is genuinely needed</li><li><strong>Providing clear remediation paths</strong>: Rather than just flagging issues, good tools suggest specific fixes</li></ul><h3>Organizational Consistency with Team Flexibility</h3><p>One of the greatest challenges in enterprise software development is balancing organizational standards with team autonomy. Dependency scanning tools help strike this balance by:</p><ul><li><strong>Establishing baseline security standards</strong>: Ensuring all projects meet minimum security requirements</li><li><strong>Supporting customizable policies</strong>: Allowing teams to adjust scanning criteria based on project risk profiles</li><li><strong>Enabling centralized visibility</strong>: Providing security teams oversight while allowing development teams to maintain velocity</li></ul><h3>Practical Implementation: Tools of the Trade</h3><h3>Renovate</h3><p>Renovate has emerged as a powerful, flexible tool for automated dependency management. It works by:</p><ol><li>Scanning repositories for dependencies</li><li>Checking for updates against package registries</li><li>Creating pull requests with dependency updates</li><li>Providing detailed change information, including changelog links and compatibility information</li></ol><p>Renovate’s configuration as code approach means teams can tailor its behavior precisely to their needs. For example, a team might configure Renovate to:</p><pre>{<br>  &quot;extends&quot;: [&quot;config:base&quot;],<br>  &quot;packageRules&quot;: [<br>    {<br>      &quot;matchUpdateTypes&quot;: [&quot;minor&quot;, &quot;patch&quot;],<br>      &quot;matchCurrentVersion&quot;: &quot;!/^0/&quot;,<br>      &quot;automerge&quot;: true<br>    }<br>  ]<br>}</pre><p>This configuration would automatically merge non-breaking updates for stable dependencies, while requiring manual review for major versions or pre-1.0 packages.</p><h3>Dependabot</h3><p>GitHub’s built-in Dependabot offers streamlined dependency management for GitHub repositories. Its key features include:</p><ul><li><strong>Automated security updates</strong>: Dependabot can automatically create PRs when security vulnerabilities are detected</li><li><strong>Scheduled version updates</strong>: Regular checks for newer versions based on configurable schedules</li><li><strong>Ecosystem support</strong>: Works with major package ecosystems including npm, Maven, NuGet, and many others</li></ul><p>A typical Dependabot configuration might look like:</p><pre>version: 2<br>updates:<br>  - package-ecosystem: &quot;npm&quot;<br>    directory: &quot;/&quot;<br>    schedule:<br>      interval: &quot;weekly&quot;<br>    open-pull-requests-limit: 10<br>    labels:<br>      - &quot;dependencies&quot;</pre><h3>CI/CD Integration</h3><p>The true power of dependency scanning emerges when integrated into CI/CD pipelines:</p><h3>GitHub Actions Example</h3><pre>name: Dependency Security Check<br><br>on:<br>  push:<br>    branches: [ main ]<br>  pull_request:<br>    branches: [ main ]<br>  schedule:<br>    - cron: &#39;0 7 * * 1&#39;  # Weekly on Mondays<br>jobs:<br>  security:<br>    runs-on: ubuntu-latest<br>    steps:<br>      - uses: actions/checkout@v3<br>      - name: Run dependency security scan<br>        uses: dependency-check/dependency-check-action@v2<br>        with:<br>          project: &#39;My Project&#39;<br>          path: &#39;.&#39;<br>          format: &#39;HTML&#39;<br>          out: &#39;reports&#39;<br>      - name: Upload results<br>        uses: actions/upload-artifact@v3<br>        with:<br>          name: dependency-check-report<br>          path: reports</pre><h3>GitLab CI Example</h3><pre>dependency_scanning:<br>  stage: test<br>  script:<br>    - dependency-check --project &quot;My Project&quot; --scan . --format JSON --out reports/dependency-check-report.json<br>  artifacts:<br>    paths:<br>      - reports/dependency-check-report.json<br>    reports:<br>      dependency_scanning: reports/dependency-check-report.json<br>  rules:<br>    - if: $CI_COMMIT_BRANCH == &quot;main&quot;<br>    - if: $CI_PIPELINE_SOURCE == &quot;merge_request_event&quot;</pre><h3>Key Benefits at a Glance</h3><ul><li><strong>Reduced security risk</strong>: Automatically identify and remediate vulnerabilities before they can be exploited</li><li><strong>Developer productivity</strong>: Eliminate tedious manual dependency reviews</li><li><strong>Operational efficiency</strong>: Detect compatibility issues before they cause production incidents</li><li><strong>Compliance support</strong>: Maintain audit trails of dependency updates and vulnerability remediations</li><li><strong>Technical debt prevention</strong>: Prevent dependency versions from falling too far behind current releases</li></ul><h3>Conclusion</h3><p>Automated dependency scanning is no longer a “nice-to-have” but a critical component of modern software development. Trying to manage dependencies manually is like trying to update a card catalog in a library that adds 10,000 new books every day. You might start with good intentions, but you’ll be buried under index cards by lunchtime.</p><p>By implementing automated dependency scanning with tools like Renovate and Dependabot, and integrating them into CI/CD pipelines, organizations can significantly reduce security risks while increasing development velocity. The key lies in creating systems that provide consistent security guardrails while remaining flexible enough to accommodate different team workflows and project requirements.</p><p>In a world where software supply chain attacks continue to rise, automated dependency scanning represents one of the most effective measures organizations can take to protect their applications and their customers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c78870fccb0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/leading-edje/the-critical-role-of-automated-dependency-scanning-8c78870fccb0">The Critical Role of Automated Dependency Scanning</a> was originally published in <a href="https://medium.com/leading-edje">Leading EDJE</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>