Scan configurations

A scan configuration is a reusable template that describes what to scan and how. You create it once and run it whenever you need a fresh scan of the same range. Creating a configuration does not start a scan — you run it when you’re ready.

Creating a configuration

Give the configuration a clear name, then set:

• Targets — the CIDR ranges or hostnames to scan. This defines the scope of what the agent will examine.
• Ports — which ports to check on each target.
• Intensity — how thorough and aggressive the scan is. Higher intensity finds more but takes longer and puts more load on the targets.
• Agent location — which deployed agent runs this configuration. Choose the agent that sits where it can reach these targets.

Tip

Name configurations by what they cover — for example by environment or subnet — so the list stays readable as it grows and you can tell at a glance which scan does what.

Editing a configuration

Update a configuration any time as your network or priorities change. Because the configuration is separate from any single run, editing it changes what the next run does without touching past results.

Running a scan from a configuration

Start a scan by selecting a configuration and launching it. While it runs you can watch live progress, and you can cancel a scan in flight or retry one that didn’t complete.

Tips for large networks

• Reachability first — make sure the configuration’s targets are reachable from the chosen agent. Firewalls between the agent and the range will silently shrink your results.
• Mind the intensity — very large ranges scanned at high intensity take much longer. Raise intensity when you need depth, not by default.
• Chunk it — for very large networks, split the range across several smaller configurations rather than scanning everything in one pass. Smaller scans finish sooner and are easier to monitor and retry.

Where to go next

• Reading network scan results — explore findings once a scan completes.