ENGINSIGHT
WebsiteLoginKostenloser Testzugang
English
English
  • Overview
  • Features
  • Operation
    • Platform overview
    • Start Guide
    • Platform
      • Dashboard
        • Vulnerability Management
        • Operation Centers
        • My Dashboards
        • Configurations
      • Issues
      • Hosts (Pulsar Agent)
        • Pulsar Agent
        • Host details
        • Policy Manager
        • Software Inventory
        • Intrusion Detection System
        • File Integrity Monitoring
        • System events
        • Update Manager
        • Plugins
        • Machine Learning
      • Host (Pulsar-Agent) BETA
        • Pulsar Agent
        • Hostdetails
        • Softwareinventar
        • Plugins
        • Policies
        • Globale Tags
        • Tag Manager
        • System Events
        • Vulnerability Manager
        • Compliance
        • Intrusion Detection System
        • File Integrity Monitoring
        • Advanced Persistent Threats
      • Endpoints (Observer)
        • Endpoint details
        • Domains
        • Certificate Manager
        • Observer
      • Observations
      • Shield
      • Penetration Testing (Hacktor)
        • Run pentest
        • Audits
        • Audit Definitions
        • Target Groups
        • Auth-Providers
        • Hacktor
        • Custom Scripts
      • Discoveries
      • SIEM
        • Data Lake
        • Cockpits
        • Obfuscators
        • Workflows
        • Incidents
        • Extractors
        • Collectors
        • Loggernaut
        • Advanced Settings
        • Models
      • Alerts
      • Settings
      • Organisations
      • Tags
      • Searchbar
  • On-Premises
    • Requirements
    • Installation
      • Automatic Installation
      • Manual Installation
      • Load Balancing
      • SIEM
      • Deinstallation
    • Update
    • Configuration
      • HTTPS and Certificates
      • Licences and Organisations
      • Mail Server
      • 2-Factor Authentication
      • SSO via Office 365
      • Storage Times
      • White Label
      • NGINX Extractor
      • Field Level Encryption
      • Loggernaut-Configurations
  • Technical Details
    • System Requirements
      • Pulsar: Operating Systems
    • Current version numbers
    • Pentest Vectors
    • API
  • Partner section
    • Licenses and organizations
Powered by GitBook
On this page
  • Preparations
  • First Steps
  • DB Server
  • App Server
  • Component-Server
  • Buy and import license file

Was this helpful?

  1. On-Premises
  2. Installation

Automatic Installation

PreviousInstallationNextManual Installation

Last updated 2 months ago

Was this helpful?

The easiest way to successfully install your own Enginsight on-premises instance is to use the Debian image we have prepared. During the installation process, important configurations are already performed automatically or asked interactively.

Preparations

1. Download the .

If your browser displays a security warning, you can ignore it. For example, in Chrome, click "Keep" to execute the download.

2. Create three virtual machines with the CPU, RAM, and mass storage values defined in the .

For a smooth automatic installation, it is crucial that the database (DB) is installed first! You can already start the app server to obtain its IP address, but you should only continue to run the script after the DB installation has been completed.

First Steps

The following steps are the same for the installation of the database and the app server. Carry these out and then continue with the appropriate instructions.

  1. Boot the database server with the Enginsight Debian image and select the corresponding server on the start page.

After you have selected the DB server, a blue screen appears for a few moments. This is correct behavior, just wait.

  1. Select the desired language, your location and the layout of your keyboard.

The setup now starts to automatically retrieve information about the network. This may take a short time, wait until everything has loaded.

  1. Assign a computer name, we recommend “ngs-db” for the database server and “ngs-app” for the app server.

  1. Then set up your network. To do this, enter your full domain name, e.g. company.com.

  1. If you are using an HTTP proxy, configure the proxy data in the standard format. If you do not need a proxy to access the Internet, you can leave the entry blank.

For example:

  • http://1.2.3.4/

  • no user / password, no port

  • http://user:secret@1.2.3.4/

  • user / password, no port

  • http://user:secret@1.2.3.4:8080/

  • User / password and port

  • The last slash “/” must be set.

  1. Now set up your new user.

  1. Enter the name of your account.

Save your entries in a password manager.

  1. Then assign a password for the newly created user.

  1. Confirm your previously selected password by entering it again.

  1. Select the hard disk to be partitioned.

The base system and other components are being installed, please be patient for a moment.

  1. You will receive this information after completing the installation and configuration. Then restart your system.

Make sure that the installation image is not loaded again, but Debian.

From this point of the installation, you can optionally continue the installation via SSH.

DB Server

  1. Then log in to your VM again. Use the previously assigned computer name and the defined password. As the script requires root rights, you will need to enter your password twice.

  1. Now specify whether you want to activate TLS and role-based access controls. We strongly recommend this.

  1. You will now be asked to enter the IP address of your app server. Now start the setup of your app server at the same time to query its IP address.

  1. Then check whether the correct IP address of the database server that can be reached by the app server has been recognized. Accept the IP address or enter the corresponding IP address if there is a discrepancy.

  1. Your TLS certificates are then issued, TLS is activated, MongoDB is initialized, a new user is created and your database access is secured.

    Certificates are now copied to the app server. To do this, enter the user name of your app server and confirm the connection to the host. You will then be asked to enter the app server password several times.

This completes the installation and configuration of your database server.

We recommend that you change the authentication procedure for SSH access as soon as you start using Enginsight productively. Use public key authentication instead of logging in with a user name and password.

App Server

  1. Then log in to your VM again. Use the previously assigned computer name and the defined password. As the script requires root rights, you will need to enter your password twice.

  1. Log in to the Docker Registry with your access data.

You will receive the access data for the Docker Registry from us.

  1. After you have logged in to the Docker Registry, please be patient while the Enginsight images are being downloaded.

  1. Read the end user license agreement and then confirm your agreement with a “y”.

  1. In the following steps you will be asked to enter the MongoDB URI, Redis URI, App URL and the API URL. You will already find an entry here, check it and confirm it for each query.

  1. Once all entries have been entered correctly, initialization starts.

    Please note that this may take some time.

  1. Finally, follow our recommendation and adjust the configuration as indicated to enable access via HTTPS.

  1. Once the installation is complete, you can log in using the temporary login credentials. You can obtain them as follows:

    sudo docker ps

    Copy the ID of the server-m2 module.

    sudo docker logs <insert ID>

    The credentials for the initial login will now be issued to you. Please save the initial login data.

Change the initial login data immediately after you have logged in for the first time.

To do this, go to Settings → User account. Adjust your e-mail address in the personal details and assign a new password under Password.

ATTENTION!

Without a changed and saved password or saved intial password you will lose access to the Enginsight platform. Use a password manager!

This completes the installation and configuration of your app server.

Component-Server

Install the Observer, Watchdog and Hacktor software components. You do not need to do anything other than run the corresponding installation scripts that you can find in the Enginsight platform.

You get detailed instructions here:

We recommend changing the authentication procedure for SSH access as soon as you start using Enginsight productively. Use public key authentication instead of logging in via username and password.

Buy and import license file

You can import the license file under Settings → License.

Make sure once again that the hard disk you have selected is large enough to meet your .

To use Enginsight OnPremises, you need a license file. Contact us to purchase a license package:

Do you want to manage multiple organisations with Enginsight and use the multitenancy? what you have to consider regarding the license.

requirements
hello@enginsight.com
Here you can find out,
Enginsight Debian image
requirements
Install Watchdog
Install Observer
Install Hacktor