> For the complete documentation index, see [llms.txt](https://docs.qapilot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qapilot.io/detailed-documentation/reports/security-reports.md).
# Security Reports
**Security Reports** in QApilot to help teams run static security analysis as part of their mobile testing workflow. This update integrates security insights directly into the Reports experience, ensuring visibility without disrupting existing QA processes\
\
While uploading the app source, the user has an option to enable security reports.
**Security Reports**
* A new **“Security Analysis”** checkbox is available in the **App Upload** flow under Settings → App Source.
* Security analysis runs only when this option is explicitly enabled, ensuring teams stay in control of when and how scans are performed.
* Uploaded app versions include a **“View Security Report”** option, allowing quick navigation to the corresponding security report for that specific version.
When Clicked on "view report", the security report will be displayed as follows -
* A new **Security Reports** tab has been added under the **Reports** section, alongside Accessibility Reports.
* Each security report is listed with key metadata, including app title, OS, package or bundle name, version, analysis duration, and execution status.
* Reports are organized per app version, with a single security report generated for each uploaded version.
* Users can view detailed findings across multiple analysis areas, including:
* Manifest Analysis
* Certificate Analysis
* Code Analysis
* Network Security
---
# 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.qapilot.io/detailed-documentation/reports/security-reports.md?ask=&goal=
```
`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.