Encryption DSC in Koyambedu Metro Depot, Chennai

Statutory form prescribed for Encryption DSC engagements; carries the information set required for filing or submission to the prescribed authority.

Statutory form prescribed for Encryption DSC engagements; carries the information set required for filing or submission to the prescribed authority.

Application Supported by Blocked Amount encryption framework used by Self Certified Syndicate Banks in IPO and FPO applications. Investor's bid details and PAN are encrypted using the registrar's public key to ensure confidentiality of subscription patterns until allotment. Built on the same X.509 PKI infrastructure as DSC, applies to retail and HNI investors equally, governed by SEBI ICDR Regulations.

Reserve Bank of India's online portal for regulatory return filing by banks, NBFCs, AD Bank category-I entities, and certain payment system operators. Requires encrypted submission of returns using RBI-published encryption certificate. Monthly XBRL returns under various RBI Master Directions and FEMA-related returns flow through this channel. Encryption is in addition to the signing DSC and not a substitute.

MCA21 portal encryption for sensitive document uploads such as Form MGT-7 annual return, Form AOC-4 financials, and Form DIR-3 KYC. Built on the same PKI framework as the signing requirement, additionally requires that the upload channel itself uses TLS 1.2 or higher. Self-signed certificates are rejected because MCA21 enforces certificate chain validation against CCA-licensed CAs.

Encryption between an Application Service Provider intermediary and GSTN's API gateway when bulk filing of GSTR-1, GSTR-3B, or GSTR-9 is routed through an ASP-GSP integration. The ASP's encryption certificate is registered on the taxpayer's GSTN profile and used to wrap the return data payload. ASP switch requires re-mapping of the new ASP's encryption certificate on GSTN before bulk filing can resume.

Indian Customs Electronic Commerce Gateway encryption for response messages back to importers and exporters such as assessed Bill of Entry, query messages, and Out of Charge orders. Requires registration of the user's encryption certificate separately from the signing certificate on the IEC holder profile. Without encryption certificate registration, ICEGATE response messages cannot be delivered causing container hold and demurrage.

Section 3A of the Information Technology Act 2000 introduced by 2008 amendment, providing legal recognition to electronic signatures using techniques notified by the Central Government in addition to digital signatures under Section 3. Practical relevance: it widens the legal acceptability of e-signatures beyond DSC, while DSCs continue to be the most robust form because they leverage CCA-licensed CA infrastructure for non-repudiation.

Section 65B of the Bharatiya Sakshya Adhiniyam 2023 (formerly Section 65B of Indian Evidence Act 1872) governing admissibility of electronic records as evidence in court. A document digitally signed with a valid DSC carries strong evidentiary weight under Section 65B because the certificate chain and timestamp create an audit trail. Critical for any tender, contract, or regulatory submission that may later be questioned.

X.509 is the standard format for digital certificates. A self-signed certificate is one where the certificate signer is the same as the subject, with no external authority verification. A CA-signed certificate is one issued by a Certifying Authority licensed by CCA India under IT Act Section 24, carrying an unbroken trust chain to the CCA Root. Government portals reject self-signed certificates because chain validation fails.

Federal Information Processing Standard 140-2 Level 2, a hardware security certification level requiring tamper-evident physical mechanisms and role-based authentication. USB cryptographic tokens like ePass2003 Auto and HYP2003 used for DSC storage in India typically meet Level 2. Defence procurement on GeM and certain CPP Portal categories explicitly mandate Level 2 compliance which rules out soft tokens or .pfx file storage.

Hard token is a physical USB cryptographic device that generates and stores private keys internally with the key never leaving the device. Soft token is a software-based key store such as a .pfx file or Windows Certificate Store entry. Hard tokens are FIPS 140-2 compliant and meet government portal security requirements; soft tokens are convenient but lack tamper resistance and are rejected by defence-category and high-value bidding portals.

A UEFI firmware feature ensuring that during boot only digitally signed bootloaders and operating system kernels execute, blocking rootkits and bootkit malware from compromising the system before security software loads. Critical for laptops used for DSC operations because compromise at boot level can intercept PIN entry and signing operations. Combined with TPM-backed disk encryption it creates a trusted execution environment.

The sequence of certificates from the end entity certificate up through one or more intermediate CA certificates to a trusted root CA. For a DSC issued by a CCA-licensed CA in India, the chain runs from the user's certificate, through the issuing CA's certificate, to the CCA Root. Portals validate this chain at every transaction; a break or missing intermediate causes signature verification failure.