Skip to main content
Docusnap365 captures your IT landscape automatically through scan modules—one for each kind of source, such as Active Directory, Windows or VMware. For this you create a scan job: the named configuration of gateway, targets, credentials and schedule. A single pass of a job is called an execution.

​
Requirement: a gateway

A job always runs through a Docusnap Enterprise Gateway—the Windows service in your network that connects it to Docusnap365. Without a connected gateway, no job can start.
You do not have to set up the gateway in advance. Starting a new scan job walks you through the setup first if none is connected yet, then continues to the module selection.
One gateway is enough for one network; for separate sites or networks, set up one more each. Installation details are in Installing and Registering the Gateway.

​
Choosing a scan module

Scan › Scan Modules shows the catalog of all modules, grouped into Favorites, Active Modules and categories such as System, Cloud or Virtualization.
For a new subscription with no existing jobs, Docusnap365 suggests Active Directory, Windows (AD) and SNMP v1 and v2 as a starting point.

​
Targets, credentials and schedule

The wizard asks for the targets—depending on the module, IP addresses, ranges, host names or a domain—and credentials for access. You create credentials as Reusable, so they remain available in the vault for further jobs, or as One-Time, for this one job only. Write permission in the Scan area is enough for credentials and scan jobs; the Administrator role is not required. Roles and module access are covered under Users and Roles.
One-time credentials are not saved. A job with one-time credentials therefore cannot be run again without entering the credentials once more.
In the last step you decide whether the job runs immediately or on a schedule. The closing button reads Run Now or Schedule Job accordingly.

​
Following the first scan

Scan › Dashboard shows how many assets are captured, when the last scan ran, how many gateways are connected and how many systems are still unknown. The Action Required section flags Failed Scans, credentials that have expired or are expiring, and Unused Scan Modules.
A captured system without a recognized type appears under Unknown Systems with the line Typing pending. It can be assigned a type afterwards.

​
Results of the first scan

Once the first scan is through, several areas fill in automatically: the inventory in the Inventory area, the software found along with its vulnerabilities under Analysis, and—if NTFS was captured—the permission structure there as well. The commercial data—responsibility, costs, warranties—does not come from the scan. It comes from ITAM and is entered there. Storing Credentials Locally and Running Your First Scan walks through the gateway, credentials and the first Active Directory and Windows scan step by step. An overview of all modules is in Scan Modules; what scanning means in general is in Scanning Fundamentals. Once the assets are there, add their ITAM data and back your NIS-2 requirements with captured systems instead of manual entries—see Assessing NIS-2.