When I started the NullSec project, the goal was simple: build a Linux distribution that I'd actually want to use for security research. Kali and Parrot are great, but I wanted something more — tighter integration with my own tooling, custom kernel patches for hardware hacking, and a framework that ties everything together.
After months of development, NullSec Linux v5.0 ships with 226+ pre-installed security tools, 5 specialized editions, and deep integration with the NullSec Framework.
Why Another Security Distro?
The security distro space is crowded. So why build another one? Three reasons:
- Framework Integration — NullSec Linux isn't just a collection of tools. It's built around the NullSec Framework, which provides unified configuration, output formatting, and tool chaining across all 226+ tools.
- Hardware Hacking First — Most security distros treat hardware hacking as an afterthought. NullSec Linux has first-class support for Flipper Zero, HackRF, WiFi Pineapple, Rubber Ducky, and other hardware tools with pre-configured drivers and udev rules.
- Edition Specialization — Instead of one bloated ISO, NullSec offers 5 editions each optimized for a specific workflow.
The Architecture
NullSec Linux is based on Debian stable, which gives us a rock-solid foundation. On top of that, we layer:
NullSec Linux Architecture
├── Custom Kernel (5.x with security patches)
│ ├── Hardware hacking drivers
│ ├── eBPF enhancements
│ └── Hardened networking stack
├── NullSec Framework
│ ├── Tool Manager (nullsec-tools)
│ ├── Config Manager (nullsec-config)
│ ├── Output Pipeline (nullsec-pipe)
│ └── Update System (nullsec-update)
├── Desktop Environment
│ ├── Hacker Edition → Custom XFCE
│ ├── Forensics Edition → MATE
│ ├── Minimal Edition → i3wm
│ ├── Server Edition → CLI only
│ └── Training Edition → GNOME
└── Pre-installed Tools (226+)
├── Network (50+)
├── Web (40+)
├── Wireless (30+)
├── Forensics (25+)
├── Hardware (20+)
├── Cloud (15+)
├── Mobile (15+)
├── AI/ML (10+)
└── Crypto (21+)
The Build System
Building an ISO from scratch is surprisingly complex. Here's the pipeline:
# The NullSec build pipeline
./build.sh --edition hacker --arch amd64
# What happens under the hood:
# 1. Bootstrap Debian base with debootstrap
# 2. Apply kernel patches and compile
# 3. Install NullSec Framework packages
# 4. Install tool packages (226+ tools)
# 5. Apply desktop environment config
# 6. Configure hardware drivers and udev rules
# 7. Generate squashfs filesystem
# 8. Build ISO with GRUB/syslinux
# 9. Generate checksums and sign
The whole process takes about 45 minutes on a modern machine, producing a ~4GB ISO. Each edition shares the same base but differs in desktop environment and pre-installed tool selection.
Tool Selection Philosophy
Not every tool makes it into NullSec Linux. Our criteria:
- Actively maintained — No abandoned projects
- Unique value — No duplicate functionality
- Quality output — Must produce parseable results
- NullSec integration — Should work with
nullsec-pipe - Ethical use — Authorized testing only
Want to suggest a tool for inclusion? Open an issue on the nullsec-linux repo with the "tool-request" label.
Lessons Learned
Building a distro taught me more about Linux than 10 years of using it. Some highlights:
- Package management is hard — Dependency resolution across 226 tools with conflicting Python/Ruby/Go versions is a nightmare. We ended up containerizing some tools.
- Kernel patching is scary — One wrong patch and nothing boots. We maintain a test suite that boots each kernel in QEMU before releasing.
- Documentation matters more than features — Users don't use features they can't find. We invested heavily in docs, which are now available as wiki pages on every major repo.
- Community feedback is gold — Some of our best features came from GitHub issues and discussion answers.
What's Next
NullSec Linux v6.0 is already in planning. On the roadmap:
- ARM64 native images (Raspberry Pi 5, Apple Silicon via QEMU)
- NullSec AI assistant built into the terminal
- Cloud deployment templates (AWS, DigitalOcean)
- Live collaboration features for red team exercises
If you want to try NullSec Linux, check out the GitHub repo or read the wiki.