Deployment schemas of Kaspersky Security Integration with Autotask

This section describes the deployment schemas of Kaspersky Security Integration with Autotask. The schemas include the two components of Kaspersky Security Integration with Autotask:

• Kaspersky Security Integration Tool for MSP—Used to configure connection between the Kaspersky Lab solution you use and Autotask, and to configure mapping between the Kaspersky Lab solution entities and Autotask entities.
• Kaspersky Security Integration Service for MSP—Synchronizes data in Kaspersky Security Center and Autotask. It is a service application only, with no user interface.

The deployment schema that suits your integration depends on the Kaspersky Lab solution you use and on your integration model. There are three deployment schemas:

• For an on-premises version of a Kaspersky Lab solution—Kaspersky Security Center.
• For an on-premises version of a Kaspersky Lab solution—Kaspersky Security Center with slave Administration Servers.
• For a cloud-based version of a Kaspersky Lab solution—Kaspersky Business Hub.

This section describes the deployment schemas in detail.

Deployment schema for on-premises solution

Deploy Kaspersky Security Integration with Autotask based on this schema if you use an on-premises version of a Kaspersky Lab solution—Kaspersky Security Center—and if you do not have slave Administration Servers in your managed company infrastructure.

The components of Kaspersky Security Integration with Autotask are shown as orange rectangles in the following figure.

Deployment schema for on-premises solution

The following list describes deployment prerequisites and data flow:

• Kaspersky Security Integration Service for MSP must be installed on the computer on which Kaspersky Security Center Administration Server is installed.
• Kaspersky Security Integration Tool for MSP must be installed on the computer on which either Administration Console or Administration Server is installed and deployed.
• In Kaspersky Security Center, virtual servers must be created for each of the managed Autotask accounts. These virtual servers are than mapped to Autotask accounts, allowing you to integrate Kaspersky Security Center and Autotask.
• In your managed environment, you may have many different Kaspersky Lab programs installed. Data on the number of programs is used by Kaspersky Security Integration with Autotask for automatic billing. Events and computer status changes sent from Kaspersky Lab programs to Kaspersky Security Center are received by Kaspersky Security Integration Service for MSP and tickets are created based on them.

Page top

Deployment schema for on-premises solution and slave servers

Deploy Kaspersky Security Integration with Autotask based on this schema if you use an on-premises version of a Kaspersky Lab solution—Kaspersky Security Center—and if you use slave Administration Servers in your managed company infrastructure.

The components of Kaspersky Security Integration with Autotask are shown as orange rectangles in the following figure.

Deployment schema for on-premises solution and slave servers

The following list describes deployment prerequisites and data flow:

• One or more Administration Servers are used in the client's infrastructure. These Administration Servers are slave Administration Servers relative to the Administration Server that is installed in the MSP infrastructure. The Administration Server installed in the MSP infrastructure is the master Administration Server. You can use this type of deployment to decrease load on your master Administration Server.
• Kaspersky Security Integration Service for MSP must be installed on the computer on which the slave Administration Server is installed in the client's infrastructure.
• Kaspersky Security Integration Tool for MSP must be installed on the computer on which either Administration Console or the master Administration Server is installed and deployed.
• On your slave Administration Server, virtual servers must be created for each of the managed accounts. These virtual servers are then mapped to Autotask accounts, allowing you to integrate Kaspersky Security Center and Autotask.
• In your managed environment, you may have many different Kaspersky Lab programs installed. Data on the number of programs is used by Kaspersky Security Integration with Autotask for automatic billing. Events and computer status changes sent from Kaspersky Lab programs to Kaspersky Security Center are received by Kaspersky Security Integration Service for MSP and tickets are created based on them.

Page top

Deployment schema for cloud-based solution

Deploy Kaspersky Security Integration with Autotask based on this schema if you use the cloud-based version of a Kaspersky Lab solution—Kaspersky Business Hub.

The components of Kaspersky Security Integration with Autotask are shown as orange rectangles in the following figure.

Deployment schema for cloud-based solution

The following list describes deployment prerequisites and data flow:

• In this deployment schema, only Kaspersky Security Integration Tool for MSP is used. Kaspersky Security Integration Service for MSP is not used.
• Kaspersky Security Integration Tool for MSP must be installed in your infrastructure, and not in the client infrastructure.
• In your Kaspersky Business Hub solution, companies must be created for each of the managed Autotask accounts. These companies are then mapped to Autotask accounts, allowing you to integrate Kaspersky Business Hub and Autotask.
• In your managed environment, you may have many different Kaspersky Lab programs installed. Data on the number of programs is used by Kaspersky Security Integration with Autotask for automatic billing. Events and computer status changes sent from Kaspersky Lab programs to Kaspersky Business Hub are received and tickets are created based on them.

Page top