A certificate outage is a service disruption caused when a digital certificate expires, is misconfigured, or becomes invalid. The impact can be immediate because encrypted connections fail, applications stop trusting each other, and customer-facing or internal systems lose secure connectivity until the certificate problem is corrected.
Expanded Definition
A certificate outage is more than a simple expiry event: it is the loss of trusted encrypted communication when a digital certificate is invalid, misissued, revoked, mismatched to the hostname, or allowed to lapse. In NHI and workload identity environments, the term covers both public-facing TLS certificates and internal certificates used for service-to-service authentication, mTLS, and automated trust relationships. Definitions vary across vendors on whether a renewal failure, a chain trust problem, or a revocation-check failure qualifies, but operationally the impact is the same: systems stop trusting each other and secure sessions fail. This is closely related to certificate lifecycle management, which is treated as a governance and resilience issue in the NIST Cybersecurity Framework 2.0 and in NHI programs that track certificate ownership, renewal windows, and deployment scope. NHIMG research shows that certificate expiry is the leading cause of outages for 45% of organisations, underscoring how often this becomes an availability problem before it is recognised as an identity control failure. The most common misapplication is treating certificates as a one-time deployment task, which occurs when ownership, rotation, and renewal monitoring are not assigned to a real operational process.
Examples and Use Cases
Implementing certificate management rigorously often introduces operational overhead, requiring organisations to weigh stronger trust assurance against the cost of inventorying every endpoint, service, and automation path that depends on it.
- A customer portal goes offline at midnight because its public TLS certificate expires and the load balancer rejects new sessions.
- A payment service cannot complete mTLS handshakes after an internal CA rotation, so downstream APIs stop accepting traffic.
- A CI/CD pipeline fails because the signing certificate for package verification was replaced without updating the pipeline trust store.
- A microservice mesh loses east-west connectivity after a certificate chain is misconfigured, even though each workload is otherwise healthy.
These failures are especially painful in large machine-identity estates, where visibility is often incomplete. NHIMG notes that only 5.7% of organisations have full visibility into their service accounts, and the same visibility gap usually applies to certificates tied to those accounts. That is why certificate outages should be read through the lens of workload identity as described in the Ultimate Guide to NHIs — What are Non-Human Identities. For implementation detail, teams often align certificate automation with NIST Cybersecurity Framework 2.0 outcomes for asset management, access control, and resilience.
Why It Matters in NHI Security
Certificate outages are a direct availability and trust failure in NHI security because certificates are the proof mechanism that many machines use to authenticate, encrypt, and authorize one another. When they fail, incident responders often discover hidden dependencies, undocumented service accounts, and unmanaged rotation paths that had been operating without clear ownership. That is why certificate control belongs in the same governance conversation as secrets management and workload identity. NHIMG research shows that 53% of organisations have experienced a security incident directly related to machine identity management failures, and certificate breakdowns are one of the most visible ways those failures surface. The issue is not only expiry; it is the absence of lifecycle discipline, which is reinforced by findings in The Critical Gaps in Machine Identity Management report. When certificate handling is weak, even well-designed Zero Trust controls can be undermined by simple trust-chain failures. Organisations typically encounter the business impact only after an outage interrupts production traffic or breaks internal service authentication, at which point certificate management becomes operationally unavoidable to address.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 and CSA MAESTRO address the attack and risk surface, while NIST CSF 2.0, NIST Zero Trust (SP 800-207) and NIST SP 800-63 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-01 | Covers lifecycle failures and trust issues in machine identity and certificate management. |
| NIST CSF 2.0 | PR.AC-1 | Certificate trust is part of identity proofing and access control for systems and services. |
| NIST Zero Trust (SP 800-207) | SC-10 | Zero Trust depends on strong, continuously validated machine authentication and secure channel control. |
| NIST SP 800-63 | AAL2 | Assurance guidance informs how strong an authenticator must be when certificates back machine access. |
| CSA MAESTRO | Agentic and workload systems rely on secure, managed machine trust and certificate lifecycle discipline. |
Treat certificates as continuously verified trust signals and replace them before they break service access.
