Skip to content
HACKTECH

Advisory & training

Threat modelling

Facilitated workshops that map how a system or feature could be attacked before it is built or shipped. We draw the data flows with your engineers, walk them with STRIDE, rank the threats by likelihood and impact, and turn the result into backlog items and test cases your team owns.

Best for
Teams designing a new product, a payment or identity flow, an AI feature or a major re-architecture, and early-stage companies not yet ready for a penetration test.
Duration
2 to 5 days per system, remote or on site
Standards
STRIDE; OWASP Threat Modeling; PASTA

What you receive

  • Data-flow diagrams with trust boundaries, agreed with your engineers
  • Ranked threat register with likelihood, impact and an owner for each threat
  • Mitigations written as backlog items and security test cases
  • Abuse cases written for your product's own flows, such as refunds, invitations and plan upgrades
  • The workshop format written down, so your team can run the next session on a new feature without us

Representative coverage

  • System decomposition: components, data stores, external dependencies and trust boundaries
  • STRIDE walkthrough for every element and data flow
  • Attacker-centric, risk-ranked analysis with PASTA for regulated or high-impact systems
  • Business-logic abuse: fraud, quota, workflow and privilege scenarios
  • Architecture review of authentication, authorisation, tenancy and secrets
  • Mapping each threat to the test that will prove its mitigation works

How the engagement runs

A 45-minute scoping call picks the system to model, then workshops with your engineers turn its design into a ranked threat register and backlog items your team owns.

  1. 45 minutes

    Scoping call

    We agree which system or feature to model, which of your engineers need to be in the room and whether the workshops run remotely or on site.

    Fixed quoteProposed datesWritten scope by email

  2. 2 to 5 days per system

    Workshops

    We draw the data flows and trust boundaries with your engineers, walk every element and flow with STRIDE, add PASTA for regulated or high-impact systems and work through abuse cases for your product's own flows.

    Data-flow diagramsAbuse cases

  3. Included

    Threat register and handover

    Each threat is ranked by likelihood and impact and given an owner, each mitigation becomes a backlog item with the security test that will prove it, and the workshop format is written down so your team can run the next session without us.

    Ranked threat registerBacklog itemsSecurity test casesWritten workshop format

Threat modelling workshops and secure-coding labs in which your engineers exploit, then fix, bugs like their own.

  • Hands-on workshops for engineers, run against a deliberately vulnerable copy of a codebase like yours. Developers exploit each bug before they fix it, so they have seen the attack their fix has to stop, and review real pull requests for the same bugs.

    Duration: 1 to 3 days on site or remote

Questions teams ask

We are pre-revenue. Is a penetration test worth it yet?

Often not yet. If you have no customers and no sensitive data, a threat modelling workshop on the product you are about to launch, plus the free secure-defaults checklist for new products in our knowledge hub, will do more for you than a penetration test, and the workshop leaves the first test a list of threats to check.

How quickly can you start?

We can usually hold the scoping call within two working days and start work within two weeks of a signed scope. If a deal deadline cannot wait that long, say so when you get in touch and we will give you the earliest date we can start. For an active incident, skip the scoping call and phone +972 52 613 9179.

Can you sign our NDA and security requirements?

Yes. We sign your NDA before the scoping call if you ask, and work under it for the whole engagement. Engagement data is encrypted at rest and destroyed when the engagement closes, or on a schedule you set. Send your supplier security requirements before the scoping call and we will tell you in writing which we meet.

Do you work outside Israel?

Yes. We test remotely for clients outside Israel. Israel is two hours ahead of UK time and one hour ahead of Central European time, so most of our working day overlaps yours. On-site work, such as internal network testing, physical assessments and training, is agreed on the scoping call.

All service questions

Scope it in one call

A 45-minute scoping call ends with a fixed quote and a proposed start date; the written scope follows by email.