Build the read-only known-flaw check and ranking

Aperta
  • Qualcosa non va?
#73 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
bash, powershell
Ambito
security, tooling

Direzione di ricerca

Start from spec design 09 section 3 and issue #72 to learn the data sources. Create module harden.vuln_check in phases/harden/modules/vuln_check/ with ranking logic for known flaws from host data, web apps, snapshots, WES-NG. Write bats and Pester acceptance tests first as listed; done means the read-only check passes them offline.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: services phase: harden platform: linux platform: windows type: build

Location & Context

Roadmap branch phase-4/vuln-check. Spec: design 09 section 3. Planned module ID: harden.vuln_check, in phases/harden/modules/vuln_check/. Depends on #72.

Current Behavior

Nobody can see which known flaws are exposed on a host. Built early, it shows the team what is exposed from the first build.

Remediation Plan

  1. Find and rank known flaws from host security data, web apps on disk, the dated known-exploited snapshot, and WES-NG on Windows.
  2. Rank a flaw in a scored service above the same flaw in an unscored one, and a domain controller flaw above both.
  3. Run with no network access, from the host's own data and the release's snapshot.
  4. Keep the module read-only.
  5. Write these acceptance tests first (bats and Pester):
    • A known-exploited flaw in a scored service ranks above the same flaw in an unscored one.
    • A known-vulnerable package planted in the lab ranks above the same package on a host where it does not listen.
    • A known-exploited WordPress plugin version planted in the lab web app is listed and ranked.
    • With no network access the check completes.
    • On a lab Windows host missing a known update, WES-NG reports the matching CVE offline.
    • A negative test: protected accounts and scored services are untouched before and after.
Lingua principale
PowerShell
Stelle
0
Fork
0
Merge medio
2h 7m
PR unite (30g)
53

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di dotnetdork/Labyrinth

Tutte le issue di dotnetdork/Labyrinth

Issue simili

Altre issue su Security

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.