06 Nov 2026 By CISO Consulting team 32 views 4 min read

SAMA CSF Network Segmentation Architecture Review Guide

Segmentation often passes policy review but fails architectural validation because the documents do not prove isolation. This guide sets out the four design decisions reviewers test and the three diagrams that evidence them.

Network architect reviewing a zoned network topology diagram on a large monitor in a quiet office.
In this article
  1. What reviewers are testing
  2. The four design decisions to document
  3. 1. Zone definitions
  4. 2. Access-control enforcement points
  5. 3. Data-flow justification
  6. 4. Monitoring placement
  7. The three diagrams that prove isolation
  8. Logical topology diagram
  9. VLAN-to-security-zone mapping
  10. Cross-zone traffic matrix
  11. A sensible order of work
  12. What changes for the organization
  13. How we help
  14. Before your review appointment

A SAMA CSF network segmentation architecture review tends to expose a specific weakness: the policy says production, UAT and DMZ are separated, but the design documents do not show how that separation is enforced. Policy review asks whether a rule exists. Architectural validation asks whether the design proves it. This article sets out four design decisions the documentation must record, and three diagram formats that make the isolation logic visible before the reviewer arrives.

What reviewers are testing

The SAMA Cyber Security Framework expects financial institutions to govern network security through defined architecture, not only through written standards. In practice, a reviewer takes your statement that zones are isolated and tries to trace it through your documents. If the trace breaks, the finding is about evidence, even when the underlying network is sound.

The usual gaps are consistent:

  • Zones named in policy but not defined by purpose, data sensitivity or trust level.
  • Firewalls drawn on a diagram without stating which rule sets govern which boundary.
  • Flows that exist in production but appear in no register.
  • Monitoring described in general terms, without sensor or log placement.
  • Diagrams that disagree with each other about the same zone.

The four design decisions to document

1. Zone definitions

Define each zone by what it is for, what data it may hold, and what level of trust it carries. Production, UAT and DMZ should each have a written definition, an owner and an entry rule for new systems. Record explicitly that UAT does not hold live customer data, or, where it does, what compensating controls apply and who approved them.

2. Access-control enforcement points

For every boundary between zones, name the enforcement point: firewall, gateway, proxy or other control. State the default posture (deny unless permitted), who approves rule changes, and how rules are reviewed. A reviewer wants to see that no path between zones exists without passing through a documented control.

3. Data-flow justification

Each cross-zone flow needs a business reason, a source, a destination, a protocol and port, an owner, and a note on encryption. Flows without a justification are the first thing a reviewer questions. Pay particular attention to administrative access, backup and replication, file transfer, and third-party or API connections, which tend to create undocumented paths.

4. Monitoring placement

Show where logging and detection sit relative to the zone boundaries: which enforcement points send logs, which segments have network sensors, and where alerts are received. Monitoring that exists but is not placed on the boundaries that matter will not persuade a reviewer that isolation is being observed.

The three diagrams that prove isolation

Logical topology diagram

This shows zones, enforcement points, key systems and monitoring components in one view. Keep it logical rather than physical. Label each boundary with the enforcement control and each zone with its defined purpose. It should answer one question quickly: what must a packet cross to get from UAT to production?

VLAN-to-security-zone mapping

This is a structured mapping, typically a list or register, linking each VLAN or subnet to its zone, owner and permitted function. It closes a common gap: the topology diagram shows zones, but the actual segments are not tied to them. If a VLAN cannot be mapped to exactly one zone, the isolation argument weakens.

Cross-zone traffic matrix

This lists permitted flows between zones as a matrix of source zone against destination zone, with each permitted flow referencing its justification and rule identifier. Blank cells should mean denied. The matrix is the document a reviewer will test against firewall configuration, so it must match what is implemented.

A sensible order of work

  1. Agree and write the zone definitions, since every other document depends on them.
  2. Build the VLAN-to-zone mapping from the live environment, not from memory.
  3. Extract current firewall rules and reconcile them to a draft traffic matrix, recording flows that lack a justification.
  4. Remove or formally approve each unjustified flow.
  5. Draw the logical topology from the reconciled facts, adding enforcement and monitoring placement.
  6. Check all three documents against each other for contradictions before the review.

What changes for the organization

Documentation becomes a controlled artefact. Rule changes, new VLANs and new integrations must update the mapping and the matrix, otherwise the evidence drifts from reality within months. Assign an owner for each document and tie updates to change management.

How we help

Our Security Architecture Review looks at the security of new and existing systems and network designs, including segmentation, identity, data flows, integration and resilience. The process follows four steps: we collect diagrams, data flows and design documents; model threats against key components and flows; assess controls against secure design principles; and advise on options, trade-offs and agreed actions.

The deliverables are an architecture review report, a threat model for key flows, prioritized design recommendations and reference security patterns. The assessment takes 2–4 weeks per system, and it is mapped to SAMA CSF and NCA ECC. Network segmentation and zoning, and data-flow and encryption review, are core parts of the scope.

Before your review appointment

Treat the three diagrams as a test of your own design. If someone outside the network team can trace an isolation claim from zone definition to enforcement point to monitored flow, a reviewer probably can too. If you would like an independent view of that before the assessment, our Security Architecture Review is built for it.

Tags: SAMA CSF network segmentation security architecture regulatory guides CISO data flows
Readiness self-check

How ready are you? Find out in two minutes

Answer a few questions for your framework. You get a score, your biggest gaps and — if you want it — a detailed assessment from our team.

Ready to talk about your compliance?

Tell us where you stand. We will show you the shortest path to what your regulator expects.

Regulatory updates in your inbox

SAMA, NCA and SDAIA changes and what they mean for your institution — once a month.

E-mails in

We confirm by e-mail; unsubscribe any time. Manage your subscription · Past issues

Schedule a Free Assessment