Network Testing
Lab environment//Stress + resilience//Firewall + IDS
A controlled lab environment for network security testing. Traffic stress simulation, resilience analysis, firewall and IDS validation — built so I can break things on purpose without breaking anything I'm not supposed to.
/overview
A self-contained lab for safely abusing networks I own. Containers, virtual interfaces, scripted attack scenarios, and observability hooked into the boundary devices — all reproducible from a single repo.
The point isn't to "win" against the firewall. The point is to know exactly what it does under load, which packets it logs, which it drops silently, and how the IDS reacts when traffic stops looking like the textbook. Every scenario lives as a script you can re-run, diff, and version.
It's the rig I reach for before I touch a real network. If a technique works here cleanly, and the IDS catches it cleanly, I trust both sides. If something behaves weird, I'd rather find out on a virtual interface than in a client engagement.
/capabilities
- Traffic stress simulation (TCP / UDP / mixed)
- Bandwidth + latency saturation harness
- Resilience scenarios — failover, partial outage, jitter
- Firewall rule validation suite
- IDS detection coverage testing
- Reproducible scenarios as scripted runs
- Pre-baked attack patterns (port sweep, SYN flood, slowloris)
- Boundary device logging hooks
- Pre/post snapshots for state diffing
- Isolated network namespaces — no host bleed
/stack
/install
# clone the lab $ git clone https://github.com/BitJacker/cybersecurity-network-testing.git $ cd cybersecurity-network-testing # bring up isolated namespaces + IDS $ sudo ./scripts/lab_up.sh # run a scripted scenario $ sudo ./scenarios/stress_tcp.sh --rate 10kpps --dur 60 $ sudo ./scenarios/syn_flood.sh --target 10.10.0.5 $ sudo ./scenarios/firewall_audit.sh # tear down $ sudo ./scripts/lab_down.sh
// Run this only on networks you own. The lab is isolated by design — keep it that way.