TLS/SSL Certificate Management for Indian Businesses

TLS/SSL certificates are the backbone of secure communication on the internet — they encrypt data in transit, authenticate your server's identity, and guarantee message integrity. For Indian businesses, a misconfigured or expired certificate does not just break the padlock icon; it triggers browser warnings that destroy conversion rates, exposes customer data to interception, and can constitute a breach of the DPDP Act 2023. This guide explains what TLS actually does, the certificate types you need to know, and the operational controls that prevent outages and failed audits.

What TLS Actually Does — Encryption, Authentication, Integrity

TLS (Transport Layer Security) is the protocol; SSL is its deprecated predecessor, but the term persists colloquially. Three security properties are established during the handshake:

Encryption — Data exchanged between browser and server is encrypted using symmetric session keys. An attacker sniffing the wire sees ciphertext, not plaintext credentials or payment data.

Authentication — The server presents a digital certificate signed by a trusted Certificate Authority (CA). The browser verifies the chain up to a root CA in its trust store, confirming the server is who it claims to be.

Integrity — Every TLS record includes a Message Authentication Code (MAC). Tampering with a single byte causes the MAC check to fail and the connection to close.

Without TLS, any attacker on the same network — hotel Wi-Fi, corporate proxy, ISP — can read and modify traffic in real time.

The TLS Handshake in Plain Terms

In TLS 1.3 (the current standard), this handshake completes in one round trip, reducing latency compared to TLS 1.2. NIST SP 800-52 Rev. 2 mandates TLS 1.2 as the floor for US federal systems and recommends TLS 1.3 — the same guidance is widely adopted as a baseline by security-conscious organisations globally.

Certificate Types — Which One Does Your Business Need

Not all certificates are equal. The type you choose affects validation depth, browser trust indicators, and what domains are covered.

The Certificate Authority Trust Model

Every browser and OS ships with a list of trusted root Certificate Authorities — around 150 globally. When your server presents a certificate, the browser walks the chain: Leaf cert → Intermediate CA → Root CA. If every signature in that chain is valid and the root is in the trust store, the connection proceeds.

The CA/Browser Forum (CABForum) governs the rules CAs must follow — certificate lifetimes, validation procedures, revocation requirements. Their Baseline Requirements are publicly available and are the reason your cert issuer cannot simply claim to verify your identity without actually doing so.

Chain of trust failures are a common misconfiguration: you install your leaf certificate but forget to include the intermediate CA certificate. The browser cannot complete the chain and throws an error — even though your cert itself is perfectly valid.

Why Expired and Misconfigured Certs Cause Real Damage

An expired certificate is not a minor inconvenience. Modern browsers display full-page blocking warnings with no easy bypass on mobile. For an Indian e-commerce or fintech site, even 30 minutes of such a warning during peak hours means abandoned carts and support tickets.

Beyond UX, misconfigured TLS creates direct security exposure:

1. TLS 1.0 / 1.1 — Both are deprecated by the CABForum and disabled by default in all major browsers since 2020. If your server still negotiates these versions for legacy clients, you expose users to POODLE, BEAST, and related downgrade attacks.
2. Weak cipher suites — RC4, DES, 3DES, and anonymous cipher suites provide little or no real security. NIST SP 800-52 Rev. 2 provides an approved cipher suite list. Any VAPT or SSL scan will flag these immediately.
3. Missing HSTS (HTTP Strict Transport Security) — Without the Strict-Transport-Security header, a user who types your domain without https:// is briefly vulnerable to SSL stripping attacks. HSTS tells the browser to always use HTTPS, even for the first request.
4. Mixed content — Serving HTTPS pages that load HTTP sub-resources (images, scripts, fonts) downgrades the security of the page and causes browser console warnings that erode the trust signal of your HTTPS padlock.
5. Self-signed certificates on production — Bypass CA validation entirely and expose users to trivial impersonation.

Automation with ACME and Let's Encrypt

The industry is moving decisively toward short-lived certificates. Let's Encrypt pioneered 90-day certificates. In March 2025, the CA/Browser Forum passed Ballot SC-081, which phases down maximum certificate validity to 47 days by March 2029. The rationale is simple: shorter validity limits the window of exposure if a private key is compromised and revocation cannot happen quickly. If you rely on manually renewed annual certificates today, the industry is mandating automation by the end of the decade.

The ACME protocol (Automatic Certificate Management Environment, RFC 8555) is the standard mechanism for automating certificate issuance and renewal. Let's Encrypt is the most widely used ACME CA. Certbot, acme.sh, and Caddy all implement ACME clients that:

1. Prove domain control to the CA (DNS-01 or HTTP-01 challenge).
2. Request a certificate.
3. Install it automatically.
4. Schedule renewal before expiry (typically at 60 days remaining for a 90-day cert).

Certificate Inventory and Expiry Monitoring

Organisations with more than a handful of domains frequently lose track of certificates installed by team members who have since left. A certificate expiring silently at 2 AM is entirely preventable.

Practical controls:

1. Centralised inventory — One record per certificate: domain, issuer, expiry date, owner, auto-renewal status.
2. Expiry alerts — Alerts at 60 days, 30 days, and 7 days. AWS CloudWatch, GCP, and Azure all support this natively.
3. Certificate Transparency monitoring — Every public CA logs issued certificates to CT logs. Monitoring these logs for your domain alerts you to unauthorised issuance — an early signal of domain hijacking.
4. Automated TLS scans — Periodic scanning validates more than expiry: cipher suites, protocol version support, HSTS, OCSP stapling, and chain completeness in a single pass.

CAA Records — Often Overlooked, Highly Effective

Certification Authority Authorization (CAA) is a DNS record type (RFC 8659) that specifies which CAs are authorised to issue certificates for your domain. Every CA is required by CABForum Baseline Requirements to check the CAA record before issuance.

A minimal CAA record set:

bachao.ai.  CAA  0 issue "letsencrypt.org"
bachao.ai.  CAA  0 issuewild "sectigo.com"
bachao.ai.  CAA  0 iodef "mailto:ceo@bachao.ai"

Only Let's Encrypt can issue standard certs; only Sectigo can issue wildcards. Any other CA is blocked. The iodef field triggers an email to your security team on a policy violation. CAA records are free to configure and provide meaningful protection against CA misissuance and domain hijacking.

How TLS Issues Surface in a VAPT

A professional VAPT engagement always includes an SSL/TLS configuration review as part of the network and application security assessment. A VAPT scan of your public endpoints will typically check and report on:

1. Certificate expiry and validity
2. Full chain installation
3. Supported TLS protocol versions (flagging 1.0 and 1.1)
4. Cipher suite strength (flagging RC4, DES, 3DES, export-grade ciphers)
5. Key length (RSA 2048-bit minimum; 4096-bit recommended; ECDSA P-256 or P-384 preferred)
6. HSTS presence and max-age value
7. OCSP stapling configuration
8. Mixed content warnings
9. CAA record configuration
10. Certificate Transparency compliance

Bachao.AI, built by Dhisattva AI Pvt Ltd (DPIIT Recognised Startup), automates this layer of TLS and SSL configuration assessment as part of every scan, giving Indian SMBs a clear remediation list without the need to interpret raw scanner output.

For more on securing your web infrastructure and staying compliant with Indian data protection requirements, explore the Bachao.AI blog or see how DPDP-related obligations intersect with certificate and encryption controls at our DPDP compliance guide.

TLS Configuration Baseline Checklist

1. NIST SP 800-52 Rev. 2 — Guidelines for the Selection, Configuration, and Use of TLS
2. Mozilla SSL Configuration Generator — generates server config for Nginx, Apache, HAProxy, and others based on modern best practices.