Description
Seal fixes the open source and OS vulnerabilities Wiz finds across your cloud workloads and containers. Instead of waiting on a dependency upgrade or a base image rebuild, Seal backports the upstream security fix into the exact package version you already run and delivers it as a signed, drop-in replacement. As a partner in the Wiz Integration Network (WIN), Seal's sealed packages are recognized by Wiz without any extra configuration on your side.
How Seal fits into your Wiz workflow
Wiz gives you the agentless visibility into which workloads carry a vulnerability; Seal is the fix. Add the Seal CLI to your CI pipeline, or run Seal OS inside your Dockerfile, and it resolves the packages covered by your Sealing Rules to their sealed versions before the image or artifact is built. The sealed package ships through your pipeline like any other dependency, with no separate Wiz-specific build step required.
Sealing Rules can be managed three ways: automatically, where Seal fixes every sealable vulnerability it finds; remotely, where rules are approved once in the Seal Platform and every build that references the affected package picks them up on its next run; or locally, in a .seal-actions.yml file committed to the repository. Remote mode is what lets one approved rule reach every workload Wiz is watching that uses a package, without a pull request against each one.
Because a sealed version keeps the original version number and adds a suffix (for example lodash 4.17.20-sp1, or an extended revision for Alpine packages), it is still the version your manifest or base image expects. There is no framework migration and no code change, so a security fix does not turn into an engineering project.
Seal and Wiz's findings
Keep Wiz scanning your cloud environment as you already do. Seal does not replace it; Seal removes the vulnerability it reports. Wiz recognizes sealed packages out of the box, so once a sealed package reaches a running workload, the next Wiz scan sees the sealed version and the finding closes. No manual override, waiver or exception is needed in Wiz.
Setting up Seal with Wiz
- Get a Seal API token from the Seal Platform.
- Add the Seal CLI to your CI pipeline, or add a Seal OS step to your Dockerfile, so builds resolve covered packages to sealed versions.
- Decide how Sealing Rules should apply: automatic, remote (managed centrally in the Seal Platform), or local (a
.seal-actions.ymlfile). - Build and deploy your image or artifact as usual. The sealed packages ship inside it with no extra Wiz configuration.
- Let Wiz's next scan of your cloud workloads run on its normal schedule.
- Check the Wiz dashboard. The finding for each sealed package clears once Wiz has scanned the workload running the sealed version.
Frequently asked questions
Does Seal replace Wiz?
No. Seal fixes the vulnerabilities Wiz finds; it does not scan your cloud environment. Keep Wiz running, since Seal backports the fix into the version your workloads already run.
Do I need to configure Wiz to recognize sealed packages?
No. As a Wiz Integration Network partner, Seal's sealed packages are recognized out of the box, with nothing to install or set up on the Wiz side.
Do I need to change my application code or Dockerfile logic to use Seal with Wiz?
No. A sealed version is a drop-in replacement with the same major version and the same API, so adopting Seal is a pipeline or build configuration change, not a code change.
Will this work for end-of-life or legacy packages Wiz flags in my containers?
Yes. Seal backports fixes into end-of-life and legacy versions as long as the upstream source is public, so workloads pinned to old versions can still be remediated without an upgrade.
Does sealing a workload require runtime access?
No. Seal works at build time, delivering sealed packages into the image or artifact before it is deployed. It runs no agents inside your running workloads.
How quickly does a cleared finding show up in Wiz?
Once a workload running the sealed package is live, the finding clears the next time Wiz scans that workload, on Wiz's normal scan cadence.


