# Installing SecurityOnion in Yandex Cloud

> Deploy SecurityOnion in Yandex Cloud - VM creation, IDS/IPS platform installation, Suricata and Zeek configuration, and ELK stack setup for monitoring

Source: https://opennix.org/en/docs/yc/securityonion/securityonion-yandex-cloud-install/

1. Before installing SecurityOnion, the user must create a virtual machine from a pre-built image.

Input parameters for the virtual machine (see Table 1).

|    Name       |   Parameter     |
|-----------|--------|
| CPU cores | 10     |
| Memory    | 20 GB  |
| disk size | 256 GB |
| NICs      | 2      |

Table 1. Parameters for Virtual Machine

Please note that the table shows only recommended minimum requirements!

2. After configuring the virtual machine with the necessary parameters, the user needs to connect via SSH. The installer window will be opened (see Figure 1). 

![SecurityOnion installation welcome screen](/img/so-intro.webp)
<p style="text-align: center;">Figure 1. SecurityOnion Installation Window</p>

Press “yes” and proceed to the next step.

3. The next screen prompts the user to select the type of installation (see Figure 2). 

![SecurityOnion installation type selection](/img/so-type.webp)
<p style="text-align: center;"> Figure 2. Selection of Installation Type </p>

To simplify the process, it is recommended to select Standalone mode. For more information please refer to the [official documentation](https://docs.securityonion.net/en/2.4/architecture.html).

4. On the next screen, the user is prompted to read the license agreement (see Figure 3).

![SecurityOnion license agreement window](/img/so-lic.webp)
<p style="text-align: center;"> Figure 3. License Agreement Window </p>

It is necessary to read the [licensing](https://securityonionsolutions.com/license). If the user agrees with it, enter “AGREE” and proceed to the next step.

5. The hostname (not the FQDN!) must be set (see Figure 4).

![SecurityOnion hostname configuration](/img/so-hostname.webp)
<p style="text-align: center;"> Figure 4. The Hostname Name </p>

The user filled in everything at this point, so they must select “Yes” (see Figure 5). 

![SecurityOnion installation continued](/img/so-dns-dhcp.webp)
<p style="text-align: center;"> Figure 5. Continued Installation  </p>

6. It is required to read the DHCP warning carefully and accept the risks (see Figure 6).

![SecurityOnion DHCP warning dialog](/img/so-warning.webp)
<p style="text-align: center;"> Figure 6. DHCP Warning Window  </p>

7. When selecting a management interface, the first one from the list should be marked. This interface will provide access to the web interface.
   
*The developers recommend using a VPN to access the web interface* (see Figure 7). 

![SecurityOnion management network interface selection](/img/so-man-nic.webp)
<p style="text-align: center;"> Figure 7. Selecting the Network Interface to Access the Web Interface  </p>

8. The user needs to go to the following screen to continue with the setting (see Figure 8). 
   
![SecurityOnion internet connection type selection](/img/so-proxy.webp)
<p style="text-align: center;"> Figure 8. Selecting the Type of Internet Connection  </p>

If the user is not using a proxy server, they should select Direct and proceed to the next step (see Figure 9).

![SecurityOnion Docker default option selection](/img/so-docker.webp)
<p style="text-align: center;"> Figure 9. Selecting a Default Option   </p>

If the user cannot answer this question, they need to select “Yes” and proceed to the next step.

9. In this step, the user must select the interface or interfaces for monitoring (see Figure 10). 

![SecurityOnion monitoring interface selection](/img/so-monitor.webp)
<p style="text-align: center;"> Figure 10. Interface Selection   </p>

The example selects an existing interface. The selection is made by pressing the spacebar.

10. Creating a user for the web interface and setting a password is necessary (see Figure 11). In the first window, you need to set the administrator's email address.

![SecurityOnion administrator email configuration](/img/so-admin.webp)
<p style="text-align: center;"> Figure 11. Setting up the Administrator Email    </p>

11. The next step is to create a secure password that complies with the cryptocurrency standards and security policy of the user's organization (see Figure 12). 

![SecurityOnion administrator password creation](/img/so-password.webp)
<p style="text-align: center;"> Figure 12. Creating an Administrator Password </p>

12. Once the user configuration is complete, select access to the web interface.

If the users are on an internal network, the user must select IP or HOSTNAME (see Figure 13). 

![SecurityOnion web interface access method selection](/img/so-redirect.webp)
<p style="text-align: center;"> Figure 13. Selecting Access to the Web Interface </p>

In the example we select OTHER. Then enter the IP address of the external virtual machine (see Figure 14). 

![SecurityOnion virtual machine IP address entry](/img/so-other-ip.webp)
<p style="text-align: center;"> Figure 14. Entering the virtual machine’s name or IP  </p>

Developers do not guarantee that this scheme will work and will not change in the future. We recommend using an internal IP address with access via VPN.

13. The next step is to allow access to the web interface (see Figure 15). 

![Enabling access to SecurityOnion web interface](/img/so-web-ui-access.webp)
<p style="text-align: center;">Figure 15. Enabling Access to the Web Interface  </p>

The user should select “Yes”. On the next screen, they must enter either the IP address or the subnet from which access will be granted. In the example, access to the web interface is allowed from all subnets (see Figure 16).

![Defining access restrictions for SecurityOnion web interface](/img/so-any-to-any.webp)
<p style="text-align: center;">Figure 16. Defining Access Restrictions to the Web Interface  </p>

The next window displays all the settings the user selected in the previous steps. It is necessary to check that everything has been entered correctly and click “Yes” (see Figure 17).

![SecurityOnion final configuration summary](/img/so-final.webp)
<p style="text-align: center;">Figure 17. Final SecurityOnion Settings  </p>

The SecurityOnion installation and configuration process will begin. This can take up to 2 hours, depending on the configuration of the virtual machine.

For example, for a virtual machine with 10 vCPU, 20GB of RAM, and a 256 GB disk, the installation and configuration took 1 hour and 30 minutes.

After successful installation, the user will see a notification (see Figure 18).

![SecurityOnion installation completion notification](/img/so-end.webp)
<p style="text-align: center;">Figure 18. Notification of Installation Completion  </p>

This completes the installation. The user can log in to the web interface with the name and password specified during configuration.

