> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-code/snyk-code-security-rules/cobol-rules.md).

# COBOL rules

Snyk Code security rules for COBOL

Each rule includes the following information.

* **Rule Name**: The Snyk name of the rule.
* **CWEs**: The [CWE numbers](https://cwe.mitre.org/) the rule covers.
* **Security Categories**: The [OWASP Top 10](https://owasp.org/Top10/2025/) (2025 edition) category the rule maps to, when applicable. This column also notes whether the rule appears in the [CWE Top 25](https://cwe.mitre.org/top25/), and any applicable [OWASP API Security Top 10](https://owasp.org/API-Security/editions/2023/en/0x11-t10/) (2023) or [OWASP Mobile Top 10](https://owasp.org/www-project-mobile-top-10/) (2024) categories.

| Rule Name                                           | CWEs             | Security Categories                                                    |
| --------------------------------------------------- | ---------------- | ---------------------------------------------------------------------- |
| Use of Hardcoded Cryptographic Key                  | CWE-321          | OWASP:A04:2025                                                         |
| Use of Hardcoded Cryptographic Initialization Value | CWE-329          | OWASP:A04:2025                                                         |
| No Dynamic SQL Clauses                              | CWE-89           | CWE Top 25, OWASP:A05:2025                                             |
| Inadequate Encryption Strength - Small Key Size     | CWE-326          | OWASP:A04:2025                                                         |
| Weak Cryptographic Primitive                        | CWE-327          | OWASP:A04:2025                                                         |
| Clear Text Logging                                  | CWE-312          | OWASP:A06:2025                                                         |
| Hardcoded Secret                                    | CWE-547          | OWASP:A02:2025                                                         |
| Use of Hardcoded Passwords                          | CWE-798, CWE-259 | OWASP:A07:2025                                                         |
| Use of Hardcoded Credentials                        | CWE-798          | OWASP:A07:2025                                                         |
| Injection on Accept                                 | CWE-20           | CWE Top 25, OWASP:A05:2025, OWASP-API:API10:2023, OWASP-Mobile:M4:2024 |
| Insecure Debug Features Enabled                     | CWE-489, CWE-215 | OWASP:A02:2025, OWASP:A10:2025                                         |
| Insecure Data Transmission                          | CWE-319          | OWASP:A04:2025, OWASP-API:API8:2023, OWASP-API:API10:2023              |
| SQL SELECT statement without WHERE clause           | CWE-668          | OWASP:A01:2025                                                         |
| Multiple CICS HANDLE ABEND Declarations             | CWE-755          | OWASP:A10:2025                                                         |
| Missing SQL Communication Area (SQLCA)              | CWE-391          | OWASP:A10:2025                                                         |
| Ignored Error Condition                             | CWE-754          | OWASP:A10:2025                                                         |
| Use of a Broken or Risky Cryptographic Algorithm    | CWE-327          | OWASP:A04:2025                                                         |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-code/snyk-code-security-rules/cobol-rules.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.