10 Scanning a System

Note

This chapter documents all possible menu options.

However, not all appliance models support all of these menu options. The model overview provides information about whether a specific feature is available on the used appliance model.

10.1 Using the Task Wizard for a First Scan

The task wizard can configure and start a basic scan with minimal user input.

10.1.1 Using the Task Wizard

A new task with the task wizard can be configured as follows:

1. Select Scans > Tasks in the menu bar.

2. Start the wizard by moving the mouse over and clicking Task Wizard.

3. Enter the IP address or host name of the target system in the input box (see Fig. 10.1).

   

   Fig. 10.1 Configuring the task wizard

   Note

   If using a DNS name however, the appliance must be able to resolve the name.

4. Click Start Scan.

   → The task wizard performs the following steps automatically:

   1. Creating a new scan target on the appliance.

   2. Creating a new scan task on the appliance.

   3. Starting the scan task immediately.

   4. Displaying the page Tasks.

After the task is started, the progress can be monitored (see Fig. 10.2).

Fig. 10.2 Page Tasks displaying the progress of the task

For the status of a task see Chapter 10.8.

Tip

The report of a task can be displayed as soon as the task has been started by clicking the bar in the column Status. For reading, managing and downloading reports see Chapter 11.

As soon as the status changes to Done the complete report is available. At any time the intermediate results can be reviewed (see Chapter 11.2.1).

Note

It can take a while for the scan to complete. The page is refreshing automatically if new data is available.

10.1.2 Using the Advanced Task Wizard

Next to the simple wizard, the appliance also provides an advanced wizard that allows for more configuration options.

A new task with the advanced task wizard can be configured as follows:

1. Select Scans > Tasks in the menu bar.

2. Start the wizard by moving the mouse over and clicking Advanced Task Wizard.

3. Define the task (see Fig. 10.3).

   Tip

   For the information to enter in the input boxes see Chapters 10.2.1 and 10.2.2.

   If an e-mail address is entered in the input box Email report to an alert is created sending an e-mail as soon as the task is completed (see Chapter 10.12).

   

   Fig. 10.3 Configuring the advanced task wizard

4. Click Create.

   → The advanced task wizard performs the following steps automatically:

   1. Starting the scan task immediately.

   2. Displaying the page Tasks.

For the status of a task see Chapter 10.8.

Tip

The report of a task can be displayed as soon as the task has been started by clicking the bar in the column Status. For reading, managing and downloading reports see Chapter 11.

As soon as the status changes to Done the complete report is available. At any time the intermediate results can be reviewed (see Chapter 11.2.1).

Note

It can take a while for the scan to complete. The page is refreshing automatically if new data is available.

10.1.3 Using the Wizard to Modify a Task

An additional wizard can modify an existing task:

1. Select Scans > Tasks in the menu bar.

2. Start the wizard by moving the mouse over and clicking Modify Task Wizard.

3. Select the task which should be modified in the drop-down list Task (see Fig. 10.4).

   

   Fig. 10.4 Modifying a task using the wizard

4. Create a schedule for the task by selecting the radio button Create Schedule (see Chapter 10.10).

   The date of the first scan can be selected by clicking and the time can be set using the input boxes.

5. Enter the e-mail address to which the report should be sent in the input box Email report to.

6. Click Modify Task.

10.2 Configuring a Simple Scan Manually

Generally speaking, the appliance can use two different approaches to scan a target:

• Simple scan

• Authenticated scan using local security checks

The following steps have to be executed to configure a simple scan:

• Creating a target (see Chapter 10.2.1)

• Creating a task (see Chapter 10.2.2)

• Running the task (see Chapter 10.2.3)

10.2.1 Creating a Target

The first step is to define a scan target as follows:

1. Select Configuration > Targets in the menu bar.

2. Create a new target by clicking .

3. Define the target (see Fig. 10.5).

   

   Fig. 10.5 Creating a new target

4. Click Save.

The following information can be entered:

Name

The name can be chosen freely. A descriptive name should be chosen if possible. Possibilities are Mailserver, ClientNetwork, Webserverfarm, DMZ or describing the entered systems in more detail.

Comment

The optional comment allows specifying background information. It simplifies understanding the configured targets later.

Hosts

Manual entry of the hosts that should be scanned, separated by commas, or importing a list of hosts.

Note

The IP address or the host name is required. In both cases it is necessary that the appliance can connect to the system. If using the host name, the appliance must also be able to resolve the name.

The maximum configurable number of IP addresses is 4096 for most appliance models. For the Greenbone Enterprise 6500, the maximum configurable number of IP addresses is 16777216.

When entering manually the following options are available:

• Single IP address, for example 192.168.15.5

• Host name, for example mail.example.com

• IPv4 address range in long format, for example 192.168.15.5-192.168.15.27

• IPv4 address range in short format, for example 192.168.55.5-27

• IPv4 address range in CIDR notation, for example 192.168.15.0/24

Note

Because of the maximum configurable number of IP addresses (see above), the maximum subnet mask is /20 for IPv4 if no other hosts are part of the configuration. If the maximum number of IP addresses is higher, for example for the Greenbone Enterprise 6500, correspondingly larger subnet masks can be configured.

Traditionally, the first IP address (network address, for example 192.168.15.0) and last IP address (broadcast address, for example 192.168.15.255) of a subnet are not included in the number of usable IP addresses and thus are not considered in scans when this notation is used. If the IP addresses are actually usable and scannable, they must be explicitly added to the scan target, for example 192.168.15.0/24, 192.168.15.0, 192.168.15.255.

• Single IPv6 address, for example fe80::222:64ff:fe76:4cea

• IPv6 address range in long format, for example ::12:fe5:fb50-::12:fe6:100

• IPv6 address range in short format, for example ::13:fe5:fb50-fb80

• IPv6 address range in CIDR notation, for example fe80::222:64ff:fe76:4cea/120

Note

Because of the maximum configurable number of IP addresses (see above), the maximum subnet mask is /116 for IPv6 if no other hosts are part of the configuration. If the maximum number of IP addresses is higher, for example for the Greenbone Enterprise 6500, correspondingly larger subnet masks can be configured.

Multiple options can be mixed. If importing from a file, the same syntax can be used. Entries can be separated with commas or by line breaks. If many systems have to be scanned, using a file with the hosts is simpler than entering all hosts manually. The file must use ASCII character encoding.

Alternatively the systems can be imported from the host asset database.

Note

Importing a host from the asset database is only possible if a target is created from the page Hosts (see Chapter 13.1.3).

Exclude Hosts

Manual entry of the hosts that should be excluded from the list mentioned above, separated by commas, or importing a list of hosts.

When entering manually the following options are available:

• Single IP address, for example 192.168.15.5

• IPv4 address range in long format, for example 192.168.15.5-192.168.15.27

• IPv4 address range in short format, for example 192.168.55.5-27

• IPv4 address range in CIDR notation, for example 192.168.15.0/24

• Single IPv6 address, for example fe80::222:64ff:fe76:4cea

• IPv6 address range in long format, for example ::12:fe5:fb50-::12:fe6:100

• IPv6 address range in short format, for example ::13:fe5:fb50-fb80

• IPv6 address range in CIDR notation, for example fe80::222:64ff:fe76:4cea/120

Note

Entering host names/FQDN is also possible. However, this does not result in an IP address not being scanned – as the scanner is IP address-based – but only excludes the specific host from the vhosts list for the IP address.

Allow simultaneous scanning via multiple IPs

Some services, especially IoT devices, may crash when scanned via multiple connections coming from the same host at the same time. This can happen, for example if the device is connected via IPv4 and IPv6.

Selecting the radio button No will avoid scanning via several addresses at the same time.

Port list

Port list used for the scan (see Chapter 10.7).

Note

A port list can be created on the fly by clicking next to the drop-down list.

Alive Test

This options specifies the method to check if a target is reachable. Options are:

• Scan Config Default (the alive test method ICMP Ping is used by default)

• ICMP Ping

• TCP-ACK Service Ping

• TCP-SYN Service Ping

• ICMP & TCP-ACK Service Ping

• ICMP & ARP Ping

• TCP-ACK Service & ARP Ping

• ICMP, TCP-ACK Service & ARP Ping

• Consider Alive

Sometimes there are problems with this test from time to time. In some environments routers and firewall systems respond to a TCP service ping with a TCP-RST even though the host is actually not alive (see Chapter 10.13).

Network components exist that support Proxy-ARP and respond to an ARP ping. Therefore this test often requires local customization to the environment.

SSH Credential

Selection of a user that can log into the target system of a scan if it is a Linux or Unix system. This allows for an authenticated scan using local security checks (see Chapters 10.3.2 and 10.3).

• Elevate Privileges

  It is also possible to store credentials for elevated privileges, for example root. For this, SSH credentials must be selected first. Then a new drop-down list is displayed for selecting the elevated credentials.

  Note

  To see the new feature for elevated SSH credentials, the cache of the browser used for the web interface may need to be emptied. Clearing the browser cache can be done in the options of the used browser.

  Alternatively, the page cache can be emptied by pressing Ctrl and F5.

  Note

  The feature is still experimental. Depending on the target system and its configuration, the feature may not be reliable.

  For more information about root rights for scans see Chapter 10.3.5.

  The elevated user’s rights must be configured on the target system beforehand. The appliance only executes the command su - <username> which has no control over the rights of use.

  If elevated SSH credentials are configured, the default SSH credentials are only used for logging in on the target system. The elevated credentials are used for the scan.

  The programs stty and unset must be available/accessible for the elevated-privileges user.

  The elevated-privileges user must be allowed to change the login prompt via an export PS1= prepended to the commands sent.

  If elevated SSH credentials are configured, they are always used even if the scan configuration does not contain relevant vulnerability tests.

  Default and elevated SSH credentials must not be the same.

  Note

  Using elevated SSH credentials may create increased load on the appliance, as well as an increased number of SSH connections from the appliance to the target system. This may need to be taken into account for firewalls, intrusion detection and logging systems.

  In addition, the duration of scans using elevated SSH credentials can be much longer than scans without elevated credentials due to the system load mentioned above.

SMB Credential

Selection of a user that can log into the target system of a scan if it is a Microsoft Windows system. This allows for an authenticated scan using local security checks (see Chapters 10.3.2 and 10.3).

ESXi Credential

Selection of a user that can log into the target system of a scan if it is a VMware ESXi system. This allows for an authenticated scan using local security checks (see Chapters 10.3.2 and 10.3).

SNMP Credential

Selection of a user that can log into the target system of a scan if it is an SNMP aware system. This allows for an authenticated scan using local security checks (see Chapters 10.3.2 and 10.3).

Note

All credentials can be created on the fly by clicking next to the credential.

Reverse Lookup Only

Only scan IP addresses that can be resolved into a DNS name.

Reverse Lookup Unify

If multiple IP addresses resolve to the same DNS name the DNS name will only get scanned once.

Note

For reverse lookup unify, all target addresses are checked prior to the scan in order to reduce the number of actual scanned addresses. For large targets and for networks in which reverse lookup causes delays, this leads to a long phase where the task remains at 1 % progress.

This option is not recommended for large networks or networks in which reverse lookups cause delays.

10.2.2 Creating a Task

The second step is to create a task.

The appliance controls the execution of a scan using tasks. These tasks can be repeated regularly or run at specific times (see Chapter 10.10).

A task can be created as follows:

1. Select Scans > Tasks in the menu bar.

2. Create a new task by moving the mouse over and clicking New Task.

3. Define the task (see Fig. 10.6).

   

   Fig. 10.6 Creating a new task

4. Click Save.

   → The task is created and displayed on the page Tasks.

The following information can be entered:

Name

The name can be chosen freely. A descriptive name should be chosen if possible. Possibilities are Mailserver, ClientNetwork, Webserverfarm, DMZ or describing the entered systems in more detail.

Comment

The optional comment allows for the entry of background information. It simplifies understanding the configured task later.

Scan Targets

Select a previously configured target from the drop-down list (see Chapter 10.2.1).

Alternatively, the target can be created on the fly by clicking next to the drop-down list.

Alerts

Select a previously configured alert from the drop-down list (see Chapter 10.12). Status changes of a task can be communicated via e-mail, Syslog, HTTP or a connector.

Alternatively, an alert can be created on the fly by clicking next to drop-down list.

Schedule

Select a previously configured schedule from the drop-down list (see Chapter 10.10). The task can be run once or repeatedly at a predetermined time, for example every Monday morning at 6:00 a.m.

Alternatively, a schedule can be created on the fly by clicking next to the drop-down list.

Add results to Assets

Selecting this option will make the systems available to the appliance’s asset management automatically (see Chapter 13). This selection can be changed at a later point as well.

Apply Overrides

Overrides can be directly applied when adding the results to the asset database (see Chapter 11.8).

Min QoD

Here the minimum quality of detection can be specified for the addition of the results to the asset database (see Chapter 11.2.6).

Alterable Task

Allow for modification of the task’s scan target(s), scanner and scan configuration, even if reports were already created. The consistency between reports can no longer be guaranteed if tasks are altered.

Auto Delete Reports

This option may automatically delete old reports. The maximum number of reports to store can be configured. If the maximum is exceeded, the oldest report is automatically deleted. The factory setting is Do not automatically delete reports.

Scanner

By default, only the built-in OpenVAS and CVE scanners are supported (see Chapter 10.11). Sensors can be used as additional scanning engines but need to be configured first (see Chapter 16).

Note

The following options are only relevant for the OpenVAS scanner. The CVE scanner does not support any options.

Scan Config

The appliance comes with several pre-configured scan configurations for the OpenVAS scanner (see Chapter 10.9). Only one scan configuration can be configured per task.

Order for target hosts

Select in which order the specified target hosts are processed during vulnerability tests. Available options are:

• Sequential

• Random

• Reverse

In order to improve the scan progress estimation, the setting Random is recommended (see Chapter 17.2.3).

This setting does not affect the alive test during which active hosts in a target network are identified. The alive test is always random.

Maximum concurrently executed NVTs per host/Maximum concurrently scanned hosts

Select the speed of the scan on one host. The default values are chosen sensibly. If more VTs run simultaneously on a system or more systems are scanned at the same time, the scan may have a negative impact on either the performance of the scanned systems, the network or the appliance itself. These values “maxhosts” and “maxchecks” may be tweaked.

Tag

Select a previously configured tag from the drop-down list (see Chapter 8.4) to link it to the task.

10.2.3 Starting the Task

In the row of the newly created task, click .

Note

For scheduled tasks is displayed additionally. The task is starting at the time that was defined in the schedule (see Chapter 10.10).

→ The task is added to the waiting queue. Afterwards, the scanner begins with the scan.

Note

In some cases, the task may remain in the queue. For more information see Chapter 17.3.

For the status of a task see Chapter 10.8.

The report of a task can be displayed as soon as the task has been started by clicking the bar in the column Status. For reading, managing and downloading reports see Chapter 11.

As soon as the status changes to Done the complete report is available. At any time the intermediate results can be reviewed (see Chapter 11.2.1).

Note

It can take a while for the scan to complete. The page is refreshing automatically if new data is available.

10.3 Configuring an Authenticated Scan Using Local Security Checks

An authenticated scan can provide more vulnerability details on the scanned system. During an authenticated scan the target is both scanned from the outside using the network and from the inside using a valid user login.

During an authenticated scan, the appliance logs into the target system in order to run local security checks (LSC). The scan requires the prior setup of user credentials. These credentials are used to authenticate to different services on the target system. In some circumstances the results could be limited by the permissions of the users used.

The VTs in the corresponding VT families (local security checks) will only be executed if the appliance was able to log into the target system. The local security check VTs in the resulting scan are minimally invasive.

The appliance only determines the risk level but does not introduce any changes on the target system. However, the login by the appliance is probably logged in the protocols of the target system.

The appliance can use different credentials based on the nature of the target. The most important ones are:

• SMB

  On Microsoft Windows systems, the appliance can check the patch level and locally installed software such as Adobe Acrobat Reader or the Java suite.

• SSH

  This access is used to check the patch level on Unix and Linux systems.

• ESXi

  This access is used for testing of VMware ESXi servers locally.

• SNMP

  Network components like routers and switches can be tested via SNMP.

The following table lists the required port – given the authenticating service uses the default port – and the allowed credential types (see Chapter 10.3.2) for each authentication method:

	Required port	Allowed credential types
SMB	445/TCP, 139/TCP	Username + Password
SSH	22/TCP, configurable in the New Target/Edit Target dialog (see Chapter 10.2.1)	Username + Password Username + SSH Key
ESXi	See https://knowledge.broadcom.com/external/article?legacyId=2039095	Username + Password
SNMP	161/UDP	SNMP

10.3.1 Advantages and Disadvantages of Authenticated Scans

The extent and success of the testing routines for authenticated scans depend heavily on the permissions of the used account.

On Linux systems an unprivileged user is sufficient and can access most interesting information while especially on Microsoft Windows systems unprivileged users are very restricted and administrative users provide more results. An unprivileged user does not have access to the Microsoft Windows registry and the Microsoft Windows system folder \windows which contains the information on updates and patch levels.

Local security checks are the most gentle method to scan for vulnerability details. While remote security checks try to be least invasive as well, they may have some impact.

Simply stated an authenticated scan is similar to a Whitebox approach. The appliance has access to prior information and can access the target from within. Especially the registry, software versions and patch levels are accessible.

A remote scan is similar to a Blackbox approach. The appliance uses the same techniques and protocols as a potential attacker to access the target from the outside. The only information available was collected by the appliance itself. During the test, the appliance may provoke malfunctions to extract any available information on the used software. Example: the scanner may send a malformed request to a service to trigger a response containing further information on the deployed product.

During a remote scan using the scan configuration Full and fast all remote checks are safe. The used VTs may have some invasive components but none of the used VTs try to trigger a defect or malfunction in the target (see example below). This is ensured by the scan preference safe_checks=yes in the scan configuration (see Chapter 10.9.4). All VTs with very invasive components or which may trigger a denial of service (DoS) are automatically excluded from the test.

Example for an Invasive VT

An example for an invasive but safe VT is the Heartbleed VT. It is executed even with safe_checks enabled because the VT does not have any negative impact on the target.

The VT is still invasive because it tests the memory leakage of the target. If the target is vulnerable, actual memory of the target is leaked. The appliance does not evaluate the leaked information. The information is immediately discarded.

10.3.2 Using Credentials

Credentials for local security checks are required to allow VTs to log into target systems, for example for the purpose of locally checking the presence of all vendor security patches.

10.3.2.1 Creating a Credential

A new credential can be created as follows:

1. Select Configuration > Credentials in the menu bar.

2. Create a new credential by clicking .

3. Define the credential (see Fig. 10.7).

   

   Fig. 10.7 Creating a new credential

4. Click Save.

The following details of the credential can be defined:

Name

Definition of the name. The name can be chosen freely.

Comment

An optional comment can contain additional information.

Type

Definition of the credential type. The following types are possible:

• Username + Password

• Username + SSH Key

• SNMP

• S/MIME Certificate

• PGP Encryption Key

• Password only

Allow insecure use

Select whether the appliance can use the credential for unencrypted or otherwise insecure authentication methods.

Depending on the selected type further options are shown:

Username + Password

• Auto-generate

  Select whether the appliance creates a random password.

  Note

  If the radio button Yes is selected, it is not possible to define a password in the input box Password.

• Username

  Definition of the login name used by the appliance to authenticate on the scanned target system.

  Note

  Only the following characters are allowed for the user name:

  • All English alphanumeric characters

  • - (dash)

  • _ (underscore)

  • \ (backslash)

  • . (full stop)

  • @ (at sign)

  This also excludes the German umlauts, which must be replaced as follows:

  • “ß” → “ss”

  • “ä” → “a”

  • “ö” → “o”

  • “ü” → “u”

• Password

  Definition of the password used by the appliance to authenticate on the scanned target system.

Username + SSH Key

• Auto-generate

  Select whether the appliance creates a random password.

  Note

  If the radio button Yes is selected, it is not possible to define a password in the input box Password.

• Username

  Definition of the login name used by the appliance to authenticate on the scanned target system.

  Note

  Only the following characters are allowed for the user name:

  • All English alphanumeric characters

  • - (dash)

  • _ (underscore)

  • \ (backslash)

  • . (full stop)

  • @ (at sign)

  This also excludes the German umlauts, which must be replaced as follows:

  • “ß” → “ss”

  • “ä” → “a”

  • “ö” → “o”

  • “ü” → “u”

• Passphrase

  Definition of the passphrase of the private SSH key.

• Private Key

  Upload of the private SSH key.

• Certificate

  Upload of the certificate file.

• Private Key

  Upload of the corresponding private key.

SNMP

SNMPv3 requires a user name, an authentication password, and a privacy password, while all older SNMP versions (SNMPv1 and SNMPv2) only require an SNMP community.

Note

Due to the singular nature of the SNMP credential, it is currently not possible to configure either SNMPv1/v2 or SNMPv3 mode.

This means that the appliance will always try to log in with all SNMP protocol versions. It is possible to see both the result SNMP Login Successful For Authenticated Checks and the result SNMP Login Failed For Authenticated Checks for a scan, for example if the SNMPv3 login information in the credential is correct, but the SNMPv1/2 information is incorrect.

• SNMP Community

  Definition of the community for SNMPv1 or SNMPv2c.

• Username

  Definition of the user name for SNMPv3.

  Note

  Only the following characters are allowed for the user name:

  • All English alphanumeric characters

  • - (dash)

  • _ (underscore)

  • \ (backslash)

  • . (full stop)

  • @ (at sign)

  This also excludes the German umlauts, which must be replaced as follows:

  • “ß” → “ss”

  • “ä” → “a”

  • “ö” → “o”

  • “ü” → “u”

• Password

  Definition of the password for SNMPv3.

• Privacy Password

  Definition of the password for the encryption for SNMPv3.

• Auth Algorithm

  Selection of the authentication algorithm (MD5 or SHA1).

• Privacy Algorithm

  Selection of the encryption algorithm (AES, DES or none).

S/MIME Certificate

• S/MIME Certificate

  Upload of the certificate file.

PGP Encryption Key

• PGP Public Key

  Upload of the key file.

Password only

• Password

  Definition of the password used by the appliance to authenticate on the scanned target system.

Note

The credential has to be linked to at least one target. This allows the scan engine to apply the credential.

10.3.2.2 Managing Credentials

List Page

All existing credentials can be displayed by selecting Configuration > Credentials in the menu bar.

For all credentials the following information is displayed:

Name

Name of the credential.

Type

Chosen credential type.

Allow insecure use

Indication whether the appliance can use the credential for unencrypted or otherwise insecure authentication methods.

Login

User name for the credential if a credential type that requires a user name is chosen.

For all credentials the following actions are available:

• Move the credential to the trashcan. Only credentials which are currently not used can be moved to the trashcan.

• Edit the credential.

• Clone the credential.

• Export the credential as an XML file.

Depending on the chosen credential type (see Chapter 10.3.2.1) more actions may be available:

• Download an EXE package for Microsoft Windows. This action is available if Username + Password was chosen.

• Download an RPM package for Red Hat Enterprise Linux and its derivates. This action is available if Username + SSH Key was chosen.

• Download a Debian package for Debian GNU/Linux and its derivates. This action is available if Username + SSH Key was chosen.

• Download a public key. This action is available if Username + SSH Key was chosen.

These installation packages simplify the installation and creation of accounts for authenticated scans. They create the user and the most important permissions for the authenticated scan and reset them during uninstalling.

Note

If the auto-generation of passwords is enabled (see Chapter 10.3.2.1), the packages have to be used, otherwise the usage is optional.

Note

By clicking or below the list of credentials more than one credential can be moved to the trashcan or exported at a time. The drop-down list is used to select which credentials are moved to the trashcan or exported.

Details Page

Click on the name of a credential to display the details of the credential. Click to open the details page of the credential.

The following registers are available:

Information

General information about the credential.

User Tags

Assigned tags (see Chapter 8.4).

Permissions

Assigned permissions (see Chapter 9.4).

The following actions are available in the upper left corner:

• Open the corresponding chapter of the user manual.

• Show the list page of all credentials.

• Create a new credential (see Chapter 10.3.2.1).

• Clone the credential.

• Edit the credential.

• Move the credential to the trashcan. Only credentials which are currently not used can be moved to the trashcan.

• Export the credential as an XML file.

Depending on the chosen credential type (see Chapter 10.3.2.1) more actions may be available:

• Download an EXE package for Microsoft Windows. This action is available if Username + Password was chosen.

• Download an RPM package for Red Hat Enterprise Linux and its derivates. This action is available if Username + SSH Key was chosen.

• Download a Debian package for Debian GNU/Linux and its derivates. This action is available if Username + SSH Key was chosen.

• Download a public key. This action is available if Username + SSH Key was chosen.

10.3.3 Requirements on Target Systems with Microsoft Windows

10.3.3.1 General Notes on the Configuration

• The remote registry service must be started in order to access the registry.

  This is achieved by configuring the service to automatically start up. If an automatic start is not preferred, a manual startup can be configured. In that case, the service is started while the system is scanned by the appliance and afterwards it is disabled again. To ensure this behavior, the following information about LocalAccountTokenFilterPolicy must be considered.

• It is necessary that for all scanned systems the file and printer sharing is activated. If using Microsoft Windows XP, take care to disable the setting Use Simple File Sharing.

• For individual systems not attached to a domain the following registry key must be set:

  HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\
  DWORD: LocalAccountTokenFilterPolicy = 1
  

• On systems with domain controller the user account in use must be a member of the group Domain Administrators to achieve the best possible results. Due to the permission concept it is not possible to discover all vulnerabilities using the Local Administrator or the administrators assigned by the domain. Alternatively follow the instructions in Chapter 10.3.3.2.

  → Should a Local Administrator be selected – which it explicitly not recommended – it is mandatory to set the following registry key as well:

  HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\
  DWORD: LocalAccountTokenFilterPolicy = 1
  

• Generated install package for credentials: The installer sets the remote registry service to auto start. If the installer is executed on a domain controller, the user account will be assigned to the group BUILTIN/Administrators (SID S-1-5-32-544).

• An exception rule for the appliance on the Microsoft Windows firewall must be created. Additionally, on XP systems the service File and Printer Sharing must be set to enabled.

• Generated install package for credentials: During the installation, the installer offers a dialog to enter the appliance’s IP address. If the entry is confirmed, the firewall rule is configured. The service File and Printer Sharing will be enabled in the firewall rules.

• Powershell execution privileges on a target system may be required for the account utilized in an authenticated scan. Policy and vulnerability tests may occasionally execute Powershell commands to increase the accuracy of results, requiring privileges for the duration of a scan.

• For compliance audits targeting Windows operating systems, it is recommended to set the Maximum concurrently executed NVTs per host/Maximum concurrently scanned hosts to 1 in order to maximize the accuracy of the results (see Chapter 12.2.1.1).

• For a fully working Windows Management Instrumentation (WMI) access which is used for, for example file search or policy scans, the following settings are required:

  • Allow WMI access in the Windows Firewall settings or a possible third-party firewall solution.

  • Verify that the user or the group of the scan user is allowed to access WMI remotely.

10.3.3.2 Configuring a Domain Account for Authenticated Scans

For authenticated scans of Microsoft Windows target systems, it is highly recommended to use a domain account with a domain policy that grants local administrator privileges. This has several advantages:

• A domain policy only needs to be created once and can then be applied or revoked for different user accounts.

• Editing the Microsoft Windows registry locally is no longer required. User administration is thus centralized, which saves time in the long term and reduces possible configuration errors.

• From a vulnerability assessment perspective, only a domain account allows for the detection of domain-related scan results. These results will be missing if using a local user account.

• There are also several security advantages to using a domain account with the domain policy recommended by Greenbone: the corresponding user may not log in locally or via the remote desktop protocol (RDP), limiting possible attack vectors. Additionally, the user credentials are secured via Kerberos, while the password of a local user account is at much greater risk of being exposed through exploits.

In order to use a domain account for host based remote audits on a Microsoft Windows target, the following configuration must be made under Windows XP Professional, Windows Vista, Windows Server 2003, Windows Server 2008, Windows Server 2012, Windows Server 2016, Windows 7, Windows 8, Windows 8.1 or Windows 10. The system must also be part of the domain.

Creating a Security Group

1. Log into a domain controller and open Active Directory Users and Computers.

2. Select Action > New > Group in the menu bar.

3. Enter Greenbone Local Scan in the input box Name.

4. Select Global for Group Scope and Security for Group Type.

5. Add the account used for the local authenticated scans by the appliance under Microsoft Windows to the group.

6. Click OK.

Creating a Group Policy Object (GPO)

1. In the left panel open the console Group Policy Management.

2. Right click Group Policy Objects and select New.

3. Enter Greenbone Local SecRights in the input box Name (see Fig. 10.8).

   

   Fig. 10.8 Creating a new Microsoft Windows group policy object for Greenbone scans

4. Click OK.

Configuring the Policy

1. Click the policy Greenbone Local SecRights and select Edit.

2. Select Computer Configuration > Policies > Windows Settings > Security Settings in the left panel.

3. Click Restricted Groups and select Add Group.

4. Click Browse… and enter Greenbone Local Scan in the input box (see Fig. 10.9).

   

   Fig. 10.9 Checking Microsoft Windows group names

5. Click Check Names.

6. Click OK twice to close the open windows.

7. At This group is member of click Add.

8. Enter Administrators in the input box Group (see Fig. 10.10) and click OK twice to close the open windows.

   Note

   On non-English systems enter the respective name of the local administrator group.

   

   Fig. 10.10 Adding a group membership

Configuring the Policy to Deny the Group “Greenbone Local Scan” Logging into the System Locally

1. Click the policy Greenbone Local SecRights and select Edit.

2. Select Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > User Rights Assignment in the left panel.

3. In the right panel double click Deny log on locally.

4. Activate the checkbox Define these policy settings and click Add User or Group.

5. Click Browse… and enter Greenbone Local Scan in the input box (see Fig. 10.11).

6. Click Check Names.

   

   Fig. 10.11 Editing the policy

7. Click OK three times to close the open windows.

Configuring the Policy to Deny the Group “Greenbone Local Scan” Logging into the System via Remote Desktop

1. Click the policy Greenbone Local SecRights and select Edit.

2. Select Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > User Rights Assignment in the left panel.

3. In the right panel double click Deny log on through Remote Desktop Services.

4. Activate the checkbox Define these policy settings and click Add User or Group.

5. Click Browse… and enter Greenbone Local Scan in the input box (see Fig. 10.12).

6. Click Check Names.

   

   Fig. 10.12 Editing the policy

7. Click OK three times to close the open windows.

Configuring the Policy to Give Read Permissions Only to the Registry for the Group “Greenbone Local Scan”

Important

This setting still exists after the GPO has been removed (“tattooing GPO”).

This changes fundamental privileges which may not be simply reversed by removing the GPO.

Research whether the settings are compatible with the environment.

Note

The following steps are optional.

1. In the left panel right click Registry and select Add Key.

2. Select USERS and click OK (see Fig. 10.13).

   

   Fig. 10.13 Selecting the registry key

3. Click Advanced and Add.

4. Enter Greenbone Local Scan in the input box and click OK (see Fig. 10.14).

   

   Fig. 10.14 Selecting the group Greenbone Local Scan

5. Select This object and child objects in the drop-down list Apply to.

6. Deactivate all checkboxes for Allow and activate the checkboxes Set Value, Create Subkey, Create Link, Delete, Change Permissions and Take Ownership for Deny (see Fig. 10.15).

   

   Fig. 10.15 Disallowing edition of the registry

7. Click OK twice and confirm the warning message by clicking Yes.

8. Click OK.

9. Select the radio buttons Configure this key then and Propagate inheritable permissions to all subkeys and click OK (see Fig. 10.16).

   

   Fig. 10.16 Making the permissions recursive

10. Repeat the steps 2 to 9 for MACHINE and CLASSES_ROOT.

Linking the Group Policy Object

1. In the right panel right click the domain and select Link an Existing GPO….

2. Select Greenbone Local SecRights in the section Group Policy objects and click OK (see Fig. 10.17).

   

   Fig. 10.17 Linking the policy

10.3.3.3 Restrictions

Based on the fact that write permissions to the registry and system drive have been removed, the following two tests will no longer work:

• Leave information on scanned Windows hosts (OID 1.3.6.1.4.1.25623.1.0.96171)

  This test, if desired, creates information about the start and end of a scan under HKLM\Software\VulScanInfo. Due to denying write access to HKLM this is no longer possible. If the test should be possible, the GPO must be adjusted respectively.

• Windows file Checksums (OID 1.3.6.1.4.1.25623.1.0.96180)

  This test, if desired, saves the tool ReHash under C:\Windows\system32 (for 32-bit systems) or C:\Windows\SysWOW64 (for 64-bit systems). Due to denying write access this is no longer possible. If the test should be possible, the tool must be saved separately or the GPO must be adjusted respectively.

  More information can be found in Chapter 12.4.3.

10.3.3.4 Scanning Without Domain Administrator and Local Administrator Permissions

It is possible to build a GPO in which the user also does not have any local administrator permissions. But the effort to add respective read permissions to each registry branch and folder is huge. Unfortunately, inheriting of permissions is deactivated for many folders and branches. Additionally, these changes can be set by GPO but cannot be removed again (tattooing GPO). Specific permissions could be overwritten so that additional problems could occur as well.

Building a GPO in which the user does not have any local administrator permissions does not make sense from a technical and administrative point of view.

10.3.4 Requirements on Target Systems with ESXi

Note

If a vCenter Server Appliance (VCSA) is used to control ESXi hosts and users are created on the VCSA, they are only known on the VCSA and not on the ESXi hosts.

Scan users must be created on each ESXi host that will be scanned.

By default, local ESXi users are limited to read-only roles. Either an administrative account or a read-only role with permission to global settings has to be used.

A read-only role with permission to global settings can be set up as follows:

1. Open the web interface of the VMware ESXi instance and log in.

2. Select Host > Manage in the Navigator column on the left.

3. Select the register Security & users.

4. Select Roles in the left menu panel (see Fig. 10.18).

   

   Fig. 10.18 Displaying the roles

5. Click Add role.

6. Enter a name for the role in the input box Role name.

7. Activate the checkbox System.

8. Click Global and activate the checkbox Settings (see Fig. 10.19).

   

   Fig. 10.19 Creating a role

9. Click Add.

10. Right click Host and select Permissions in the Navigator column on the left.

11. Select the scan user account used by the appliance.

12. Click Assign role.

13. Select the previously created role in the drop-down list (see Fig. 10.20).

    

    Fig. 10.20 Assigning the role to the scan user

14. Click Assign role.

15. Click Close.

10.3.5 Requirements on Target Systems with Linux/Unix

• For authenticated scans on Linux or Unix systems, regular user access is usually enough. The login is performed via SSH. The authentication is done either with passwords or a private SSH key stored on the appliance.

• A remote SSH server should have the following defaults configured in the file sshd_config:

  • MaxSessions: 10

  • MaxAuthTries: 6

  When using non-default and lower values, failed logins may occur.

• Generated installation package for credentials: the install package for Linux distributions based on Debian is a DEB file, the install package for Linux distributions based on Red Hat is an RPM file. Both install packages create a new user without any specific permissions. A public SSH key that is created on the appliance is stored in the user’s home folder. For users of other Linux distributions or Unix derivatives, the public key is offered for download. Creating a user and saving the public key with the proper file permissions is the responsibility of the user.

• In both cases it must be made sure that public key authentication is not prohibited by the SSH daemon. The line PubkeyAuthentication no must not be present.

• Existing SSH key pairs may also be used. SSH key pairs can be generated using the command ssh-keygen on Linux or puttygen.exe if using PuTTY on Microsoft Windows. To use an existing SSH key pair for authentication, the private key must be supplied when the credential is created. The private SSH key must be either in PEM or OpenSSH format. The key types Ed25519, ECDSA, RSA and DSA are supported.

• For scans that include policy testing, root permission or the membership in specific groups (often wheel) may be necessary. For security reasons, many configuration files are only readable by super users or members of specific groups.

• The more permissions a user has, the more results and settings can be detected on a system. In some cases root user access may be required.

• The following commands are executed with root user access during an authenticated scan.

  Important

  • This list is not static. New or changed VTs may add new commands at any time.

  • Depending on the found software, additional commands may be executed.

  • The executed commands depend on the Linux distribution and the selected scan configuration.

  • bash

  • cat

  • date

  • dpkg

  • egrep

  • find

  • grep

  • host

  • id

  • ip

  • lastlog

  • locate

  • ls

  • md5sum

  • mlocate

  • netstat

  • perl

  • ps

  • rpm

  • sh

  • sha1sum

  • slocate

  • uname

  • uptime

  • whereis

  • which

• The installation of the package locate (alternatively mlocate) to provide the command locate/mlocate on the target system is recommended. The use of this command reduces calls to the command find used to search for files and thus, improves the search performance and lowers the resource usage on the target system.

  For the commands to work, the corresponding database permissions and regular database updates, for example via a cron job, may need to be configured.

10.3.6 Requirements on Target Systems with Cisco OS

The appliance can check network components like routers and switches for vulnerabilities as well. While the usual network services are discovered and checked via the network, some vulnerabilities can only be discovered by an authenticated scan. For the authenticated scan, the appliance can use either SNMP or SSH.

10.3.6.1 SNMP

The appliance can use the SNMP protocol to access the Cisco network component. The appliance supports SNMPv1, v2c and v3. SNMP uses the port 161/UDP. The default port list does not include any UDP port. Therefore, this port is ignored during the vulnerability scan using the scan configuration Full and fast and no SNMP check is enabled. To scan network components the port list should be modified to include at least the following ports:

• 22/TCP SSH

• 80/TCP 8080/TCP HTTP

• 443/TCP 8443/TCP HTTPS

• 2000/TCP SCCP

• 2443/TCP SCCPS

• 5060/TCP 5060/UDP SIP

• 5061/TCP 5061/UDP SIPS

• 67/UDP DHCP Server

• 69/UDP TFTP

• 123/UDP NTP

• 161/UDP SNMP

• 162/UDP SNMP Traps

• 500/UDP IKE

• 514/UDP Syslog

• 546/UDP DHCPv6

• 6161/UDP 6162/UDP Unified CM

The administrator can set up special port lists used only for such network components.

The appliance needs to access only very few objects from the SNMP tree. For a less privileged access an SNMP view should be used to constrain the visibility of the SNMP tree for the appliance. The following two examples explain how to set up the view using either a community string or an SNMPv3 user.

To use an SNMP community string the following commands are required on the target:

# configure terminal

Using an access list the usage of the community can be restricted. The appliance’s IP address is 192.168.222.74 in this example:

(config) # access-list 99 permit 192.168.222.74

The view gsm should only allow accessing the system description:

(config) # snmp-server view gsm system included
(config) # snmp-server view gsm system.9 excluded

The last command links the community gsm-community with the view gsm and the access list 99:

(config) # snmp-server community gsm-community view gsm RO 99

If using an SNMPv3 user including encryption the following configuration lines are required on the target:

# configure terminal
(config) # access-list 99 permit 192.168.222.74
(config) # snmp-server view gsm system included
(config) # snmp-server view gsm system.9 excluded

SNMPv3 requires the setup of a group first. Here the group gsmgroup is linked to the view gsm and the access list 99:

(config) # snmp-server group gsmgroup v3 priv read gsm access 99

Now the user can be created supplying the password gsm-password and the encryption key gsm-encrypt. The authentication is done using MD5 while the encryption is handled by AES128:

(config) # snmp-server user gsm-user gsm-group v3 auth md5 gsm-password priv
aes 128 gsm-encrypt

To configure either the community or the SNMPv3 user on the appliance, the administrator selects Configuration > Credentials in the menu bar (see Chapter 10.3.2).

10.3.6.2 SSH

The authenticated scan can be performed via SSH as well. If using SSH, the usage of a special unprivileged user is recommended. The appliance currently requires only the command show version to retrieve the current version of the firmware of the device.

To set up a less privileged user who is only able to run this command, several approaches are possible. The following example uses the role-based access control feature.

Note

Before using the following example, make sure all side effects of the configuration are understood. If used without verification, the system may restrict further logins via SSH or console.

To use role-based access control AAA and views have to be enabled:

> enable
# configure terminal
(config)# aaa new-model
(config)# exit
> enable view
# configure terminal

The following commands create a restricted view including just the command show version. The supplied password view-pw is not critical:

(config)# parser view gsm-view
(config-view)# secret 0 view-pw
(config-view)# commands exec include show version
(config-view)# exit

Now the user gsm-user with the password gsm-pw is created and linked to the view gsm-view:

(config)# username gsm-user view gsm-view password 0 gsm-pw
(config)# aaa authorization console
(config)# aaa authorization exec default local

If SSH is not enabled yet the following commands take care of that. Use the appropriate host name and domain:

(config)# hostname switch
(config)# ip domain-name greenbone.net
(config)# crypto key generate rsa general-keys modulus 2048

Finally, enable SSH logins using the following commands:

(config)# line vty 0 4
(config-line)# transport input ssh
(config-line)# Crtl-Z

Note

For executing a full scan, for example with the scan configuration Full and fast, the setting ssh server rate-limit must be set to 240. Before scanning, this value should be checked and adjusted if necessary.

The credentials of the user must be entered on the appliance. Select Configuration > Credentials in the menu bar and create the appropriate user (see Chapter 10.3.2).

Link the credentials to the target to be used as SSH credentials.

10.3.7 Requirements on Target Systems with Huawei VRP

The appliance can check network components like routers and switches for vulnerabilities as well. While the usual network services are discovered and checked via the network, some vulnerabilities can only be discovered by an authenticated scan. For the authenticated scan, the appliance can use either SNMP or SSH.

Note

The commands in this chapter serve as an example and should work on most Huawei routers.

Depending on the software version or hardware, some commands may differ (for example the order of the parameters or values), may not be necessary, or may not be available.

More information can be found in the related documentation for the respective device and software version.

10.3.7.1 SNMP

The appliance can use the SNMP protocol to access the Huawei network component. The appliance supports SNMPv1, v2c and v3. SNMP uses the port 161/UDP. The default port list does not include any UDP port. Therefore, this port is ignored during the vulnerability scan using the scan configuration Full and fast and no SNMP check is enabled. To scan network components, the port list should be modified to include at least the following ports:

• 22/TCP SSH

• 80/TCP 8080/TCP HTTP

• 443/TCP 8443/TCP HTTPS

• 2000/TCP SCCP

• 2443/TCP SCCPS

• 5060/TCP 5060/UDP SIP

• 5061/TCP 5061/UDP SIPS

• 67/UDP DHCP Server

• 69/UDP TFTP

• 123/UDP NTP

• 161/UDP SNMP

• 162/UDP SNMP Traps

• 500/UDP IKE

• 514/UDP Syslog

• 546/UDP DHCPv6

The administrator can set up special port lists used only for such network components.

The appliance needs to access only very few objects from the SNMP tree. For a less privileged access, an SNMP view should be used to constrain the visibility of the SNMP tree for the appliance. The following two examples explain how to set up the view using either a community string or an SNMPv3 user.

To use an SNMP community string the following commands are required on the target:

<HUAWEI>system-view

Using an access list the usage of the community can be restricted. The appliance’s IP address is 192.168.222.74 in this example:

[~HUAWEI]acl 2000
[~HUAWEI-acl4-basic-2000]rule permit source 192.168.222.74 32
[*HUAWEI-acl4-basic-2000]commit
[~HUAWEI-acl4-basic-2000]quit

Allow Version 2c of SNMPv:

[~HUAWEI]snmp-agent sys-info version v3 v2c
[*HUAWEI]commit

The view gsm should only allow accessing the system description:

[~HUAWEI]snmp-agent mib-view included gsm system
[*HUAWEI]snmp-agent mib-view excluded gsm system.9
[*HUAWEI]commit

The last command links the community gsm-community with the view gsm and the access list 2000:

[~HUAWEI]snmp-agent community read gsm-community mib-view gsm acl 2000
[*HUAWEI]commit

If using an SNMPv3 user including encryption, the following configuration lines are required on the target:

<HUAWEI>system-view
[~HUAWEI]acl 2000
[~HUAWEI-acl4-basic-2000]rule permit source 192.168.222.74 32
[*HUAWEI-acl4-basic-2000]quit
[*HUAWEI]snmp-agent sys-info version v3
[*HUAWEI]snmp-agent mib-view included gsm system
[*HUAWEI]snmp-agent mib-view excluded gsm system.9
[*HUAWEI]commit

SNMPv3 requires the setup of a group first. Here the group gsmgroup is linked to the view gsm and the access list 2000:

[~HUAWEI]snmp-agent group v3 gsmgroup privacy read-view gsm acl 2000
[*HUAWEI]commit

Now the user can be created supplying the password gsm-password and the encryption key gsm-encrypt. The authentication is done using MD5 while the encryption is handled by AES128. This is done in three steps:

Configure the password gsm-password:

[~HUAWEI]snmp-agent usm-user v3 gsm-user authentication-mode md5
Please configure the authentication password (8-255)
[*HUAWEI]commit

Configure encryption key gsm-encrypt:

[~HUAWEI]snmp-agent usm-user v3 gsm-user privacy-mode aes128
Please configure the privacy password (8-255)
[*HUAWEI]commit

Add the user to the group:

[*HUAWEI]snmp-agent usm-user v3 gsm-user group gsmgroup
[*HUAWEI]commit

To configure either the community or the SNMPv3 user on the appliance, the administrator selects Configuration > Credentials in the menu bar (see Chapter 10.3.2).

10.3.7.2 SSH

The authenticated scan can be performed via SSH as well. If using SSH, the usage of a special unprivileged user is recommended. The appliance currently requires only the commands display device, display version and display patch-information to retrieve the device’s current firmware version.

Note

If a compliance scan is performed, the following additional commands may be used:

• display arp speed-limit

• display arp-miss speed-limit source-ip

• display current-configuration

• display current-configuration configuration bgp

• display current-configuration configuration pim

• display current-configuration configuration user-interface

• display current-configuration configuration vpn-instance

• display current-configuration interface

• display current-configuration | include multicast

• display current-configuration | include ntp

• display current-configuration | include snmp

• display current-configuration | include ssh

• display ftp-server

• display isis peer

• display mpls ldp session verbose

• display mpls rsvp-te interface

• display ospf peer brief

• display ospfv3 peer

• display snmp-agent sys-info version

• display ssh server status

• display telnet server

• display telnet server status

• display vrrp

To set up a less privileged user who is only able to run this command, several approaches are possible. The following example uses the role-based access control feature.

Note

Before using the following example, make sure all side effects of the configuration are understood. If used without verification, the system may restrict further logins via SSH or console.

The following commands create a restricted view including just the commands display device, display version and display patch-information. The supplied password Hello-secret123 is not critical.

<HUAWEI> system-view
[~HUAWEI]aaa
[~HUAWEI-aaa]local-user gsm-user password cipher Hello-secret123
[*HUAWEI-aaa]local-user gsm-user level 0
[*HUAWEI-aaa]local-user gsm-user service-type ssh
[*HUAWEI-aaa]commit
[~HUAWEI-aaa]quit
[~HUAWEI]ssh user gsm-user authentication-type password
[*HUAWEI]ssh user gsm-user service-type stelnet
[*HUAWEI]commit

The following commands add just the commands display version, display patch-information and display device to “level 0”, so that gsm-user is restricted:

[~HUAWEI] command-privilege level 0 view global display device
[*HUAWEI] command-privilege level 0 view global display version
[*HUAWEI] command-privilege level 0 view global display patch-information
[*HUAWEI]commit

If SSH is not enabled yet the following commands take care of that:

[~HUAWEI] rsa local-key-pair create
[*HUAWEI]commit

Enable SSH logins using the following commands:

[~HUAWEI] user-interface vty 0 4
[*HUAWEI-ui-vty0-4] authentication-mode aaa
[*HUAWEI-ui-vty0-4] protocol inbound ssh
[*HUAWEI-ui-vty0-4] quit
[*HUAWEI]commit

Enable the STelnet server:

[~HUAWEI] stelnet server enable
[*HUAWEI] ssh authentication-type default password
[*HUAWEI]commit

Using an access list, the usage of the SSH login can be restricted. The appliance’s IP address is 192.168.222.74 in this example.

Note

This may restrict any SSH logins from other IP addresses and render the device inaccessible via network.

[~HUAWEI]acl 2000
[*HUAWEI-acl4-basic-2000] rule permit source 192.168.222.74 32
[*HUAWEI-acl4-basic-2000] quit
[*HUAWEI] HUAWEI acl 2000
[*HUAWEI] commit

Depending on the security settings the password for gsm-view has to be changed on the first login. This should be checked by logging in manually once via SSH.

The credentials of the user need to be entered on the appliance. Select Configuration > Credentials in the menu bar and create the appropriate user (see Chapter 10.3.2).

Link the credentials to the target to be used as SSH credentials.

10.3.8 Requirements on Target Systems with EulerOS

• For authenticated scans on EulerOS, regular user access is usually enough. The login is performed via SSH. The authentication is done either with passwords or a private SSH key stored on the appliance.

• Generated installation package for credentials: the install package for EulerOS is an RPM file. The install package creates a new user without any specific permissions. A public SSH key that is created on the appliance is stored in the user’s home folder.

• In both cases it needs to be made sure that public key authentication is not prohibited by the SSH daemon. The line PubkeyAuthentication no must not be present.

• Existing SSH key pairs may also be used. SSH key pairs can be generated using the command ssh-keygen on EulerOS or puttygen.exe if using PuTTY on Microsoft Windows. To use an existing SSH key pair for authentication, the private key must be supplied when the credential is created. The private SSH key must be either in PEM or OpenSSH format. The key types Ed25519, ECDSA, RSA and DSA are supported.

• For scans that include policy testing, root permission or the membership in specific groups (often wheel) may be necessary. For security reasons, many configuration files are only readable by super users or members of specific groups.

• The more permissions a user has, the more results and settings can be detected on a system. In some cases root user access may be required.

• The following commands are executed with root user access during an authenticated scan.

  Important

  • This list is not static. New or changed VTs may add new commands at any time.

  • Depending on the found software, additional commands may be executed.

  • bash

  • cat

  • date

  • dpkg

  • egrep

  • find

  • grep

  • host

  • id

  • ip

  • lastlog

  • locate

  • ls

  • md5sum

  • mlocate

  • netstat

  • perl

  • ps

  • rpm

  • sh

  • sha1sum

  • slocate

  • uname

  • uptime

  • whereis

  • which

• The installation of the package locate (alternatively mlocate) to provide the command locate/mlocate on the target system is recommended. The use of this command reduces calls to the command find used to search for files and thus, improves the search performance and lowers the resource usage on the target system.

  For the commands to work, the corresponding database permissions and regular database updates, for example via a cron job, may need to be configured.

10.3.9 Requirements on Target Systems with GaussDB

Note

It has to be ensured that the scan is performed by a user that has GaussDB executing permissions.

10.3.9.1 Requirements for System User root

Note

Generally, scanning with the user root is not recommended.

A root user has the following requirements for scanning a target system with GaussDB:

• On the appliance:

  • Credentials for the target host(s), either as a password or as an SSH key

• On the target system:

  • Root user is able to execute zsql/zengine (for example LD_LIBRARY_PATH is set properly and not on default)

  • PermitRootLogin yes in sshd_config or PermitRootLogin prohibit-password in sshd_config for SSH key based credentials

10.3.9.2 Requirements for Database Administrator Accounts (for example gaussdba)

A database administrator has the following requirements for scanning a target system with GaussDB:

• On the appliance:

  • Credentials for the target host(s), either as a password or as an SSH key

• On the target system:

  • User gaussdba is the database installation user

10.3.9.3 Requirements for a Regular User Accounts

A regular user has the following requirements for scanning a target system with GaussDB:

• On the appliance:

  • Credentials for the target host(s), either as a password or as an SSH key

• On the target system:

  • User is able to execute zsql/zengine (for example LD_LIBRARY_PATH is set properly and not on default)

10.3.9.4 Requirements for a Regular Database User Accounts (for example gauss)

A regular database user has the following requirements for scanning a target system with GaussDB:

• On the appliance:

  • Credentials with the user name gauss and a password configured in each used scan configuration

• On the target system:

  • Public facing database server port

10.4 Configuring a CVE Scan

Not every vulnerability justifies a new scan of the network or of individual systems. If the appliance has already obtained information about vulnerabilities by previous scans, it can make a prognosis of which security risks could currently exist.

Using the CVE scanner allows for a quick prediction of possible security risks without the need of another vulnerability scan. This is especially interesting for environments in which most vulnerabilities have been removed or remediated by using the appliance. If new security risks are predicted, an actual vulnerability scan can be run to verify the prognosis.

The CVE scanner checks the CPEs of the target hosts present in the latest report for the same IP address for assigned CVEs present in the current SecInfo (see Chapter 14). Only reports of tasks that have the Add results to Assets setting enabled will be included. It is not relevant whether the setting is enabled before or after the scan.

Note

The CVE scanner might show false positives for the following reasons:

• The scanner does not check whether the vulnerability actually exists.

• The scanner has no capabilities to detect “backported” security fixes, for example on Unix-like systems, because it depends on the National Vulnerability Database (NVD), which does not maintain this fixed status and because there is no exposure of the fixed status in the version of the product.

Note

There are some prerequisites for successfully running a CVE scan:

• In order to be detected, a CVE must have a CPE assigned in the National Vulnerability Database (NVD).

  • As long as the CVE is not analyzed yet (see the corresponding entry in the NVD), no results are expected for a CVE when running a CVE scan.

  • Additionally, a correct CPE must be assigned to the CVE in the NVD. In case of doubt, the CPE-CVE assignment should be checked manually on the related NVD web page(s).

• The asset database requires current data for the CVE scanner. For detecting the products, a full scan, for example with the scan configuration Full and fast, must be performed before running the CVE scan.

  • Whether a product was detected can be checked in the Applications register of the full scan’s report.

  • For the full scan, the task option Add results to Assets must be activated, so that the results are added to the asset database and are available to the CVE scanner.

  • Running a full scan with authentication may increase the results found by the CVE scan.

  • A full scan of the systems should be run regularly.

A CVE scan can be run as follows:

1. Run a full scan (see Chapter 10.2).

   Note

   A full scan configuration has to be chosen, for example Full and fast.

   Additionally, the radio button Yes has to be selected for Add results to Assets.

2. Select Scans > Tasks in the menu bar.

3. Create a new task by moving the mouse over and clicking New Task.

4. Define the task (see Chapter 10.2.2).

5. Select CVE in the drop-down list Scanner.

6. Click Save.

7. In the row of the task, click .

   → The scan is running. For the status of a task see Chapter 10.8.

   Tip

   The report of a task can be displayed as soon as the task has been started by clicking the bar in the column Status. For reading, managing and downloading reports see Chapter 11.

   As soon as the status changes to Done the complete report is available. At any time the intermediate results can be reviewed (see Chapter 11.2.1).

   Note

   It can take a while for the scan to complete. The page is refreshing automatically if new data is available.

8. When the scan is completed select Scans > Reports in the menu bar.

9. Click on the date of the report to show the results.

   → The report shows each found CVE as a vulnerability (see Fig. 10.21).

   

   Fig. 10.21 Results of a CVE scan

10. Click on a vulnerability and click .

    → The details page of the vulnerability is opened.

    The VT to which the result is assigned is displayed in the section Detection Method (see Fig. 10.22). By clicking on the VT, the details page of the corresponding VT is opened.

    Tip

    For available actions on this page see Chapter 11.2.1.

    

    Fig. 10.22 Details of a detected CVE

10.5 Using Container Tasks

10.5.1 Creating a Container Task

A container task can be used to import and provide reports created on other appliances.

A container task can be created as follows:

1. Select Scans > Tasks in the menu bar.

2. Create a new container task by moving the mouse over and clicking New Container Task.

3. Enter the name of the container task in the input box Name (see Fig. 10.23).

   

   Fig. 10.23 Creating a container task

4. Click Save.

5. To add a report to the container task click in the row of the container task.

6. Click Browse… and select the XML file of a report (see Fig. 10.24).

   

   Fig. 10.24 Adding a report to a container task

7. Select the radio button Yes to add the report to the assets (see Chapter 13).

8. Click Import.

10.5.2 Managing Container Tasks

List Page

All existing container tasks can be displayed by selecting Scans > Tasks in the menu bar.

Note

Container tasks can be identified by in the column Status.

For all container tasks the following actions are available:

• Import reports to the container task.

• Move the container task to the trashcan.

• Edit the container task.

• Clone the container task.

• Export the container task as an XML file.

Note

By clicking or below the list of tasks more than one task can be moved to the trashcan or exported at a time. The drop-down list is used to select which tasks are moved to the trashcan or exported.

Details Page

Click on the name of a container task to display the details of the container task. Click to open the details page of the container task.

The following registers are available:

Information

General information about the container task.

User Tags

Assigned tags (see Chapter 8.4).

Permissions

Assigned permissions (see Chapter 9.4).

The following actions are available in the upper left corner:

• Open the corresponding chapter of the user manual.

• Show the list page of all container tasks.

• Create a new task (see Chapter 10.2.2) or container task (see Chapter 10.5).

• Clone the container task.

• Edit the container task.

• Move the container task to the trashcan.

• Export the container task as an XML file.

• Import reports to the container task.

• Show the last report for the container task or show all reports for the container task.

• Show the results for the container task.

• Show the notes for the container task.

• Show the overrides for the container task.

10.6 Managing Targets

List Page

All existing targets can be displayed by selecting Configuration > Targets in the menu bar.

For all targets the following information is displayed:

Name

Name of the target.

Hosts

Hosts that are scanned if the target is used for a scan (see Chapter 10.2.2).

IPs

Number of scanned hosts.

Port List

Port list used if the target is used for a scan (see Chapter 10.2.2).

Credentials

Credentials configured for the target.

For all targets the following actions are available:

• Move the target to the trashcan. Only targets which are currently not used can be moved to the trashcan.

• Edit the target.

• Clone the target.

• Export the target as an XML file.

Note

By clicking or below the list of targets more than one target can be moved to the trashcan or exported at a time. The drop-down list is used to select which targets are moved to the trashcan or exported.

Details Page

Click on the name of a target to display the details of the target. Click to open the details page of the target.

The following registers are available:

Information

General information about the target.

User Tags

Assigned tags (see Chapter 8.4).

Permissions

Assigned permissions (see Chapter 9.4).

The following actions are available in the upper left corner:

• Open the corresponding chapter of the user manual.

• Show the list page of all targets.

• Create a new target (see Chapter 10.2.1).

• Clone the target.

• Edit the target.

• Move the target to the trashcan. Only targets which are currently not used can be moved to the trashcan.

• Export the target as an XML file.

10.7 Creating and Managing Port Lists

If applications run on unusual ports and they should be monitored and tested with the appliance, the default port lists should be adapted. If necessary, an individual port list including the desired port can be created.

All default port lists by Greenbone are data objects that are distributed via the feed. They are downloaded and updated with each feed update.

If no default port lists are available, a feed update may be necessary, or the Feed Import Owner may need to be set (see Chapter 7.2.1.10.1).

Default port lists cannot be edited. Additionally, they can only be deleted temporarily by the Feed Import Owner or by a super administrator. During the next feed update, they will be downloaded again.

Note

To permanently delete a default port list, the Feed Import Owner has to delete it. Afterwards the Feed Import Owner has to be changed to (Unset) (see Chapter 7.2.1.10.1).

In addition to the default port lists, custom port lists can be created (see Chapter 10.7.1) or imported (see Chapter 10.7.2).

10.7.1 Creating a Port List

A new port list can be created as follows:

1. Select Configuration > Port Lists in the menu bar.

2. Create a new port list by clicking .

3. Define the port list (see Fig. 10.25).

   

   Fig. 10.25 Creating a new port list

4. Click Save.

The following details of the port list can be defined:

Name

Definition of the name. The name can be chosen freely.

Comment

An optional comment can contain additional information.

Port Ranges

Manual entry of the port ranges or importing of a list of the port ranges. If entering manually, the port ranges are separated by commas. If importing from a file, the entries can be separated with commas or line breaks. The file must use ASCII character encoding.

Each value in the list can be a single port (for example 7) or a port range (for example 9-11). These options can be mixed (for example 5, 7, 9-11, 13).

An entry in the list can be preceded by a protocol specifier (T: for TCP, U: for UDP), for example T:1-3, U:7, 9-11 (TCP ports 1, 2 and 3, UDP ports 7, 9, 10 and 11). If no specifier is given, TCP is assumed.

10.7.2 Importing a Port List

A port list can be imported as follows:

1. Select Configuration > Port Lists in the menu bar.

2. Click .

3. Click Browse… and select the XML file of the port list.

4. Click Import.

   → The imported port list is displayed on the page Port Lists.

10.7.3 Managing Port Lists

List Page

All existing port lists can be displayed by selecting Configuration > Port Lists in the menu bar.

For all port lists the following information is displayed:

Name

Name of the port list.

Port Counts – Total

Total number of ports in the port list.

Port Counts – TCP

Number of TCP ports in the port list.

Port Counts – UDP

Number of UDP ports in the port list.

For all port lists the following actions are available:

• Move the port list to the trashcan. Only port lists which are currently not used can be moved to the trashcan. As long as the port list is not deleted from the trashcan, it is not downloaded anew during the next feed update.

• Edit the port list. Only self-created port lists which are currently not used can be edited.

• Clone the port list.

• Export the port list as an XML file.

Note

By clicking or below the list of port lists more than one port list can be moved to the trashcan or exported at a time. The drop-down list is used to select which port lists are moved to the trashcan or exported.

Details Page

Click on the name of a port list to display the details of the port list. Click to open the details page of the port list.

The following registers are available:

Information

General information about the port list.

Port Ranges

All port ranges included in this port list. The first and the last port of a range as well as the protocol specifier are displayed.

User Tags

Assigned tags (see Chapter 8.4).

Permissions

Assigned permissions (see Chapter 9.4).

The following actions are available in the upper left corner:

• Open the corresponding chapter of the user manual.

• Show the list page of all port lists.

• Create a new port list (see Chapter 10.7.1).

• Clone the port list.

• Edit the port list. Only self-created port lists which are currently not used can be edited.

• Move the port list to the trashcan. Only port lists which are currently not used can be moved to the trashcan. As long as the port list is not deleted from the trashcan, it is not downloaded anew during the next feed update.

• Export the port list as an XML file.

10.8 Managing Tasks

List Page

All existing tasks can be displayed by selecting Scans > Tasks in the menu bar.

Fig. 10.26 Page Tasks displaying all tasks

For all tasks the following information is displayed:

Name

Name of the task. The following icons may be displayed:

The task is marked as alterable. The task’s scan target(s), scanner and scan configuration can be edited, even if reports were already created.

The task is configured to run on a remote scanner (see Chapter 16).

The task is visible to one or more other user(s).

The task is owned by another user.

Status

Current status of the task. The following status bars are possible:

There are no runs/reports for the task.

The task was just started. The appliance is preparing the scan. Tasks with this status cannot be stopped, resumed, or deleted.

The task was added to the waiting queue. In some cases, it may remain in the queue. For more information see Chapter 17.3.

The task is currently running. The percent value is based on the number of VTs executed on the selected hosts. For this reason the value does not necessarily correlate with the time spent.

The scan or the container task upload is complete and the appliance is processing data. Tasks with this status cannot be stopped, resumed, or deleted.

The task has been completed successfully.

The task was requested to stop recently. However, the scan engine has not yet reacted to this request yet. Tasks with this status cannot be stopped, resumed, or deleted.

The task was stopped. The latest report is possibly not yet complete. Other reasons for this status could be the reboot of the appliance or a power outage. After restarting the scanner, the task will be resumed automatically.

The task was just resumed. The appliance is preparing the scan. Tasks with this status cannot be stopped, resumed, or deleted.

When resuming a scan, all unfinished hosts are scanned completely anew. The data of hosts that were already fully scanned is kept.

The task was deleted. The actual deletion process can take some time as reports need to be deleted as well. Tasks with this status cannot be stopped, resumed, or deleted.

An error has occurred and the task was interrupted. The latest report is possibly not complete yet or is missing completely.

The task is a container task.

The report is currently being uploaded into the container task.

Reports

Number of reports for the task. By clicking on the number of reports the page Reports is opened. A filter is applied to show only the reports for the selected task.

Last Report

Date and time of the latest report. By clicking it the details page of the latest report is opened.

Severity

Highest severity found by a scan of the task.

Trend

Change of vulnerabilities between the newest and the second newest report (see Chapter 11.5).

For all tasks the following actions are available:

• Start the task. Only currently not running tasks can be started.

• Stop the currently running task. All discovered results will be written to the database.

• Show details of the assigned schedule (only available for scheduled tasks, see Chapter 10.10).

• Resume the stopped task. All unfinished hosts are scanned completely anew. The data of hosts that were already fully scanned is kept.

• Move the task to the trashcan.

• Edit the task.

• Clone the task.

• Export the task as an XML file.

Note

By clicking or below the list of tasks more than one task can be moved to the trashcan or exported at a time. The drop-down list is used to select which tasks are moved to the trashcan or exported.

Details Page

Click on the name of a task to display the details of the task. Click to open the details page of the task.

The following registers are available:

Information

General information about the task.

User Tags

Assigned tags (see Chapter 8.4).

Permissions

Assigned permissions (see Chapter 9.4).

The following actions are available in the upper left corner:

• Open the corresponding chapter of the user manual.

• Show the list page of all tasks.

• Create a new task (see Chapter 10.2.2) or container task (see Chapter 10.5).

• Clone the task.

• Edit the task.

• Move the task to the trashcan.

• Export the task as an XML file.

• Start the task. Only currently not running tasks can be started.

• Stop the currently running task. All discovered results will be written to the database.

• Resume the stopped task. All unfinished hosts are scanned completely anew. The data of hosts that were already fully scanned is kept.

• Show the last report for the task or show all reports for the task.

• Show the results for the task.

• Show the notes for the task.

• Show the overrides for the task.

10.8.1 Granting Permissions for a Task

On the details page of a task permissions for the task can be managed as follows:

Note

By default, regular users cannot create permissions for other users as they do not have access to the user database. To be able to create permissions for other users, a user must have the global and the specific get_users permission (see Chapter 9.4.3).

1. Select Scans > Tasks in the menu bar.

2. Click on the name of a task to display the details of the task. Click to open the details page of the task.

3. Click on the register Permissions.

4. In the section Permissions click .

5. Select the permission type in the drop-down list Grant.

6. Select the radio button User, Group or Role and select the user/role/group in the respective drop-down list (see Fig. 10.27).

Fig. 10.27 Creating a new permission

7. Click Save.

   → The permission is displayed on the details page of the task (see Fig. 10.28).

   

   Fig. 10.28 Permission displayed on the details page of a task

After logging in the user can see the task and can access the respective reports.

10.9 Configuring and Managing Scan Configurations

The appliance comes with various predefined scan configurations. They can be customized and new scan configurations can be created.

10.9.1 Default Scan Configurations

All default scan configurations by Greenbone are data objects that are distributed via the feed. They are downloaded and updated with each feed update.

If no default scan configurations are available, a feed update may be necessary, or the Feed Import Owner may need to be set (see Chapter 7.2.1.10.1).

Default scan configurations cannot be edited. Additionally, they can only be deleted temporarily by the Feed Import Owner or by a super administrator. During the next feed update, they will be downloaded again.

Note

To permanently delete a default scan configuration, the Feed Import Owner has to delete it. Afterwards the Feed Import Owner has to be changed to (Unset) (see Chapter 7.2.1.10.1).

Note

In addition to the default scan configurations, custom scan configurations can be created (see Chapter 10.9.2) or imported (see Chapter 10.9.3).

By default, the following scan configurations are available:

Empty

This scan configuration is an empty template containing no VTs. It can be cloned and used for a completely individual created scan configuration.

The VT families are static, which means that new VTs of the chosen VT families are not added and used automatically.

Base

This scan configuration only uses VTs which collect information about the target system. No vulnerabilities are being detected. It can be cloned and used for a completely individual created scan configuration.

The used port scanner is Ping Host which detects whether a host is alive. Additionally, information about the operating system is collected.

The VT families are static, which means that new VTs of the chosen VT families are not added and used automatically.

Discovery

This scan configuration only uses VTs that provide information about the target system. No vulnerabilities are being detected.

Amongst others, the collected information contains information about open ports, used hardware, firewalls, used services, installed software and certificates. The system is inventoried completely.

The VT families are dynamic, which means that new VTs of the chosen VT families are added and used automatically.

Host Discovery

This scan configuration is used to detect target systems. No vulnerabilities are being detected.

The used port scanner is Ping Host which detects whether a host is alive.

The VT families are static, which means that new VTs of the chosen VT families are not added and used automatically.

System Discovery

This scan configuration is used to detect target systems including installed operating systems and used hardware. No vulnerabilities are being detected.

The used port scanner is Ping Host which detects whether a host is alive.

The VT families are static, which means that new VTs of the chosen VT families are not added and used automatically.

Full and fast

For many environments this is the best option to start with.

This scan configuration is based on the information gathered in the previous port scan and uses almost all VTs. Only VTs that will not damage the target system are used. VTs are optimized in the best possible way to keep the potential false negative rate especially low. The other “Full” configurations only provide more value in rare cases but with much higher effort.

The VT families are dynamic, which means that new VTs of the chosen VT families are added and used automatically.

Full and fast ultimate

This scan configuration expands the scan configuration Full and fast with VTs that could disrupt services or systems or even cause shutdowns.

The VT families are dynamic, which means that new VTs of the chosen VT families are added and used automatically.

This scan configuration may not always be absolutely reliable depending on environmental conditions, which may be reflected in an increased false-positive rate. Narrowing down the suspected false-positive edge cases may require manual analysis and setting overrides (see Chapter 11.8).

Full and very deep

This scan configuration is based on the scan configuration Full and fast but the results of the port scan or the application/service detection do not have an impact on the selection of the VTs. Therefore, VTs that wait for a timeout or test for vulnerabilities of an application/service which were not detected previously are used. A scan with this scan configuration is very slow.

The VT families are dynamic, which means that new VTs of the chosen VT families are added and used automatically.

Full and very deep ultimate

This scan configuration expands the scan configuration Full and very deep with dangerous VTs that could cause possible service or system disruptions. A scan with this scan configuration is very slow.

The VT families are dynamic, which means that new VTs of the chosen VT families are added and used automatically.

This scan configuration may not always be absolutely reliable depending on environmental conditions, which may be reflected in an increased false-positive rate. Narrowing down the suspected false-positive edge cases may require manual analysis and setting overrides (see Chapter 11.8).

10.9.2 Creating a Scan Configuration

Note

Any custom scan configuration with the scanner preference safe_checks set to no (see Chapter 10.9.4.1) may not always be absolutely reliable depending on environmental conditions, which may be reflected in an increased false-positive rate. Narrowing down the suspected false-positive edge cases may require manual analysis and setting overrides (see Chapter 11.8).

A new scan configuration can be created as follows:

1. Select Configuration > Scan Configs in the menu bar.

2. Create a new scan configuration by clicking .

   Note

   Alternatively, a scan configuration can be imported (see Chapter 10.9.3).

3. Enter the name of the scan configuration in the input box Name (see Fig. 10.29).

4. Select the radio button of the base that should be used.

   It can be chosen between Base with a minimum set of NVTs, Empty, static and fast, Full and fast and a previously created scan configuration.

   

   Fig. 10.29 Creating a new scan configuration

5. Click Save.

   → The scan configuration is created and displayed on the page Scan Configs.

6. In the row of the scan configuration, click .

7. In the section Edit Network Vulnerability Test Families select the radio button if newly introduced VT families should be included and activated automatically (see Fig. 10.30).

   

   Fig. 10.30 Editing the new scan configuration

8. In the section Edit Network Vulnerability Test Families activate the checkboxes in the column Select all NVTs if all VTs of a family should be activated.

9. Click for a VT family to edit it (see Fig. 10.31).

   Note

   The following VT families cannot be edited:

   • AIX Local Security Checks

   • AlmaLinux Local Security Checks

   • Amazon Linux Local Security Checks

   • CentOS Local Security Checks

   • Debian Local Security Checks

   • Fedora Local Security Checks

   • FreeBSD Local Security Checks

   • Gentoo Local Security Checks

   • HP-UX Local Security Checks

   • Huawei EulerOS Local Security Checks

   • Mageia Linux Local Security Checks

   • Mandrake Local Security Checks

   • Oracle Linux Local Security Checks

   • Red Hat Local Security Checks

   • Rocky Linux Local Security Checks

   • Slackware Local Security Checks

   • Solaris Local Security Checks

   • SuSE Local Security Checks

   • Ubuntu Local Security Checks

   For more information see Chapter 6.5.1.

   

   Fig. 10.31 Editing a family of VTs

10. In the column Selected activate the checkboxes of the VTs that should be activated.

    Note

    For the Notus Scanner (see Chapter 6.5.1) to work, the VT Determine OS and list of installed packages via SSH login (OID: 1.3.6.1.4.1.25623.1.0.50282) must be activated.

11. Click for a VT to edit it (see Fig. 10.32).

    Note

    If editing the VT includes uploading a text file, the file should use UTF-8 text encoding.

    

    Fig. 10.32 Editing a VT

12. Click Save to save the VT.

13. Click Save to save the family of VTs.

14. Optional: edit scanner preferences (see Chapter 10.9.4).

15. Optional: edit VT preferences (see Chapter 10.9.5).

16. Click Save to save the scan configuration.

10.9.3 Importing a Scan Configuration

Note

Only scan configurations created with the currently used GOS version should be imported. Importing scan configurations from other GOS versions may cause an error message or unexpected behavior.

Any custom scan configuration with the scanner preference safe_checks set to no (see Chapter 10.9.4.1) may not always be absolutely reliable depending on environmental conditions, which may be reflected in an increased false-positive rate. Narrowing down the suspected false-positive edge cases may require manual analysis and setting overrides (see Chapter 11.8).

A scan configuration can be imported as follows:

1. Select Configuration > Scan Configs in the menu bar.

2. Click .

3. Click Browse… and select the XML file of the scan configuration.

4. Click Import.

   Note

   If the name of the imported scan configuration already exists, a numeric suffix is added to the name.

   → The imported scan configuration is displayed on the page Scan Configs.

5. Execute steps 6 to 16 of Chapter 10.9.2 to edit the scan configuration.

10.9.4 Editing the Scanner Preferences

Scanner preferences can be edited as follows:

1. Select Configuration > Scan Configs in the menu bar.

2. In the row of the scan configuration, click .

3. In the section Edit Scanner Preferences click to edit the scanner preferences (see Fig. 10.33).

   

   Fig. 10.33 Editing the scanner preferences

4. After editing the scanner preferences click Save to save the scan configuration.

10.9.4.1 Description of Scanner Preferences

Note

Documenting all scanner preferences is out of scope of this document. Only the most important preferences of the scanner are covered.

Undocumented preferences may also be deprecated despite still being visible. These preferences will be ignored by the scanner and should not be considered.

• alive_test_ports: TCP ports used by the Boreas alive scanner for the alive test. This setting only affects the alive test methods TCP-ACK Service Ping and TCP-SYN Service Ping. Only valid ports (port range 0–65535) may be configured. If an invalid value is configured, the Boreas alive scanner uses the default ports.

• auto_enable_dependencies: this defines whether VTs that are required by other VTs are activated automatically.

• cgi_path: path used by the VTs to access CGI scripts.

• checks_read_timeout: timeout for the network sockets during a scan.

• test_alive_wait_timeout: timeout for the Boreas alive scanner to wait for replies after the last packet was sent. Values between 1 and 20 are allowed.

• test_empty_vhost: the scanner also scans the target by using empty vhost values in addition to the target’s associated vhost values.

• max_sysload: maximum load on the appliance. Once this load is reached, no further VTs are started until the load drops below this value again.

• min_free_mem: minimum available memory (in MB) which should be kept free on the appliance. Once this limit is reached, no further VTs are started until sufficient memory is available again.

• non_simult_ports: these ports are not being tested simultaneously by VTs.

• optimize_test: VTs will only be started if specific prerequisites are met (for example open ports or detected application).

• plugins_timeout: maximum run time of a VT.

• safe_checks: some VTs can cause damage on the host system. This setting disables those respective VTs.

• scanner_plugins_timeout: maximum run time (in seconds) for all VTs of the VT family Port scanners. If a VT runs longer, it is terminated.

• expand_vhosts: the target’s host list of vhosts is expanded with values gathered from sources such as reverse lookup queries and VT checks for SSL/TLS certificates.

• time_between_request: wait time (in milliseconds) between two actions such as opening a TCP socket, sending a request through the open TCP socket and closing the TCP socket.

• timeout_retry: number of retries if a socket connection attempt times out.

• unscanned_closed: this defines whether TCP ports that were not scanned should be treated like closed ports.

• unscanned_closed_udp: this defines whether UDP ports that were not scanned should be treated as closed ports.

10.9.5 Editing the VT Preferences

1. Select Configuration > Scan Configs in the menu bar.

2. In the row of the scan configuration, click .

3. In the section Network Vulnerability Test Preferences click to edit the VT preferences.

4. In the row of the VT preference, click .

5. Edit the VT preference.

6. Click Save to save the VT preference.

7. Click Save to save the scan configuration.

10.9.5.1 Description of VT Preferences

Note

Documenting all VT preferences is out of scope of this document. Only the VT preferences of the Nmap and Ping Host port scanners are covered for now.

10.9.5.1.1 Preferences of the VT Ping Host

Note

Most of the Ping Host parameters are no longer supported in GOS 22.04, because they are incompatible with the new Boreas alive scanner. Parameters that are not documented here are not supported and may not be functional.

The VT Ping Host in the VT family Port scanners contains the following configuration parameter:

• Report about reachable Hosts: this defines whether a host discovered by this VT should be listed.

10.9.5.1.2 Preferences of the VT Nmap (NASL wrapper)

The following options of the VT Nmap (NASL wrapper) in the VT family Port scanners will be directly translated into options for the execution of the Nmap command. Additional information can be found in the documentation for Nmap.

• Do not randomize the order in which ports are scanned: Nmap will scan the ports in ascending order.

• Do not scan targets not in the file: see File containing grepable results.

• Fragment IP packets: Nmap fragments the packets for the attack. This allows bypassing simple packet filters.

• Identify the remote OS: Nmap tries to identify the operating system.

• RPC port scan: Nmap tests the system for Sun RPC ports.

• Run dangerous ports even if safe checks are set: UDP and RPC scans can cause problems and usually are disabled with the setting safe_checks. With this setting, they can be enabled anyway.

• Service scan: Nmap tries to identify services.

• Use hidden option to identify the remote OS: Nmap tries to identify more aggressively.

• Data length: Nmap adds random data of specified length to the packet.

• Host Timeout: host timeout.

• Initial RTT timeout: initial round trip timeout. Nmap can adjust this timeout dependent on the results.

• Max RTT timeout: maximum RTT.

• Min RTT timeout: minimum RTT.

• Max Retries: maximum number of retries.

• Maximum wait between probes: this regulates the speed of the scan.

• Minimum wait between probes: this regulates the speed of the scan.

• Ports scanned in parallel (max): this defines how many ports should at most be scanned simultaneously.

• Ports scanned in parallel (min): this defines how many ports should at least be scanned simultaneously.

• Source port: source port. This is of interest when scanning through a firewall if connections are in general allowed from a specific port.

• File containing grepable results: allows for the specification of a file containing line entries in the form of Host: IP address. If the option Do not scan targets not in the file is set at the same time only systems contained in the file will be scanned.

• TCP scanning technique: actual scan technique.

• Timing policy: instead of changing the timing values individually the timing policy can be modified.

The timing policy uses the following values:

	Paranoid	Sneaky	Polite	Normal	Aggressive	Insane
initial_rtt_timeout	5 min	15 s	1 s	1 s	500 ms	250 ms
min_rtt_timeout	100 ms	100 ms	100 ms	100 ms	100 ms	50 ms
max_rtt_timeout	10 s	10 s	10 s	10 s	1250 ms	300 ms
max_parallelism	serial	serial	serial	parallel	parallel	parallel
scan_delay	5 min	15 s	400 ms	0 s	0 s	0 s
max_scan_delay	1 s	1 s	1 s	1 s	10 ms	5 ms

10.9.6 Managing Scan Configurations

List Page

All existing scan configurations can be displayed by selecting Configuration > Scan Configs in the menu bar (see Fig. 10.34).

For all scan configurations the following information is displayed:

Name

Name of the scan configuration.

Type

Type of the scan configuration.

Family – Total

Number of activated VT families for the scan configuration.

Family – Trend

Trend of VT families

New VT families are included and activated automatically after a feed update. This ensures that new VTs are available immediately and without any interaction by the administrator.

New VT families are not included automatically after a feed update.

NVTs – Total

Number of activated VTs for the scan configuration.

NVTs – Trend

Trend of VTs.

New VTs of the activated VT families are included and activated automatically after a feed update. This ensures that new VTs are available immediately and without any interaction by the administrator.

New VTs are not included automatically after a feed update.

Note

Greenbone publishes new VTs regularly. New families of VTs can be introduced through the Greenbone Enterprise Feed as well.

Fig. 10.34 Page Scan Configs displaying all available scan configurations

For all scan configurations the following actions are available:

• Move the scan configuration to the trashcan. Only scan configurations which are currently not used can be moved to the trashcan. As long as the scan configuration is not deleted from the trashcan, it is not downloaded anew during the next feed update.

• Edit the scan configuration. Only self-created scan configurations which are currently not used can be edited.

• Clone the scan configuration.

• Export the scan configuration as an XML file.

Note

By clicking or below the list of scan configurations more than one scan configuration can be moved to the trashcan or exported at a time. The drop-down list is used to select which scan configurations are moved to the trashcan or exported.

Details Page

Click on the name of a scan configuration to display the details of the scan configuration. Click to open the details page of the scan configuration.

The following registers are available:

Scanner Preferences

All scanner preferences for the scan configuration with current and default values (see Chapter 10.9.4.1).

NVT Families

All VT families for the scan configuration with the number of activated VTs and the trend.

NVT Preferences

All VT preferences for the scan configuration (see Chapter 10.9.5.1).

User Tags

Assigned tags (see Chapter 8.4).

Permissions

Assigned permissions (see Chapter 9.4).

The following actions are available in the upper left corner:

• Open the corresponding chapter of the user manual.

• Show the list page of all scan configurations.

• Create a new scan configuration (see Chapter 10.9.2).

• Clone the scan configuration.

• Edit the scan configuration. Only self-created scan configurations which are currently not used can be edited.

• Move the scan configuration to the trashcan. Only scan configurations which are currently not used can be moved to the trashcan. As long as the scan configuration is not deleted from the trashcan, it is not downloaded anew during the next feed update.

• Export the scan configuration as an XML file.

• Import a scan configuration (see Chapter 10.9.3).

10.10 Performing a Scheduled Scan

For continuous vulnerability management the manual execution of task is tedious. The appliance supports the scheduling of tasks for their automation and refers to schedules as automatic scans at a specific time. They can be run once or repeatedly.

The appliance does not provide any schedules by default.

10.10.1 Creating a Schedule

A new schedule can be created as follows:

1. Select Configuration > Schedules in the menu bar.

2. Create a new schedule by clicking .

3. Define the schedule (see Fig. 10.35).

4. Click Save.

   → The schedule is created and can be selected when creating a new task (see Chapter 10.2.2).

   

   Fig. 10.35 Creating a new schedule

The following details of the schedule can be defined:

Name

Definition of the name. The name can be chosen freely.

Comment

An optional comment can contain additional information.

Timezone

Definition of the timezone the time refers to. UTC±00:00 is default.

Note

Since the appliance runs in the UTC±00:00 timezone internally, the chosen time zone is very important. For Eastern Standard Time (EST) America/New York has to be selected.

First Run

Definition of the date and time for the first scan to start.

By clicking the date can be chosen. By clicking Now the current date and time are set for the first run.

Run Until

Definition of the date and time for the first scan to end. Tasks with a specified end time cannot be started manually.

By clicking the date can be chosen. Activate the checkbox Open End to leave the end time open.

Duration

Definition of the maximum duration a task can take for its execution. The duration depends on the given start and end time. If an end time is defined and the assigned time is expired, the task is aborted and will be suspended until the next scheduled time slot becomes available. This way it can be ensured that the scan will always run with a specific (maintenance) time window.

Recurrence

Definition of the repetition rate of the task. It can be selected between Once, Hourly, Daily, Weekly, Monthly, Yearly, Workweeks (Monday till Friday) or Custom. If the option Custom is selected, the repetition rate and the days on which the task should be run can be chosen.

10.10.2 Managing Schedules

List Page

All existing schedules can be displayed by selecting Configuration > Schedules in the menu bar.

For all schedules the following information is displayed:

Name

Name of the schedule.

First Run

Start time of the first run of the task.

Next Run

Next run of the task according to the current date and time.

Recurrence

Repetition rate of the task.

Duration

Maximum duration a task can take for its execution. The duration depends on the given start and end time. If an end time is defined and the assigned time is expired, the task is aborted and will be suspended until the next scheduled time slot becomes available. This way it can be ensured that the scan will always run with a specific (maintenance) time window.

For all schedules the following actions are available:

• Move the schedule to the trashcan. Only schedules which are currently not used can be moved to the trashcan.

• Edit the schedule.

• Clone the schedule.

• Export the schedule as an XML file.

Note

By clicking or below the list of schedules more than one schedule can be moved to the trashcan or exported at a time. The drop-down list is used to select which schedules are moved to the trashcan or exported.

Details Page

Click on the name of a schedule to display the details of the schedule. Click to open the details page of the schedule.

The following registers are available:

Information

General information about the schedule.

User Tags

Assigned tags (see Chapter 8.4).

Permissions

Assigned permissions (see Chapter 9.4).

The following actions are available in the upper left corner:

• Open the corresponding chapter of the user manual.

• Show the list page of all schedules.

• Create a new schedule (see Chapter 10.10.1).

• Clone the schedule.

• Edit the schedule.

• Move the schedule to the trashcan. Only schedules which are currently not used can be moved to the trashcan.

• Export the schedule as an XML file.

10.11 Creating and Managing Scanners

The appliance comes with two predefined scanners. They can be managed and new scanners can be created.

The following scanners are already available:

• OpenVAS Default

• CVE: the CVE scanner allows forecasting possible security risks based on current information about known vulnerabilities from the SecInfo management (see Chapter 14) without the need of a new scan (see Chapter 10.4).

Note

The desired scanner for a task is selected when creating the task (see Chapter 10.2.2).

10.11.1 Creating a Scanner

Note

The creation of a new scanner is only used for creating a new remote scanner (see Chapter 16.4).

10.11.2 Managing Scanners

List Page

All existing scanners can be displayed by selecting Configuration > Scanners in the menu bar (see Fig. 10.36).

For all scanners the following actions are available:

• Move the scanner to the trashcan. Only self-created scanners can be moved to the trashcan.

• Edit the scanner. Only self-created scanners can be edited.

• Clone the scanner. Only self-created scanners can be cloned.

• Export the scanner as an XML file.

• Verify that the scanner is online and that the manager can connect to it using the provided certificates and credentials.

• Download the certificate or CA certificate. The certificate or CA certificate can only be downloaded for self-created scanners.

Note

By clicking or below the list of scanners more than one scanner can be moved to the trashcan or exported at a time. The drop-down list is used to select which scanners are moved to the trashcan or exported.

Fig. 10.36 Page Scanners displaying all existing scanners

Details Page

Click on the name of a scanner to display the details of the scanner. Click to open the details page of the scanner.

The following registers are available:

Information

General information about the scanner.

User Tags

Assigned tags (see Chapter 8.4).

Permissions

Assigned permissions (see Chapter 9.4).

The following actions are available in the upper left corner:

• Open the corresponding chapter of the user manual.

• Show the list page of all scanners.

• Create a new scanner (see Chapter 10.11.1).

• Clone the scanner. Only self-created scanners can be cloned.

• Edit the scanner. Only self-created scanners can be edited.

• Move the scanner to the trashcan. Only self-created scanners can be moved to the trashcan.

• Export the scanner as an XML file.

• Verify that the scanner is online and that the manager can connect to it using the provided certificates.

10.12 Using Alerts

Alerts are anchored within the system. If a configured event (for example a task is finished) happens, a specified condition is checked (for example vulnerability with a high severity category detected). If the conditions is met, an action is performed, for example an e-mail is sent to a defined address.

10.12.1 Creating an Alert

A new alert can be created as follows:

1. Select Configuration > Alerts.

2. Create a new alert by clicking .

3. Define the alert (see Fig. 10.37).

4. Click Save.

   

   Fig. 10.37 Creating a new alert

The following details of the alert can be defined:

Name

Definition of the name. The name can be chosen freely.

Comment

An optional comment can contain additional information.

Event

Definition of the event for which the alert message is sent. Alerts can be sent if the status of a task changes, if SecInfo (VTs, CVEs, CPEs, CERT-Bund Advisories, DFN-CERT Advisories) is added or updated or if a ticket is assigned or edited (see Chapter 11.6).

Condition

Definition of the additional conditions that have to be met.

Note

The options differ for task, for SecInfo and for ticket related alerts.

The alert message can occur:

• Always

• If a specific severity level is reached.

• If the severity level changes, increases or decreases.

• If a Powerfilter matches at least the specified number of results more than in the previous scan.

Report Content (only for task related alerts)

The report content can be limited with an additional filter. By clicking the scan report content composer is opened and a Powerfilter can be chosen (see Chapter 11.2.2). The filter must be created previously (see Chapter 8.3). For Include, activate the checkbox Notes to include attached notes, and the checkbox Overrides to label enabled overrides and include their text field content. For Pagination, activate the checkbox Ignore to have the filter settings for the results displayed per page on the web interface not apply to the results in the sent report.

Details URL (only for SecInfo related alerts)

Definition of the URL from which the SecInfo is obtained.

Delta Report (only for task related alerts)

Optionally, a delta report can be created, either in comparison to a previous report or to a report with a certain ID.

Method

Selection of the method for the alert. Only one method per alert can be chosen. If different alerts for the same event should be triggered, multiple alerts must be created and linked to the same event.

Note

Some methods cannot be used for SecInfo or ticket related alerts.

The following methods are possible:

Email

The report is sent to a given e-mail address.

To use this method the used mailhub must be configured using the GOS administration menu (see Chapter 7.2.11).

The settings To Address, From Address and Content have to be configured for the e-mail alert to work. The e-mail subject and encryption is optional.

• To Address

  E-mail address to which the e-mail is sent.

• From Address

  E-mail address that is stated as the e-mail’s sender.

• Subject

  For the subject the following placeholders can be used:

  • $d: the date of the last SecInfo check or blank for task/ticket alerts.

  • $e: the event description.

  • $n: the task name or blank for SecInfo/ticket alerts.

  • $N: the alert name.

  • $q: the type of SecInfo event (New, Updated) or blank for task/ticket alerts.

  • $s: the SecInfo type (for example NVT or CERT-Bund Advisory) or blank for task/ticket alerts.

  • $S: see $s, but pluralized (for example NVTs, CERT-Bund Advisories) or blank for task/ticket alerts.

  • $T: the total number of objects in the list for SecInfo alerts or 0 for task/ticket alerts.

  • $u: the owner of the alert or the name of the currently logged in user if the alert was triggered manually.

  • $U: the UUID of the alert.

  • $$: the dollar sign ($).

• Email Encryption

  The e-mail can be encrypted using a configurable S/MIME or PGP key. The key can be selected in the drop-down list Email Encryption or created by clicking . The certificate file must fulfill the following conditions:

  • PEM encoded (a binary DER file cannot be used)

  • Using the X.509 format

  • Issued for the recipient e-mail address (To Address) and valid (not expired)

  • If the certificate originally came in a bundled format that included the private key as well, only the unencrypted certificate must be uploaded.

  In case of S/MIME credentials, the certificate file additionally must fulfill the following condition:

  • Combines all certificates of the chain (root certificate and all intermediate certificates)

• Content

  The content of the e-mail can be a simple notice, an included or an attached report.

  • Include Report

    The report can be included directly in the e-mail. Any report format that uses a content type starting with text/ can be chosen because e-mails do not support binary content directly.

  • Attach Report

    The report can be attached to the e-mail. Any report format can be chosen. The report will be attached to the generated e-mail in its correct MIME type.

  The content of the e-mail message can be edited for both, the included and the attached report. For the message the following placeholders can be used:

  • $c: the condition description.

  • $d: the date of the last SecInfo check or blank for task/ticket alerts.

  • $e: the event description.

  • $F: the name of filter.

  • $f: the filter term.

  • $H: the host summary.

  • $i: the report text or list of SecInfo objects (only if including the report/list).

  • $n: the task name or blank for SecInfo/ticket alerts.

  • $N: the alert name.

  • $q: the type of SecInfo event (New, Updated) or blank for task/ticket alerts.

  • $r: the name of the report format.

  • $s: the SecInfo type (for example NVT or CERT-Bund Advisory) or blank for task/ticket alerts.

  • $S: see $s, but pluralized (for example NVTs, CERT-Bund Advisories) or blank for task/ticket alerts.

  • $t: the note if the report was truncated.

  • $T: the total number of objects in the list for SecInfo alerts or 0 for task/ticket alerts.

  • $u: the owner of the alert or the name of the currently logged in user if the alert was triggered manually.

  • $U: the UUID of the alert.

  • $z: the timezone.

  • $$: the dollar sign ($).

HTTP Get

The URL is issued as HTTP Get. Example: an SMS text message can be sent via HTTP Get gateway or a bug report can be created in an issue tracker. For the URL the following placeholders can be used:

• $n: the task name or blank for SecInfo/ticket alerts.

• $e: the event description.

• $c: the condition description.

• $$: the dollar sign ($).

Example: https://example.com/$n → https://example.com/Scan_task_1

SCP

The report is copied to the given destination via Secure Copy Protocol (SCP) using the given login credentials for authentication.

All settings (Credential, Host, Known Hosts, Path and Report) have to be configured for the SCP alert to work.

• Credential

  A user name and password or user name and SSH key credential that contains valid login information for the destination system.

• Host

  The host name or IP address of the destination system. Only one destination system per SCP alert is supported.

• Port

  The port used to connect to the destination system. By default, port 22 is used. Only values corresponding to the list of standardized ports (between 1 and 65535) are supported. If an unsupported value is saved, either the default value 22 is used instead, or the entered value is truncated, for example 70000 becomes 7000.

• Known Hosts

  The SSH public key of the destination system in the format “host protocol public_key”, for example localhost ssh-rsa AAAAB3NzaC1y...P3pCquVb. The “host” part must match the host name or IP address respectively.

• Path

  The full path of the destination directory and file, for example /home/user/Downloads/report.xml. Shortening the path, for example by using ~ is not supported. For the file name the following placeholders can be used:

  • $$: the dollar sign ($).

  • $n: the task name.

• Report

  Format of the copied report.

Send to host

The report is sent to an arbitrary host-port combination via TCP. The IP address or the host name is allowed.

The format of the report can be chosen from the installed report formats.

SMB

The report is copied to the given destination via Server Message Block (SMB) protocol using the given login credentials for authentication.

The settings Credential, Share path and File path have to be configured for the SMB alert to work. The selection of a report format is optional.

• Credential

  A user name and password credential that contains valid login information for the destination system.

• Share path

  The share path contains the part of the UNC path containing the host and the share name, for example \\host\share. The share path has to be created on the destination system before the alert can be used.

• File path

  Location of the report in the share folder that is defined by the share path.

  Note

  If the file path contains subdirectories which do not exist, the necessary subdirectories are created.

  The file extension is appended corresponding to the format selected in the drop-down list Report Format.

  The default report export file name (see Chapter 8.7) is appended to the file path if the file path ends with \.

  Note

  If a task uses the tag smb-alert:file_path with a value, then the value is used as the file path instead of the one that has been configured with the alert (see Chapter 8.4). Example: smb-alert:file_path=alert_1 assigns the file path alert_1.

  For the file path the following placeholders can be used:

  • %C: the creation date in the format YYYYMMDD. Changed to the current date if a creation date is not available.

  • %c: the creation time in the format HHMMSS. Changed to the current time if a creation time is not available.

  • %D: the current date in the format YYYYMMDD.

  • %F: the name of the used report format (XML for lists and types other than reports).

  • %M: the modification date in the format YYYYMMDD. Changed to the creation date or to the current date if a modification date is not available.

  • %m: the modification time in the format HHMMSS. Changed to the creation time or to the current time if a modification time is not available.

  • %N: the name for the object or the associated task for reports. Lists and types without a name will use the type (see %T).

  • %T: the object type, for example “task”, “port_list”. Pluralized for list pages.

  • %t: the current time in the format HHMMSS.

  • %U: the unique ID of the object or “list” for lists of multiple objects.

  • %u: the name of the currently logged in user.

  • %%: the percent sign (%).

• Report Format

  Format of the copied report. If no report format is defined, XML is used by default.

• Max Protocol

  SMB version in case the SMB server only supports a specific version. The following options can be selected:

  • Default

  • SMB3

  • SMB2

  • NT1 (for SMBv1)

  If no SMB version or Default is selected, the latest supported version is used.

SNMP

An SNMP trap is sent to the given agent. The provided community string is used to authenticate the SNMP trap. The agent is the targeted SNMP trap receiver. For the message the following placeholders can be used:

• $$: the dollar sign ($).

• $d: the date of the last SecInfo check or blank for task/ticket alerts.

• $e: the event description.

• $n: the task name or blank for SecInfo/ticket alerts.

• $q: the type of SecInfo event (New, Updated) or blank for task/ticket alerts.

• $s: the SecInfo type (for example NVT or CERT-Bund Advisory) or blank for task/ticket alerts.

• $S: see $s, but pluralized (for example NVTs, CERT-Bund Advisories) or blank for task/ticket alerts.

• $T: the total number of objects in the list for SecInfo alerts or 0 for task/ticket alerts.

Sourcefire Connector

The data can be sent to a Cisco Firepower Management Center (formerly known as Sourcefire Defense Center) automatically. For more information see Chapter 18.3.

Start Task

The alert can start an additional task. The task is selected in the drop-down list.

System Logger

The alert is sent to a Syslog daemon. The Syslog server is defined using the GOS administration menu (see Chapter 7.2.12).

Note

The time zone of the appliance (UTC±00:00) is used for the time stamps of the logs unless adjusted on the syslog server.

verinice.PRO Connector

The data can be sent to a verinice.PRO installation automatically. For more information see Chapter 18.1.

TippingPoint SMS

An HTTPS API is used to upload a report in CSV format to the TippingPoint Security Management System (SMS).

• Hostname / IP

  Host name or IP address of the TippingPoint SMS. The CSV report is then sent to https://<address>/vulnscanner/import where <address> is the entered host name/IP address.

• Credentials

  A user name and password credential that contains valid login information for the TippingPoint SMS.

• SSL / TLS Certificate

  A CA certificate used to verify that the host the alert connects to is the TippingPoint SMS. The certificate file must fulfill the following conditions:

  • PEM encoded (a binary DER file cannot be used)

  • Using the X.509 format

• Use workaround for default certificate

  By default, the certificate uses Tippingpoint as the common name (CN) which does not match the host name/IP address of the TippingPoint SMS in most cases. If enabled, the workaround temporarily changes the CN and resolves it to the actual host name/IP address within the internal connector script.

Alemba vFire

A new ticket in the service management application vFire is created. The report can be attached in one or more formats. For more information see Chapter 18.4.

10.12.2 Assigning an Existing Alert to a Task

If an alert should be used afterwards, the alert has to be defined for a specific task as follows:

Note

Already defined and used tasks can be edited as well as it does not have any effect on already created reports.

1. Select Scans > Tasks in the menu bar.

2. In the row of the task, click .

3. Select the alert in the drop-down list Alerts (see Fig. 10.38).

   Note

   A new alert can be created by clicking .

   

   Fig. 10.38 Configuring a task with an alert

4. Click Save.

   → Afterwards the task using the alert appears on the details page of the alert (see Fig. 10.39).

   

   Fig. 10.39 Task using a specific alert

10.12.3 Managing Alerts

List Page

All existing alerts can be displayed by selecting Configuration > Alerts in the menu bar.

For all alerts the following information is displayed:

Name

Name of the alert.

Event

Event for that the alert is triggered.

Condition

Condition that has to be fulfilled to trigger the alert.

Method

Chosen alert method with additional information, for example to which IP address or e-mail address the alert message is sent.

Filter (only for task related alerts)

Filter that is applied to the report content.

Active

Indication whether the alert is enabled or disabled.

For all alerts the following actions are available:

• Move the alert to the trashcan. Only alerts which are currently not used can be moved to the trashcan.

• Edit the alert.

• Clone the alert.

• Export the alert as an XML file.

• Test the alert.

Note

By clicking or below the list of alerts more than one alert can be moved to the trashcan or exported at a time. The drop-down list is used to select which alerts are moved to the trashcan or exported.

Details Page

Click on the name of an alert to display the details of the alert. Click to open the details page of the alert.

The following registers are available:

Information

General information about the alert.

User Tags

Assigned tags (see Chapter 8.4).

Permissions

Assigned permissions (see Chapter 9.4).

The following actions are available in the upper left corner:

• Open the corresponding chapter of the user manual.

• Show the list page of all alerts.

• Create a new alert (see Chapter 10.12.1).

• Clone the alert.

• Edit the alert.

• Move the alert to the trashcan. Only alerts which are currently not used can be moved to the trashcan.

• Export the alert as an XML file.

10.13 Obstacles While Scanning

There are several typical problems which might occur during a scan using the default values of the appliance. While the default values of the appliance are valid for most environments and customers, depending on the actual environment and the configuration of the scanned hosts they might require some tweaking.

10.13.1 Hosts not Found

During a typical scan (either Discovery or Full and fast), the appliance will by default first use the ping command to check the availability of the configured targets. If the target does not reply to the ping request it is presumed to be dead and will not be scanned by the port scanner or any VT.

In most LAN environments this does not pose any problems because all devices will respond to a ping request. But sometimes (local) firewalls or other configuration might suppress the ping response. If this happens the target will not be scanned and will not be included in the results and the scan report.

To remediate this problem, both the target configuration and the scan configuration support the setting of the alive test (see Alive Test).

If the target does not respond to a ping request, a TCP ping may be tested. If the target is located within the same broadcast domain, an ARP ping may be tried as well.

10.13.2 Long Scan Periods

Once the target is discovered to be alive using the ping command, the appliance uses a port scanner to scan the target. By default, a TCP port list containing around 5000 ports is used. If the target is protected by a (local) firewall dropping most of these packets the port scan will need to wait for the timeout of each individual port. If the hosts are protected by (local) firewalls the port lists or the firewalls may be tuned. If the firewall does not drop the request but rejects the request the port scanner does not have to wait for the timeout. This is especially true if UDP ports are included in the scan.

10.13.3 VT not Used

This happens especially very often if UDP based VTs like VTs using the SNMP protocol are used. If the default configuration Full and fast is used, the SNMP VTs are included. But if the target is configured using the default port list, the VTs are not executed. This happens because the default port list does not include any UDP ports. Therefore, the port 161/UDP (SNMP) is not discovered and excluded from further scans. Both the discovery scans and the recommended scan configuration Full and fast optimize the scan based on the discovered services. If the UDP port is not discovered, no SNMP VTs are executed.

Do not enable all ports per default in the port lists. This will prolong the scans considerably. Best practice is the tuning of the port lists to the ports which are used in the environment and are supported by the firewalls.

10.13.4 Scanning vhosts

The scanner is able to find all relationships of host names and IP addresses without needing additional user input.

In environments with virtual hosts (vhosts), the scan reports will have less results because duplicates are avoided.

Two scanner preferences handle vhost scanning (see Chapter 10.9.4):

test_empty_vhost

If this preference is enabled, the scanner also tests the target by using empty vhost values in addition to the target’s associated vhost values.

expand_vhosts

If this preference is enabled, the target’s host list of vhosts is expanded with values gathered from sources such as reverse lookup queries and VT checks for SSL/TLS certificates.