iQSonar has been designed as an onpremises scanning solution. As more of our customers are increasingly relying on cloud based infrastructure (public cloud or private cloud) we are being asked how iQSonar supports cloud based solutions.

The following are based on experiences of some of our customers:

Scan of Cloud based targets

Several of our customers have used an on-premesis iQSonar instance to scan targets hosted in AWS and/or Azure cloud environments. The requirement to scan cloud-hosted VMs using a scan-engine in your private data center is that you have a VPN configured to allow the scan engine server to connect to all the required ports on the target.

Open

Scan in Cloud Infrastructure

Two of our major customers have carried out Proof-of-concept builds where the entire iQSonar deployment (SQL Server, Scan engine) was hosted in a cloud environment - one each for AWS and for Azure. In each case both the SQL Server and the scan engine server were hosted on dedicated Windows 2016 servers, and the tests used SQL Server 2016.

Open

Cloud-hosted Database

One of our major customers has a production (i.e. not test/proof of concept) set-up with multiple self-hosted data centers each with a Scan Engine, all communicating with a back-end SQL server hosted in AWS. Firewall/VPN rules need to be in place to allow the scan engines in each data center to communicate with the cloud-hosted database. (This is a single TCP port that needs to be open)