Can I restrict iDBQuery access to specific IP addresses?
Yes. iDBQuery supports IP allow-listing so access is limited to trusted networks, such as your office ranges or corporate VPN, and requests from anywhere else are refused. In a VPC or on-prem deployment you can go further and make iDBQuery reachable only from inside your private network.
IP allow-listing lets you bound where iDBQuery can be reached from, adding a network-level control on top of authentication.
- Trusted ranges only - permit your office CIDRs, corporate VPN, or egress gateways, and reject everything else before a login is even attempted.
- Layered with identity - allow-listing complements SSO and MFA; a request has to come from an approved network and pass authentication.
- Private by architecture - deployed in your VPC or on-prem, iDBQuery can be published only on internal networks, so there is no public endpoint at all.
For example, a finance team can require that iDBQuery is only usable from the corporate VPN, so an analyst on untrusted Wi-Fi must first connect through the VPN to reach it. This is where iDBQuery's deployment flexibility pays off - because it can run inside your own VPC or fully air-gapped, network isolation is not a bolt-on but part of the design. Combined with query-in-place (your data is not force-copied out), RBAC, and encryption in transit and at rest, IP restrictions help ensure that both the network path and the identity are trusted before anyone touches your data. Contact us to scope allow-listing for your environment.
Updated 2026-06-22