Forcepoint Data Loss Prevention is used for endpoint email security and data loss prevention for web.
The deployment is straightforward once you understand the solution's architecture. A proper understanding of the different components of Forcepoint DLP is essential, as deploying an enterprise-level DLP could be confusing because the policy server is separate from the main engine sitting on the Triton server. Understanding the components of the enterprise DLP suite is the most critical element for a successful deployment. Still, I rate the solution seven out of ten in terms of ease of setup. The scale of the particular DLP deployment is also a factor; we had cases where the customer only required endpoint or network DLP, a relatively quick job that two staff can complete. A complete DLP suite, including email, web, and network DLP, plus data classification and labelling, would require four associates. Our most recent deployment was a complete enterprise DLP, which required four staff. The entire deployment took almost three months, including a one-month planning phase. During the planning phase, we prepared the documentation, designed the HLDs and LLDs, and high and low-level diagrams. Following acceptance from the customer, we started the implementation, which took roughly 50 to 60 days. The level of maintenance required depends on how many events per hour a particular tool is putting out. If a customer wants to check analytics or identify an email or data leak, that situation doesn't require much policy fine-tuning, and a single staff member could deal with it. The customer can also decide what coverage they want, which may be 24/7, an admin to monitor events only, or Monday-to-Friday support. The coverage determines how many engineers will be required. Another factor in maintenance requirements is the volume of events, as an extensive client could have more than 10,000 servers with many sensitive data in motion. The customer had 24,000 users for our last deployment, and there wasn't a dedicated team for the DLP. The engineering team took care of the network, endpoint, and data security together. There were ten of us on the team, with two engineers per shift for 24/7 coverage.
