ci: turn dedicated 0pt security scan into a blocking gate
This commit is contained in:
@@ -1,21 +1,15 @@
|
||||
name: Security Scan (SIAX Cloud)
|
||||
|
||||
# Advisory security scanning on every push/PR + weekly re-run, matching the
|
||||
# fleet convention (--exit-code 0 so findings never block merges; they are
|
||||
# triaged via the repo's security channel and BACKLOG).
|
||||
#
|
||||
# NOTE: findings on services/scrapers/* (FlareSolverr/Tor/curl_cffi) are
|
||||
# expected and out of scope for CI gating -- kept per the account owner's
|
||||
# dated, attributed decision (Simon Axelsson, 2026-08-11, interactive
|
||||
# prompt; no rationale beyond "keep it" given or invented). See SECURITY.md
|
||||
# and docs/compliance/GOLDEN-STANDARD-REPORT.md control C6 for full context.
|
||||
# Blocking vulnerability/secret scan on every push/PR + weekly re-run.
|
||||
# HIGH/CRITICAL findings must be fixed or carried by an explicit, scoped,
|
||||
# time-bounded exception outside this workflow; CI never silently downgrades them.
|
||||
on:
|
||||
push:
|
||||
branches: ["**"]
|
||||
pull_request:
|
||||
workflow_dispatch:
|
||||
schedule:
|
||||
- cron: "0 5 * * 1" # weekly Monday re-scan
|
||||
- cron: "0 5 * * 1"
|
||||
|
||||
jobs:
|
||||
security:
|
||||
@@ -25,6 +19,6 @@ jobs:
|
||||
- name: Install Trivy
|
||||
run: |
|
||||
curl -sfL https://raw.githubusercontent.com/aquasecurity/trivy/main/contrib/install.sh | sh -s -- -b /usr/local/bin
|
||||
- name: Trivy fs scan (vuln + secrets, advisory)
|
||||
- name: Trivy fs scan (vulnerability + secret; HIGH/CRITICAL blocking)
|
||||
run: |
|
||||
trivy fs --scanners vuln,secret --severity HIGH,CRITICAL --exit-code 0 .
|
||||
trivy fs --scanners vuln,secret --severity HIGH,CRITICAL --exit-code 1 .
|
||||
|
||||
Reference in New Issue
Block a user