This site is an archive and is no longer updated.
    Back to ADCS Overview
    Windows ADCSArchitectureNEW

    ADCS Architecture

    Root CA, Issuing CA, and Two-Tier PKI Explained

    10 min readDecember 2025
    LinkedInX
    ADCS Architecture showing Offline Root CA, Issuing/Subordinate CA, and certificate distribution to computers, users, and servers

    Why Two-Tier?

    A properly designed ADCS deployment uses a two-tier hierarchy: an offline Root CA that stays powered off (protected), and an online Issuing CA that handles day-to-day certificate operations.

    The Root CA's private key is the "master key" to your entire PKI. If compromised, every certificate in your organization is suspect.

    One-Tier (Bad)Two-Tier (Good)
    Root CA online, issuing certsRoot CA offline, in a safe
    Root key exposed to networkRoot key air-gapped
    Compromise = game overCompromise issuing CA = reissue from root
    Simple but riskyMore work but recoverable

    Architecture Diagram

    Click on any component to learn more about it:

    Signs
    Issues certificates to:

    Additional Components

    CDP/AIA (CRL Distribution Points / Authority Information Access)

    Where CRLs and CA certificates are published. Usually HTTP and LDAP locations that clients check to verify certificate revocation status.

    OCSP Responder

    Optional component for real-time revocation checking. Faster than downloading CRLs, but adds infrastructure complexity.

    NDES (Network Device Enrollment Service)

    SCEP protocol support for network devices. Allows routers, switches, and mobile devices to request certificates without Active Directory. Learn more →

    Web Enrollment

    Browser-based certificate requests. Useful for manual enrollment when autoenrollment isn't appropriate. Note: Can be a security risk (see ESC8 attack).

    Enterprise vs Standalone CA

    FeatureEnterprise CAStandalone CA
    Active DirectoryRequires AD DSNo AD required
    TemplatesUses templatesNo templates
    AutoenrollmentSupportedManual only
    Best ForIssuing CARoot CA

    Best Practice: Use a Standalone CA for your offline Root (no AD dependency), and an Enterprise CA for your Issuing CA (enables templates and autoenrollment).

    Next Steps

    Related Resources