EaseFilter Data Protection SDK

EaseFilter Data Protection SDK provides a comprehensive data protection solutions for the sensitive data.The SDK includes the build in encryption driver engine, it can encrypt and decrypt the files transparently with 256 bit AES algorithm; The SDK includes the file access control driver engine, it can prevent the access to sensitive files by unauthorized users or processes; The SDK also includes the file I/O access monitor driver engine, it can monitor the file access in real time and generate the autit logs for the auditor with full history of the file access activities. The SDK provides the flexible filter rules, which allow you to create data protection policies based on file types, process names, process Ids and user names. You can protect your local file with the policies, or you can add the access control policy to the encrypted file and distribute the encrypted file to the trusted user and processes.

With the EaseFilter SDK, you can create the softwares in these categories: 1. File Encyption software. Develop transparent file level encryption software with encryption filter driver engine source code in one step. 2.Secure file access control software. Develop the secure file access control software in c#/c++ with source code of the examples, no filter driver experience needed. 3.Confidential file sharing software. Protect your confidential files be leaked, develop the build in software to integrate with your encrypted sensitive data and embedded with access control policies. 4. File content management software. Develop the secure software to screen the file content before it is accessed by the application, make sure your content has not been tampered. 5. Anti-virus software. Build your own custom anti-virus software with complete filter driver framework source code, reduce your development time and improve the efficiency. 6. Customize filter driver development. Develop your custom filter driver with the filter driver framework.

Whats new in this version:

Version 4.2.3.1 fixed a file name related BSOD bug.