DocumentaciónHelp

Vulnerability probes

Register and install the probes that scan for vulnerabilities, review each one's detail page, and choose how they're updated.

On this page

Vulnerability probes scan your hosts for vulnerabilities. This page shows how to install a probe and the list of your probes; each probe has its own detail page.

Before you start

  • The Settings → Vulnerabilities → Vulnerability probes menu appears if your plan includes Vulnerabilities and you're a company administrator.

  • The probe runs in Docker on a VPS or a virtual machine with Ubuntu 22.04/24.04 or Debian 12, with at least 2 vCPU, 4 GB of RAM and 20 GB free.

Register and install a probe

  1. Go to Settings → Vulnerabilities → Vulnerability probes.

  2. Click Register probe and copy the token the platform gives you (it expires in 24 hours).

  3. In Install a probe, click Copy command.

  4. Log in to the server over SSH and paste the command (it's a single one).

  5. When prompted, paste the token and press Enter. Nothing shows when you paste it: that's normal.

  6. When it finishes, the probe appears Online in the Probes list.

A probe's detail page

Click a probe's name to open its detail page. There you see:

  • Status: connection, last heartbeat, version and when it was registered.

  • Host: server name, system and architecture.

  • Probe update: how it's updated and whether it's up to date.

  • Scopes: the scopes that probe scans, with the link to their jobs.

At the top are the Update probe, Re-enroll, Revoke and Delete buttons (the same icons are in the list).

Update a probe

The probe has two parts:

  • The probe version (its program) updates automatically from ARGUNIS if the policy is Automatic. With Notify only, ARGUNIS notifies the administrators and you click Update now.

  • The image (OpenVAS, nmap and the system) only changes by running the command with --actualizar on the probe's server. When needed, the detail page shows the command with the Copy command button.

Reinstall, revoke and delete

  • Re-enroll gives you a new token. If the probe was installed, its connection is cut: run the command shown on screen on its server (it ends with --reenrolar) and paste the new token.

  • Revoke disconnects the probe and erases its identity; it stops scanning. To use it again, register another one.

  • Delete removes it from the list (only if revoked or never installed). If any scope uses it, assign another probe first. Then uninstall it from the server with the same command and --desinstalar.

Argunis probes

If Argunis enabled its perimeter probe for your company, it appears under Argunis probes with its source IP. Choose it when creating a "Perimeter (external)" scope and, if you filter inbound traffic, allow that IP in your firewall. You don't have to install anything.

Credentials and external targets

They have their own page in Security (SIEM) → Vulnerabilities (administrators only):

  • Credentials: click New credential to give read-only access to the hosts during the scan (SSH, Windows/WinRM, SNMPv3 or HTTP basic). Credentials live in the company vault.

  • Target ownership: before scanning public IPs or domains, click Register target, publish the TXT record the screen shows you, and verify. Without this, the external scan is blocked.

Related

Search Argunis Monitoring

Type at least 2 characters to search Argunis Monitoring.

↑↓ to navigate · Enter to open · Esc to close