Proxy Configuration

In FutureVuls, the server executing the scan needs internet access during scanner installation and scan result upload. In environments where internet access is routed through a proxy server, please configure the following settings.

For Linux

During Installation

Set the proxy in the environment variables before installation.

export http_proxy='http://<proxy server address or hostname>:<port number>'
export https_proxy='http://<proxy server address or hostname>:<port number>'


# For proxy with authentication
export http_proxy='http://<proxy user>:<proxy password>@<proxy server address or hostname>:<port number>'
export https_proxy='http://<proxy user>:<proxy password>@<proxy server address or hostname>:<port number>'

The installer execution method is the same as the standard procedure. After the installation is complete, please refer to the "After Installation" section below to configure the settings.

After Installation

To enable uploading scan results via a proxy, uncomment the relevant lines in the /opt/vuls-saas/vuls-saas.sh file and set the proxy according to your environment, then save the file.

Before change:

#!/bin/bash

## If you are using proxy, please uncomment ##
# PROXY='http://<modify>:<port>'

~~~ Omitted below ~~~

After change:

#!/bin/bash

## If you are using proxy, please uncomment ##
PROXY='http://<proxy server address or hostname>:<port number>'
#For proxy with authentication
PROXY='http://<proxy user>:<proxy password>@<proxy server address or hostname>:<port number>'

~~~ Omitted below ~~~

When you set the proxy address, it will be exported as http_proxy and https_proxy as shown below. For details, please refer to the vuls-saas.sh script.

export http_proxy=${PROXY}
export https_proxy=${PROXY}

For Windows

During Installation

Set the Windows OS proxy before installation.

1. Search for and launch "Internet Options" from the search box.
2. Select the "Connections" tab.
3. Click "LAN settings" and enter the proxy server settings.
4. Click the "OK" button.

The installer execution method is the same as the standard procedure. After the installation is complete, please refer to the "After Installation" section below to configure the settings.

If you encounter an error while downloading the installer with the above procedure, please follow the steps below to install.

No.	Procedure	Command
1	Open Command Prompt with administrative privileges	-
2	Get the installer	-
3	Create a bitsadmin task	・> bitsadmin /create get-vuls-installer ・> bitsadmin /addfile get-vuls-installer https://installer.vuls.biz/vuls-installer-v2.bat "%cd%\vuls-installer.bat"
4	Set proxy settings	・> bitsadmin /setproxysettings get-vuls-installer override {proxy server address:port number} NULL ・> bitsadmin /setcredentials get-vuls-installer PROXY BASIC username password (Only if authentication is required)
5	Run the task	・>bitsadmin /resume get-vuls-installer (Wait about 1 minute after execution) ・>bitsadmin /complete get-vuls-installer
6	Verify that "vuls-installer.bat" has been downloaded to the current directory	-
7	Set environment variables	・> set VULS_SAAS_GROUPID={ID of the destination group} ・> set VULS_SAAS_TOKEN={token with scan permissions} ・> set VULS_PROXY={{proxy server address:port number}} (If necessary)
8	Run the installer	> vuls-installer.bat inst

After Installation

1. Configure batch_config.toml

To enable uploading scan results via a proxy, modify the C:\Program Files\vuls-saas\batch_config.toml file as follows. Add the proxy server address or hostname and port number according to your environment and save the file.

  AutoRefreshBinary = true
  TimeoutRefreshBinary = 60
  Proxy = proxy.contoso.com:8080
  ///The following is for a proxy with password authentication
  Username = xxxxx
  Password = xxxxx

The http:// prefix for the URL is not required (when the Vuls scanner runs, it will be executed with proxy environment variables set for the process scope).

2. Configure netsh

Set the WinHTTP proxy used by Windows Update.

• If the Vuls scanner communicates with the Windows Update server via a proxy, set the "WinHTTP Proxy value" using the netsh command.
• If the WSUS server is located inside the proxy network and communication with the Windows Update server does not go through the proxy, configuration with the netsh command is not necessary.

■ Environment where netsh configuration is required
Scanner -> Proxy Server -> Internet -> Windows Update Server

■ Environment where netsh configuration is not required (when not going through a proxy)
Scanner -> (Internet) -> Windows Update Server

You can check the currently configured WinHTTP Proxy settings with the command below.

netsh winhttp show proxy

Here is an example command to set the WinHTTP proxy with the following information.

• Proxy URL: proxy.contoso.com:8080

netsh winhttp set proxy proxy.contoso.com:8080 "localhost;*.contoso.com"

The WinHTTP setting with netsh is an OS-wide setting and may affect the communication of other applications.

For example, there may be cases where there are two proxy servers in the environment, or where another application refers to the WinHTTP proxy settings internally, and changing the WinHTTP proxy settings could affect that application's communication.

Please test thoroughly in a staging environment before applying changes to the production environment. Reference: How the Windows Update client determines which proxy server to use to connect to the Windows Update website

If an Error Occurs

If you encounter an error like the one below in a proxy environment, please remove HTTPS_PROXY from the environment variables and try again.

"Failed to report. err: Post https://auth.vuls.biz/one-time-auth: proxyconnect tcp: tls: first record does not look like a TLS handshake"