> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/kubernetes-security/cloud-workload-policies-and-rules/cloud-workload-rules/cloud-workload-rules-page.md).

# Cloud workload rules page

The **Cloud Workload Rules** page allows users to manage rules. Users can create, edit, filter, and manage rules.

{% hint style="info" %}

#### Note

Keep the following caveats in my mind when working with Rules:

* Instance Administrators are able to view all facets of Rules without restrictions, even if Scope Based Access Control (SBAC) roles are in effect. Learn more about [SBAC](file:///document/preview/1410276#UUID-c3eebdf1-af6e-6820-c11d-457e6aabae48).Manage user scope
* If you’ve been assigned a custom role with View/Edit permissions limited by SBAC, you may not be able to view specific Rules.
* You can further narrow your search in a Rules table by using SBAC to limit the scope of the finding, issues, and case counts.
  {% endhint %}

The Widget section enables the users to get 'at-a-glance' based on Platform, Rule type and Scanner type.

The Cloud Workload Rules page displays both the default rules and user-configured rules, with the following fields.

**Rule table columns**

| Column Name           | Description                                                                                                                                                              |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Rule ID**           | A unique identifier assigned to each rule.                                                                                                                               |
| **Rule Name**         | The name of the rule, typically defined by the user or system.                                                                                                           |
| **Description**       | A brief summary of the rule's purpose and functionality.                                                                                                                 |
| **Policies**          | Lists the policies in which the rule is included.                                                                                                                        |
| **Controls**          | Compliance controls associated with the rule for regulatory adherence.                                                                                                   |
| **Platform**          | Specifies the platform or environment the rule applies to. For example: **Linux, Windows**or **Kubernetes**.                                                             |
| **Scanner**           | The tool or method used to evaluate findings, such as *Inventory Scanner*, *Agentless Disk Scan, Host Scanner, Kubernetes Connector or Kubernetes File System Scanner* . |
| Severity              | Defines the severity of the rule.                                                                                                                                        |
| **Data Type**         | The type of data the rule evaluates. For example: **Hosts** or **Kubernetes Resources**                                                                                  |
| **Created By**        | The user who created the rule.                                                                                                                                           |
| **Last Modified**     | The date and time the rule was last updated.                                                                                                                             |
| **Rule Type**         | Indicates whether the rule is a **Built-in** or Custom rule.                                                                                                             |
| Remediation           | Defines the remediation steps to address the detected misconfiguration.                                                                                                  |
| **Applicable assets** | Supported applicable asset types.                                                                                                                                        |
| **Available actions** | Indicates whether the available action is **Prevent and Create an Issue** or **Create an Issue**                                                                         |
| **Standards**         | Associated compliance standards or controls                                                                                                                              |
| **Open issue**        | No. of open issue related to this rule.                                                                                                                                  |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/kubernetes-security/cloud-workload-policies-and-rules/cloud-workload-rules/cloud-workload-rules-page.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.