Show HN: SecureBuild – Zero-CVE Images That Pay OSS Projects(securebuild.com)
40 pointsby grantlmiller7 days ago7 comments
  • jenny917 days ago
    The intersection of entities whose security is based around "responding to every CVE quickly" and the entities that care about supporting OSS projects has measure zero.
    • grantlmiller7 days ago
      well... our core users are ISVs (who distribute commercial software into enterprise controlled, self-hosted environments... think big banks, governments, tech companies). They care about supporting OSS (almost 1/2 of them are open core themselves) and their customers mandate that they care about closing out CVEs quickly in the software they're consuming from them.
  • 7 days ago
    undefined
  • westwater6 days ago
    What's the process to add new images?

    I assume this is limited to CVEs in the underlying layers, and adding in the latest of the primary package. Given that how/are you testing the images after you fix the CVEs?

    • marcc6 days ago
      Adding images involves us creating a new package (APK) in our APK repo. This is done by creating a melange build config (https://github.com/chainguard-dev/melange). The melange config defines some basic tests. It's not comprehensive, but generally validates that the binary produced is functional.

      When we build the OCI image, we validate it via some custom tests that we've written. We have identified the canonical image (i.e. DockerHub, GHCR, etc), and we confirm that our image has the same entrypoint, args, env that the canonical image has. Then we have some generated scenarios we run the OCI image through to make sure it functions the same as the canonical image runs.

      For example, we have Postgres in the catalog today. When we rebuild, we have some tests that run with various configurations of PG_DATABASE/PG_PASSWORD, etc env vars. We run these with our image and with index.docker.io/library/postgres, and expect to see the same output with both.

  • sheepybloke3 days ago
    How does this compare with something like IronBank? Looks like that could be a great partnership!
  • cube007 days ago
    > New SecureBuilds are created whenever upstream CVEs are available, with a 6-day SLA for critical vulnerabilities.

    Aren't most SecOps pushing 48 hours as the absolute limit for critical vulns or are ours just being extra pushy?

    • marcc7 days ago
      We often deliver in way less than 6 days but sometimes the dependency tree is deep for a patch.

      I've seen most auditors mandate 30 days for Critical, but you clearly want to move a lot quicker than that.

      • grantlmiller7 days ago
        the goal is going to be 6 hours!
      • mike_d7 days ago
        > I've seen most auditors mandate 30 days for Critical, but you clearly want to move a lot quicker than that.

        You seem to fundamentally not understand security. A proper security program should never be driven by an auditors expectations or even used as a reasonable guideline.

        Don't track CVEs and SLAs in days. You need to have patches out before active exploitation in the wild begins, that is the only metric that matters. Go talk to Greynoise about how to get that data.

        • grantlmiller7 days ago
          We’d love for this to be true... most images fill up with CVEs so fast in dependencies, we’re providing minimal images (much less surface area) and have the automation to rebuild the entire dependency graph at least daily, if not multiple times per day.

          Hopefully everyone will run a "proper security program" someday!

          • mike_d7 days ago
            It can be true for you if your correct your thinking on the problem.

            CVEs are basically just bugs that are not triggered by normal operation. If you race to "fix" them all, you are going to drown (as you are discovering).

            Focus on your solution for tracking actively exploited vulnerabilities and a prioritization system and you'll greatly simplify the problem while better serving your customers.

  • siggy7 days ago
    thanks for sharing. what's the onboarding process look like? if i'm maintaining my own Dockerfiles today, do you or I evaluate and port those to SecureBuild/Wolfi?
    • marcc7 days ago
      We work together on it. Assuming you have a build process and dockerfile (we all do), generally our team can get you listed in the catalog quickly.

      It's not too much work since we built on an existing set of tools (melange & apko). I've actually found that putting a Dockerfile into ChatGPT generates a really good first iteration.

  • dhorthy7 days ago
    this looks cool - your homepage video should open with what it is though!
    • grantlmiller7 days ago
      thanks! say more about what you mean... you're saying instead of: Secure, Sustainable Open Source Partner with SecureBuild to offer secure, vulnerability-free builds of your open source project while generating recurring software revenue, no support contracts required.

      we should say something different?

      • justinludwig6 days ago
        More about what you actually do -- I'd suggest something like "Secure, Sustainable Open Source: We partner with open source projects to monitor their upstream dependencies for security fixes, and automatically rebuild and distribute our partners' projects with those fixes. Our partners don't have to change what they do, and we share 70% of our subscription revenue with them."

        Also:

        > New SecureBuilds are created whenever upstream CVEs are available, with a 6-day SLA for critical vulnerabilities.

        Surely this should be "New SecureBuilds are created whenever upstream fixes for CVEs are available" -- you cut new builds for the fixes, not the bugs, no?

        • grantlmiller6 days ago
          i like it! and yes, that is correct :)