Skip to main content

DLP CONFIGURATION WITH EXCHANGE AGENT

DLP CONFIGURATION WITH EXCHANGE AGENT


DLP CONFIGURATION WITH EXCHANGE AGENT


Pre-requisites

1.Windows Server with MS Exchange Installed
2.GW with DLP blade enabled
3.Exchange Agent
Configuration

1.Enable DLP on the gateway and also enable user check client support with out which the end user will not get any user check messages. Also allow notification emails so that users using outlook can get notification mails.
Enabling self handling is also important since the user can login to the portal and either send the mail or discard it from the dlp portal gateway properties and dlp portal details are as below.
2.Once you have installed the Exchange server on your windows server you can install exchange agent on the exchange server. And configure the same in smart dashboard under dlp tab > Gateways refer to screen shot below.

3.Once you have installed the the exchange agent on both exchange server as well as on dashboard you can initialize the sic between the gateway and the exchange agent.
4.The DLP rules remain the same, the dlp out of the box policy usually does not work so you can create custom data types and use the same in the rule base please refer to the screen shots below.

5.Also for dlp to work optimum you need to edit a parameter under $DLPDIR/dlp/config/dlp.conf, you need to edit the consider_ip_address_in_smtp to yes refer to screen shot below.
6.Once the dlp agent is installed and configured you can see the following stats on the dlp agent.

Labels:

Comments

Post a Comment

Popular posts from this blog

How to modify SSH/HTTP/Telnet time out in Cisco ASA firewall?

How to modify SSH/HTTP/Telnet time out in Cisco ASA firewall? By default tcp idle timeout is 1:0:0 hh:mm:ss. If in case you need to modify it you can do it by MPF (Modular Policy Framework). Let us setup a custom timeout when traffic is coming from particular host 10.77.241.129. !— Match the traffic using the access-list —! object-group service DM_INLINE_TCP_1 tcp port-object eq www port-object eq ssh port-object eq telnet access-list outside_mpc extended permit tcp host 10.77.241.129 <source ip> any object-group DM_INLINE_TCP_1 !— Define the class map Cisco-class –! class-map Cisco-class match access-list outside_mpc !— Call this class-map into policy map and set the connection reset after 10 min when traffic is coming from particular host —! policy-map Cisco-policy class Cisco-class set connection timeout idle 0:10:00 reset !— Apply the policy-map Cisco-policy on the interface. —! service-policy Cisco-p...
Post a Comment
Read more

Checkpoint firewall common commands part 2

Checkpoint firewall common commands part 2 For basic firewall informaton gathering: fgate stat -Status and statistics of Flood-Gate-1. fwaccel <stat|stats|conns>  – View status, statistics or connection table of SecureXL. fw getifs -Show list of configured interfaces with IP and netmask. cpstat <app_flag> [-f flavour] -View OS, HW and CP application status. Issue cpstat without any options to see all possible application flags <app_flag> and corresponding flavours. Examples: cpstat fw -f policy – verbose policy info cpstat os -f cpu – CPU utilization statistics cpinfo -y all   -List all installed patches and hotfixes. cpd_sched_config print -Show task scheduled with CPD scheduler. enabled_blades -View enabled software blades avsu_client [-app <app>]   , get_version <app>  -Get signature version and status of content security .Without the -app option “Anti Virus” is used. show co...
Post a Comment
Read more

CLI Commands for Troubleshooting FortiGate Firewalls

CLI Commands for Troubleshooting FortiGate Firewalls 2015-12-21 Fortinet , Memorandum , Network Cheat Sheet , CLI , FortiGate , Fortinet , Quick Reference , SCP , Troubleshooting Johannes Weber This blog post is a list of common troubleshooting commands I am using on the FortiGate CLI . It is not complete nor very detailled, but provides the basic commands for troubleshooting network related issues that are not resolvable via the GUI. I am not focused on too many memory, process, kernel, etc. details. These must only be used if there are really specific problems. I am more focused on the general troubleshooting stuff. I am using it personally as a cheat sheet / quick reference and will update it from time to time. Coming from Cisco, everything is “show”. With Fortinet you have the choice confusion between show | get | diagnose | execute . Not that easy to remember. It is “ get router info6 routing-table” to show the routing table but “ diagn...
Post a Comment
Read more