Test the design on paper
Security Architecture
Review
We review how your networks, identity, data flows and cloud connections fit together, then judge whether that design holds against the attacks you are likely to face. You get a clear verdict on where the architecture is sound, where one failure spreads, and what to change before the next build.
Threats first, diagrams second
Built to hold
against real threats.
We start with a threat model built from MITRE ATT&CK techniques used against your sector, then read your architecture against it. Zero trust principles from NIST SP 800-207 and the CIS Controls v8.1 give the yardstick. We interview the people who built it and check diagrams against live configuration.
What we examine
Threat model
Decide what the design has to withstand.
A short list of realistic threats and attacker techniques that every later finding is measured against.
- Business critical systems and data named with their owners.
- Likely attackers and their ATT&CK techniques mapped to your environment.
- Existing trust assumptions written down so they can be tested.
Network design
Find where one compromise spreads freely.
Trust zones and the flat areas between them, with the routes an attacker would use to cross.
- Zones, segments and firewall placement reviewed against data sensitivity.
- Remote access, VPN and management networks examined.
- Controls on internal east west traffic compared to what the diagrams claim.
Identity design
Check that identity holds the architecture together.
How authentication and authorization work across systems, and the single accounts or trusts that would undo it.
- Directory structure, federation and trust relationships reviewed.
- Administrative separation between tiers checked.
- Service accounts and machine identities traced to what they reach.
Data flows
Follow sensitive data from entry to deletion.
A data flow view showing where sensitive data is stored, copied and exposed, and which controls guard each step.
- Flows of regulated data drawn with the systems they cross.
- Encryption in transit and at rest checked at each boundary.
- Third party and SaaS integrations traced.
Cloud & third parties
Review the connections you did not build yourself.
Every external connection rated by how much trust it carries and what it could reach if compromised.
- Links between cloud and on premises systems reviewed, including hybrid identity.
- Vendor and managed service provider access paths mapped.
- API gateways and integration platforms examined.
Recovery & visibility
Confirm you can see an attack and recover from it.
Gaps in logging coverage and recovery design, including backups an attacker could reach.
- Log sources compared to the techniques in the threat model.
- Backup isolation and restore paths reviewed.
- Single points of failure in security tooling identified.
Key benefits
Fix design flaws before they cost a rebuild.
You get a plain answer on whether the architecture holds against your threats, with the reasoning shown, so leadership can decide where to invest instead of reading a list of controls.
Every weakness is mapped to the MITRE ATT&CK techniques that would use it. Your team sees which design choices matter against the attackers you face and which are theoretical.
A design flaw found before a build or migration costs a drawing change. Found after, it costs a project. We review plans and live systems alike, so you can bring us in at either point.
What you get
What lands on
your desk.
Written for the architects who will change the design and the leaders who approve the cost.
The document
The architecture review report
The threat model, a verdict by area, annotated diagrams showing weak points and attack routes, and recommended design changes ranked by the risk they remove and the effort they take.
The working file
The design decisions log
Each recommendation with the threat it answers, the systems it touches, an owner and a status. Architects use it to carry changes through design review and change control.
The conversation
The architecture workshop
A working session with your architects and engineering leads. We walk the attack routes on your own diagrams and agree which changes go into the next roadmap.
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 review
What architects
ask first.
Straight answers from the practitioners who do the work. If yours is not here, ask us directly.
No. An architecture review reads the design and checks it against the live configuration. It does not exploit anything. It often shows where a penetration test would be most useful, and we can scope one to prove the highest risk findings.
Current diagrams, even rough ones, read access to firewall and cloud configuration, and time with the people who designed and run the environment. If diagrams are missing or out of date, we draw them as part of the work.
Yes, and that is often the cheapest moment. We review the proposed design and the threat model behind it, and the recommendations go into the build plan instead of a remediation list.
NIST SP 800-207 for zero trust principles, the CIS Controls v8.1 for safeguards, and MITRE ATT&CK for attacker behavior. If you are held to PCI DSS, CMMC or HIPAA, we note where the design affects compliance scope.
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.








