> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/compliance/mapped-rules.md).

# Mapped Rules

**Mapped rules** lists the native application rules of one standard, the controls each rule counts towards, and the customer impact and likelihood of each rule. Impact and likelihood give each rule its risk score in the [Risk Matrix](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/compliance/risk-matrix.md). Platform and change controls keep their own checks and evidence in [Change Controls](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/compliance/change-controls.md).

Open it from **Workspaces** → **Compliance** → **Mapped rules** in the sidebar.

{% hint style="warning" %}
You need a role that can view compliance standards. Adding rules needs a role that can create compliance standards and view quality rules; changing or removing them needs a role that can edit or delete compliance standards.
{% endhint %}

## Choose a Standard

Select a standard in **Choose a standard**. Its rules appear below. You can also open this screen from a standard's **Rule impact** link in [Standards & Frameworks](broken://pages/2ded2e2e308bc0fe50fc7a95b55dad213487f979).

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FCIdtz0e8C9wFKzGDOIn7%2Fv2-compliance-mapped-rules.png?alt=media&amp;token=c600c8b9-4d21-4cbe-aef4-6bba1ab9293a" alt="Mapped rules for a standard"><figcaption><p>Mapped rules</p></figcaption></figure>

**Control hierarchy** opens the standard's control hierarchy.

## Rules in This Standard

| Filter              | Description                                                                 |
| ------------------- | --------------------------------------------------------------------------- |
| **Impact**          | One impact level, or **Any impact**.                                        |
| **Likelihood**      | One likelihood level, or **Any likelihood**.                                |
| **Control mapping** | **Mapped to a control**, **Not mapped to a control**, or **Mapped or not**. |
| Search              | **Search rules by name or identifier**.                                     |

| Column         | Description                                                |
| -------------- | ---------------------------------------------------------- |
| **Rule**       | The rule. Expand it to see the controls it counts towards. |
| **Impact**     | The rule's impact level for this standard.                 |
| **Likelihood** | The rule's likelihood level.                               |
| **Notes**      | Notes recorded with the rule.                              |
| **Manage**     | **Edit impact** and **Remove rule**.                       |

**Export rules on this page** downloads the rules on the current page.

## Add a Rule

A rule can be added to a standard once.

1. Select **Add rule**.
2. Search for the **Rule** by name or identifier. **Required.**
3. Choose the impact:
   * If the standard sets impact manually, choose the **Overall impact**. **Required.**
   * If the standard derives impact from its impact measures, choose an impact for each measure. **Overall impact** is set to the highest one.
4. Choose the **Likelihood**. **Required.**
5. Optionally add **Notes**.
6. Save the rule.

To change a rule's ratings, select **Edit impact** on its row. The levels you can choose are listed in [Scoring Settings](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/compliance/scoring-settings.md).

{% hint style="danger" %}
**Remove rule** removes the rule and its control mappings from the standard, so its results stop counting towards any control.
{% endhint %}

## Next Steps

* [Risk Matrix](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/compliance/risk-matrix.md): see where each rule's rating places it.
* [Scoring Settings](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/compliance/scoring-settings.md): read what each impact and likelihood level means.
* [Standards & Frameworks](broken://pages/2ded2e2e308bc0fe50fc7a95b55dad213487f979): return to the standards library.


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/compliance/mapped-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.
