I'm building JANISSARY, a differential Dynamic Application Security Testing (DAST) tool focused on precision-led application security testing.
The objective is straightforward: make security testing results more meaningful, evidence-driven and actionable.
Finding something unusual isn't the same as verifying a vulnerability.
JANISSARY is being developed around that distinction.
The principles behind JANISSARY
Disciplined discovery: Identify potentially interesting application behaviour.
Evidence-driven verification: Separate discovery from confirmed results.
Transparency: Clearly distinguish verified, unproven and inconclusive outcomes.
Actionable findings: Prioritise useful security information over volume.
Why JANISSARY?
Security testing should provide engineers with information they can trust and investigate.
The goal isn't simply to produce more findings. It's to improve the quality of the findings that matter.
I'll be sharing development progress, technical decisions, implementation challenges and lessons learned as JANISSARY evolves.
Follow the project on GitHub:
https://github.com/Hetaireia/janissary
JANISSARY — SIGNAL OVER NOISE.
