Knocknoc

Day one of RSA at 9.37am Citrix published a security advisory and patches, rated as critical. By March 27, attackers were captured exploiting the bugs in the wild. This was probably through reverse engineering the patch and Citrix handed them the roadmap. This is the paradox of patches: the fix itself tells attackers exactly where to look, and with AI it's done by lunch time. So even when a vendor does everything right - finds it first, patches it fast you're still in a race you can't win. Unless the target isn't there. That's exactly why you need Knocknoc - if your NetScaler isn't on the internet, reverse-engineering the patch gives attackers nothing to hit. Find out more at https://lnkd.in/gqgTynW2 #Knocknoc #JustInTimeAccess #NetworkAllowlisting #Prevention

Let’s face it, flat networks are alive and kicking inside most enterprises On the latest episode of Risky Business, our CEO Adam Pointon sat down with Patrick Gray to unpack how organizations are applying Knocknoc’s network controls internally, and well beyond the external attack surface reduction use-case we originally solved. If you care about lateral movement, this conversation is worth your time. 👉 Watch here: https://lnkd.in/gjKHNKbk #cybersecurity #Zerotrust #RiskyBusiness #Knocknoc

The project finished. The contractor's remote access didn't. Knocknoc keeps every remote-access path closed by default. Your contractor signs in with your IdP and MFA, gets a path to the one system they need, and that path closes itself when the job is done. All using the firewalls you already own. Who still has access from last year's project?

No new box. Just no way in. Zero trust usually arrives on a trolley. Knocknoc doesn't. It takes the identity signal you already have and drives the firewalls you already own. When someone authenticates, their IP goes on the trusted list, and it comes off again when their access ends. Your policy doesn't change. The trusted list does. A config change, not a forklift upgrade.

The patch is next week. The exploit is today. A critical bug drops, the patch still needs testing, and scanners are already looking. Knocknoc closes the exposed service to everyone except your authenticated users, with one change on the firewall you already own. You test and ship the patch on your schedule. What's sitting exposed while your patches wait for testing?

Keep the VPN. Lose the exposure. Your VPN is the most exposed box you own, and you can't rip it out this quarter. You can stop it answering the internet. Knocknoc sits beside the traffic, not in it, and opens the VPN only to people who have already signed in through your IdP and MFA. Everyone else gets no response. No new client. No routing change. Same VPN.