Skip to content
Solvex Space
Web3 & EmergingFixed price — $1,499Advisory engagement

Threat Modelling Workshop

Understand your threats before you build defences. In a collaborative workshop, we work with your team to map what could go wrong, who would attack you and how, and where to focus — turning security from guesswork into strategy.

Verified Solvex Specialist

Verified by Solvex

Direct specialist contact for Solvex engagements

What this means. An authorized Solvex administrator registered and approved this exact public identity. What it does not. Solvex has not inspected the account on the platform, and this is not the platform's own verification.

Solvex specialists never ask for your passwords, recovery phrases, one-time codes, or payments to a personal account. Work, scope and invoices are agreed in writing through the official channels on this site.

What's covered

  • Facilitated threat-modelling session with your team
  • System decomposition and data-flow mapping
  • Threat identification (STRIDE or attack-tree methods)
  • Risk prioritisation and control mapping
  • Actionable mitigation planning
  • Knowledge transfer so your team can continue

What you receive

  • Documented threat model
  • Prioritised threats and risks
  • Recommended controls and mitigations
  • Workshop artefacts and diagrams
  • Guidance for ongoing threat modelling

Evidence and reporting

How the work is kept honest
  • Evidence, frozen at issuanceFindings tie to something observed. When the report is issued, the evidence behind it is frozen in the same transaction and cannot be edited afterwards.
  • A signed reportAn Ed25519 signature covers both the report content and the delivered file. Alter a byte of either and verification fails.
  • Written scope firstAdvisory work runs to a written scope agreed before it starts, so what you receive is what was agreed.

Anyone holding a Solvex report can verify it publicly without seeing its contents.

Our boundaries

What this engagement does not do, stated before it starts.

  • Advisory workshop — no live-system testing
  • Depends on the information shared in the session
  • Implementation of controls by your team
  • A model to maintain as the system evolves

How this engagement runs

  1. 01

    Intake

    Tell us the system, the goal and the constraints. If the work is not a good fit, we say so before anyone is invoiced.

  2. 02

    Scope and authorization

    Written scope and signed authorization before anything is touched. Security testing runs only against systems you own or are contractually entitled to have tested.

  3. 03

    Investigation or build

    Specialists matched to the work. Findings are proven by hand — scanner output is a lead, never a finding.

  4. 04

    Evidence

    Every finding ties to something observed. When a report is issued, its evidence is frozen in the same transaction, so what backed the report cannot change afterwards.

  5. 05

    Delivery

    A signed report: an Ed25519 signature over both the content and the file, with a short verification reference you can read down a phone.

  6. 06

    Verification and retest

    Anyone holding the report can verify it publicly without seeing its contents. Fixes are retested as part of the engagement — “fixed” means we confirmed it.

Questions we are asked

When should we run a threat model?
Ideally early — during design — when addressing a threat costs a decision rather than a rebuild. It's also valuable for existing systems facing new features or changing risk.
Who should attend?
A mix of engineering, architecture and product people who know the system. The workshop is collaborative — the best threat models come from the people who built and run the thing.
What's the lasting value?
Beyond the model itself, your team learns to think adversarially and can keep threat modelling future changes. The fixed price covers a focused workshop; larger programmes are quoted.