Search Results

Overview This integration allows for IP addresses to be dynamically managed within Azure Network Security Groups (NSGs), which are used by default as the inner firewalls protecting virtual machines. Other Azure assets (PaaS etc) are managed using separate Kno...

To create a SaaS Server instance (we host it) log in to the licensing portal and follow the prompts. Set a hostname. We can BYOK on Standard+ and above plans. Once payment information has been completed the instance will build. The initial username/pass...

User sessions can be created using the API. This is handy for machine to machine authentication, and is where knocknoc-client authentication requests are also configured. As an Admin, create a local user, selecting API Key as the authentication method: Vis...

User sessions can be terminated using the API. This is handy for integration with revocation systems, SOAR/SIEM integrations whereby immediate termination of network access and sessions is desired. As an Admin, visit the API keys section and choose"Manage use...

Allowlists or External Dynamic Lists (EDLs) served from Knocknoc require an API key for access, in conjunction with the specific EDL URI. These API keys are automatically created when a Passive integration is established, however can be edited or expanded. A...

API keys can be created to allow just-in-time orchestration Agent registration, which is suitable for infrastructure-as-code or pipeline deployments whereby the Admin doesn't want to create an Agent registration key prior to deployment and registration. As an...

Users are assigned a default "grant period" (in minutes), either within Knocknoc for local users, or passed as a SAML attribute through "sessionDuration".  These can be overridden per-Knoc, allowing certain access oaths to have shorter periods if so desired. ...