Skip to main content
A scan module describes a type of source—Windows, Active Directory or VMware, for example. A job is the named, concrete configuration of a scan module that the Docusnap Enterprise Gateway in your network executes.

​
The Four Components

Gateway

The Windows service in your network that executes a job.

Scan Module

The type of source—Windows, Active Directory or VMware, for example.

Job

The named configuration of a scan module: gateway, targets, credentials and schedule.

Credentials

The access data the job uses to sign in to the source.
A job stays in place as a configuration; each execution is a single run on schedule. Docusnap365 uses both terms itself, for example Next Execution and Execution History.

​
Where the Results Come From

Whatever a job finds enters the inventory. If a find can be matched to a type, it becomes an asset—the Captured Assets metric counts it. If it cannot be matched to a type, it appears under Unknown Systems until it is typed. The data refresh transfers the results of scheduled jobs from the gateway to Docusnap365 at fixed intervals: every 24 hours in Pro, every 12 in Business, every 6 in Enterprise (see Editions). A job started with Run Now transfers its result immediately. The result of a completed scheduled job appears in the inventory only with the next data refresh. This applies to all scan modules, including Microsoft 365 and Microsoft Intune.

​
Basis for Other Modules

The captured assets form the inventory that ITAM manages for lifecycle, warranty and cost, that ISMS assesses for risk, and that CVE analysis checks for known vulnerabilities.

​
Limits

Docusnap365 only captures automatically what a scan module exists for. The module catalog shows which sources those are. The path from the first gateway to the first scan is in Scanning Your Network and in the tutorial The First Scan. Individually: Installing and Registering the Gateway and Creating a Scan Job. How credentials and transmission are protected is in Security.