What is a one sentence summary of your feature request?
Request to Expand DRM Files Detection or Add MARKANY DRM in CAP
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
Currently, we have confirmed that the Content Aware Protection (CAP) file types include both “DRM Files” and “FASOO DRM” as separate categories.
However, based on our observations in the actual operating environment, some DRM-protected files, including MARKANY DRM, are not being identified as “DRM Files”,
and as a result, these files are classified under the “Unidentified” file type.
Due to this behavior, in order to control these DRM files, it is necessary to enable the “Unidentified” file type.
However, enabling this option also causes non-DRM and irrelevant files to be detected, which leads to a significant increase in unnecessary logs.
Therefore, we would like to request an improvement in one of the following directions:
Expand the detection scope of the “DRM Files” file type so that other DRM-protected files, including MARKANY DRM, can be properly identified, or
Add MARKANY DRM as a separate DRM file type, similar to the existing FASOO DRM support.
If required, we can provide sample MARKANY DRM files for further analysis, and we kindly request your review of this matter.
How do you currently solve the challenges you have by not having this feature?
At this time, there is no available workaround, and we are still operating with the “Unidentified” file type enabled in order to block DRM files.