Deployment Scenarios

The following scenarios are the most common Scan Engine deployments. These do not represent every deployment scenario possible. These are meant as a guide to give you a good idea of how a deployment works. You will work with our support team to decide what type of deployment is best for your company.
The reader may note a similarity of this document with the User Guide use-case scenarios. The purpose of the deployment document is to identify the possible installation locations of the Scan Engine components. The purpose of the user guide use-cases is to identify the possible roles and responsibilities within a deployment model.
In all of the typical deployment scenarios, the following product components are typically deployed:

Product

Description

Scan Engine

Consists of three major components:
Scanning Service: Discovers devices through methods laid out in the Discovery Strategies section in this document.
Scan Database: This is a joint database that contains:
(1) User Interface (UI) database. It receives user information from the UI and shares it with the Scan Database in encrypted form (e.g. credential passwords)
(2) Scan data. It stores the raw data from the scan data retrieval operations.
UI: This is web-based User Interface (UI) that is used to control and configure the scan operations.
Rest API: Provides a programmatic access to the Scan Engine scan data. Allows for integration with customer in-house used tools.

The Scan Engine is typically deployed on a single machine instance (virtual or physical) within a customer data center.