Start a project

Service

Secure by design — and able to prove it

Threat modelling, supply-chain security and secure-development practice that engineers actually follow, plus the evidence customers and regulators now expect.

A good fit if…

  • You sell software or connected products into the EU and need to prepare for the Cyber Resilience Act.
  • Enterprise customers send security questionnaires you struggle to answer.
  • A pen test found issues and you want them fixed at the root, not patched.

What we do

Threat modelling

Map assets, attack surfaces and abuse cases with your engineers, not just for them.

Supply-chain security

SBOMs, dependency policy, signed builds and provenance for what you ship.

Secure SDLC

Code review checklists, secrets handling, SAST and fuzzing that fit your delivery flow.

Vulnerability handling

Intake, triage, disclosure and patch processes — including CRA reporting readiness.

Remediation

Fix the findings that matter, in code, with tests so they stay fixed.

Evidence

Technical documentation and records that stand up to customer and regulatory scrutiny.

What you get

  • Threat model and risk register
  • SBOM pipeline
  • Vulnerability-handling process
  • CRA gap analysis and plan

How an engagement runs

  1. Diagnose (1–2 weeks). We read the code and the data, and agree the baseline and the number we expect to move.
  2. Prove (3–5 weeks). A thin, real slice in production, measured against that baseline.
  3. Scale and hand over. Widen the change with your engineers, then leave docs, runbooks and a team that owns it.