Documentation (how it works) — Twingate

Cited by

Facts read from this source

• Components Report an error

  “Twingate relies on four components—the Controller, Clients, Connectors and Relays—that together ensure that only authenticated users are able to access the Resources that they have been authorized to access.”

• Fqdn ip access Report an error

  “authorized users can connect to any Resource using its FQDN or IP address—with addressing local to the Resource on the Remote network—without needing to know anything about the underlying network configuration or even what Remote network the Resource resides on.”

• Controller data flow Report an error

  “The Controller is the only component that does not interact with any data flow.”

• Controller hosting Report an error

  “The Controller, with full redundancy and clustering, runs as a Twingate-hosted, multi-tenant service.”

• Controller idp delegation Report an error

  “The Controller always delegates user authentication to a third party identity authority.”

• Least privilege acls Report an error

  “Client ACLs represent the discrete set of Resources that a given user is allowed to access and as such are the “least privileged access” representation of what the user is entitled to.”

• Acl intersection Report an error

  “traffic can only be forwarded to a Resource if it falls in the intersection set between the two ACLs.”

• Client protocols Report an error

  “The Client uses a transparent proxy to forward traffic for any TCP or UDP port/protocol to protected Resources.”

• Client local dns Report an error

  “DNS requests are forwarded for resolution to the Remote network Connector. This means that DNS lookups for protected Resources are always resolved locally even though the Client is on a different network.”

• Client tls tunnel Report an error

  “Establishing a certificate-pinned TLS tunnel with the appropriate Connector. The Client is responsible for establishing an encrypted tunnel with the appropriate Connector to access a protected Resource.”

• Connector deployment Report an error

  “The Connector is intended to be deployed behind the firewall of a private Remote network.”

• Connector outbound relay Report an error

  “it maintains active outbound connection(s) with at least one Relay.”

• Connector dns Report an error

  “For inbound connections for FQDN Resources, local DNS resolution is performed by the Connector before forwarding traffic to the resolved IP address.”

• Peer to peer Report an error

  “Twingate always attempts to establish a peer-to-peer connection between the Client and Connector in order to provide low latency access to Resources. Relayed connections are used as a backup method.”

• Relay no data Report an error

  “No data or network-identifiable information is stored in the Relay and no data-carrying connections are terminated at the Relay.”

• Connector anonymous id Report an error

  “This Connector ID is the only identifying information that is ever shared with Twingate Clients.”

• Zero trust design Report an error

  “no single component can independently make a decision to allow traffic to flow to another component or Resource in your Remote networks. Authorization for user access or data flow is always confirmed with a second—or even with a third—component depending on the sensitivity of the decision being authorized.”

1 fact read from this page is not shown because it could not be confirmed on the page as captured.

Scores citing this record

• The DevOps Engineer Access model & connectivity
• The DevOps Engineer Identity, access policy & device posture
• The DevOps Engineer Architecture, reliability & security assurance
• 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 Architecture, reliability & security assurance
• The MSP Technician Access model & connectivity
• The MSP Technician Identity, access policy & device posture
• The MSP Technician Architecture, reliability & security assurance
• The Operations Manager Access model & connectivity
• The Operations Manager Identity, access policy & device posture
• 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 Architecture, reliability & security assurance
• The Skeptic Access model & connectivity
• The Skeptic Identity, access policy & device posture
• The Skeptic Architecture, reliability & security assurance