Frequently asked questions

15 days from the first trial installation or activation. No credit card is required.

No. VARQOO does not require RDP to be moved to another port. You can still do so if your infrastructure requires it, but it is not a product requirement.

No. VARQOO uses Windows Firewall as the native enforcement component and applies its policies through Windows APIs.

Yes. Private networks and infrastructure addresses can be excluded from automatic blocking. Firewall changes should still be validated in your own environment before production deployment.

Yes. Allowlists are designed to keep trusted addresses or networks authorized even when other protection policies are active.

When the client determines that its license is no longer valid, active VARQOO protection stops and its managed firewall rules are removed. Check the displayed license and protection status, and renew or activate a valid license to continue protection.

A dedicated model for partners and resellers is planned. Contact us with an approximate number of servers or customers you expect to manage.

No. Connection monitoring can detect repeated observed TCP connections before a valid sign-in, alongside authentication-event detectors. See pre-authentication connection protection.

Password spraying targets multiple accounts with a small number of passwords. VARQOO can block sources reaching its failed-login or connection thresholds, and correlates distributed failures against the same account. These controls do not guarantee detection of every slow cross-account campaign. Read the Password Spray guide.