Threat modelling

A threat model that shows its working

Describe the system in prose. Netras extracts the components, the data flows and the trust boundaries, then works STRIDE, PASTA, DREAD and NIST CSF over that model. Every claim in the report is either established by your description or marked as an open question.

Book a demo Platform overview
STRIDE · PASTA · DREADNIST CSF maturityPublishable report
A Netras threat model: overall DREAD risk, the methodologies applied, threats identified and the share of claims traced back to the description
What it does

Four methodologies over one model

The model is built once from your description. Each methodology then asks its own questions of that same model, which is why the answers do not contradict one another.

The architecture, extracted

Components, data flows, trust boundaries and entry points, pulled from prose and shown back to you as a diagram you can correct before anything is scored.

STRIDE per element

Spoofing, tampering, repudiation, information disclosure, denial of service and elevation, raised against the elements they can actually apply to.

PASTA, all seven stages

From business objectives through to attack modelling and risk analysis, with the weaknesses it asserts downgraded where your description does not support them.

DREAD scoring

Damage, reproducibility, exploitability, affected users and discoverability, scored so the ranking separates threats rather than putting everything at nine.

Attack paths from the graph

A route is a chain through real data flows. A path cannot invent a door that your architecture does not have, which is the usual failure of generated threat models.

NIST CSF maturity

Identify, protect, detect, respond and recover, scored against the description with the gaps under each function stated as the questions that would settle them.

A published Netras threat model, with its methodologies and risk score
The report

Twenty sections an auditor can follow

The deliverable is a report, not a screen. It carries the diagram, the threats, the attack paths, the blast radius, the business-logic coverage, the security debt, the compliance exposure and a sequence to do the work in, each numbered and cross-referenced.

  • Blast radius separating what is reachable from what is gated by a boundary or an authenticated call
  • Every recommendation traced to the threat or open question that justifies it
  • Assumptions marked as assumptions, so a reader knows what the model did not establish
  • Published as PDF from the same record the screens read, so the two cannot disagree
Questions people actually ask

Before you book anything

Do we have to draw a diagram?

No. You write a description of the system and the platform produces the diagram. You can correct it, and the correction feeds the model rather than sitting beside it.

Is the analysis generated by a model?

The extraction and the first pass are. Everything published is then checked against your description: a claim the description does not support is weakened or turned into an open question, never strengthened.

Can we re-run it when the architecture changes?

Yes, and the previous version is kept. A regenerated model does not quietly discard the recommendations somebody had already accepted.

See it against your own estate

A working demo with your data shape, not a slide deck.

Book a demo Back to overview