Security Engineering · Platform team
Unifying findings across four scanners
Spring BootKafkaElasticsearchPostgreSQL
Problem
Findings from Nessus, Semgrep, Trivy, and Snyk were stored in per-scanner shapes. Dedup, severity normalization, and cross-tool reporting were manual and unreliable. Adding a new scanner took an average of three weeks.
Solution
Built an ingestion API with a normalized finding schema, per-scanner adapters, and Kafka fan-out to Elasticsearch for search and Postgres for canonical storage. Deterministic finding-fingerprints made dedup trivial across scanners.
Impact
Onboarding a new scanner dropped from three weeks to two days. Analysts stopped writing cross-tool SQL and started using the search endpoint. Coverage went from three scanners to seven within a quarter.
Measured impact
3w → 2d
New scanner onboarding
2.3M
Findings ingested / mo
< 200ms
Search p95
Have a system that's failing under real load?
That's the work we take on. Send a short brief and we'll tell you honestly whether it's a fit.
Next · CS · 03
An AI SQL assistant that non-analysts trust