← Field notesSecurity

Threat modelling before the first line of code

Why we map the attack surface during discovery — and how it changes what we build.

Orbyte · June 10, 2026 · 6 min read


Security is cheapest when it is a design input, not a final audit. We threat-model during discovery so the architecture itself removes whole classes of risk.

Start from the data

We list the data the system holds, classify it, and ask who should ever touch it. Least privilege falls out of that exercise naturally.

If a component never needs the data, it should never be able to read it.

Make it concrete

Each threat becomes a control with an owner and a test. Nothing stays abstract.

Have a project like this?

Tell us what you want to build. We reply within one business day.