Null Warden is a security research and defensive engineering practice. We break systems the way an attacker would, then rebuild the defences so the same path is closed permanently.
We keep research and defence under the same roof, because the people who find the flaw are the people who fix it.
Authorised testing of networks, applications, cloud estates and hardware. Every engagement starts from a threat model, so we test the paths an adversary would actually take rather than a checklist.
Findings are delivered with working exploits, a reproduction path and a fix that closes the class of bug, not just the instance.
Offensive securityWe build tooling, fuzz targets and harnesses to find bugs that scanners miss. Our work covers userspace, kernel, firmware and embedded targets.
Everything publishable is disclosed responsibly under a coordinated timeline. Everything that matters to a customer is reported privately first.
Our researchBaselines built for the platform you actually run, not a generic checklist. Kernel configuration, LSM policy, secure boot chains, reproducible builds.
We measure the cost of every control on your target hardware and give you numbers you can take to a board.
Hardening servicesWhen something has already gone wrong, containment comes before forensics. We stabilise the environment, establish what happened, and leave you with a system that is actually harder to re-enter.
Available on retainer or as an emergency response, remote or on-site.
Incident responseWe have operated in environments where the cost of a mistake is measured in more than money.
We are deliberately small. The person who scopes your engagement is the person who executes it.
Senior researchers and engineers. No juniors billed as seniors, no bench, no account management layer.
New Zealand owned and operated, with research, source and IP held onshore.
Coordinated disclosures with advisories, patches and detection guidance for defenders.
Every finding ships with a working proof of concept and a reproduction path you can hand to engineering.
Engagements run in fixed phases with defined outputs. Stop at any boundary and you leave with something usable.
Most of the interesting bugs in modern systems live in the places where developers were told not to look: kernel memory management, firmware boot chains, and hardware offload paths.
We built a coverage-guided fuzzer that runs in a hypervisor, so we can explore kernel interfaces safely and at speed. It found four distinct privilege escalation bugs in the first month.
Read the researchTell us what it runs, what it protects, and what would hurt most if it fell. A researcher will come back to you — not a sales team.