> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/digital-identity-use-cases/operations.md). # Operations Issuing the first credential is the start, not the finish. A digital national ID must stay accurate, secure and supported for as long as citizens rely on it. ## **Credential status and revocation** The issuer maintains a published status list for every credential it has issued. When a credential is suspended or revoked, because details changed, a device was lost or fraud was detected, the list is updated promptly. Relying parties and the identity provider check this list at every verification, so a revoked credential stops working everywhere at once. ## **Keeping the credential in step with the registry** The registry remains the source of truth. When a citizen's record changes, the issuer is notified, the old credential is revoked, and an updated credential is offered to the citizen. Agreeing how quickly this must happen is part of the trust framework. ## **Key management** The issuer's signing keys are the root of trust for every credential. They are kept in hardware security modules, rotated on a set schedule, and published so verifiers can always find the current and recent keys. A documented procedure covers a suspected key compromise, including revoking affected credentials and re-issuing. ## **Recovery and support** Citizens need a clear route to report a lost phone, recover their wallet on a new device, correct their details, or dispute a disclosure. Support should be available through the same channels the ID authority already uses, including assisted counters, with the face match used again where the credential must be re-issued. ## **Security and assurance** Wallets are certified against the trust framework before they are listed as trusted, and re-assessed when they change. Issuer systems, face-matching components and the identity provider are subject to regular independent security audits and penetration tests. An incident response plan sets out who acts, and how citizens and relying parties are informed. ## **Monitoring and measuring success** Operators track the health of the system and whether it is delivering value. Useful measures include: * Credentials issued and actively used. * Face-match success rates and the reasons for failure. * Sign-ins by path (OTP and wallet) and the services they reach. * Revocations, re-issuances and the time taken to process them. * Support requests and how quickly they are resolved. ## **Growing over time** The same wallet and trust infrastructure can later carry further credentials, from other authorities or sectors, and integrate with other digital public services such as e-signatures and payments. Planning for this from the start keeps each addition incremental rather than a new build. --- # 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://experience-digital-transform.gitbook.io/experience-digital-transformation/digital-identity-use-cases/operations.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.