Security Rules Reference
Browse all 221 static-analysis (SAST) rules Zennoxa Shield checks across 14 languages and 51 CWE classes — each with what it detects, severity, CWE, CVSS and how to fix it.
What these rules check
Zennoxa Shield ships 221 static-analysis (SAST) rules across 14 languages. Each rule is a deterministic pattern — matched with regex and, where it matters, intra-file taint tracking that follows untrusted input from a source to a dangerous sink across lines. A match becomes a finding tagged with a severity, a CWE class, a CVSS base vector, and a concrete fix.
How to read a rule
- Severity — critical, high, medium or low, from the impact if the pattern is exploited.
- CWE — the Common Weakness Enumeration class it maps to (e.g. CWE-89, SQL injection). These rules cover 51 distinct CWEs.
- CVSS — a base vector so findings are comparable.
- Fix — every rule carries a specific remediation, not just a warning.
At scan time, findings are re-ranked by reachability — whether untrusted input can actually reach the vulnerable line — so the exploitable ones rise to the top. Accuracy is measured on the public OWASP Benchmark and reproducible with the free CLI.
Ruby · 23 rules
JavaScript / TypeScript · 22 rules
C/C++ · 21 rules
C# · 21 rules
Java · 18 rules
Kotlin · 18 rules
PHP · 18 rules
Python · 17 rules
Swift · 17 rules
Rust · 15 rules
Dart · 14 rules
Go · 12 rules
General · 3 rules
CI/CD · 2 rules
Common questions
What is a SAST rule?
A SAST (static application security testing) rule is a pattern that flags a class of security bug in source code without running it. Each Zennoxa Shield rule maps a code pattern to a CWE weakness class, a severity, a CVSS base vector, and a concrete fix.
How does Shield decide a rule’s severity?
Severity (critical, high, medium, low) reflects the impact if the pattern is exploited, aligned to the rule’s CWE class and a CVSS base vector. At scan time, findings are then re-ranked by reachability — whether untrusted input can actually reach the vulnerable line — so exploitable issues rise above theoretical ones.
Which CWEs does Shield cover?
Shield’s 221 rules span 51 distinct CWE classes across 14 languages, including SQL injection (CWE-89), cross-site scripting (CWE-79), command injection (CWE-78), path traversal (CWE-22), hardcoded credentials (CWE-798) and weak cryptography (CWE-327).
Can I reproduce these findings?
Yes. The Shield CLI is free and MIT-licensed and runs fully offline. Its accuracy is measured on the public OWASP Benchmark and reproducible with a single command, so you can verify the rules against your own code and against the labelled test suite.