> For the complete documentation index, see [llms.txt](https://docs.halosecurity.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.halosecurity.com/docs/platform/reports.md).

# Reports

Access reports and data related to findings.

This section allows you to access, generate and download a variety of reports.

## Dashboard Reports

The reports section includes a list of reports on data about your attack surface. These include the key reports on your [firewalls](/docs/platform/firewalls.md), [websites](/docs/platform/websites.md), [DNS records](/docs/platform/firewalls/dns-records.md), and much more.

{% hint style="success" %}
Use the **star** icon to favorite reports you care about most for quick access from the Favorites tab.
{% endhint %}

## PDF Reports

The [PDF](https://app.halosecurity.com/user/security/report/pdf) section allows you to generate the following reports in the PDF format:

* **Issue Report**: A list of all issues found across your targets. It has a 50 target limit.
* **Executive Summary**: A high-level overview of your risk rating, attack surface, issues, and other sections of the scan findings.

Generated reports will be available in the [Files](https://app.halosecurity.com/user/security/report/files) section for download.

## Files

Generated PDF reports are stored in the Files tab.


---

# 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://docs.halosecurity.com/docs/platform/reports.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.