> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/impl-eidas-wallet/9.-operations-and-continuous-compliance.md).

# 9. Operations and Continuous Compliance

Supervisory bodies require evidence that the wallet remains compliant with eIDAS, GDPR, and national rules. Regular audits examine configuration baselines, source code controls, build pipelines, distribution channels, WSCD usage, and logging practices. Results feed into improvement plans and, where necessary, corrective actions. Incident reporting mechanisms ensure that serious events are communicated to national authorities and, when appropriate, to EU bodies and affected users. Records of incidents, responses, and follow‑up are kept in a way that supports both regulatory review and internal learning.


---

# 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://specs.govstack.global/impl-eidas-wallet/9.-operations-and-continuous-compliance.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.