> For the complete documentation index, see [llms.txt](https://safedpi.gitbook.io/safeguards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://safedpi.gitbook.io/safeguards/universal-dpi-safeguards-framework/processes/o4.7-invite-security-audits-by-third-parties.md).

# O4.7 Invite security audits by third parties

{% tabs %}
{% tab title="Principle" %}
[O4 Assure data security by design ](/safeguards/universal-dpi-safeguards-framework/principles/operational-principles/o4-assure-data-security-by-design.md)
{% endtab %}

{% tab title="Risk" %}
[RS2 Digital insecurity](/safeguards/universal-dpi-safeguards-framework/risks/risks-to-safety.md)

[SV4 Technical shortcomings](/safeguards/universal-dpi-safeguards-framework/risks/risks-to-structural-vulnerabilities.md)
{% endtab %}

{% tab title="Life Cycle Stage" %}
[L5 - Operations and Maintenance ](/safeguards/universal-dpi-safeguards-framework/responsible-authorities/r3-donor/l5-operations-and-maintenance.md)
{% endtab %}
{% endtabs %}

## Practice

* Conduct regular security audits, red teaming exercises, and bug bounty programmes to ensure the continued robustness and security of underlying frameworks.
* Setting clear objectives, engaging skilled ethical hackers, and simulating real-world attacks to test defenses, followed by a thorough debrief to improve security measures.
* Define the scope of eligible systems, selecting a platform or creating an internal submission system, establishing a tiered reward structure for vulnerabilities, and implementing a triage process to review and address findings.
* Continuously monitor and adapt these practices based on feedback and emerging threats.

## Resources

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><mark style="color:yellow;"><strong>References</strong></mark></td><td><a href="https://openfuture.eu/wp-content/uploads/2022/12/TowardsPublicDigitalInfrastructure_v0.2.pdf">TOWARDS PUBLIC DIGITAL INFRASTRUCTURE: A PROPOSED GOVERNANCE MODEL</a></td><td></td></tr><tr><td></td><td></td><td></td></tr></tbody></table>


---

# 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://safedpi.gitbook.io/safeguards/universal-dpi-safeguards-framework/processes/o4.7-invite-security-audits-by-third-parties.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.