Glossary
Terms that have a specific meaning in NODE64.
Agent The program on your system. Collects data, judges nothing, runs nothing.
Anchor A measurement node operated by NODE64 itself. It is always available – which makes "from outside" measurements work even when few customers are taking part.
Baseline The state of a monitored file that counts as "this is how it should be". Deviations produce an integrity finding.
CVE A publicly documented vulnerability with a unique identifier.
Device key The permanent secret a device identifies itself with. Lives locally in /var/lib/node64/state.json and can be revoked in the dashboard.
Drift Changes to the system between two runs: new packages, new ports, new accounts.
Enrollment Connecting a device to your account.
File integrity monitoring (FIM) Watching important files by checksum.
Finding A concrete observation on a concrete device, with rating, rationale and a way to fix it.
One-time token The code a device uses to connect once. After that the agent uses its own device key.
Catalog The collection of checks. Hardening (what makes you attackable) and recommendations (what could be better), per system and role.
Probe A device that takes part in the measurement network and runs measurements for others.
Role What kind of system this is: server, endpoint, router, firewall. Determines which checks apply at all.
Probe (also: measurement node) A device that takes part in the measurement network and runs measurements for others. Since mid-2026 that is a device of its own with its own agent – no longer a switch on a security device.
Master node A measurement node that serves as a reference point: everyone else measures against it, and its values are the yardstick. It used to be called an anchor. The operator appoints it, with a reason and on the record – you cannot apply.
Sonar The measurement network. Answers questions that cannot be answered from the inside.
Upload A package of collected data from the agent to the server. Contains no verdict, only measurements.