For the scenario you’re describing, what settings/configuration do you currently have in place?
→ We have a Content Aware Protection policy with the Clipboard feature enabled, and the Detect Images option is also enabled.
What error messages or unexpected behavior are you seeing?
→ This is more of a clarification question.
We would like to understand how Detect Images within the Clipboard policy is supposed to work.
From our testing, it seems that copying an image (Ctrl+C) is only detected, and the action is logged.
However, since the Clipboard policy itself is configured as a blocking policy, we expected that Ctrl+C for images would also be blocked, similar to how text clipboard actions are handled.
Therefore, we would like to confirm the expected behavior.
When Detect Images is enabled under a blocking policy, should the image copy action (Ctrl+C) be blocked, or is it designed to only detect the action and generate logs/alerts?
When a Content Aware Protection policy configured to Block&Report and Clipboard monitoring with Detect Images enabled, the expected behavior is the following:
When a graphic file is copied into the clipboard (CTRL+C), the user will get File Transfer Blocked notification
Pasting the file is blocked, so the user will not be able to paste it
For this to work, the graphic file (e.g. PNG) must also be selected in the policy’s File Type filter.
If you experience a different behavior, please make sure you are testing on the latest client/server version. If the issue persists, feel free to open a support ticket so our technical support team can investigate.
I am currently testing on the latest server version (2602) and client version (2602.1.2.0).
I would like to clarify the expected behavior when the Detect Images option is enabled in a Content Aware Protection policy configured as Block & Report.
Should the action of copying a graphic file to the clipboard (Ctrl+C) itself be blocked?
During my testing, when I copy a graphic file (Ctrl+C), it seems that the action is detected, but the copy action itself is not blocked.
In Windows, when I check the clipboard history using Win + V, the copied image appears in the clipboard normally.
Therefore, I would like to confirm whether the Detect Images feature with a blocking policy is supposed to block the copy action itself when pressing Ctrl+C, or if it only detects the action.
If the copy action is supposed to be blocked, I believe we may need to open a support ticket for further investigation.
The Copy action is not supposed to be blocked. The file needs to be loaded into the Clipboard so the EPP agent can scan it against the Content Aware Protection policies. If the agent determines that the clipboard content violates any of the policies, it immediately clears the Clipboard content to prevent the Paste action. The client notification is displayed once the agent completes scanning the Clipboard.