Menu

Authorization before the scanner: building King Malhare
📰

Authorization before the scanner: building King Malhare

DEV Community: go·James Ngandu·7 days ago
#6k2qsoiU
#devtogo#devto#dev#worker#scanner
Reading 0:00
15s threshold

Most vulnerability scanners are easy to point at a host. You give them a URL, choose a profile, and they start sending traffic. The hard part is proving that the host was allowed to be scanned in the first place.

King Malhare is a self-hosted security assessment platform I built around one rule: no active scan runs without a valid authorization record, and that record has to survive the trip from the API to the scanner worker. The live instance is at https://kingmalhare.mukuvi.tech . The code is proprietary, so this post focuses on the architecture and the decisions behind it.

The stack

The platform runs as four services:

A Go API built on chi and pgx

PostgreSQL 16 as the source of truth

Redis 7 for the job queue, cancellation and progress fan-out

Python workers that run the scanner adapters

The console is React with Vite and TanStack Query. Caddy handles TLS in the production Compose stack.

I split the API from the workers for a specific reason. Scanners deal with hostile input in both directions.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.