agent-security-config-v1
2 rules · Keryn Software Licence · rules 0.8.0 · all packs
How to read a rule
- Severity
- How bad the finding is if it is real:
errorfails a default gate,warningandinfodo 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.config.guardrail-fail-open-default-allow
Section titled “keryn.config.guardrail-fail-open-default-allow”warning generic config
A guardrail / gateway / policy config sets its error or default action to allow/open/continue. When the check cannot run the request is permitted — fail-open. Set the error and default action to deny and allow only on an explicit positive decision.
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 authority is given or left unchecked.
CWE-636 CWE-280 LLM06 ASI08 ASI03
Fix: Make the error and default action deny/block/closed. Permit a request only after the guard returns an explicit allow; never let an error, timeout or unavailable checker fall through.
References: https://cwe.mitre.org/data/definitions/636.html · https://genai.owasp.org/resource/owasp-top-10-for-agentic-applications-for-2026/
keryn.config.jwt-algorithm-none
Section titled “keryn.config.jwt-algorithm-none”error generic config
A config enables the JWT “none” algorithm. A “none” token has no signature, so anyone can forge claims. Set the algorithm to the exact signing algorithm you issue (for example RS256) and never “none”.
Confidence P1: dangerous in context. False-positive risk low: an exact API or flag, so hits are almost always real.
Edge inspected: trusts one party believes another without evidence.
Fix: Set the JWT algorithm (and any allowed-algorithms list) to the exact asymmetric or HMAC algorithm you issue; remove “none”.
References: https://cwe.mitre.org/data/definitions/347.html