Skip to content

feat(vuln): vulnerability management — 7 integrations + risk-based prioritisation#132

Merged
alex-dembele merged 1 commit into
masterfrom
feat/vulnerability-management
Jul 16, 2026
Merged

feat(vuln): vulnerability management — 7 integrations + risk-based prioritisation#132
alex-dembele merged 1 commit into
masterfrom
feat/vulnerability-management

Conversation

@alex-dembele

Copy link
Copy Markdown
Member

Dedicated Vulnerability Management module (user request: integrate Nessus, OpenVAS, Qualys, Microsoft Defender, AWS Inspector, Azure Defender, CrowdStrike; prioritise by CVSS, exploitability, business criticality, affected assets). No such module existed — the scanner produces transient findings and CTI holds feed data, but there was no persistent, per-asset, prioritised vulnerability register.

Backend:

  • domain.Vulnerability (tenant-scoped: CVSS/EPSS/KEV/exploit, linked-asset business criticality, blast radius, remediation status, priority score + P1..P4 tier; in AutoMigrate) + VulnerabilityRepository port + Gorm impl (dedup upsert that preserves triage status, filtered/sorted list, stats, distinct-asset count).
  • pkg/vulnprio: pure, deterministic prioritisation engine (8 tests) over the 4 requested axes — CVSS 0.40, exploitability 0.30 (EPSS/KEV/exploit; KEV floors to P1), business criticality 0.20, affected assets 0.10 — → 0-100 + tier + why.
  • internal/vulnscan: a normaliser per product (native finding JSON → common shape) for all 7 tools + connector catalogue (AWS Inspector live-pull; others import + honest seam, never fabricated data).
  • application/vulnerability: ingest (normalise → resolve asset → recount blast radius post-upsert → re-prioritise → upsert), list/get/update-status/delete/stats (tenant-safe, typed errors, tests). Handler + routes under vulnerabilities:*.

Frontend (features/vulnerabilities): register sorted by priority + KPI stats + filters, detail drawer (prioritisation breakdown, KEV/exploit signals, status lifecycle, delete), multi-source ingest modal, connectors panel; sidebar item + route + FR/EN i18n.

Live-verified (Postgres:5434): 7 connectors; Nessus Log4Shell → CVE extracted, matched to web-01 (CRITICAL) → P2 62.2; CrowdStrike exploit → maturity high 76.4; manual KEV CVSS 5.0 → floored P1 (80); same CVE on 3 assets → blast radius 3 → 66.97; priority-sorted list; stats; status update (invalid 400); delete 204 → 404; bad source 400; headless screenshot of the rendered page. go build/vet/test + tsc/vite all green.

…ioritisation

Dedicated Vulnerability Management module (user request: integrate Nessus,
OpenVAS, Qualys, Microsoft Defender, AWS Inspector, Azure Defender, CrowdStrike;
prioritise by CVSS, exploitability, business criticality, affected assets). No
such module existed — the scanner produces transient findings and CTI holds feed
data, but there was no persistent, per-asset, prioritised vulnerability register.

Backend:
- domain.Vulnerability (tenant-scoped: CVSS/EPSS/KEV/exploit, linked-asset business
  criticality, blast radius, remediation status, priority score + P1..P4 tier;
  in AutoMigrate) + VulnerabilityRepository port + Gorm impl (dedup upsert that
  preserves triage status, filtered/sorted list, stats, distinct-asset count).
- pkg/vulnprio: pure, deterministic prioritisation engine (8 tests) over the 4
  requested axes — CVSS 0.40, exploitability 0.30 (EPSS/KEV/exploit; KEV floors
  to P1), business criticality 0.20, affected assets 0.10 — → 0-100 + tier + why.
- internal/vulnscan: a normaliser per product (native finding JSON → common shape)
  for all 7 tools + connector catalogue (AWS Inspector live-pull; others import +
  honest seam, never fabricated data).
- application/vulnerability: ingest (normalise → resolve asset → recount blast
  radius post-upsert → re-prioritise → upsert), list/get/update-status/delete/stats
  (tenant-safe, typed errors, tests). Handler + routes under vulnerabilities:*.

Frontend (features/vulnerabilities): register sorted by priority + KPI stats +
filters, detail drawer (prioritisation breakdown, KEV/exploit signals, status
lifecycle, delete), multi-source ingest modal, connectors panel; sidebar item +
route + FR/EN i18n.

Live-verified (Postgres:5434): 7 connectors; Nessus Log4Shell → CVE extracted,
matched to web-01 (CRITICAL) → P2 62.2; CrowdStrike exploit → maturity high 76.4;
manual KEV CVSS 5.0 → floored P1 (80); same CVE on 3 assets → blast radius 3 → 66.97;
priority-sorted list; stats; status update (invalid 400); delete 204 → 404; bad
source 400; headless screenshot of the rendered page. go build/vet/test + tsc/vite
all green.
@alex-dembele
alex-dembele merged commit 4608738 into master Jul 16, 2026
11 of 18 checks passed
@alex-dembele
alex-dembele deleted the feat/vulnerability-management branch July 16, 2026 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant