CyberKareemContact Abdullah
Menu

Project case study · reviewed source

seg-test

A scoped CDE reachability evidence runner for authorized PCI DSS segmentation-testing workflows.

Open reviewed source opens in a new tabRead the methodology article
Role
Designer and developer
Runtime
Shell
License
MIT
Reviewed revision
db8d0cce2c3a

Problem to outcome · 01

How the problem shaped the design and implementation.

01

Challenge

Segmentation testing needs a repeatable source boundary, bounded probes, and evidence that can be reviewed later. A broad scan alone does not show where the test started or support a defensible retest.

02

Design decision

Treat source validation, dry-run visibility, bounded execution, and evidence packaging as part of the test itself. Leave effectiveness and compliance conclusions to qualified human review.

03

Contribution

Designed and built the source-CIDR guard, dry-run plan, scoped Nmap, netcat, and curl checks, prior-finding retest path, and timestamped evidence archive.

04

Outcome

The utility produces a consistent reachability evidence package with a SHA-256 sidecar while keeping pass, fail, and compliance decisions outside the script.

Implementation trace · 02

The implementation follows four reviewable stages.

  1. Validate source

    Confirm that the runner is executing from the authorized source boundary.

  2. Preview scope

    Show the planned targets and checks before any probe is sent.

  3. Test routes

    Run bounded TCP, UDP, and application-layer reachability checks.

  4. Package evidence

    Archive timestamped outputs and create a SHA-256 integrity sidecar.

Proof and boundaries · 03

Verified behavior and known limits.

Verified in the reviewed source

What the project demonstrates

  • The Bash workflow passes syntax validation.
  • A source-CIDR guard and dry-run preview are present in the reviewed source.
  • The workflow packages timestamped evidence with a SHA-256 sidecar.
Operating boundary

What the project does not claim

  • There is no public automated test suite or tagged release.
  • Reachability evidence does not by itself prove segmentation effectiveness or PCI DSS compliance.
  • The utility is intended only for explicitly authorized and carefully bounded testing.

CyberKareem/seg-testThis page references commit db8d0cce2c3a06af20d3974a9cc59611f4415099. The repository may move after that point; the pinned revision keeps this review reproducible.

Inspect pinned revision opens in a new tab

Continue through the portfolio

Open the source, read the method, or compare the wider project set.

The case study separates demonstrated behavior from maturity and operating limits. The repository remains the source of truth.

Browse all projects View professional background