Hi, Thank you for your reply. It's very helpful. "you could use storage that would seem write-only from the Application Server´s perspective" : We have ruled out this alternative, as it doesn't seem possible in windows (without using some sort of airlock mecanism that will move dropped files somewhere safe, solution our customer does not want) : http://superuser.com/questions/911242/setting-ntfs-permissions-to-write-but-not-read https://technet.microsoft.com/en-us/library/cc783530%28v=ws.10%29.aspx#w2k3tr_randp_how_xgvr One last question, what would happen if application server drop a file in a LanCrypt protected remote folder ? Would it fails ? Would it copy the file in "clear" ? In other word, The remote folder has to be excluded from lancrypt protection in order for the application server be able to drop files in it ? We are thinking of encrypting the files within the application server with a public key whose private pair is only knew of the remote folder's workstation's user keystore.
↧
