Changelog
This page tracks the release history of Twingate. Visit our documentation for detailed instructions on Upgrading Connectors and Managed Windows Deployments.
Kandji Integration


Our Device Security integrations now include Kandji! You can now configure Twingate Security Policies so that only Kandji-verified devices can sign into Twingate or access protected Resources. This means organizations using Kandji can opt not to use manual device verification and choose to identify company-managed devices through Kandji instead.
For more information, see our documentation.
WebAuthn support for Two-Factor Authentication


Twingate has expanded its native two-factor authentication capabilities. Twingate now supports authentication with WebAuthn using biometrics and security keys, in addition to our existing time-based one-time password authentication option. Authenticating via methods such as Touch ID or YubiKeys are more secure as they provide device-based two-factor authentication while also offering more ease of use. Users will now be given the option to configure biometrics or security keys for authentication, allowing these methods to be used to meet Twingate’s native two-factor authentication requirements.
For more information, see our documentation.
SentinelOne Integration


We’ve expanded our Device Security integrations to now include SentinelOne. Twingate Security Policies can now be configured so that only SentinelOne-compliant devices can sign into Twingate or access protected Resources. This means SentinelOne users can bypass manual device verification and opt to identify company-managed devices through SentinelOne instead.
For more information, see our documentation.
Archiving and Blocking Devices


Twingate admins can now archive and block devices. Old or decommissioned devices can be archived and hidden from the Admin Console. Lost devices can be blocked so that they can no longer authenticate with or access Twingate.
For more information, see our documentation.
Surfacing additional Connector metadata


We’re now surfacing additional metadata for Connectors, making it easier to troubleshoot issues and understand where a Connector is located in a Remote Network. View a Connector’s uptime, STUN discoverability, hostname, public and private IP addresses, and potential time synchronization issues in the Admin Console. This is available for all Connectors on version 1.44.0
and newer.