Skip to content

Set up minimal security scanners (CI) #1478

Description

@ktursunov

Goal

Establish a minimal security-scanning baseline in CI for the Security quality vector (currently undefined in the Quality Framework). Start report-only, then ratchet to gating once thresholds are agreed with the team.

Scope (minimal first pass)

  • Secret scanning on PRs (e.g. gitleaks / GitHub secret scanning).
  • Dependency / vulnerability scan: cargo audit (Rust workspace), pnpm audit (frontend), and a container-image scan (e.g. Trivy) for the images we build.
  • SAST baseline: CodeQL for the languages in the repo — report-only to start.

Acceptance

  • Each scanner runs on PRs to main, surfaced in checks / job summary (report-only, non-blocking at first).
  • Real findings are triaged; follow-up issues filed for anything actionable.
  • Gate thresholds (what blocks a PR) decided with the team before flipping any scanner to blocking.

Children

The bundled security-gates.yml (PR #1463) was closed and decomposed into a per-tool task
per scanner, so each can be triaged and ratcheted to blocking independently:


Part of the Quality Framework → Security vector. QA-owned. Tracked on the Insights project.

Planning: first pass starts next week — ETA 15 Jul 2026 · Konstantin Tursunov.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestpriority:P2Second waveteam:qaTest installation and scenario validation

Type

Fields

No fields configured for Task.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions