# Revocation and Decommissioning Revocation and Decommissioning ensure that certificates are properly invalidated and removed when they are no longer trusted or required. Revocation is critical for responding to security incidents, key compromise, or policy violations. #### Certificate Revocation CERTInext enables revocation by: * Initiating revocation requests with the issuing CA * Updating certificate status in inventory * Reflecting revocation in CRLs and OCSP (where applicable) Revoked certificates are clearly marked and excluded from active lifecycle workflows. #### Decommissioning Decommissioning completes the lifecycle by: * Removing certificates from servers and applications * Cleaning up keystores and certificate stores * Updating inventory status to prevent reuse * Preserving historical records for audit and compliance Decommissioning ensures certificates do not linger in infrastructure after they are retired, reducing security and compliance risks. --- # Agent Instructions: 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: ``` GET https://docs.certinext.io/documentation/certificate-lifecycle-management/revocation-and-decommissioning.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.