How to install Qualys Cloud Agent on Linux/Windows

Red Hat Enterprise Linux (RHEL) / Amazon Linux

1. Download the latest Qualys Cloud Agent installer from below.

https://qualysguard.qualys.com/am/help/sensors/cloud_agent.htm

2. Perform installation with the following command:

sudo rpm -ivh qualys-cloud-agent.x86_64.rpm

3. Activate Qualys Cloud Agent with the following command:

sudo /usr/local/qualys/cloud-agent/bin/qualys-cloud-agent.sh ActivationId=1032h37-dd20-4fde-93c8-2q3dwedae34 
CustomerId=aa9845nb0-6643-5564-8045-1234wsDDAS

4. Update Qualys Proxy setting and restart the service.

echo "qualys_https_proxy=\"http://<proxy-url>:1080\"" > /etc/sysconfig/qualys-cloud-agent
systemctl restart qualys-cloud-agent

5. For troubleshooting -> log path in Linux environment

/var/log/qualys/qualys-cloud-agent.log

Ubuntu

1. Download the latest Qualys Cloud Agent installer from below.

https://qualysguard.qualys.com/am/help/sensors/cloud_agent.htm

2. Perform installation with the following command:

sudo dpkg --install QualysCloudAgent.deb

3. Activate Qualys Cloud Agent with the following command:

sudo /usr/local/qualys/cloud-agent/bin/qualys-cloud-agent.sh ActivationId=10feb827-dd20-4fde-93c8-q234dasds CustomerId=aa41eda0-6643-5564-8045-23edsdsdDs

4. Update Qualys Proxy setting and restart the service.

echo "qualys_https_proxy=\"http://<proxy-url>:1080"" > /etc/sysconfig/qualys-cloud-agent
systemctl restart qualys-cloud-agent

Windows

1. Download the latest Qualys Cloud Agent installer from below:

https://qualysguard.qualys.com/am/help/sensors/cloud_agent.htm

2. Copy the installer to the Windows server and execute the following command in an elevated command prompt (Run as administrator):

QualysCloudAgent.exe CustomerId={aa41eda0-6643-5564-8045-q2342eaweds} ActivationId={10feb827-dd20-4fde-93c8-234daweda} WebServiceUri=https://qagpublic.qg3.apps.qualys.com/CloudAgent/

3. Execute the command below to update Qualys proxy setting:

cd C:\Program Files\Qualys\QualysAgent\
QualysProxy /u <proxy-url>:1080

4. Agent will be running as a service. Instance reboot is not required.