> For the complete documentation index, see [llms.txt](https://manual.bubble.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.bubble.io/help-guides/security/security-dashboard/security-tests.md).

# Security tests

At its core, the security dashboard is a tool for simplifying the security management of your Bubble app. It streamlines the process of identifying and addressing potential vulnerabilities. The majority of the security dashboard's features are centered around its core security test.

This test runs a comprehensive analysis across various security checkpoints and returns a list of potential vulnerabilities, each accompanied by recommendations for improvement. These findings can include insights into data privacy settings, user access controls, and exposure risks of specific data fields. By highlighting these areas, the security dashboard helps you take targeted actions to strengthen your app’s security.

It’s important to approach the security dashboard with the mindset that these are *potential* vulnerabilities, meaning that they don’t automatically translate to a threat or bug in your app. You can see it as a map that guides you towards points that are worth reflecting on, but it’s not the purpose of all apps to keep all information strictly secure: as a Bubble developer, it’s still your responsibility to identify what and when page and data should be available to any given user.

Similarly, it’s important to remember that due to the vast variety of apps built on Bubble, the security dashboard cannot test for or identify every possible security concern. As a developer, it’s ultimately your responsibility to review your app’s structure and ensure it aligns with your desired level of security. While the security dashboard serves as a powerful tool to highlight potential vulnerabilities, its findings should complement—rather than replace—your own thorough testing and implementation of security best practices.

Before running your first security dashboard test, we recommend reading through the Security section in the User Manual. This foundational overview of Bubble’s security mechanics will help you better interpret the test results, equipping you with the context needed to make informed adjustments to your app’s security settings and design decisions.

Article series: [Security](/help-guides/security.md)

{% content-ref url="/pages/Bpyd6CsvbNEEjqznl3Gu" %}
[Issue explorer](/help-guides/security/security-dashboard/security-tests/issue-explorer.md)
{% endcontent-ref %}

{% content-ref url="/pages/xMPMAXlcGMYDBpgDTgYW" %}
[Issue details](/help-guides/security/security-dashboard/security-tests/issue-details.md)
{% endcontent-ref %}


---

# 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://manual.bubble.io/help-guides/security/security-dashboard/security-tests.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.