The Seal product family
Five products covering your stack, all built on the same sealing approach.
Seal has five products that together cover your stack. They all use the same underlying sealing approach: a sealed package replaces a vulnerable origin version without changing your code. They differ in what they secure and in how the fix reaches your environment.
Application open-source dependencies (npm, pip, Maven, Gradle, ...)
Sealed dependencies pulled in during your CI/CD build, or via the Seal Artifact Server
OS-level packages and language runtimes on Linux servers and in containers, including EOL distributions
Sealed packages installed by the Seal CLI, in place
OS-level packages and language runtimes inside container base images
Clean base image, pulled from a Seal-hosted registry
OS-level packages, language runtimes, and embedded open-source artifacts inside your private container images
Sealed copy of your container image, pushed back to your registry
OS-level packages, language runtimes, and embedded open-source artifacts inside vendor-supplied containers
Seal CLI applies fixes in place inside the vendor's container in your environment
The pages below cover each product in turn. For day-1 setup, see Application and OS setup or Container and image setup. For the day-to-day operating view, see Using the Seal Platform.
Last updated