V3 Violations - Sample Responses

The following sections show examples of message and attachment violations:

V3 Messages - Content Violation

This first sample response is of a violation on message content with no attachment. The "details" field of the violation is where the outcome of the enforcement is described. Within the "details" json structure, there will be an array of "policyResults". Each object within this array corresponds to the result of each policy that was applicable to the given request. In this instance a policy of type TEXT_MATCH was application. The details of the exact policy used is described in the "matchedPolicy" json structure. Within each "policyResult" object, there will be an array of "ruleResults", each of which will describe the exact reasons that the policy matched. There is a field named "complianceDetail" that will show the specifics of the match . For this specific violation, the document contains a "ruleDescriptor" json, which describes the rule that is contained in the policy, and a "content" json, which is specific to a violation of content. In this particular document, the "content" json says that a dictionary, with the shown id and version, contains a word "dlp_test" that was found in the message content.

V3 Attachments - Content Violation

This is a sample violation on attachment content of an attachment included in a message. The details of the violation can be found by the following "details" → "policyResults" → "ruleResults" → "complianceDetail" → "detail". Within "complianceDetail"→"detail", the specifics of this attachment content match are specified. In this situation, the policy contains a dictionary, with id: "5b67f44e1cd27a3d4e65c1da" and version: "1.1", that matches the word "testing". This word was found in the file content and then caused the violation.

V3 Attachments - Password Protection Violation

This is a sample violation on the password protection of an attachment included in a message. The details of the violation can be found by the following "details" → "policyResults" → "ruleResults" → "complianceDetail" → "detail". Within "complianceDetail"→"detail", the specifics of this file password protection match are specified. In this situation, the policy matches files that are password protected and this can be seen in the "complianceDetail' → "detail" → "password". If "passwordProtected" was false, it would mean that the policy blocked files that are not password protected for the given extension.

V3 Attachments - Classification Tags Violation

Classification tags are key-value pairs that can be added to the metadata of an attachment. The EFv3 system is able to detect these key-value pairs for certain file types. This is a sample violation on file classification tags of an attachment included in a message. The details of the violation can be found by the following "details" → "policyResults" → "ruleResults" → "complianceDetail" → "detail". Within "complianceDetail"→"detail", the specifics of this file classification tag(s) match are specified. In this situation, the policy matches files that have certain classification tags and this can be seen in the "complianceDetail' → "detail" → "classifiers". The "matchedPair" array describes the key-value pair of the violating classification tag(s).

V3 Attachments - Size Violation

This is a sample violation on the attachment size of an attachment included in a message. The details of the violation can be found by the following "details" → "policyResults" → "ruleResults" → "complianceDetail" → "detail". Within "complianceDetail"→"detail", the specifics of this attachment size match are specified. In this situation, the policy matches attachments that have a size greater than a size limit and this can be seen in the "complianceDetail' → "detail" → "size". The size of the attachment will be specified in megabytes.

V3 Attachments - Extension Violation

Attachment Extension Violation - Mismatched extensions:

This is a sample violation on the extension of an attachment included in a message. This violation can only occur if the extension of the attachment is in the system's allowed extension list. If the system then detects that the actual file type is different than the provided extension of the file, a violation will be generated. The details of the violation can be found by the following "details" → "policyResults" → "ruleResults" → "complianceDetail" → "detail". Within "complianceDetail"→"detail", the specifics of this file extension match are specified. In this situation, the policy matches attachments that have different extension than the detected extension by our system and this can be seen in the "complianceDetail' → "detail" → "extension".

Attachment Extension Violation - Not Allowed Extension:

This is a sample violation on the extension of an attachment included in a message. The details of the violation can be found by the following "details" → "policyResults" → "ruleResults" → "complianceDetail" → "detail". Within "complianceDetail"→"detail", the specifics of this attachment extension match are specified. In this situation, the policy matches attachments that have an extension that is not allowed by the policy and this can be seen in the "complianceDetail' → "detail" → "extension".

Last updated

Was this helpful?