Skip to content

Prove the walls hold

Network Segmentation
Assessment

We test whether the boundaries around your cardholder data environment, CUI enclave or critical systems actually stop traffic. From every network that should be shut out, we probe the boundary, confirm what gets through, and give you evidence PCI DSS and CMMC assessors can rely on.

Test from every side

Isolation you can
show an assessor.

Testing follows PCI DSS requirement 11.4.5 and the CMMC Level 2 scoping guidance for enclaves built on NIST SP 800-171. We test from inside each segment that claims to be separate, and every open path is confirmed by hand with a check you can reproduce.

Phase 01 · Scope & claims

Write down what is meant to be isolated.

A segment map listing every boundary, what it protects, and which flows are allowed by design.

  • Cardholder data environment, CUI enclave or critical zones defined with you.
  • Firewall rules, ACLs and cloud security groups collected for each boundary.
  • Allowed business flows documented so they are not reported as findings.

Phase 02 · Test positions

Stand in every network that should be shut out.

A documented test point in each out of scope segment, so every result traces back to where it came from.

  • Test devices or virtual machines placed in each segment, agreed in scoping.
  • Cloud VPCs and VNets included where the boundary crosses into cloud.
  • Wireless and guest networks added where they exist.

Phase 03 · Boundary testing

Probe every port and protocol across the boundary.

Every path that crosses a boundary it should not, with source, destination, port and protocol.

  • Full TCP and UDP port scans toward the protected segment.
  • Checks for routing leaks, VLAN hopping and dual homed hosts.
  • Shared services such as DNS, Active Directory and backup reviewed as bridges.

Phase 04 · Verification

Confirm each open path by hand.

Each leak proven with a reproducible check, separated from scanner noise and from flows you allow.

  • Open ports confirmed with manual connection attempts.
  • The firewall rule or ACL behind each leak traced.

Phase 05 · Assessor evidence

Hand over evidence your assessor can file.

A segmentation test report written for PCI DSS and CMMC assessors, plus a fix list for network engineers.

  • Method, test positions and results documented for each boundary.
  • Leaks ranked by what they expose, with the rule change that closes each one.
  • Retest of closed paths available after remediation.

Write down what is meant to be isolated.

A segment map listing every boundary, what it protects, and which flows are allowed by design.

  • Cardholder data environment, CUI enclave or critical zones defined with you.
  • Firewall rules, ACLs and cloud security groups collected for each boundary.
  • Allowed business flows documented so they are not reported as findings.

Key benefits

Keep audit scope small, with evidence.

Scope reduction that holds up

Segmentation is how you keep the wider network out of PCI DSS or CMMC scope. A tested boundary lets you defend that scope to an assessor with evidence instead of diagrams.

Written for your assessor

The report follows PCI DSS requirement 11.4.5 and the CMMC scoping guidance, with test points, methods and results laid out the way QSAs and C3PAO assessors expect to read them.

Leaks fixed at the rule

Each open path comes with the firewall rule, ACL or security group that allows it, so engineers close the leak directly instead of hunting for the cause.

What you get

What lands on
your desk.

One piece for the assessor, one for the network team, and time with the person who ran the tests.

The document

The segmentation test report

Scope, boundaries tested, test positions, method and results for every segment, with each leak documented by source, destination, port and the rule responsible. Built to file with your PCI DSS or CMMC evidence.

The working file

The boundary leak tracker

One row per open path: source segment, destination, port, protocol, the rule that allows it, owner and retest status. Network engineers work from it directly.

The conversation

The segmentation readout

A session with your network team and compliance lead. We walk each leak, agree which flows are legitimate business needs to document, and plan the retest.

Client case studies

Real engagements.
Documented outcomes.

YHB | CPAs & Consultants testimonial

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."

Cyrus Kapadia
Chief Technology & Information Officer, YHB | CPAs & Consultants

Trusted by industry leaders.

Segmentation questions

Asked before
every assessment.

Straight answers from the practitioners who do the work. If yours is not here, ask us directly.

Requirement 11.4.5 calls for testing at least once every 12 months and after any change to segmentation controls or methods. Service providers test more often under 11.4.6. Your QSA confirms what applies to you.

Yes. If CUI lives in an enclave, the boundary is what keeps the rest of the company out of assessment scope. We test it from the outside in and document results against the NIST SP 800-171 boundary protection requirements.

Scans are paced and run in windows you approve. Fragile systems are flagged in scoping and handled with lighter checks. We do not exploit anything we find; the goal is to prove the path exists.

Network diagrams, the rule sets for each boundary, a place to put a test device or virtual machine in each segment, and a contact who can confirm whether a flow is intended.

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.