Make hardened containers the default with Cloudsmith and RapidFort

Cut vulnerability exposure by up to 99.9% with RapidFort, then see which teams are running the new near-zero-CVE images. Cloudsmith serves RapidFort's hardened images as a prioritized upstream, and RapidFort scans the images stored in your Cloudsmith repositories.

RapidFort hardens the images. Cloudsmith controls how teams get them.

Cloudsmith is the registry and control point for every container image your teams build or pull. RapidFort supplies the hardened content that flows through it.
    Upstream prioritization
    Select RapidFort's hardened images in the Cloudsmith app and set them as a prioritized upstream. Developers and build pipelines pull the hardened version first, ahead of public registries, so the safer image wins by default instead of relying on each developer to choose it.
    Image caching
    Cloudsmith caches each RapidFort image your teams request in your repository and serves the cached copy each time. It's warm, so downloads are faster, and there's less chance of tampering.
    Registry scanning
    Add Cloudsmith as a registry source in the RapidFort app. RapidFort runs regular scans of the images stored in your Cloudsmith repositories and recommends its curated, near-zero-CVE images as replacements. You see where unhardened images are pulled and get a clear path to replace them
    Your current base images
    RapidFort hardens the base images and libraries you already run, such as Ubuntu, RHEL, Debian, and Alpine, with no migration to a new base image family. Teams keep the images they know, so rollout is faster and nothing gets rebuilt on a new base.

Fewer CVEs with proof that your teams are pulling hardened images

Hardened images reduce risk when teams run them. Pairing RapidFort's software supply chain security with Cloudsmith's governed distribution puts the hardened version in front of your teams and shows you who is using it.
Without CloudsmithRapidFort profiles which binaries, libraries, and OS components execute in production, then removes the rest. The result is a curated, near-zero-CVE image.
With CloudsmithCloudsmith sets those curated images as a prioritized upstream, so your developers and build pipelines pull the hardened version first, ahead of public registries.
Without CloudsmithRapidFort scans container images, traces their vulnerabilities to the source, and recommends a curated replacement.
With CloudsmithAdd Cloudsmith as a registry source in RapidFort, and the scans cover the images stored in your Cloudsmith repositories.
Without CloudsmithRapidFort hardens the base images and libraries you already run, such as Ubuntu, RHEL, Debian, and Alpine.
With CloudsmithCloudsmith caches the hardened images your teams request and serves them from one registry. Access controls and policy as code apply, and every pull is logged, so security teams can see which teams use them.

Frequently asked questions

  1. The integration runs both ways. Cloudsmith serves RapidFort's hardened, near-zero-CVE images as a prioritized upstream and caches the images your teams request. RapidFort scans the images stored in your Cloudsmith registry.

  2. No. You keep your current base images. RapidFort hardens the base images and libraries you already run, such as Ubuntu, RHEL, Debian, or Alpine, so there is no move to a new image family.

  3. In your Cloudsmith repository, open the Sources tab, choose RapidFort Curated Images under Hardened images, and set its priority. To scan your registry, add Cloudsmith as a registry source in the RapidFort app.

  4. Yes. Cloudsmith lets you set the order of your upstream sources, so RapidFort's curated images are retrieved first when available.

  5. Cloudsmith records every artifact pull, including which image was requested, which repository it came from, and which team initiated the request.

  6. Yes. RapidFort offers a free starter bundle of its curated images.

  7. Yes. RapidFort Curated Libraries are available as a prioritized upstream in Cloudsmith, for npm and Maven today. RapidFort holds new package versions through a mandatory cooldown period (14 days by default) and independently validates its curated libraries for malware and tampering.

  8. Platform and security teams that want to keep their current base images and pull near-zero-CVE versions of them from one registry.

Start shipping with confidence

Pair RapidFort's near-zero CVE images and libraries with Cloudsmith's caching, policy, and distribution to keep every release trusted and compliant.