Identity Firewall Overview | Twingate

Identity Firewall Overview

Twingate Identity Firewall

Availability

Twingate Identity Firewall is available now for all plans, free for up to 5 Resources.

Twingate Identity Firewall extends Zero Trust and Privileged Access Management controls to every user, resource, and agent in your organization.

Twingate Identity Firewall is available now with support for the Kubernetes API, SSH, and Web Apps, with future support for database protocols and Model Context Protocol (MCP), which enables Identity Firewall to be used with remote MCP servers to facilitate and secure access to tools, resources, and prompt templates.

Key Benefits

Unified Identity Enforcement: Your users authenticate once through your existing IdP. That identity seamlessly passes through to every Resource they access, from Kubernetes clusters to databases to internal APIs.
Dynamic Zero-Standing Access: Access is granted just-in-time, based on identity, device posture, location, and context. Permissions are automatically revoked when no longer needed.
Complete Visibility and Control: Every command, API call, and database query is tied to a specific user or agent with forensic-level detail and session replay capabilities.
Cost-Effective Scale: Deploy comprehensive privileged access controls across your entire environment at a fraction of traditional PAM costs. No hardware appliances. No complex infrastructure requirements.

How Twingate Identity Firewall Works

Identity Firewall introduces the Twingate Gateway, an open-source Layer 7 reverse proxy deployed within your environment. The Twingate Gateway enables identity propagation and session recording within those environments.

Before any request hits your protected environment, Twingate authenticates the user and enforces access policies with no static credentials or separate authentication tokens required.

Getting Started with Twingate Identity Firewall

For more information about deploying and using Twingate Identity Firewall, explore our protocol-specific documentation:

Last updated 2 months ago