This would be appropriate because the control goes directly in the hands of IT head rather than users.
This thread was automatically locked due to age.
This would be appropriate because the control goes directly in the hands of IT head rather than users.
DLP works based on the process, e.g. Chrome.exe for example, opening a file that is subjected to the filename/content rules defined in policy.
Chrome is seen to be opening a file by the on-access scanner: The decisions are to block or alert the user with a popup, until then the request is pending.
The idea that a process is being blocked from opening a file for the time it takes for the client to send an email, be read by an admin as say an alert in the console, actioned, a policy/command sent down and processed doesn't seem very practical without quite a change to the workflow.
Regards,
Jak
DLP works based on the process, e.g. Chrome.exe for example, opening a file that is subjected to the filename/content rules defined in policy.
Chrome is seen to be opening a file by the on-access scanner: The decisions are to block or alert the user with a popup, until then the request is pending.
The idea that a process is being blocked from opening a file for the time it takes for the client to send an email, be read by an admin as say an alert in the console, actioned, a policy/command sent down and processed doesn't seem very practical without quite a change to the workflow.
Regards,
Jak