> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/code-scanning/scanning-practices/custom-rules.md).

# Custom Rules Overview

You can define your own rules in Aikido across code security, cloud security, and code quality, so checks align with your your environment and standards.

### **Where you can add custom rules**

* [**Custom SAST & IaC Rules**](https://help.aikido.dev/general-information/add-custom-sast-iac-rules)

  Define rules to detect application or infrastructure patterns that are specific to your stack, such as enforcing internal security APIs or common misconfigurations specific to your organization.
* [**Custom CSPM Rules**](https://help.aikido.dev/cloud-scanning/custom-cspm-rules)

  Add your own cloud misconfiguration checks on top of Aikido’s managed rules. Custom CSPM rules can be mapped to compliance benchmarks via tags, and they show up in compliance reports like any other cloud rule (for example, mapping a backup rule to ISO 27001 sections).
* [**Custom Code Quality Rules**](https://help.aikido.dev/code-quality/add-custom-code-rules)

  Describe code patterns or conventions you want to enforce in natural language. Aikido turns these into AI-powered checks that run on pull requests and help you enforce team-specific coding guidelines. Add an [AutoFix](/autofix-and-remediation/overview-aikido-autofix.md) prompt on the rule so Aikido can fix violations.

### Typical use cases

* Encode internal security guidelines, such required wrappers or safe helpers
* Flag cloud configurations that are risky in your particular architecture and tying them to your compliance framework
* Enforce local coding standards and architectural rules


---

# 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://help.aikido.dev/code-scanning/scanning-practices/custom-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.