Check the design first
Application Security
Architecture Review
We review the design of an application before it is built or rebuilt, and give you a verdict on whether it holds. Trust boundaries, identity, data protection, tenant isolation and third party dependencies are tested on paper, where a flaw costs a meeting to fix instead of a rewrite.
A verdict before the build
Will the design
hold up?
We work from your diagrams, design documents and conversations with the architects, and threat model the design with STRIDE. Each area is judged against OWASP ASVS and NIST SP 800-218 (SSDF). The verdict for each area is plain: holds, holds with changes, or needs rework.
What we examine
Trust boundaries
Where data crosses from one level of trust to another.
A data flow diagram with every trust boundary marked and the threats at each one listed.
- Entry points, internal services and external calls traced.
- STRIDE applied at every boundary crossing.
- Assumptions about network position challenged.
Identity & access
How users and services prove who they are and what they may do.
A judgement on whether authentication and authorization decisions are made in the right place, and made once.
- Single sign on, session and token design reviewed.
- Authorization enforced on the server for every action.
- Service to service credentials and their scope.
Data protection
How sensitive data is stored, moved and kept.
A map of sensitive data with the controls that protect it at rest and in transit, and where they fall short.
- Encryption choices and secrets management reviewed.
- Retention and deletion paths checked against your obligations.
- Logs and backups examined for data that should not be there.
Tenant isolation
Whether one customer can ever reach another's data.
A verdict on tenant separation at the data, compute and identity layers.
- Tenant scoping in queries, storage and caches.
- Shared components that could leak across tenants.
- Admin and support tooling that crosses tenant lines.
Third parties
What you inherit from the services and packages you depend on.
External dependencies ranked by what they can reach and what happens if one is compromised.
- SaaS integrations and the permissions granted to them.
- Open source dependencies and how they are updated.
- AI models and APIs, checked against the OWASP Top 10 for LLM Applications where used.
Logging & failure
Whether the design will show you an attack and fail safely.
Named gaps in audit logging, alerting hooks and error handling, with the design change for each.
- Security events the application must record.
- Failure modes that default to open instead of closed.
- Rate limits and abuse cases for public functions.
Key benefits
Fix it on paper, not in production.
A design flaw found before code is written costs a conversation. Found after launch, it can mean a rewrite. The review puts the hard questions where changes are still easy to make.
Each area ends in a decision your architects can act on, with the reasoning attached. You know what must change before the build starts and what can safely wait.
The review is done by a senior practitioner who also tests applications, so the risks raised are ones attackers use, and purely theoretical concerns stay off the list.
What you get
What lands on
your desk.
Three handoffs that architects can build from and leaders can sign off against.
The document
The architecture review
The verdict for each area, the threat model and annotated data flow diagram, and every design change we recommend, ranked by risk and by how hard it gets to change later.
The working file
The design change tracker
One row per recommended change with area, risk, the decision needed, owner and status. It moves straight into your design backlog and travels with the project.
The conversation
The design session
A working session with your architects and the practitioner who did the review. We walk through each verdict, test alternatives on the whiteboard and agree what changes before the build.
Client case studies
Real engagements.
Documented outcomes.
In their words
"ForgePath has become a trusted security partner for YHB. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
In their words
"ForgePath has become a trusted security partner for YHB. Beyond helping us comply with FTC Safeguards requirements, they provide the governance, oversight, and guidance we rely on to protect our firm and our clients’ data. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
Trusted by industry leaders.
Before the build
When to
bring us in.
Straight answers from the practitioners who do the work. If yours is not here, ask us directly.
Once the design is clear enough to draw but before most of the code is written, usually after the architecture is proposed and before the first major build. A rewrite or a move to a new platform is another good moment.
Architecture diagrams, design documents or an honest whiteboard sketch, plus time with the architects and lead developers who made the decisions. Rough material is fine. Part of the review is drawing what is missing.
Yes. For a live application, we compare the documented design with how it was actually built, and can pair the review with a penetration test or secure code review to confirm what we find on paper.
No, though it helps with one. Results are tied to OWASP ASVS and NIST SP 800-218, which customers and auditors recognize. The goal is a design that holds against attackers, with evidence you can reuse.
Ready?
Bring us
the problem.
One conversation with a senior practitioner who has carried this responsibility before. We will tell you what we would do, and whether it is us.








