You can use this dialog to configure scan destinations. Even complex paths and URLs can be put together with just a few clicks.
All available scan targets are listed on the left-hand side of the dialog. To the right, the directory to be scanned in the currently selected scan target can be specified and, in the case of cloud/remote targets, the access data for the connection can also be entered there. The currently selected path is displayed in the input field at the bottom of the dialog. Paths (or URLs) can also be entered in this field to select the path to be analyzed as quickly as possible. Click on the button next to it to start the scan.
Available scan targets
You can select one of the supported scan types on the left-hand side of the dialog to start configuring a more complex scan target:
Drives |
Scan of a local drive or a network drive. |
Directory |
Scan of a specific directory. |
Outlook |
Scan one or more Outlook mailboxes. |
SharePoint |
Scan of SharePoint sites. |
Amazon S3 |
Scan of an Amazon S3 bucket. |
Azure Blob Storage |
Scan of an Azure Blob Storage container. |
SSH |
Scan of a Linux or Unix file system using SSH.. |
WebDav |
Scan a target via the WebDav protocol. |
Specifying the path to be scanned
The content displayed next to the scan targets results from the selected scan type and allows you to specify a specific path and, if necessary, authentication data.
Drives & Directory |
For these two scan targets, the corresponding drive or directory can be selected in the list or in the directory tree. Double-click on a drive or folder to start the scan immediately. |
Outlook: Mailbox |
Here you can select the mailbox to be analyzed. |
Outlook: Subpath (optional) |
A path or folder within the mailbox can be selected for the scan here. This means that the entire mailbox is not scanned, but only the corresponding subpath. |
SharePoint: Server name |
The URL of the corresponding server to be scanned (e.g. for SharePoint: "https://testserver.sharepoint.com") is entered in this field. |
SharePoint: Path (optional) |
The subpath on the specified server (e.g. "sites/general" for SharePoint) can be entered in the path field in order to analyze only this path and other sub-paths of it. |
SharePoint: Authentication type and fields dependent on this |
Here you can specify how the connection to the SharePoint is to be established. You can choose between "User name", "Certificate" and "Windows account". User name: Authentication via user name and password. Certificate: Authentication via a saved certificate and a password. Windows account: Authentication via the Windows account currently in use (only possible with Azure Active Directory set up as described here). |
Amazon S3: Bucket name |
The name of the Amazon S3 bucket you want to scan. |
Amazon S3: Prefix (optional) |
The prefix on the respective bucket that is to be analyzed. For example, if there is a folder called "folder" and another folder called "subfolder" exists in this folder and the latter is to be analyzed, you would use the prefix "folder/subfolder". |
Amazon S3: Access key |
The access-token of the user to perform the scan as. |
Amazon S3: Secret access key |
The secret access-token that fits to the used access key. |
Azure Blob Storage: Container name |
The name of the container to be analyzed. |
Azure Blob Storage: Virtual directory prefix (optional) |
Analogous to the prefix for Amazon S3. |
Azure Blob Storage: Storage account name |
A type of user name that is used to connect to the selected container. |
Azure Blob Storage: Access key |
A kind of password for the connection to the selected container. |
SSH: Server name |
Analogous to the server name for SharePoint. |
SSH: Path (optional) |
Analogous to the path for SharePoint. |
SSH: User name |
User name for authentication on the selected server. |
SSH: Password |
Password for authentication on the selected server. |
WebDav: Server name |
Analogous to the server name for SharePoint. |
WebDav Path (optional) |
Analogous to the path for SharePoint. |