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.

Comments

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...

Check Throughput of Interfaces - Palo Alto Networks NGFW

Check Throughput of Interfaces - Palo Alto Networks NGFW Following command shows brief interface throughput. > show system statistics session To see the complete statistics, run the show system state browser command > show system state browser Press Shift+L and click on Ports To enable tracking and updates press Y and U To see additional ports, press space bar

From MPLS to SD-WAN to SASE: An Evolution of Enterprise Networking

From MPLS to SD-WAN to SASE: An Evolution of Enterprise Networking The way we do business is changing. As critical business applications migrate to the cloud, and the mobile workforce continues to grow, networking and security solutions need to evolve in order to meet the changing business needs. Gartner believes (and we agree) that the future of networking lies with SASE (Secure Access Service Edge) – the convergence of networking and security into one cloud service. Here’s why. 1990s – 2000s: MPLS and the Era of Clear Network Boundaries? Back in the day, networking models were hardware-centric and manually configured. Applications, data, and services lived within private datacenters and relied on remote access solutions to connect remote workers. Dedicated network connectivity, known as MPLS, was the preferred approach for connecting remote locations. MPLS provides predictable performance, low latency and packet loss, and central management. However, MPLS is ...

Secure IT

Search This Blog