> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/cybersecurity/threat-analysis/reports.md). # Reports In the **Reports** section, it is possible to track and evaluate the organization's security, offering detailed information about the vulnerabilities found and the progress of their resolution. This feature is divided into two reports: **Summary** and **Detailed**. To obtain the reports in PDF format, simply click the **Download** button. Follow the available metrics below: #### Summary Report In the **Summary Report,** you will find the following information: * Vulnerabilities found by criticality * Quantity of targets by type * Pending vulnerabilities by criticality * Pending vulnerabilities by type * Quantity of schedules * Average resolution time * Resolution of vulnerabilities * Top 5 most vulnerable targets * Evolution of vulnerabilities * Main information #### Detailed Report In the **Detailed Report,** you will find the following information: * Vulnerabilities found by criticality * Quantity of targets by type * Pending vulnerabilities by criticality * Pending vulnerabilities by type * Quantity of schedules * Average resolution time * Resolution of vulnerabilities * Top 5 most vulnerable targets * Threat level by exposure over time * Security level * Vulnerabilities List --- # 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.skyone.cloud/english/cybersecurity/threat-analysis/reports.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.