In some examples, detection module 110 may conclude that the format is unreadable and obfuscated based on a determination that the format is not included within the list of readable formats, even if the format is also not included within the list of unreadable formats (e.g., in the case that the format refers to a new, customized, unsupported, and/or encrypted format). In further examples, detection module 110 may detect that the application is requesting to output the data object in the format that obscures underlying content by detecting that the data object has a file signature that specifies the format (e.g., a file signature that corresponds to a file signature for a format that is not included in the list or set of readable formats and/or is included within the list or set of unreadable formats). In some examples, the file signature may include a file extension (e.g., “.JPG”).
In general, in response to detecting that the application is attempting to output the data object, detection module 110 may request the status of the application from the application data radar, as discussed above (i.e., the flag or other indication of whether the application has accessed sensitive data). Performance module 112 may then perform a remedial action in response to a determination that the application was flagged, as discussed further below.