Skip to main content

What are you looking for?

Explore our services and discover how we can help you achieve your goals

Client Workspace

Threat modelling workshop with STRIDE: agenda and output template for a mid-market product

A STRIDE threat modelling workshop for a mid-market product is a half-day session where the builders of one feature draw its data flows, ask six threat questions at each trust boundary and leave with one page of owned, ticketed threats. Netbase treats this as security by design, done before coding.

Book a solution review See the related solution

By Netbase Delivery and Quality Desk · Reviewed by David (CEO) · Updated · 11 min read

star

This guide is for CTOs, product owners and tech leads of a SaaS product, portal, ERP or store with a small team and no security department. It gives the attendee list, a timed agenda, a decision matrix for STRIDE and the output template. If you want the workshop, the follow-up testing and the fixes done with you, see application security assurance.

In this guide

What does a STRIDE workshop give a mid-market team?

A STRIDE workshop gives a team a shared picture of how one part of the product can be attacked, and a short list of design changes to make before release. It replaces a vague worry about security with named threats, each with an owner, a ticket and a decision.

STRIDE is a set of six threat categories. The Microsoft Threat Modeling Tool page on threats describes them as Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service and Elevation of Privilege, and says the model exists to help teams formulate pointed questions. For a small team, six questions are easy to remember.

The workshop sits inside four broader questions. The Threat Modeling Manifesto asks what are we working on, what can go wrong, what are we going to do about it, and did we do a good enough job. The agenda below gives each question a time slot.

Who should attend, and what should they prepare?

Five roles are enough for a mid-market product. Keep the room under eight people.

  • Product owner. Knows which data and actions matter to the business and can accept a risk.
  • Tech lead or architect. Draws the data flow diagram and knows the trust boundaries.
  • Two engineers who will build the feature. They know the real code paths and will own most tickets.
  • QA engineer. Turns threats into test cases later.
  • Facilitator. Keeps time, asks the STRIDE questions and writes the output. An outside security specialist helps most in this seat for a first workshop.

Preparation takes about an hour from the tech lead: a draft data flow diagram of the feature, a list of the data it stores and who may see it, and the roles that use it. The OWASP Threat Modeling Cheat Sheet lists what the model must show: trust boundaries, data flows, data stores, processes and external entities.

Which STRIDE question fits which part of the diagram?

Not every category applies to every element. Asking all six questions of every box is the most common reason a first workshop runs out of time. Use this matrix to ask only the questions that fit.

STRIDE category (property it breaks) Ask it of Question for a mid-market product Usual control
Spoofing (authentication) Users, external systems, processes Can someone act as another user, tenant or service? MFA, signed tokens, verified webhooks
Tampering (integrity) Data flows, data stores, processes Can someone change data in transit, in storage or in a request we trust? TLS, server-side validation, integrity checks
Repudiation (accounting) Users, processes, logs Can someone deny an action because we cannot prove who did it? Audit log with user, time and object
Information disclosure (confidentiality) Data flows, data stores, processes Can someone read data, files or errors they should not see? Record-level access checks, encryption, clean errors
Denial of service (availability) Processes, data flows, data stores Can one user or bot make this unavailable for others? Rate limits, quotas, queue limits
Elevation of privilege (authorization) Processes Can a normal user reach an admin action or another tenant's data? Deny by default, server-side role checks

Start with the arrows that cross a trust boundary, such as browser to API, API to a third-party service or one tenant's data to a shared store. Then cover data stores that hold personal or payment data. Internal calls between trusted services come last, if time allows.

How do you run the workshop?

  1. Scope one feature or product slice (15 minutes)

    The product owner states what is being built, who uses it and which data matters most. Write the scope at the top of the output; anything outside it waits for another session.

  2. Validate the data flow diagram (30 minutes)

    The tech lead walks through the draft; the room corrects it and marks every trust boundary.

  3. Run the STRIDE pass at the boundaries (75 minutes)

    For each boundary crossing and sensitive store, the facilitator asks the matching questions from the matrix. Write every threat as one sentence: who, does what, to which element, with what impact. No debate about fixes yet.

  4. Rank the threats (20 minutes)

    Rate each threat high, medium or low by impact and how easy it is to exploit. Keep the scale simple.

  5. Decide a response for each high and medium threat (30 minutes)

    The OWASP cheat sheet names four responses: mitigate, eliminate, transfer or accept. Every decision gets an owner; every mitigation gets a ticket; every accepted risk gets the product owner's name.

  6. Close with the fourth question (10 minutes)

    Ask whether the model is good enough to build on, what was left out of scope, and which change will trigger the next review.

That is about three hours with a break, or two sessions in the same week.

What should the output template contain?

The output is one page that an engineer can act on and an auditor can read. A photo of a whiteboard is not an output, because nobody owns a photo.

  • Scope and assumptions

    What it holds
    The feature, the version of the diagram, what is out of scope, assumptions such as "the identity provider is trusted"
    Owner
    Tech lead
  • Data flow diagram

    What it holds
    The validated diagram with trust boundaries marked
    Owner
    Tech lead
  • Threat table

    What it holds
    ID, element, STRIDE category, threat sentence, rank, response, owner, ticket
    Owner
    Facilitator, then each owner
  • Accepted risks

    What it holds
    Each accepted threat, the reason and the name of the person who accepted it
    Owner
    Product owner
  • Test and review hooks

    What it holds
    Which threats become test cases, which need a penetration test, what change triggers a new session
    Owner
    QA engineer

Keep the template in the repository next to the design, not in a slide deck. Then a change to the design shows up next to the threats it affects, and code reviewers can check the OWASP Top 10 review prompts against the threat table.

When is a STRIDE workshop the wrong next step?

A STRIDE workshop is the wrong next step when the product has no basic hygiene yet: no dependency scanning, no access checks on existing endpoints, no backups. Fix those first; a workshop will only list threats the team already knows. The secure development lifecycle guide gives the order in which to add controls.

It is also wrong for a small, low-risk change, such as a new report on data the user can already see. And it is wrong as a one-off before an audit: a model nobody updates describes last year's product. For a large existing system, model one high-risk slice, such as login and billing, rather than the whole product.

Where AI fits

AI helps with the preparation and the paperwork, not with the judgement. A model can draft a first data flow description from architecture notes, suggest STRIDE threats per element as a starting list, turn agreed threats into ticket text and test case outlines, and flag design changes that should trigger a new review. Engineers and the product owner still decide which threats are real, rank them and accept risks, because a plausible but wrong threat list gives false comfort.

Netbase works with the major commercial and open-source AI tools and models, chosen per project, and runs AI-assisted engineering under human review.

What delivery record exists, and what does not

Netbase's published security practices are secure code review and version control, TLS in transit and AES at rest, role-based access control, MFA for admin dashboards, vulnerability scanning and penetration testing, and disaster recovery; NDAs, data processing agreements and SLAs are available on request. Security by design is part of how Netbase delivers its own projects.

Netbase holds ISO 27001 certification and a SOC 2 Type II attestation for its own operations. These describe how Netbase works; they do not certify a client's application or its threat model.

Delivery follows a six-step lifecycle from discovery and architecture planning to ongoing support, with weekly reviews and a named project manager, which is where open threats and accepted risks are reviewed. Netbase also works as offshore development partner on a multi-tenant cloud ERP for a US client, the kind of product where tenant isolation is the first trust boundary a workshop has to cover.

Most Netbase projects are delivered on fixed-price contracts. No Netbase record publishes threat counts, workshop durations or before-and-after results, and none is offered here as proof that the agenda works.

Alternatives: who runs the workshop, and how to choose

There are three common ways to run threat modelling in a mid-market team.

  • The team runs it alone with this template. Best when a tech lead has some security depth and the product is not regulated. Risk: the team misses threats it has never seen, and the model fades after the first session.
  • A security champion facilitates for each team. Best when one engineer can own the practice across features. Risk: the champion becomes a bottleneck.
  • An outside partner facilitates the first workshops. Best for a first session, a regulated product, or before a customer security review. Ask who writes the output, who owns the tickets and how fixes are verified. A penetration test later checks whether the mitigations hold.

Choose by three criteria: who can tell a real threat from a theoretical one in your product, who will keep the model current when the design changes, and who will own the accepted risks a year from now.

Limits of this guide

  • The agenda fits one feature or product slice of a web or business application, not firmware, hardware or machine learning models.
  • STRIDE covers security threats; privacy threats need a separate pass, for example with a privacy framework.
  • A threat model finds design issues; it does not replace code review, scanning or testing.

Plan the next step with a Netbase consultant

Frequently asked questions

About three hours for one feature or product slice, including scoping, the diagram, the STRIDE pass, ranking and decisions. If the team cannot give that in one block, split it into two sessions in the same week, before the design is final.

A product owner, a tech lead or architect, two engineers who will build the feature, a QA engineer and a facilitator. Keep the group under eight people so that everyone takes part in the analysis.

No, but an experienced facilitator helps in the first workshops. STRIDE gives non-specialists six questions to ask, and a specialist adds the attack patterns a team has not seen before.

Update it whenever a change adds a data flow, a role, a third-party service or a new kind of sensitive data, and review open threats at regular delivery reviews. A model that is never updated describes an old product.

Next step

If you want a first STRIDE workshop run on your product by the team that will also test and fix what it finds, book a solution review.

Application security assurance for web, SaaS and AI features Application security assurance for web, SaaS and AI features

Netbase provides application security testing for product and engineering leaders to find and fix vulnerabilities before release, including in AI features. We review code with AI-assisted triage, scan dependencies and test running applications, then rank findings and retest fixes. Netbase's own alignment with ISO 27001 and SOC 2 Type II covers Netbase's operations, never your application.

Learn More
line
AI-assisted QA and software testing that run inside delivery AI-assisted QA and software testing that run inside delivery

Netbase provides software testing and QA services for product and commerce teams to release often without breaking what customers use. QA runs inside delivery, not after it: acceptance criteria, automated regression with AI-generated test drafts, performance budgets and release readiness checks. Page speed shows the result: USticker's page load fell 21%, and PrintLeo's improved 35%.

Learn More
line
SaaS product accelerator: launch an AI-ready SaaS on proven Netbase modules SaaS product accelerator: launch an AI-ready SaaS on proven Netbase modules

A SaaS product accelerator is a set of reusable Netbase modules for accounts, billing, roles and integrations that helps founders and product teams launch subscription software faster, with room for in-product AI from the first release. Reusing these modules can shorten development time, and the approach is proven on Printcart, Netbase's own web-to-print SaaS.

Learn More
line

Work with Netbase remotely

Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.

Contact Netbase

Discuss a project

Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.
Project enquiries

project@netbasejsc.com

WhatsApp

+84 937 869 689

Office address

91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam

Get in touch

Tell us what you want to build, modernize, or operate.

Tell us what you want to build, modernize, or operate.

Contact Netbase