network – SGBox Next Generation SIEM & SOAR https://www.sgbox.eu Next Generation SIEM & SOAR Fri, 28 Nov 2025 16:19:56 +0000 en-US hourly 1 https://wordpress.org/?v=6.8.2 https://www.sgbox.eu/wp-content/uploads/2025/02/cropped-SGBox-symbol-png-32x32.webp network – SGBox Next Generation SIEM & SOAR https://www.sgbox.eu 32 32 Network Requirements https://www.sgbox.eu/en/knowledge-base/network-requirements/ Tue, 30 May 2023 15:16:23 +0000 http://10.253.1.91/?post_type=epkb_post_type_1&p=8649

SGBox and Collector network requirements

Following table explains the different network configuration you in order to: 

  • Manage SGBox and the Collector using WebUI and CLI.
  • Keep SGBox and the Collector updated.
  • Make a correct communication between SGBox and the Collector.
  • Allow data sources to send data to SGBox and Collector.
FromToPortDescription
Client (User)SGBox443/tcpHTTPS WebUI
Client (User)SGBox 22/tcpSSH (CLI)
Client (User)Collector22/tcpSSH (CLI)
Client (User)Collector (v5)4000/tcpOpenVAS console HTTPS
Client (User) / SGBoxSGBox4000/tcpHTTPS (API)
SGBox/Collectorapps.sgbox.it80/tcp
443/tcp		HTTP/S (Updates)
SGBox/Collector*.ubuntu.com80/tcp
443/tcp		HTTP/S (Updates)
Collector (v5)feed.community.greenbone.net873/tcpRSYNC (Updates)
SGBox / Qualys probequalysguard.qg3.apps.qualys.it443/tcpCloud (scans, results)
SGBox / Collector (v6)registry.sgcloud.it7442/tcpHTTPS (Updates), mandatory connection
SGBox / Collector (v6)No Syslog datasourceseg. 1433/tcp, 1521/tcp, 443/tcpDB, other (receive data)
SGBox / Collector (v6)Active Directory (LDAP)389/tcp, 636/tcpLDAP/LDAPS
Collector SGBox443/tcpHTTPS (send data)
SGAgentCollector / SGbox443/tcpHTTPS (send data)
Data sourceCollector / SGbox514/udpSyslog (send data)
Data sourceCollector / SGBox514/tcpSyslog (send data)
Data sourceCollector / SGBox6514/tcpSyslog + TLS (send data)

Containers networks

SGBox and Collector (V6) introduce containers for different activities.
Here you can find the default networks used. If for some reason your internal networks overlap the default containers networks you can change them by connecting to the collector’s CLI:
Network Configuration > Change Docker network configuration

VMNetwork NameNetwork Address
SGBox, Collectordefault10.42.78.0/24
Collectorsg-internal10.10.0.0./16
Collectorsg-external10.20.0.0/24
Collectorswarm10.43.0.0/16

]]> Prepare an asset to NVS https://www.sgbox.eu/en/knowledge-base/prepare-an-asset-to-nvs/ Fri, 28 Jun 2019 15:29:37 +0000 https://10.253.1.90/sgbox/EN/?post_type=epkb_post_type_1&p=1680 How to prepare an asset to NVS

This article explains how to prepare an asset to NVS. In this way, the hosts that are part of it, can be used as target of the scan test. For more information about the assets, look the article that explains how to create an asset.

Requirements:

  • The asset must be created. Look this section to see how to create it.

Connect to the SGBox web interface.
SGBOX > SCM > Network > Asset

Prepare an asset to NVS

Click on Edit button of the asset you want to modify. In our caseAsset1.

Prepare an asset to NVS

Asset configuration window is shown.
In Assign Module tab, select Network Vunerability Scanner and click on ADD.

Prepare an asset to NVS

In Assign NVS Policy tab, select the network on which our hosts belong and the policy you want to use.
In our case, the previously created policy: Openvas Default Scan. Click on Modify to save changes.

Prepare an asset to NVS

]]>