Advanced Search
Search Results
62 total results found
v8.0
Knocknoc 8.0 Knocknoc 8.0 delivers a powerful set of updates, enhancing validation on connecting clients beyond just source IP addresses through the introduction of Knocknoc Access Tokens for web transactions. Additionally, fine-grained per-Knoc session limits...
Knocknoc client (scriptable login)
To gain access to underlying networks and systems, end-users log in to Knocknoc interactively via the Server component. This provides registered orchestration-Agents information to perform ongoing access provisioning. If you need to script access in a non-int...
HAProxy + KAT
Sometimes IP address restrictions or IP-based allowlisting is not enough, think: airport lounge, CGNat or other large, untrusted NAT environments. That's why Knocknoc extends a reverse-proxy in an innovative way through the addition of Knocknoc Access Tokens. ...
VPNs, internal addresses and access
You may want to limit the ability to access a Knoc, depending on where your user is logging in to Knocknoc from. For example, an internal subnet should only be opened up if the user is connecting from an internal IP address range, or if they are connected to a...
v8.5
Knocknoc 8.5 Knocknoc 8.5 delivers key improvements in usability, integrations, and security, while paving the way for future growth. Security is enhanced through updated server components, Golang and library upgrades, and additional hardening measures, incl...
Redirecting Users
Knocknoc supports a couple of ways to redirect users to and from Knocknoc, which can be useful for when you want users to get where they're trying to go ASAP. Redirecting to a Referrer URL This is the most basic way to redirect users to a custom URL from the K...
Sophos (UTM)
The Sophos UTM device provides firewall and UTM capabilities. Note that this series of devices is being EOL'd by Sophos in favor of the SFOS devices (June 2026), which can also be integrated with Knocknoc following this guide. UTM Configuration Firstly create ...
Sophos (SFOS/XGS)
The Sophos SFOS/XGS based devices provide advanced firewall and UTM capabilities. This replaces the previous UTM devices, which can be integrated here. Knocknoc manages IP addresses within a host-group, it does not edit/change firewall policies, and operates w...
Agent as a Reverse Proxy
The orchestration agent can be configured to reverse-proxy traffic, simply by enabling this mode and completing a few configuration options, you'll be on your way to controlling HTTPS or TCP attack surface, without an additional firewall or other layer beyond ...
v25.12
Knocknoc 25.12 Knocknoc 25.12 is a Windows-first release focused on making Just-In-Time (JIT) access easier to deploy and operate across Windows environments. The headline upgrade is the Windows Agent now managing the local Windows Firewall for true on-host ne...
Knocknoc Reverse Proxy
The Knocknoc orchestration Agent - which is deployed alongside managed infrastructure (not on desktops) - can be converted to an in-line reverse proxy, providing access control at layer-7 (HTTP/HTTPs) or layer-3 for TCP, linked to Knocknoc. This allows the cen...
High availability
A Knocknoc deployment has three parts: the Server (web app), its Database (PostgreSQL), and one or more Orchestration Agents. How you run the first two decides your availability. The Agents are resilient by design (see below). One thing makes Knocknoc forgivin...
SonicWall
The SonicWall can be orchestrated in three ways, Actively (API call from an Orchestration Agent to the Firewall), Passively via SonicWalls DEAG polling capability, or a combination known as Passive+, where a DEAG is used with an active force-download-now call ...
Windows Firewall
Microsoft Windows comes equipped with a built-in native firewall which Knocknoc orchestrates to provide just-in-time network access control, effectively removing always-on attack surface for your Windows Servers. Ports and services like RDP become invisible, p...
How Knocknoc removes attack surface
Knocknoc enables you to remove the attack surface of systems, by enacting just-in-time network/application-based allow-listing. It can operate in a number of ways - from orchestrating network access controls (e.g., adding to firewall rules - while presenting n...
Use cases (overview)
Knocknoc use cases Knocknoc enables just-in-time network access control. These are some of the ways it has been deployed. SSH Bastion hosts: Network based IP allowlisting: add MFA, link in your IdP, remove the servers attack surface (read more) High security s...
SSH
Use case: Eliminating SSH attack surface in a distributed environment A large distributed enterprise needed to eliminate the attack surface of its internet-facing SSH servers - without adding latency, changing its network architecture, or compromising on secur...
High security subnets and JIT network access
Use case: Dynamic just-in-time IP restrictions for high-security subnet A critical infrastructure environment needed to restrict access to specific high-security internal networks to trusted IP addresses dynamically, allowing access only for short-lived period...