> 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/data-security-documentation/onboard-and-configure/post-onboarding/how-to-review-errors-in-cortex-data-security.md).
# How to review errors in Cortex Data Security
**Review errors**
To review errors in Cortex Data Security, do the following:
1. In the lower left part of the screen, click Settings → Data Sources.
2. On the Data Sources screen, click a cloud service provider or other data source and then click the View Details link. Alternatively, you can click the Error button near the top of the screen. This button displays the data sources that have errors.
3. In the Cloud Instances screen, click the Instance Name link. A screen displaying the instance name and related information opens.
4. In the Security Capabilities list, click Data Security Scanning to display the Errors pane with the details of the errors that were found.
5. Click Add Filters to create a filter that displays the assets you want to review.
6. Click an asset row to display a popup window with information about the error and a raw error string that you can copy.
**Error table columns**
| Column Name | Description |
| ----------- | ------------------------------------------------------------------ |
| Asset Name | The technical name of the asset. |
| Error Name | An explanation of the error. |
| Timestamp | The date and time when the error was found. |
| Region | The geographical location of the asset with the error. |
| Asset Type | The type of asset, such as an Amazon S3 bucket or an RDS database. |
---
# 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://cortex-docs.paloaltonetworks.com/data-security-documentation/onboard-and-configure/post-onboarding/how-to-review-errors-in-cortex-data-security.md?ask=&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.
