DocumentaciónHelp

Scan and schedule scans

Run a scope whenever you need it or leave it scheduled with a calendar and a time window, and review what it found on each asset.

On this page

A scope can be run on demand or left scheduled. The time window ensures the scan doesn't run during office hours.

Before you start

  • Operate permission on Vulnerabilities to scan; Administer to create scopes and accept authorizations.

  • A scope with its authorization Accepted. See Create a scope.

Scan now

  1. Go to Security (SIEM) → Vulnerabilities → Scopes.

  2. On the scope's row, click Scan now.

  3. The Last run column changes to Queued and then to Scanning.

  4. If you need to cut it short, click Stop.

When it finishes, the status shows Done (or Partial, Stopped or Failed, with the reason), with how many hosts, services and findings it found.

Schedule a scan

The schedule is defined when you create the scope, in the Schedule section. The screen doesn't let you edit a scope that has already been created: to change its schedule, create a new one and delete the old one.

  • Cron schedule (optional): when it runs. For example 0 3 * * * is every day at 03:00. Empty means it only runs when you request it.

  • Time zone: America/Santiago by default.

  • Window from and Window to (HH:MM): the hours during which the probe may scan, for example from 22:00 to 06:00.

Schedule example

When it runs

0 3 * * *

Every day at 03:00

0 2 * * 6

Saturdays at 02:00

0 1 1 * *

The first day of each month at 01:00

With Private connection, the window is mandatory (from and to): the tunnel is only used within it.

See what it found

  1. Click Results on the scope's row.

  2. The table shows each asset with its Address, Name, Operating system, the Services with an open port (port, protocol, product and version) and when it was seen.

  3. Click View findings to go to the vulnerabilities.

What happens next

Each completed scan updates the findings: new ones appear as Open, those no longer seen change to Resolved and those seen again are reopened. If something is serious, ARGUNIS notifies you:

What was found

Without the SIEM

With the SIEM enabled

A KEV (actively exploited) vulnerability seen from the internet

Critical incident

Critical detection and automatic case

A confirmed critical vulnerability

Warning incident

High detection to review

A new service exposed on the perimeter

Warning incident

Medium detection

No longer seen in a completed scan

The incident is closed

The detection is closed

Notifications are grouped by asset: ten new critical vulnerabilities on the same server in one scan are a single notification. Active exceptions don't notify.

Related

Search Argunis Monitoring

Type at least 2 characters to search Argunis Monitoring.

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