# ci-security-gate-fail-open-v1

> ci-security-gate-fail-open-v1: 1 Keryn rule for generic (1 warning).

Source: https://keryn.dev/rules/ci-security-gate-fail-open-v1/

1 rules · Keryn Software Licence · rules 0.8.0 · [all packs](https://keryn.dev/rules/)

**How to read a rule**

- **Severity**: How bad the finding is if it is real: `error` fails a default gate, `warning` and `info` do not.

- **Confidence**: **P0** exploitable as written; **P1** dangerous in context; **P2** a heuristic or a posture check: confirm by reading the code.

- **False-positive risk**: **low**: an exact API or flag, so hits are almost always real; **medium**: the pattern is legitimate in many programs, so check each hit; **high**: it finds a lead to confirm, so expect benign hits.

- **Edge**: The relationship the finding sits on. **reaches**: content or traffic gets to a thing; **calls**: one thing invokes another; **reads**: one thing reads from another; **writes**: one thing writes to another; **sends**: data leaves for another party; **grants**: authority is given or left unchecked; **depends_on**: something relies on a component it does not verify; **trusts**: one party believes another without evidence. The boundary it crosses, when there is one: **user->prompt** (untrusted input reaching a prompt); **model->code** (model output reaching code, a shell, a query or a page); **secret->outside** (a secret leaving the trusted side); **supply-chain** (code, models or prompts pulled in from outside).

- **Taxonomy chips**: References for readers who work in OWASP LLM 2025, OWASP Agentic, CWE or NIST AI RMF. They say where a rule belongs, not that a framework is satisfied.

## keryn.cigate.security-scanner-continue-on-error

`warning` generic github-actions, gitlab-ci, azure-pipelines, ci

A security scanner step (CodeQL, Semgrep, Snyk, Trivy, gitleaks, Bandit, Checkov, tfsec, ...) is set to continue-on-error / allow\_failure, so its findings never fail the pipeline. The gate does not gate. Remove continue-on-error from the security step, or gate the merge/deploy on its result.

Confidence **P2**: a heuristic or a posture check: confirm by reading the code. False-positive risk **medium**: the pattern is legitimate in many programs, so check each hit.

Edge inspected: [grants](https://keryn.dev/docs/edges/edge-kinds/#grants) authority is given or left unchecked.

[CWE-636](https://keryn.dev/rules/?cwe=CWE-636) [LLM06](https://keryn.dev/taxonomies/owasp-llm/#llm06-excessive-agency) [ASI08](https://keryn.dev/taxonomies/owasp-agentic/#asi08-cascading-failures)

**Fix:** Let the security step fail the pipeline: remove continue-on-error: true (and GitLab allow\_failure: true) from scanner steps, or branch the merge/deploy on the scan outcome.

**References:** [https://cwe.mitre.org/data/definitions/693.html](https://cwe.mitre.org/data/definitions/693.html) · [https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-jobs-with-conditions](https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-jobs-with-conditions)
