Supply chain security

Control over what your software is built from — and proof that the package at the client came out of your process.

We address the technical requirements of
CRANIS2UKSC
The path of a package to the client
  1. New dependencychecked before it is added
  2. Buildfrom pinned versions
  3. SBOMwith every release
  4. Signaturesigned artifact
  5. Provenancerecord of what was built, and where
  6. At the clientindependent verification

Your client checks where the package came from without asking you for a statement.

How it looks today

Most of your product is code you didn't write.

Most of your product is someone else's code. No one has to attack you directly — a library or a tool you use is enough. One compromised element reaches everyone who downloads it, along with the update.

  1. Open-source library
  2. Update
  3. Your build
  4. Release
  5. Every client

What we do

We define the scope after an assessment — starting with the element that lowers your risk fastest.

You know what your product is built from.

We generate the bill of materials automatically with every release, not by hand once a year — so the question "do you use this library" stops being a week-long project. We sign artifacts so the client can independently verify they received what came out of your process. New dependencies pass a check before they enter the project, because the cheapest moment to reject a risky library is before it is added. We arrange the whole thing to close the technical layer of the CRA requirements.

Four stages

Each stage leaves you with a concrete result, not meeting notes.

  1. 01

    We create a bill of materials

    An SBOM generated automatically with every release, not once a year by hand.

    ResultAn SBOM generated automatically with every release

  2. 02

    We sign artifacts

    The client can verify they received what came out of your process.

    ResultSigned artifacts your client can verify on their own

  3. 03

    We control dependencies

    A new library passes a check before it enters the project.

    ResultRules for accepting new dependencies, built into code review

  4. 04

    We prepare for CRA

    Technical documentation and the ability to respond to a vulnerability report.

    ResultTechnical documentation and a vulnerability reporting procedure for the CRA

What you get in practice

A signature on every release

Your client knows they received exactly what left your process.

Every software release carries a digital signature the client can check on their own.

Bill of materials (SBOM)

“Do you use this library?” becomes a single search.

Every release comes with a list of all the libraries it is made of.

Vulnerability reporting (CRA)

Templates and roles are agreed before the first report is due.

Everyone knows who reports a vulnerability, to whom, by when and using which template.

What stays with you

You answer "do you use this library" in a minute

The client can independently verify the package's origin

The bill-of-materials requirement is closed technically

Frequently asked questions

How long does it take?+

We define the scope after a call and an assessment. Smaller engagements close in a few weeks; larger ones we split into stages, so the result is visible after the first.

Do we have to give you access to the code?+

Usually not to all of it. In most cases access to the build pipeline configuration and organization settings is enough. We define the scope in writing before we start.

Does our team have to get involved?+

Yes, but not full time. We need contact with someone who knows the system, and a review of our changes. The rest is on us.

Is this enough for CRA compliance?+

Not entirely. We cover the technical layer: the bill of materials, release signatures, artifact provenance and the vulnerability reporting process. Full CRA compliance also requires organisational and legal measures, and our work does not replace a legal opinion or a formal audit.

What if we already have tools?+

We plug into what already works for you. Replacing a tool is the most expensive and least often necessary way to improve security.

Do we become dependent on you?+

No. We work with standards and tools your team knows or will quickly learn. Everything is documented and handed over.

Won't this slow down releases?+

We wire controls so they run in the background. If one starts blocking work, we tune it or move it to a different point in the process.

Let's find where risk
enters your delivery process

We reply within 24h on business days