ARCHITECTURE
Security before the first line of code
The first architecture review is the cheapest place to find a security gap. Three decisions to make before the first endpoint exists.
Airintha Team · Engineering and security
3 min read

A startup's first architecture review is the cheapest place to find a security gap. Once the product is live, every fix touches real users, real data and a release calendar that is already full.
01Three decisions to make early
- Who can see what. Write down roles, tenants and admin access before the first endpoint exists. Retrofitting permissions usually means rewriting queries.
- Where secrets live. Keep credentials out of the repository and out of build logs. Pick a secret store on day one, even if it is only the one your cloud provider already runs.
- What you log. Record sign-ins and permission changes. Keep personal data out of logs, because logs get copied to places nobody reviews.
02A threat model on one page
List the assets worth protecting, the people who might want them, and the routes they would likely take. One page is enough for an early product. Review it again before launch and after every new third-party integration.
03What this costs
Early decisions take an afternoon. The same decisions after launch take a sprint, plus the uncomfortable conversation about what happened in the meantime. Writing them down first is the cheaper path.


