article
Security review belongs in product design
Late security review finds expensive facts after customers, contracts and architecture have hardened.
Emil Shirokikh · Published August 31, 2026 · Updated September 23, 2026 · 2 min read
Abstract
Security choices affect identity, data models, deployment and support. Reviewing them after implementation guarantees friction and encourages waivers.
Review irreversible choices early
Identity, tenancy, data retention and update design become expensive to change after contracts and implementation harden.
Design review
At concept stage, diagram assets, actors, trust boundaries and abuse cases. Put security acceptance criteria beside functional criteria and repeat the review at material changes.
Release gate
Keep independent release review, but stop using it as the first security conversation.
Challenge the conclusion
Final review remains essential. Earlier involvement makes that review more meaningful, not less independent.
Use this in a working session
Review the hardest-to-reverse architecture choice and one abuse case before approving implementation.
BELTO editorial analysis. It does not describe a client engagement or claim a commercial result.
References
2 sourcesAuthor
Emil ShirokikhFounder
Founder of Belto Inc. Writes on engineering, venture building and applied intelligence.
Related
Read next
Most AI pilots should be killed sooner
The polite fiction around enterprise AI is that every pilot teaches something. Many teach only that nobody defined the decision, owner or failure cost.
AI agents need boundaries, not personalities
The market is decorating automation with human traits while neglecting permissions, reversibility and evidence.
A computer-vision demo is not a system
Benchmark accuracy says little about glare, drift, maintenance, latency or the operator who must act on an alert.