A private root and issuing CA on audited DigiCert or Sectigo infrastructure, issuing certificates that only your devices trust. XcellHost designs the hierarchy, runs enrolment and renewals, and bills you in rupees.
Security for Private CA is built into how the service is delivered, not bolted on afterwards. Certificates are issued from publicly trusted roots and tracked through their whole lifecycle, because the common failure is not weak crypto but an unnoticed expiry.
XcellHost is ISO 27001 and ISO 20000-1 certified · Indian Tier-4 datacenters · DPDPA and RBI aligned · 24×7 NOC and SOC.
Private CA gave us a clearer way to handle unlimited internal certs. The rollout was well organised, and the support team stayed responsive throughout.
We chose Private CA because your trust hierarchy mattered to our team. It now fits naturally into our day-to-day workflow.
The biggest improvement with Private CA has been automation-ready. We have better clarity, dependable support and fewer operational surprises.
A certificate authority that only your organisation trusts. It has its own root and one or more issuing CAs, and it issues certificates for internal servers, users and devices. Because its root is not in public browser or operating-system trust stores, its certificates are trusted only by devices where you install that root.
A public certificate chains to a root that every browser trusts, so it must follow CA/Browser Forum rules: registered domain names only, validated ownership and a maximum lifetime that is now 200 days. A private certificate follows your own policy — internal names, private IPs, custom key usages and longer lifetimes are all allowed — but only your managed devices trust it.
That is by design. Your root is distributed only to your own devices through Group Policy, Intune or MDM. Anything public-facing — your website, customer portals, public APIs — should keep using a publicly trusted certificate. The decider on this page shows which systems belong where.
Self-signed certificates have no common root, no revocation and no lifecycle tracking, so users learn to click through warnings and attackers can impersonate internal services. A private CA gives every internal certificate one trusted chain, CRL and OCSP revocation, and automatic renewal.
No. A hosted management platform can sit over AD CS so Microsoft and non-Microsoft certificates live in one inventory with the same policies and alerts. When you are ready, we plan a phased migration to the hosted private CA, template by template.
In a hardware security module operated by the vendor, behind layered, multi-person access controls, and kept offline except to sign issuing CAs. On the Dedicated edition the HSM is single-tenant; where the platform supports on-prem, it can sit in your own data centre.
ACME for servers and Kubernetes, SCEP for phones and network gear (often via Intune or another MDM), EST for devices and Linux, Windows auto-enrolment through AD, a REST API for your own apps, and manual CSR upload. Exact connectors depend on the platform; we confirm them for your stack.
Windows devices receive it through Group Policy or Intune, Macs and phones through an MDM profile, and Linux servers through configuration management. We prepare the packages and verify coverage before the first certificate goes live.
Explore practical guides and expert insights on cloud, cybersecurity and Indian compliance to help your business move forward.
New insights are on the way. Explore all insights for more guides and articles.
FREE Consultation · FREE Demo · FREE Trial · 24×7 support in English & Hindi
