The Check Point Solution for DLP

Check Point solves the complexity of Data Loss Prevention with unique features.

• UserCheck™ - Provides rapid response for incident handling with automated user notification and the unique Ask User mode. Each person in your organization learns best practices as needed, preventing future unintentional leaks - the vast majority of DLP incidents - and quickly handling immediate incidents. The user handles these incidents either through the DLP Self Incident Handling Portal , or through the UserCheck client.

  Without UserCheck, a security administrator, or even a security team, would have to check every email and data transfer in real time and approve or reject each. For this reason, other products offer only detection of suspicious incidents. With UserCheck, the decision-making is distributed to the users. They are presented with the reason for the data capture and must provide a reason for letting it pass (if the notification did not change their minds about sending it on). User decisions (send or discard) and reasons for sending are logged. With the original message and user decisions and reasons, you can develop an effective prevention policy based on actual use.

• MultiSpect™ - Provides unmatched accuracy in identifying and preventing incidents through multi-parameter correlation with Compound Data Types and customizable Data Types with CPcode.

• Out of the Box Security - A rich set of pre-defined Data Types recognizes sensitive forms, templates, and data to be protected. The Data Types are enforced in an effective out-of-the-box policy.

• Data Owner Auditing - The Data Owner is the person responsible for controlling the information and files of his or her own area in the corporation. Data Owners get timely and relevant information through automated notifications and reports that show exactly how their data is being moved. Check Point DLP gives Data Owners the information they need to handle usage issues directly related to their areas of responsibility. Without Data Owner control, the security administrator would often be placed in an awkward position between managers and employees.

• CPcode - DLP supports fully customized data identification through the use of CPcode. You define how data is to be matched by DLP, with the greatest flexibility possible. See the R77 versions CPcode DLP Reference Guide. .

Check Point DLP saves time and significantly improves ROI. Its innovative technologies provide automation that negates the need for long and costly analysis and a team for incident handling. You can now move from a detection-only policy to an accurate and effective prevention policy without bringing in outside consultants or hiring a security team.

All of this functionality is easy to manage through the SmartConsole Check Point GUI application used to manage a Check Point environment - configure Security Policies, configure devices, monitor products and events, install updates, and so on., in an interface similar to other Software Blades. You are not expected to be a DLP expert from the day of deployment. Check Point Data Loss Prevention guides you on how to customize and improve your DLP policy - with the Improve Accuracy flag, for example. The DLP Software Blade comes with a large number of built-in Data Types that can be quickly applied as a default policy. You can fine-tune the out-of-the-box policy to easily convert the confidentiality and integrity guidelines of your organization into automated rules. And later, you can create your own Data Types. This cycle of updating the policy, moving from a detection policy to a preventative policy, is close with the Check Point Logs & Monitor tool.

DLP Workflow:

1. The Data Loss Prevention Software Blade is enabled on a Security Gateway (2) (or ClusterXL Security Cluster Two or more Security Gateways that work together in a redundant configuration - High Availability, or Load Sharing.). This makes it a DLP Gateway (or a DLP security cluster). Alternatively, a dedicated DLP Gateway can be installed behind a protecting Security Gateway.

2. You use the SmartConsole and the Security Management Server Check Point Single-Domain Security Management Server or a Multi-Domain Security Management Server. to install the DLP Policy on the DLP Gateway.

3. The DLP Gateway (2) uses the built-in Data Types and rules to provide out-of-the-box Data Loss Prevention. It may use the Active Directory or LDAP server (6) to identify the internal organization.

   It catches all traffic containing data and being sent through supported protocols. Thus, when users send data that goes to an HTTP proxy (4) or a mail server (5), for example, the DLP Gateway catches the data before it leaves the organization.

   It scans the traffic, including email attachments, for data that should be protected from being sent outside the organization. This data is recognized by protocol, source, destination, and complex Data Type representations.

   It can also scan internal traffic between Microsoft Exchange clients within the organization. This requires installation of the Exchange Security Agent on the Microsoft Exchange server. The agent forwards internal emails to the DLP Gateway which then scans them. If the organization only uses Exchange servers for managing emails (internal and external), you can use this setup to also scan emails that are sent outside of the organization.

   If the data does not match any of the rules of the DLP policy, the traffic is allowed to pass.

4. The Logs & Monitor view (7) provides effective logging, tracking, event analysis, and reporting of incidents captured by the DLP Gateway.

In a Dedicated DLP Gateway deployment, a separate gateway (2) (or cluster) is installed in addition to the protecting gateway (3) (or cluster). The Data Loss Prevention Software Blade is enabled on that separate gateway.

Install the dedicated DLP Gateway behind the protecting Security Gateway to ensure its protection. We recommend that you enable only the Data Loss Prevention Software Blade to maximize the use of available hardware resources.

As an alternative to putting the DLP Gateway on the network perimeter, you can put the DLP Gateway between the user networks and the servers, to allow DLP to inspect traffic before it goes to the servers. This deployment is the necessary configuration if you want to use a DLP rule Set of traffic parameters and other conditions in a Rule Base (Security Policy) that cause specified actions to be taken for a communication session. that inspects data transmissions between departments.

For example, you can create a DLP rule that checks emails between internal groups: Source is a specific network, Destination is Outside Source (anything outside of this Source). Such a rule would be applied only if this deployment was used.

You can put the DLP Gateway between the users and the switch, to directly protect a subnet.

1. Incident is logged.

   • The data is stored in a safe repository on a log server or Security Management Server that stores DLP logs.

   • The DLP Gateway logs an incident with the Logs & Monitor view.

2. Action of rule is performed.

   • If the matched rule is set to Detect, the user gets no notification. A DLP log incident is created, and the actual data is stored.

     Action of rule is performed.

     • If the matched rule is set to Detect, the user gets no notification. A DLP log incident is created, and the actual data is stored.

     • If the matched rule is set to Inform User, DLP notifies the user that the captured traffic violates DLP rules. The traffic is passed.

     • If the matched rule is set to Ask User, DLP notifies the user that the message is being held and contains a link to the DLP Portal, where the user decides whether the transmission should go through or be dropped. User decisions, and reasons for sending, are logged for your analysis.

     • If the matched rule is set to Prevent, the traffic is blocked. The user and the Data Owner may be notified.

   • If the matched rule is set to Inform User, DLP notifies the user that the captured traffic violates DLP rules. The traffic is passed.

   • If the matched rule is set to Ask User, DLP notifies the user that the message is being held and contains a link to the DLP Portal, where the user decides whether the transmission should go through or be dropped. User decisions, and reasons for sending, are logged for your analysis.

   • If the matched rule is set to Prevent, the traffic is blocked. The user and the Data Owner may be notified.

3. Optionally, Data Owners, and other users set to be notified, will get notification about the incident.