What is a one sentence summary of your feature request?
We request support for inspecting Rhino (.3dm) files based on their actual internal content rather than relying solely on filename-based evaluation.
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
In our current environment, the DLP/inspection engine is unable to analyze Rhino (.3dm) files based on their internal structure or content. As a result, we can only apply controls using filename-based rules, which is both impractical and insufficient for ensuring proper data protection. Rhino models often contain sensitive design data, intellectual property, or prototypes; therefore, relying solely on filenames does not provide the security or accuracy required in real production workflows.
Enabling content-based inspection for .3dm files would allow us to apply more granular rules, prevent data leakage more effectively, and ensure that sensitive CAD/3D design files are properly protected. This enhancement would significantly improve detection accuracy and reduce false negatives for these file types.
How do you currently solve the challenges you have by not having this feature?
Currently, we rely on basic filename-based filtering, which is only a partial workaround and does not guarantee real protection. We attempt to mitigate risks by combining filename rules with user/group restrictions and monitoring policies, but these methods are far from ideal and still allow potential data leakage if filenames are modified or disguised.