RFP.2.2 demo: severity gate — blocks on Critical & High#2
Conversation
Demonstrates RFP.2.1 + RFP.2.2 — PR-triggered scan, runner isolation, secret-based credential handling, and severity gating: - APISEC_MAX_HIGH: "0" → any High finding blocks the PR - Medium advisory runs with continue-on-error (warns, does not block)
Tightens RFP.2.2 demo to a single blocking step: APISEC_MAX_CRITICAL=0 and APISEC_MAX_HIGH=0. Container exits non-zero on any Critical or High finding, which fails the check and prevents merge.
…URL to PR comment
APIsec API Security Scan
|
APIsec API Security Scan
|
1 similar comment
APIsec API Security Scan
|
☂️ Python Coverage
Overall Coverage
New FilesNo new covered files... Modified FilesNo covered modified files...
|
APIsec API Security Scan
|
APIsec API Security Scan
|
APIsec API Security Scan
|
APIsec API Security Scan
|
APIsec API Security Scan
|
APIsec API Security Scan
|
What this demonstrates
RFP.2.1 + RFP.2.2 — Scan triggered on PR with a hard severity gate.
ubuntu-latestGitHub-hosted VMAPISEC_TOKENas GitHub Secret,APISEC_AUTH_IDas GitHub Variabledocker.io/apisec/apisec-scan-and-gate:latestcontainerAPISEC_MAX_CRITICAL=0andAPISEC_MAX_HIGH=0— any Critical or High finding exits non-zeroExpected result: ❌ Check fails (crAPI has known High/Critical findings). PR comment shows BLOCKED status with a direct link to the scan in APIsec.