What is a one sentence summary of your feature request?
Align Content Aware Protection (CAP) policies with File Tracking by adding directional controls (Outbound, Inbound, Bidirectional) to prevent unnecessary scanning of incoming file transfers.
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
Problem:
Currently, File Tracking in Endpoint Protector allows administrators to select transfer directions (Outbound, Inbound, or Bidirectional). However, Content Aware Protection (CAP) policies do not offer this granular control and evaluate file transfers regardless of direction.
When users copy files from external media (e.g., External HDD) to local storage (e.g., C: drive), CAP applies full content inspection and can trigger false-positive blocks. Because Data Loss Prevention (DLP) primarily focuses on preventing data exfiltration (Outbound), scanning incoming files creates severe operational bottlenecks and frustrates end users.
Proposed Solution:
Bring consistency across features by adding Directional Control options to CAP policies, matching the existing File Tracking menu:
Outbound Only (Default): Inspects files moving from local storage to external media/network destinations (standard DLP behavior).
Inbound Only: Inspects files imported from external media to local storage.
Bidirectional: Inspects file transfers in both directions.
This feature parity allows administrators to focus CAP enforcement specifically on data exfiltration pathways while preventing disruption during internal file imports.
How do you currently solve the challenges you have by not having this feature?
Administrators must apply CAP policies globally across all transfer directions. When users are blocked from importing required files from external drives to local disks, administrators are forced to temporarily disable policies or create broad exceptions, introducing potential security risks and manual management overhead.