What the installation needs, and what it runs

An appliance on your hardware, read-only collection from your management network, and upgrades you trigger.

Request access Security and architecture

What to plan for

One machinePhysical or virtual: 4 vCPUs, 13 GB of memory and 50 GB of disk at least.
A collection accountRead access on the devices, from the management network.
One HTTPS path outTo our service, for the licence and the catalogues.

Two ways to install

The NacTrack ISO: AlmaLinux 9, SELinux enforcing and hardening applied at install, or Debian. On a physical or virtual machine. Disk encrypted with LUKS2, unlocked by the TPM 2.0 when there is one. Minimum: 4 vCPUs, 13 GB of memory, 50 GB of disk.
An Ubuntu virtual machine: Installation onto an existing Ubuntu machine, x86_64 or arm64. Disk encryption is then your hypervisor's.
What runs: Six containers: the application, nginx, MySQL, Elasticsearch, Redis, and Certbot for the certificate. One machine, with no high availability.
Network flows: To your devices: SSH on port 22, Telnet 23 only for a device where you enable it. Outbound: HTTPS 443 to our service and to the image registry, UDP 51820 if you turn the support tunnel on.

How collection behaves

The collection account

A read account. On Cisco, when the prompt is not privileged and an enable password is supplied, collection enters enable mode; without one it carries on, and a refused configuration is flagged as such.

Parallelism

Eight devices at a time by default, up to sixty four, set per schedule. Taken down to one on sensitive equipment.

Timeouts

Each command has its own timeout, from one minute to thirty depending on the expected volume. A command the device refuses is recorded, not repeated.

Named failures

Password refused, enable refused, host unreachable, connection refused, timed out, SSH algorithm mismatch: every failure carries its reason.

Scheduling

Scheduled collections, or started by hand. On loaded equipment, they are scheduled outside the hours that matter.

The commands

The exact list, platform by platform, is published on the vendors page, session setup included.

Upgrades, backups and support

Two channels: A stable channel and one that runs ahead. You choose yours, and an upgrade only starts from your side. The releases on record are in the release history.
How it runs: Image download, container restart, database migration. The interface pauses for the restart.
Rollback: The previous version redeploys with one command; database migrations are not reverted.
Without internet: No tooled offline upgrade yet: the image downloads from the registry.
Backup: Every night, a password-encrypted backup of the database and configuration, kept seven days on the appliance, and a daily snapshot of the indices. Copying them off the machine is for you to organise.
Support: By ticket, opened from the installation, Monday to Friday, 9:00 to 18:00 Morocco time, in French and English.

A specific installation constraint?

Tell us your environment, and the answer comes from the people who install the product.