In this article:

  • Vulnerability remediation requires more than just merging code: While opening a pull request (PR) updates a dependency, that's not the end of the process. Safely moving that change to production requires integration testing, change management, controlled traffic draining, and patch verification.
  • Lightwell provides stable, backported fixes: Lightwell delivers signed, version-specific binary fixes for eligible application dependencies without forcing major framework or runtime upgrades.
  • Red Hat Ansible Automation Platform orchestrates the release lifecycle, from continuous integration (CI) webhook triggers to pre-flight snapshots, traffic management, gated approvals, and automated rollback. Ansible Automation Platform provides trusted, repeatable execution across IT operations. 

The last mile of vulnerability remediation

In a recent post, How to patch application vulnerabilities without upgrading, we examined why full version upgrades can sometimes introduce regression risk, how Lightwell provides targeted vulnerability fixes, and the stages of a governed remediation workflow.

But the delivery of a fix by itself solves only one part of the problem. In many organizations, dependency updates face significant challenges after CI tests pass:

  • Applications require functional and integration testing beyond isolated unit tests
  • Change management requires deployment context, including common vulnerabilities and exposure (CVE) identifiers and build artifacts
  • Production deployments require traffic draining, state snapshots, and validation steps
  • Operators need an immediate, dependable rollback procedure if something fails

If these steps are executed manually using disjointed tools, internal wikis, and chat channels, your patch deployment lags, extending the period in which your application remains exposed. 

In this article, we'll talk about how automation excels at the "last mile of remediation," covering all the operational steps that need to occur once an impacted service has been identified and a remediated dependency is submitted in a PR. 

Balancing security exposures with operational stability

Security teams and operations teams share common goals of protecting IT services, however: 

  • SecOps focuses on closing the vulnerability exposure window and verifying CVE mitigation
  • ITOps focuses on service availability and performance
  • Platform engineering builds repeatable, self-service paths that deliver a verified change to production without breaking services

Using Red Hat Ansible Automation Platform along with Lightwell and your existing CI tools (such as those included in Red Hat OpenShift) allows you to resolve these often conflicting priorities. Instead of managing the process through ad-hoc communications, teams can integrate the workflow directly into their standard change records and automated pipelines so that patches are applied faster without taking down production systems. Teams can coordinate remediation with the operational steps required to move an application change toward production faster. 

Dependency remediation in the build pipeline

For illustrative purposes, imagine a Python application called inventory-service. Like many applications, it relies on libraries—reusable packages that provide functionality developers don’t need to build from scratch. One of its libraries is aiohttp, which helps Python applications handle web traffic and serve files.

In this example, inventory-service uses aiohttp version 3.9.0. A security advisory for CVE-2024-23334 describes a path traversal vulnerability in aiohttp’s static file handling when follow_symlinks=True. The upstream fix is available in version 3.9.2. If moving to that version right away creates API changes or dependency conflicts, teams can use a Lightwell-remediated artifact instead.

In our example repository, the pull request updates the package specification to:

aiohttp==3.9.0.rhlw-00001

Note: the .rhlw suffix identifies the Lightwell-patched version and patch level. This provides direct benefits across teams:

  • ITOps receives a predictable artifact that can be tested, staged, deployed, and rolled back using standard release procedures
  • SecOps maintains traceability, as the specific CVE identifier remains linked to the deployment record and build artifact
  • Platform engineering gets a standard golden path from the dependency change in the PR through CI to approval steps and production deployment so every CVE can follow the same workflow

When the PR is submitted, a corresponding change request (such as a ServiceNow change record) is linked in the metadata. This record tracks the dependency modification, associated CVEs, and deployment lifecycle. Software supply chain and security metadata provided by Lightwell—including package provenance, software bill of materials (SBOM), and (where applicable) Vulnerability Exploitability eXchange (VEX) metadata—attach directly to the record, creating an auditable history as code moves forward.

Using CI completion to trigger automation

After the PR merges into the target branch, the standard CI pipeline executes:

  1. Repository checkout
  2. Dependency installation
  3. Unit test execution
  4. Validation that the vulnerable library version has been replaced

Once tests pass, your CI pipeline (Jenkins, Tekton, OpenShift Pipelines) sends an outbound webhook to Ansible Automation Platform (through Event-Driven Ansible). The payload includes the execution parameters required for deployment:

  • Application identifier
  • Build version and Git commit hash (SHA)
  • CI build URL
  • Target CVE identifiers
  • Associated change ticket number

This webhook acts as an automated event trigger to initiate the next steps. Rather than waiting for manual handoffs, Ansible Automation Platform ingests the build metadata and initiates the governed deployment process.

Orchestrating post-CI operations with automation

The newly released automation orchestrator directs the overarching multistep deployment. Automation orchestrator is a dedicated extension to Ansible Automation Platform. While Ansible Automation Platform handles specific, linear tasks through individual playbooks (such as stopping a service or running a health check), the automation orchestrator introduces complex workflows with decision points, branching conditions, and approval gates.

A screenshot of the automation orchestrator interface displaying a CI/CD pipeline workflow for 'Dev Test'. The interface shows the project is set to 'default' and its status is 'Published'. It includes action buttons and options to 'Add step', 'Run', 'Save', and 'Publish workflow'.

With Lightwell patches, automation orchestrator receives the payload from the PR which kicks off the following process: 

  1. Change ticket synchronization: Ansible Automation Platform receives the webhook payload and appends operational metadata to the open change ticket. Variables such as the service name, Git SHA, deployed port, and target CVE are recorded automatically.
  2. Pre-production deployment and validation: The platform deploys the updated container or package to a staging environment and executes integration tests against connected dependencies. This verifies application stability in an integrated runtime environment.
  3. Conditional branching:
    • If the integration test succeeds, the workflow updates the change ticket and advances to the production step. 
    • If the test fails, the workflow stops, attaches test logs to the ticket, and notifies the responsible team.
  4. Context-aware approval gate: Before touching production systems, the workflow pauses at an approval gate. The approver is presented with the complete context, including: service name, version diff, target CVE, CI build URL, and staging test results. This means operational decisions are made with complete data.
  5. Traffic draining: Once approved, the production playbook begins by draining active connections from the load balancer pool (e.g., F5, HAProxy, or cloud application load balancers).
  6. System snapshot, deployment, and verification:
    • Snapshot: The automation captures a recovery snapshot (such as a virtual machine (VM) checkpoint, storage volume snapshot, or configuration backup).
    • Deploy: The new package is installed, configurations are applied, and services are restarted.
    • Smoke test: Post-deployment validation routines query the endpoints to confirm the service is responding and reporting the updated version string.
  7. Completion or automated rollback
    • On success: The load balancer re-enables the node, the change record is updated with verification outputs, and the service ticket is set to Closed.
    • On failure: If smoke checks fail, the workflow automatically initiates the rollback branch: restoring the snapshot, restarting the prior version, re-engaging traffic, and marking the change record as Failed with relevant diagnostic details.

This process aligns SecOps, ITOps, and platform engineering to share one trusted, repeatable path. Watch this workflow in action:

Putting Lightwell patches into production with Red Hat

Red Hat (along with your existing tools) can help you deliver Lightwell patches at scale, but the process after Lightwell delivers the fix depends on where your application runs: 

Containerized applications running on OpenShift 

In this scenario, your existing build and CI workflow incorporates the Lightwell-remediated dependency and validates the resulting application artifact. For applications running on OpenShift, the platform rebuilds and tests the app with the Lightwell dependency. OpenShift GitOps then promotes the updated image into the cluster with Ansible Automation Platform handling the steps around that deployment including updating the service ticket and deploying changes to infrastructure outside the cluster.

Applications running on VM or bare metal 

Here your existing CI tools build and test the remediated dependency. Ansible Automation Platform puts the patch into production with approvals, traffic draining, health checks, and rollback if needed.

In either case, with Lightwell and Red Hat, IT teams can establish predictable, repeatable, auditable remediation workflows. 

Summary and next steps

Effectively addressing application vulnerabilities requires careful coordination of software packaging, deployment, and operational safety checks. You can enable CVE remediation without breaking production systems, reliably roll back changes upon failure, produce audit-ready reporting, and enable operational consistency without replacing existing CI investments.

Learn more

Lightwell newsletter

Sign up for the Lightwell newsletter to get the latest news and insights directly to your inbox

About the authors

Anshul is a Principal Marketing Manager at Red Hat, where he brings his software development and QE experience to increase Ansible Automation Platform's adoption experience for customers by producing technical content on all aspects of the product.

Tricia McConnell is Principal Product Marketing Manager, Red Hat Ansible Automation Platform. She brings more than twenty years of experience marketing technical solutions to enterprise IT audiences. 

UI_Icon-Red_Hat-Close-A-Black-RGB

Keep exploring

Browse by channel

automation icon

Automation

The latest on IT automation for tech, teams, and environments

AI icon

Artificial intelligence

Updates on the platforms that free customers to run AI workloads anywhere

open hybrid cloud icon

Open hybrid cloud

Explore how we build a more flexible future with hybrid cloud

security icon

Security

The latest on how we reduce risks across environments and technologies

edge icon

Edge computing

Updates on the platforms that simplify operations at the edge

Infrastructure icon

Infrastructure

The latest on the world’s leading enterprise Linux platform

application development icon

Applications

Inside our solutions to the toughest application challenges

Virtualization icon

Virtualization

The future of enterprise virtualization for your workloads on-premise or across clouds