Install

Before continuing, make sure you have these items:

Considerations

Read through these sections before you start the installation process.

Default account creation

In the course of your installation, you’ll create a default account with Global Administrator privileges. When you configure these credentials, take care to store them in a safe place.

IMPORTANT - Avoid conflicts with other authentication source accounts

As a general guideline, the username for your default account should be totally unique from any other account name that you may have already configured in other external authentication sources.

The Security Console requires that all user accounts have unique usernames. If you intend to configure an external authentication source for console access (such as Active Directory or SAML), do not use one of your external authentication accounts as the default account username.

Installation options

There are two installation options:

  • Security Console with a local Scan Engine
  • Scan Engine only

If you’re following the basic deployment plan, you’ll install a Security Console with a local Scan Engine.

Only installing a Scan Engine?

While this will generally be unnecessary for trial deployments, keep in mind that production deployments make extensive use of dedicated Scan Engines.

Scan Engines are controlled by the Security Console and cannot operate without being paired with one. Scan Engine-only installations assume that you have a Security Console installed elsewhere in your network.

See the Distributed Scan Engines page for instructions on how to pair and configure a dedicated Scan Engine.

Enable/disable initialization

Enabled by default, this option will initialize the Security Console after it’s been installed. Initialization configures the application for use and updates the vulnerability database. If you enable initialization, your installation time will increase respective to that process. Initialization time ranges from 10 to 30 minutes.

IMPORTANT - FIPS Mode requirements

While most organizations do not require this configuration, ensure that you DO NOT initialize the console during your installation if you intend to use FIPS mode.

FIPS mode must be configured before the Security Console is started for the first time. See Enabling FIPS mode for instructions.

Install

Now that you’ve considered your options, follow one of the procedures below according to your OS:

Linux

REQUIRED

You must have root-level access.

For Ubuntu and Red Hat installations, you must also have the screen package installed. Use APT or YUM, respectively, to install the screen package.

  1. Make sure your installer and checksum file are in the same directory.
  2. Open a terminal and browse to the directory where your installer and checksum file are located.
  3. Run the following command, substituting <installer_file_name> with the appropriate value:
md5sum -c <installer_file_name>.md5sum
  1. If this command returns an OK message, the file is valid.
    • If the check fails, download the installer again and retry.
  2. Modify the permissions of the installer to make it executable:
chmod +x <installer_file_name>
  1. Run the installer:
./<installer_file_name> -c

Using a GUI?

If you are using a Graphical User Interface, omit the -c switch at the end of the installer run command. You’ll use a wizard similar to the Windows version instead.

  1. Follow the instructions prompted by the installer. You’ll decide on the considerations mentioned previously throughout the process.

Windows

REQUIRED

You must have Administrator privileges.

  1. Make sure your installer and checksum file are in the same directory.
  2. Open a command prompt and browse to the directory where your installer and checksum are located.
  3. Run the following command, substituting <installer_file_name> with the appropriate value:
certutil -hashfile <installer_file_name> md5
  1. Run the installer.

IMPORTANT

A command line window will appear during the installation, but you will not need to interact with it. DO NOT close this window.

  1. An installation wizard will guide you through the steps. You’ll decide on the considerations mentioned previously throughout the process.

Installation complete!

You should now have the Security Console with a local Scan Engine installed. It’s time to log in and complete your activation.

Updated 4 months ago


Install


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.