What is ShieldGate?

Goal

By the end of this lesson you can explain what ShieldGate is, name its major capabilities, and describe where it sits between the internet and your applications.

The problem ShieldGate solves

Modern applications are exposed to a constant stream of hostile traffic: bots, credential stuffing, injection attacks, volumetric floods, and targeted exploits. At the same time, the network underneath those applications needs segmentation, routing, address translation, and VPN connectivity.

ShieldGate combines both layers in one platform:

• A Web Application Firewall (WAF) and reverse proxy that inspects HTTP(S) traffic before it reaches your apps.
• A network firewall appliance that manages zones, interfaces, routing, NAT, and VPN tunnels.
• A management console and API so everything is configured in one place and published atomically to the data plane.

Core capabilities

Capability	What it gives you
Reverse proxy & gateway	TLS termination, routing to upstreams, load distribution
WAF policies	Rules that block injections, bots, and abusive clients
Network firewall	Zones, interfaces, L3 routing, firewall rules, NAT, VPN
Traffic control	Rate limits, quotas, and per-client shaping
Observability	Live metrics, structured logs, SIEM export
Threat detection	IDS/IPS signatures, threat intel feeds, anomaly detection

Where it sits

Client traffic enters ShieldGate first. The proxy terminates TLS, WAF policies evaluate the request, traffic controls apply, and only clean traffic is forwarded to your upstream applications. On the network side, the appliance enforces zone-to-zone rules for everything else that crosses the wire.

Verify your understanding

• Can you name the two planes ShieldGate operates on (application and network)?
• Can you explain why the proxy must terminate TLS to apply WAF rules?

Tips

• Keep this mental model handy: console configures, API stores, appliance enforces. The rest of the course builds on it.