Zscaler Import Substitution for an International Logistics Company

1. The project was divided into stages.

   1. Study of the current infrastructure and comparative analysis of available solutions

   At this stage, several fundamentally different, proven solutions were proposed, but only those that met the client's actual needs were retained.

   2. Development of an architectural solution and a detailed migration plan

   Before launching into production, the client wanted to see how the solution worked in a "production" infrastructure, rather than in an isolated example. This approach required in-depth consideration of the integration component even during the pilot phase.

   3. Piloting

   Here, a pilot of the selected solution was conducted on the infrastructure and user workstations, taking into account the specifics of the company's business processes. During the test implementation, the advantages of the ICL Services solution were demonstrated.

   Some of the requirements were adjusted by the client after familiarizing themselves with the solution. The pilot implementation was essentially a "productive" implementation, as it required real integration with corporate services.

   4. Developing and testing automation scripts for user migration

   Migrating end users to the new solution was a separate and complex task. It was necessary to develop scripts to automate the removal of the old solution and the configuration of the new one. Instructions for users and support lines were prepared.

   5. Integration with Active Directory

   Full integration with the company's "global" domain became possible only after the project had completed the pilot phase and the first users had arrived.

   6. Infrastructure Scaling

   The solution is similar to Zscaler and allows for horizontal and vertical scaling. During this phase, the necessary failover tests and cluster switchover automation were conducted. The customer was satisfied with the solution, and during implementation, the scale of work was more than tripled (from 1,000 to 2,500 users).

   7. Mass User Migration

   As the migration progressed, a stack of tasks and configurations unique to each user emerged. Additional resources were allocated to ensure users did not experience delays in response due to increased support load.

   
   

   The project also included integrating the customer's infrastructure with the following services:

   — a failover remote access gateway for 1,500 remote users. Multifactor authentication was implemented to enhance security;

   — a web traffic security system for 2,500 hosts in a failover and scalable cluster. Transparent authentication based on Active Directory Kerberos was implemented for security.

Products and technologies

• Kaspersky SD-WAN, Kaspersky Web Traffic Security
• Cloud (Virtualization/Compute/Networking)
• Microsoft Always On VPN
• Zscaler