Source
Access model & connectivity — found from sitemap — Pomerium
Checked for Pomerium on 10 Nov 2026
- Page
- https://www.pomerium.com/docs/deploy/clients
- Checked
- 10 Nov 2026, 12:05 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:f0a7b629b9f4b6587d12288e6e55e55decdfbd4634be89a7a23e162a478ae889
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Protocols secured Report an error
“Pomerium can secure non-HTTP protocols such as SSH, RDP, MySQL, Redis, or DNS with the same identity-aware policy enforcement used for HTTP.”
-
VPN replacement Report an error
“Enjoy zero trust-style security without needing a separate VPN or dedicated tunnels.”
-
SSO Report an error
“Single Sign-On (SSO): Unified authentication with your existing IdP.”
-
Authorization policies Report an error
“Granular Authorization: Leverage Pomerium's policies (e.g. allow by email, group membership).”
-
Tcp udp audit Report an error
“Audit & Visibility: Centralize logs and control for non-HTTP traffic.”
-
Tcp route syntax Report an error
“Use tcp+https:// in the route From field and tcp:// in To.”
-
Tcp route port selection Report an error
“The port in From (e.g., :6379) differentiates multiple routes on the same domain, even though requests typically arrive on port 443.”
-
Udp support version Report an error
“Starting with v0.29, Pomerium supports UDP.”
-
Udp route syntax Report an error
“Use udp+https:// in From and udp:// in To”
-
Udp connect udp Report an error
“CONNECT-UDP is used internally, so no HTTP-specific settings apply.”
-
Policy validated at connection Report an error
“When you create a TCP or Websocket connection, Pomerium validates the access policy at the time the connection is made. Currently, there is no mechanism in place to terminate long-running connections if a policy becomes invalid.”
-
Encryption e2e Report an error
“Pomerium encrypts traffic from user to proxy. If you want full end-to-end encryption, ensure the upstream also runs TLS or mTLS.”
-
Tcp proxy chaining Report an error
“If you want Pomerium to send an HTTP CONNECT to another proxy, use an HTTP scheme in To”
-
Cli listen stdin stdout Report an error
“If you use -, the CLI pipes STDIN/STDOUT directly (useful for ssh -o ProxyCommand).”
-
Cli install channels Report an error
“Binaries Packages (RPM/DEB) Homebrew (macOS) Docker Source Build”
-
Desktop os support Report an error
“Windows macOS Linux”
-
Cli client cert auth Report an error
“If provided, pomerium-cli will attempt to use a client certificate from the system trust store (macOS and Windows only)”
-
Cli service account auth Report an error
“--service-account Pomerium service account token to use for authentication.”
-
Mtls support Report an error
“If the upstream requires mutual TLS, both CLI and Desktop can supply client certs.”
-
Connection logging Report an error
“Pomerium logs each connection attempt, including identity. This provides an audit trail.”
-
Session duration tied to pomerium session Report an error
“Non-HTTP connections remain open as long as your Pomerium session is valid.”
-
Unified control plane Report an error
“Pomerium unifies access for HTTP, TCP, and UDP behind a single identity-based control plane.”
-
Desktop advanced settings Report an error
“Pomerium URL: The Pomerium Proxy service address. This is required if the Destination URL can't be resolved from DNS or a local hosts entry, or if the Proxy service uses a non-standard port.”
-
Desktop TLS verification toggle Report an error
“Disable TLS Verification: Allows untrusted certificates from the Pomerium gateway”
-
Desktop route tags Report an error
“Tags: Customizable tags to sort and organize TCP routes”
-
Certificate name filters Report an error
“The certificate name filter syntax is attribute=value. A name filter can accept only one name attribute. The value must be an exact match (not a substring match).”
-
Tcp listen default Report an error
“--listen Local address to start a listener on (default "127.0.0.1:0").”
Scores citing this record
- The DevOps Engineer Access model & connectivity
- The DevOps Engineer Identity, access policy & device posture
- The DevOps Engineer Logs, audit trail & incident response
- The DevOps Engineer Deployment, API & administration
- The IT Lead Access model & connectivity
- The IT Lead Identity, access policy & device posture
- The IT Lead Logs, audit trail & incident response
- The IT Lead Deployment, API & administration
- The IT Lead Architecture, reliability & security assurance
- The MSP Technician Access model & connectivity
- The MSP Technician Identity, access policy & device posture
- The MSP Technician Logs, audit trail & incident response
- The Operations Manager Access model & connectivity
- The Operations Manager Identity, access policy & device posture
- The Operations Manager Logs, audit trail & incident response
- The Operations Manager Deployment, API & administration
- The Operations Manager Architecture, reliability & security assurance
- The Information Security Officer Access model & connectivity
- The Information Security Officer Identity, access policy & device posture
- The Information Security Officer Logs, audit trail & incident response
- The Information Security Officer Deployment, API & administration
- The Information Security Officer Architecture, reliability & security assurance
- The Skeptic Access model & connectivity
- The Skeptic Identity, access policy & device posture
- The Skeptic Logs, audit trail & incident response
- The Skeptic Deployment, API & administration
- The Skeptic Architecture, reliability & security assurance