Internal Web systems carry more important business data and sensitive information. Deploying firewalls at network boundaries or continuing to use unencrypted HTTP does not adequately protect data in transit across an intranet.
Organizations commonly face several challenges when deploying intranet HTTPS:
Zotrus HTTPS Automation Gateway (Intranet Edition) consolidates MiniCA-based certificate self-supply, HSM-protected sub-CA keys, HTTPS cryptographic processing, traffic forwarding, and Web protection in a dedicated gateway. Together with pre-established ZT Browser trust, it helps organizations deploy intranet HTTPS and advance cryptographic modernization with lower implementation and operational overhead.
Zotrus HTTPS Automation Gateway (hereinafter referred to as Zotrus Gateway) is an innovative product that has obtained China Commercial Cryptography Product Certification. It enables HTTPS encryption for Internet-facing websites and web systems through automated deployment without requiring modifications to existing applications or infrastructure. To automatically obtain and configure SSL/TLS certificates for customer websites, the Gateway connects to the Zotrus Cloud SSL Service. Therefore, the Internet Edition is designed for websites and web systems accessible from the Internet and is not suitable for isolated intranet environments without Internet connectivity.
However, intranet environments also require HTTPS encryption and automated certificate management to protect internal web traffic. To address this need, Zotrus Technology has developed a dedicated edition of the HTTPS Automation Gateway for intranet deployment. Based on the same core technology, Zotrus HTTPS Automation Gateway (Intranet Edition) or named as Zotrus Intranet HTTPS Automation Gateway, enables automated HTTPS certificate management and encryption entirely within an intranet environment, without relying on external cloud services.

Zotrus HTTPS Automation Gateway (Intranet Edition) is a dedicated HTTPS automation and security appliance for intranet Web systems used by government agencies, financial institutions, and medium-to-large enterprises. It integrates a MiniCA and an embedded PCIe HSM that protects the SubCA private keys, enabling autonomous issuance and management of dual RSA OV and SM2 OV certificates within the local network. The Organization (O) field in both certificate types is set to the deploying organization's name.
Deployed between users and existing Web servers, the gateway centrally handles HTTPS encryption/decryption and traffic forwarding. The original Web servers do not need to install the server certificates issued by the gateway directly, nor do they need to be upgraded to SM2-capable server software solely to enable gateway-side HTTPS encryption. Actual deployment must be configured and validated according to the existing network topology, traffic paths, application protocols, and security policies.

The Intranet Edition provides certificate self-sufficiency: it can issue and manage intranet certificates without an Internet connection and without relying on recurring external CA services for internal server certificates. The five-year deployment package removes the need for repeated purchases of individual intranet server certificates. Models are differentiated primarily by supported website capacity and CPU capacity for processing HTTPS traffic.
The gateway integrates a MiniCA to issue and manage RSA OV and SM2 OV server certificates locally for intranet websites. The Organization (O) field in both certificate types is set to the deploying organization's name, providing consistent organizational identity across the two cryptographic algorithms. The gateway supports certificate renewal and revocation management for intranet IP addresses, internal domain names, and hostnames.

RSA and SM2 certificates serve different client cryptographic capabilities. Clients that support SM2 can use SM2 connections; clients that do not support SM2 can use RSA according to gateway configuration and protocol negotiation. Algorithm selection depends on client capabilities, server configuration, and negotiation.
The private keys of the gateway's built-in SubCA are protected by an embedded PCIe HSM. Critical CA cryptographic operations are performed within the hardware security boundary, reducing exposure of sensitive CA private keys.
The Gateway does not include a self-signed root CA by default. Its SubCA is issued by an intranet root CA trusted by ZT Browser, ensuring that all intranet SSL certificates are automatically incorporated into the Zotrus Intranet Root Trust System. Alternatively, the SubCA certificate can be issued by the enterprise's existing corporate root CA. A self-signed root CA can also be established upon customer request.
The gateway's built-in SubCA issued SSL certificate is already trusted by ZT Browser. The gateway uses this SubCA to automatically issue and manage intranet TLS/SSL certificates. ZT Browser can validate certificates that meet the applicable chain, usage, and other validation requirements, without requiring organizations to manually deploy the corresponding Root CA certificate to every device running ZT Browser.
The certificate chains for RSA-based and SM2-based Intranet SSL certificates are illustrated below.


In addition, to accommodate specific use cases where an organization's intranet uses public IP addresses and public domain names that cannot be validated, the Zotrus Intranet Gateway can provision two additional SubCAs (SM2 and RSA), each issued by a separate self-signed root CA (Intranet SM2 Root and Intranet RSA Root) that is not trusted by ZT Browser. These SubCAs are used to automatically issue intranet SSL certificates bound to public IP addresses and public domain names for which domain or IP address control cannot be validated.
The certificate chains for RSA-based and SM2-based Intranet SSL certificates are illustrated below.


This pre-established trust relationship significantly simplifies the large-scale deployment of intranet HTTPS. However, the pre-established trust in ZT Browser addresses only the trust deployment within ZT Browser; it does not mean that all other browsers and operating systems will automatically trust the intranet certificate chains. Organizations must deploy the intranet root certificates themselves in accordance with their endpoint management policies. These include the two intranet root certificates trusted by ZT Browser and the two special-purpose intranet root certificates that are not trusted by ZT Browser.
The gateway includes CRL-related functionality for publishing certificate revocation information for retrieval by clients that support the relevant mechanism. The effectiveness of revocation checking depends on whether clients perform CRL checks, whether the CRL distribution point is reachable, and the organization's publication and update policies.
One-time HTTPS Automation Gateway upgrade enables enterprises to address two major challenges in their HTTPS infrastructure: certificate lifecycle automation and post-quantum cryptography migration.
The product supports two hybrid post-quantum key exchange algorithms: X25519MLKEM768 and SM2MLKEM768. Supporting both international and national-cryptography hybrid approaches gives organizations flexibility in selecting cryptographic components and planning migration paths, while reducing dependence on a single algorithm family or implementation ecosystem.
Certificate signature algorithms, key exchange algorithms, and symmetric encryption algorithms perform different roles in the protocol. Actual use of a hybrid algorithm depends on client implementation, TLS version, gateway software version, and the configuration negotiated by both sides.
The built-in CA issues and manages certificates locally within the intranet, reducing dependence on public CAs and cloud-based certificate services. The product specifications list a 90-day server SSL certificate validity period and an 80-day renewal cycle. The applicable certificate policy is subject to the delivered configuration and relevant certificate policies.
The Intranet Gateway is offered as a five-year deployment package. Because RSA OV and SM2 OV intranet certificates are issued and managed autonomously by the built-in MiniCA, organizations do not need recurring purchases of individual intranet server certificates from external CAs. Models are selected primarily according to supported website capacity and CPU capacity for HTTPS traffic processing. Website limits and the exact scope of the five-year package are defined by the selected model and contract.
Zotrus HTTPS Automation Gateway handles HTTPS encryption/decryption offloading and traffic forwarding. This allows backend Web servers to focus more on business processing and enables other security devices in the network to perform their specialized roles.
In an appropriately designed network service chain and deployment topology, responsibilities can be assigned as follows:
The gateway can work alongside existing security devices. Where no standalone WAF is deployed, its built-in WAF can provide Web application protection. The order of devices, whether traffic must be decrypted before or after the gateway, and whether each device can inspect plaintext HTTP content depend on the network topology, device capabilities, and service-chain design.
This structure key value is a clearer division of responsibilities: HTTPS cryptographic processing is no longer distributed across every server, and security devices do not have to perform tasks outside their intended roles.
There are 12 main functional modules of Zotrus HTTPS Automation Gateway (Intranet Edition):
Supports X25519MLKEM768 and SM2MLKEM768 hybrid key exchange, giving organizations flexibility across international and national-cryptography approaches and supporting a resilient, phased transition toward post-quantum cryptography.
Supports RSA and SM2 HTTPS access according to client cryptographic capabilities and gateway configuration, helping organizations maintain interoperability while expanding algorithm choice.
The built-in MiniCA locally issues RSA OV and SM2 OV certificates for intranet IP addresses, internal domain names, and hostnames. The Organization (O) field is set to the deploying organization's name.
The gateway handles HTTPS cryptographic processing, reducing the cryptographic workload on backend servers.
Dynamic connection pooling and connection reuse reduce the number of TCP connections that backend servers need to handle, actual results depend on connection patterns and configuration.
Supports GZIP and Deflate compression to reduce transmitted data and improve bandwidth utilization.
Uses memory caching and storage mechanisms to cache Web content temporarily and reduce backend load.
Supports session persistence based on Cookie and source IP. Load balancing supports Round Robin, Weighted Round Robin, Least Connections, and IP Hash strategies.
Supports secure delivery scenarios using TCP, UDP, DTLS, and SSL/TLS channels, as applicable.
Supports mutual authentication using certificates on SKF-standard USB Keys, as well as RSA/SM2 client certificate authentication. Client compatibility should be verified in the target environment.
Based on BIND 9 DNS, supports DNS over HTTPS (DoH) and allows SSL/TLS certificates to be configured for DoH services.
Provides Web application protection and supports custom WAF rules. The specific rule set and protection scope depend on the product version and configuration.
Deploy the gateway in the traffic path between users and existing Web servers. The gateway provides HTTPS access, certificate management, and traffic forwarding. Before deployment, assess DNS resolution, routing, backend connection methods, certificate trust distribution, and business traffic paths. Validate the configuration before switching production traffic.

Recommends a two-gateway deployment and an Active-Active operating mode: both appliances process business traffic, and if one appliance fails, the other can take over its traffic. The specific high-availability mode, state synchronization, traffic distribution, and failover behavior must be confirmed against the delivered version, configuration, and site network conditions.
For intranet Web systems hosted in other data centers or branch offices, the gateway can use local forwarding or remote backend access, depending on network connectivity. Remote backend links should use HTTPS or another approved encryption method as required by the security policy, so that protection for both client-to-gateway and gateway-to-backend connections meets the organization's requirements.

For government platforms or large enterprises with many Web systems across internal and external networks, multiple gateways can be deployed as a cluster to distribute HTTPS offloading and WAF processing and provide redundancy according to the design. Cluster size and failover scope should be planned based on performance requirements, network architecture, and business capacity.

Model selection should consider target concurrency, TLS/TLCP handshake rates, throughput, interface types, certificate capacity, and business traffic growth in the next 5 years.
*Maximum throughput is based on four-port aggregation (MG-1-3 aggregates 4 Gigabit ports, while the rest are aggregated as 4 10-Gigabit ports, supporting more port aggregation). Actual performance depends on traffic characteristics, cryptographic algorithms, security policies, and deployment configuration. *
** All models can be expanded with 8 gigabit ports or 8 10-gigabit ports except MG-1-3.
The gateway supports dedicated ECC and SM2 certificate autoconfigurations for website domains. The specific certificate-related parameters are as follows:
Each website can have its own certificate and private key. The gateway purchase includes five years of certificate automation service for the supported certificate configurations and website capacity. Hardware maintenance fees will be charged after five years.
Hardware and deployment configurations can be customized according to specific throughput, website capacity, cryptographic processing, network interface, and infrastructure requirements.
Contact Zotrus for detailed technical specifications and configuration recommendations.
Zotrus HTTPS Automation Gateway (Intranet Edition) is suitable for organizations that need to automatically implement HTTPS encryption and certificate management for multiple websites or business systems within the intranet. Typical scenarios include:
Provide automated intranet HTTPS, RSA/SM2 access, and centralized certificate management for government platforms, office systems, business portals, and cross-department Web applications.
Provide centralized HTTPS offloading, certificate lifecycle management, and security infrastructure integration for internal business Web systems and management platforms.
Standardize HTTPS encryption and WAF protection for internal Web systems distributed across departments, campuses, data centers, and branch offices.
Use the built-in CA for local certificate issuance and management in environments that cannot connect to the Internet or should not depend on external cloud certificate services.
Provide gateway-side infrastructure for organizations deploying SM2 HTTPS, evaluating hybrid post-quantum key exchange, and progressively upgrading their cryptographic systems.
Zotrus HTTPS Automation Gateway (Intranet Edition) works with existing browsers and client applications. Deploying the gateway does not require an organization to replace its current browsers. ZT Browser is a free optional companion client for organizations seeking pre-established trust in the Zotrus Intranet Root CA, broader cryptographic agility, and clearer visibility into website security attributes.
Based on Chromium, ZT Browser retains a familiar browsing experience while adding capabilities focused on cryptographic agility and digital trust. It is not a prerequisite for operating the gateway; it is a complementary client-side offering from Zotrus.
ZT Browser presents client-side cryptographic capabilities, website identity, and security status information. The gateway handles server-side certificate automation, HTTPS processing, and traffic protection. Together, they provide client/server-side capabilities that complement each other, while remaining independently deployable and usable.
Zotrus HTTPS Automation Gateway (Intranet Edition) integrates automated RSA OV + SM2 OV certificate issuance, PCIe HSM-protected SubCA private keys, pre-established browser trust, HTTPS encryption/decryption offloading, traffic forwarding, and Web protection in a dedicated gateway. Its self-sufficient intranet certificate model eliminates recurring purchases of individual intranet server certificates and supports predictable planning through a five-year deployment package.
From intranet HTTPS deployment and RSA/SM2 certificate automation adoption to hybrid post-quantum key exchange, organizations can plan cryptographic modernization around a unified gateway architecture. The gateway can also work with existing firewalls, IPS, WAF, Anti-DDoS systems, and load balancers as part of a network service chain.
Core value proposition: Intranet certificate self-sufficiency | PCIe HSM-protected SubCA keys | Dual RSA OV + SM2 OV certificates with the organization's name in the O field | Pre-established ZT Browser trust | Five-year deployment package | Model selection by website capacity and HTTPS processing capacity.
Discover how Zotrus HTTPS Automation Gateway (Intranet Edition) can simplify intranet certificate management, modernize intranet cryptographic capabilities, and improve the efficiency of intranet website security infrastructure.
Contact Zotrus for Product Information and Deployment Consultation.