Join our Newsletter — 33% off our NHI Course
Home› FAQ› Cyber Security› What is the difference between a SAN certificate…
Cyber Security

What is the difference between a SAN certificate and issuing separate certificates for each website?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated November 3, 2026 Domain: Cyber Security

A SAN certificate can cover multiple domains, subdomains, IP addresses, or other supported identifiers under one certificate, while separate certificates require one issuance per site. The SAN model reduces administrative overhead and can improve consistency across a multi site estate. Separate certificates may be simpler in small environments, but they scale poorly as sites multiply.

Why a SAN Certificate and Separate Certificates Behave Differently

A SAN certificate is designed to present multiple identifiers under one trust object, so the same private key and certificate chain can validate several websites at once. Separate certificates keep each site isolated at issuance time. That difference changes how you manage renewals, inventory, and consistency across a fleet, especially when sites share hosting, tooling, or operational ownership.

For a small estate, separate certificates can feel straightforward because each site is handled independently. As the number of sites grows, the SAN model usually becomes easier to operate because you renew and deploy one certificate instead of many. The trade-off is that the trust object is broader, so one certificate lifecycle mistake can affect more than one site.

That operational difference is why teams often treat SAN certificates as a scaling choice, not just a naming choice. The question is less about whether both approaches are valid, and more about whether you want one certificate to represent a broader service boundary or prefer tighter separation between individual sites and their deployment cycles.

Operational Trade-Offs Across a Multi-Site Estate

Separate certificates reduce the blast radius of a certificate-specific mistake. If one site needs to be reissued, revoked, or replaced, the others do not automatically inherit that operational event. The downside is overhead: more renewals, more inventory to track, more expiry dates to watch, and more chances for drift between sites that should be governed the same way.

SAN certificates reduce that administrative burden by centralising the lifecycle. That makes them attractive when domains, subdomains, or supporting identifiers are owned by the same team and follow the same control plane. They are less attractive when different sites have different owners, different release schedules, or different risk tolerances, because the shared certificate can become an unwanted dependency.

The practical choice often comes down to how much common governance exists across the sites. If they are updated together and secured together, a SAN certificate can simplify operations. If they are independent products or environments, separate issuance may fit the organisational reality better even if it costs more to maintain.

What the Certificate Design Changes for Governance and Failure Response

Certificate structure changes how you think about ownership, renewal, and response. A SAN certificate requires clear responsibility for every included name, because any change to that certificate affects all covered sites. Separate certificates make ownership boundaries more explicit, which can help when different applications, teams, or vendors manage their own release and rotation schedules.

In practice, the main governance question is whether the certificate reflects a real shared trust boundary. If it does, SAN coverage can be efficient. If it does not, shared issuance can hide dependency problems until renewal time or until a site is added, removed, or compromised. The right model is the one that matches the operational boundary you can actually defend.

For readers who want the underlying certificate mechanics, the PKI Basics Guide covers how trust chains, subject alternative names, and validation work together in practice. If you are managing certificate lifetime at scale, the Machine Identity, PKI and Certificate Lifecycle Guide is the better fit for renewal, expiry, and automation decisions.

Risk and Threat Considerations

Broader certificates concentrate operational risk. If a SAN certificate is misissued, mishandled, or exposed, the impact can extend across every site that depends on it. Separate certificates limit that exposure, but they increase the number of objects that can expire, be misconfigured, or be forgotten.

Failure mechanism: Shared issuance increases blast radius, while separate issuance increases lifecycle complexity and the chance of inconsistent renewal or revocation handling.

Impact: A shared certificate problem can take multiple sites out at once, while fragmented certificate management can create outages, weak governance, or uneven security posture across the estate.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-57, CSA Cloud Controls Matrix, NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-57Key ManagementCertificate choice affects lifecycle handling, renewal, and rotation at scale.
Recommendation — Align certificate issuance and renewal to a defined key lifecycle and cryptoperiod policy.
CSA Cloud Controls MatrixIAM — Identity & Access ManagementCertificate usage is part of identity and trust management for websites and services.
Recommendation — Manage certificate-bound trust and rotation as part of IAM governance.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementCertificates function as authenticators whose issuance and rotation must be controlled.
Recommendation — Control certificate issuance, renewal, replacement, and revocation under authenticator management.
ISO/IEC 27001:2022A.8.24 — Use of cryptographyCertificate deployment is a cryptographic control that needs governed use and lifecycle handling.
Recommendation — Define how certificates are issued, protected, renewed, and revoked under cryptographic controls.
CIS Controls v8CIS-5 — Account ManagementCertificate sprawl and renewal ownership create governance overhead similar to account lifecycle management.
Recommendation — Track certificate ownership, renewal responsibility, and removal as part of asset lifecycle governance.

Practitioner Guidance

What to verify: Confirm whether the sites share the same owner, deployment path, and renewal process before choosing SAN coverage. If the answer is no, separate certificates are usually the cleaner governance model even when SAN looks simpler on paper.

Decision rule: Use SAN when the domains behave like one managed service boundary; use separate certificates when each site needs independent lifecycle control, rollback, or revocation. That rule matters more than raw certificate count.

What good looks like: Your certificate model should mirror your operational model. If you cannot explain who owns every name on a SAN certificate, the design is probably too broad for your current governance.

For issuance and trust expectations, the CA/Browser Forum is the relevant baseline reference for publicly trusted certificate practices, and the NIST SP 800-57 Key Management guidance is useful when certificate lifecycle handling becomes the real operational issue.

Practitioner takeaway: Choose SAN for shared lifecycle efficiency, not because it is inherently simpler, and choose separate certificates when independence, isolation, or different owners matter more than consolidation.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 3, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org