> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/opsmx-1/opsmx-context-engine/additional-resources/previous-releases/isd-3.12/data-and-intelligence-module-autopilot/audit-and-traceability/application-audit/policy-audit.md).

# Policy Audit

From the ISD application dashboard, Click "**Security**" --> Click "**Audit Trail**" and then click "**Policy Audit**".  This will take you to the available policy list. 

![](/files/E9rbLKWT4uNcR9Z1gpuB)

The policy audit tab is contains all the policies in a list view as shown in the image below:

![](/files/dTlxvQYThDMAUjVpyXKL)

In the above image, the list of policies is displayed and has the following details:

**Application** – This column shows the application in which the policy exists.

**Service -** This column shows the name of the service.

**Pipeline** – This column shows the pipeline in which the policy exists.

**Gate Name** – This column shows the name of the gate.

**Action -** This column shows the policy action.

**Policy Name** – This column shows the name of the policy.

**Time** - This column shows the date and time on which the policy is created.

**Triggered By -** This column shows the user by whom the policy was created or triggered.

**Policy Event** - This column shows the event of the policy.

**Description** – This column shows the description of the policy.

### Show/Hide Columns

You can opt to show or hide these columns in the list available. To do so, click the **menu icon** as shown in the image below. The list of available columns will appear. You can select/deselect a particular column to remove it from the policy table.

![](/files/zgKNa9RLWTDTcNNqWqD4)

### Filter **Policies**

Let’s take an example where you have around 200 policies in the list. But you want to view the details of one particular policy or a set of policies. This is where you can search to the list and view the specific policy(s) as per your requirement. There are two type of search available, **Basic** and **Advanced search (Filter by Column)** .

#### **Basic Search**

The basic search allows you to simply search a policy using the name of the policy. To do so, enter the name of the policy in the **Search** text box as shown below. The list will only show the policies with that particular name.

![](/files/yPceC5Kb0Xl1d9D3crPR)

**Advanced Search (Filter by Column)**

You can also opt to filter the policies by the columns of the table showing the list of policies. To do so click the filter icon. Refer to the image below:

![](/files/hEcCkbmpt8OYKA4VWXn1)

As of now, you can filter by 10 columns as shown in the image below:

![](/files/OXi3d3Lnm0ELGsq6Ma4B)

#### Download(.csv)

Users can download the **.csv** file containing the entire list of policies and their associated details by clicking the download symbol as shown below:

![](/files/KqefSklLmagnWmmKz777)


---

# 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://docs.opsmx.com/opsmx-1/opsmx-context-engine/additional-resources/previous-releases/isd-3.12/data-and-intelligence-module-autopilot/audit-and-traceability/application-audit/policy-audit.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.