Integrations
How Seal connects to your existing security stack — SCA scanners, package renaming, Artifactory, GitHub.
Last updated
How Seal connects to your existing security stack — SCA scanners, package renaming, Artifactory, GitHub.
This section covers how Seal connects to the rest of your security stack: the SCA scanners your organization already runs, external scanners that consume Seal's vulnerability feed, JFrog Artifactory, and GitHub. Integrations don't change what Seal does — they keep your existing tools' views of your environment accurate after Seal has remediated something.
Internal scanner integrations: synchronizing remediation findings into the SCA scanners you run (Snyk, Black Duck, Checkmarx, GHAS, Ox Security, SentinelOne, Grype, Cycode).
External scanner support: the Seal vulnerability feed and VEX records consumed natively by Trivy and Wiz.
Package renaming: the fallback for scanners that don't consume the feed — renaming sealed packages so external scanners don't match them.
Artifactory integrations: JFrog Artifactory as an intermediary remote.
GitHub: the Seal GitHub App and the Seal GitHub Action.
Last updated