Install Access Analyzer
The installer is a single Linux binary, dspm-installer. Run it as root on the server, and it checks the hardware, asks for anything you haven't supplied, sets up every service, and prints the address and credentials for the first sign-in.
Before you start, work through Requirements. You need the license key, the server's fully qualified hostname, the TLS certificate and private key files, and the email address & name of the first administrator at hand.
Download the Installer
-
Download the Access Analyzer installer for your server's architecture from the download link Netwrix supplied with your license:
dspm-installer-linux-amd64for 64-bit x86 ordspm-installer-linux-arm64for Arm. -
Copy the file to the server, for example with
scp. -
Rename it.
mv dspm-installer-linux-amd64 dspm-installer -
Make it executable.
chmod +x dspm-installer -
Confirm it runs.
./dspm-installer --version
Copy the TLS Certificate to the Server
The installer expects the certificate at /etc/dspm/tls.crt and the private key at /etc/dspm/tls.key. If you keep them somewhere else, enter the paths when the installer prompts for them, or pass them with --tls-cert and --tls-key.
-
Create the directory.
sudo mkdir -p /etc/dspm -
Move the certificate and key into place.
sudo mv /path/to/your.crt /etc/dspm/tls.crtsudo mv /path/to/your.key /etc/dspm/tls.key -
Restrict the key to root.
sudo chmod 600 /etc/dspm/tls.key
If a private certificate authority (CA) issued the certificate, copy its CA bundle too. /etc/dspm/ca-bundle.pem is a convenient place; the installer asks for the path.
Run the Installer
Run the installer with sudo. The -E flag carries your environment through to root, which matters if you export the license key as LICENSE_KEY instead of typing it.
sudo -E ./dspm-installer
If your sudo policy doesn't allow -E, pass the variable inline instead: sudo LICENSE_KEY="$LICENSE_KEY" ./dspm-installer.
The installer runs its preflight checks first, then collects any value it doesn't have yet. You can let it ask, or supply everything up front.
- Answer the prompts
- Pass flags
When you run the installer with no flags in a terminal, it asks for each value it needs, one screen at a time. It asks only for values it doesn't already have, so a re-run skips what you answered before.
- License Key - paste your Netwrix license key in the form
XXXX-XXXX-XXXX-XXXX-XXXX-V3. The installer validates it online before moving on. - Hostname - enter the fully qualified domain name users open in their browsers, for example
dspm.corp.example.com. If the server's own name is a valid choice, the installer offers it as a suggestion. - First Admin Email and First Admin Name - enter the email address of the first administrator, and optionally their full name. The address becomes their username.
- TLS Certificate File, TLS Private Key File, and CA Bundle File (optional) - press Enter to accept
/etc/dspm/tls.crtand/etc/dspm/tls.key, or enter other paths. Fill in the CA bundle only if a private certificate authority issued the certificate. The installer checks that the certificate and key match, that the certificate hasn't expired, and that it covers the hostname you entered. - Show advanced settings? - select No.
- Check the review screen. It lists the hostname, the certificate path (and the CA bundle path if you gave one), the first administrator, and a masked license key.
- Answer Yes to Everything look good?
The installer saves each answer to /etc/dspm/installer.yaml as soon as you confirm it. On the first save it prints Progress saved to /etc/dspm/installer.yaml — future runs will pre-fill these values. If you cancel with Esc or Ctrl-C, the installer exits with installation cancelled, and your answers stay in that file for the next run.
Pass every value as a flag and the installer asks nothing. Use this form in scripts or over a connection without a terminal, where the installer can't prompt and exits with an error for any missing value.
sudo ./dspm-installer \
--license-key "<license-key>" \
--hostname dspm.corp.example.com \
--tls-cert /etc/dspm/tls.crt \
--tls-key /etc/dspm/tls.key \
--size medium \
--first-admin-email admin@corp.example.com \
--first-admin-name "Alice Smith" \
--accept-warnings
--accept-warnings lets the install continue past preflight warnings. Without a terminal the installer can't ask you, so it stops on warnings unless you pass this flag. Leave it out the first time if you'd rather see the warnings and decide.
--size defaults to medium when you omit it. Pass --tls-cert and --tls-key together; if you omit both, the installer uses /etc/dspm/tls.crt and /etc/dspm/tls.key. Add --ca-bundle <path> for a certificate from a private certificate authority.
If /etc/dspm/installer.yaml exists from an earlier run and you're in a terminal, the installer still asks Show advanced settings? and shows the review screen before it starts. Add --assume-yes to skip both.
Every flag also has an environment variable, listed in the Installer reference.
Preflight Checks
The installer checks the server first, under the heading Running preflight checks.... Checks that pass are silent. Each failure or warning gets its own line, tagged [FAIL] or [WARN], for example:
[FAIL] 48.0 GB RAM; the medium size requires 64 GB
[WARN] clock-sync no clock sync daemon detected
A [FAIL] stops the install. There's no way to override it: fix the server or choose a smaller size, then run the installer again. Failures cover CPU cores, RAM, the 40 GB disk floor, DNS resolution of the hosts the installer downloads from, and the availability of cgroups, a kernel feature the platform depends on.
A [WARN] is a condition the install can continue past, such as less disk than the size recommends, no time-sync service, or antivirus software that may need exclusions. In a terminal the installer asks Continue despite these warnings?; answer Yes to go on. Without a terminal, warnings stop the install unless you pass --accept-warnings.
The full list of checks, thresholds, and messages is in the Installer reference. The installer also writes the complete result of each run to /var/log/dspm-preflight.json (a --dry-run doesn't write it).
Install Phases
After the checks and prompts, the installer validates the certificate and hostname, confirms the license key online, and saves your answers. Then it works through these phases, printing a progress line for each:
- Sets up the platform Access Analyzer runs on. The installer waits up to 5 minutes for it to become ready.
- Downloads and starts the Access Analyzer services. A live line reads
Starting Access Analyzer (<n> of <total> services running)and counts up. The installer waits up to 30 minutes for every service to become healthy. - Creates the first administrator account, under
Provisioning first admin user....
If the platform or the services don't become ready inside those limits, the installer stops with a non-zero exit code; the Installer reference lists the codes. If creating the first administrator fails, the installer prints a warning and still finishes. The installer logs everything it does to /var/log/dspm-installer.log.
Install Summary
The installer prints a summary. It contains:
- The web application URL,
https://<hostname>. - First Admin Credentials: the Username, which is the email address you gave, and a one-time Password.
- A reminder to allow inbound port 443 through the firewall.
- The installation log path,
/var/log/dspm-installer.log.
Copy the password somewhere safe. It works once, and Access Analyzer asks you to replace it when you first sign in. Then open the URL in a browser and continue with Sign in for the first time, which also explains how to read the password back from the server if you lose it.