Beat SSL Certificate Renewal Fatigue with Microsoft Certificate Services

I recently realized that not everyone is aware that there is an option to run your own Certificate Authorities internally.  Not all situations call for you to purchase a commercial SSL certificate.  If you are running internally facing systems and have control of the clients that access those systems, standing up Microsoft Certificate Services might be a viable option.

What does it cost?

  • You’ll need at least two Windows Server licenses to follow best practices
  • Virtual or physical hardware to install onto.

What are the benefits?  

  • Depending on your licensing and if you already have a virtual environment to add these servers to, this is a pretty low cost solution.
  • Certificates issued through your own Certificate Authorities are not held to the certificate lifetime rules that publicly issued certificates are.   You can choose to adhere to those lifetimes, but you don’t have to.
  • Domain joined systems and Azure joined systems can have the trusted root and issuing CA(s) certificates automatically pushed to them so that they trust certificates issued from your CA(s)

What does a best practice deployment look like?

  • You install one server as your Root CA and keep it non domain joined and offline once configured
  • You install the other server as your Issuing CA (or Subordinate CA is another name for it).  This one is domain joined and stays online to issue all of the certificates needed by your endpoints.
  • If you want redundancy you can have two Issuing CAs.
  • Never take the default CA name during the install.  It uses the server name which will make no sense later if you have to migrate to a new OS.
  • CAs should never be installed on a server with another role, like a domain controller.  You keep them separate for security reasons.
  • By default the Certificate Revocation location for issued certificates is an LDAP location.  In other words it is stored in Active Directory.  If you have non domain joined devices you’ll want to have an http location defined as well.
  • Domain
  • If you want to add a security layer your CAs and your IIS server can run Windows Core.  In this scenario you manage them from a jump box using either the MMC CA tool or PowerShell.

If you are currently purchasing certificates for internal systems, Microsoft PKI might be something you want to take a look at.  Especially as the public certificate lifespan drops from 200 days to 47 days in 2029.

Have questions or need assistance setting this up?  Contact me or one of my colleagues at https://trc-group.com/contact

What’s your Reaction?
+1
0
+1
0
+1
0

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top