Action summary
This article explains the columns (fields) of the rule group configuration file for admins who perform initial setup and operational management of Email DLP.
By using the configuration file, you can register and update Email DLP settings in bulk.
For instructions on how to create and import the configuration file, please refer to the following article.
[Email DLP] Creating Import Data (Configuration File)
Notes
- The content of this article is based on the product specifications as of May 2026 and is subject to change without notice.
- Admin privileges for Email DLP are required to check the actual screens or change settings.
For instructions on how to configure admin privileges, please refer to the following article.
[Email DLP] Configuring Admin Privileges - For instructions on how to access the Email DLP Administration, please refer to the following article.
[Email DLP] How to Log in to the Administration
Fields
- Supported file formats are YAML and JSON.
- The unique key is "name" (Rule Group Name).
- When using "Overwrite," all information associated with the above unique key will be overwritten.
If you want to modify only part of a rule, be sure to retain the necessary information for each filter.
| Column | Description |
|---|---|
| version | Specify 1. (Fixed value) |
| rule_groups | Creates the rule groups specified in the following lines. * For JSON, use "AddressGroups:". |
| name | Specify the Rule Group Name. |
| description | Enter a description for the rule group. |
| rules | Creates the rules specified in the following lines. |
| priority | Set the priority of the rule. |
| name | Specify the Rule Name. |
| description | Enter a description for each rule. |
| action | Creates the actions specified in the following lines. |
| type |
Specify the type of action. ・send…Send |
| attribute | If the value of type is send, delete, or request_approval, specify "{}". If the type is suspend, specify only the field name. No value is required. |
| auto_release | Specify this field when the type is suspend. If you want to send automatically, specify true. If you do not want to send automatically (suspend indefinitely), no value is required. |
| visible_to_from_address_group | Specify this field when the type is suspend. If you want to make the operation visible to people in From Address Group, specify true. If you do not want to make it visible to people in From Address Group, this field is not required. |
| duration | If the action type is suspend, specify the duration to suspend (minutes). * If no value is specified for auto_release, indefinite suspension takes precedence. |
secure_transfer |
If you want to send attachments with Secure Download, specify true. If you do not use Secure Download for attachments, this field is not required. |
| box_upload | If you want to send attachments with Secure Download for Box, specify true. If you do not use Secure Download for Box for attachments, this field is not required. |
| encrypt | If you want to encrypt attachments, specify true. If you do not want to encrypt attachments, this field is not required. |
| forwards | Specify this field if you want to add BCC. If you do not want to add BCC, this field is not required. |
| envelope_to |
Specify the email addresses to add as BCC. * Up to 5 addresses can be specified. |
Possible predicate values for each target
| target | Possible predicate (Filter Conditions) values |
|---|---|
| header:to:address | ・exist ・not-exist ・match ・not-match ・exist-in-address-group |
| header:cc:address | ・exist ・not-exist ・match ・not-match ・exist-in-address-group |
| header:tocc:address | ・exist ・not-exist ・match ・not-match ・exist-in-address-group |
| header:to:domain | ・exist ・not-exist ・match ・not-match |
| header:cc:domain | ・exist ・not-exist ・match ・not-match |
| header:tocc:domain | ・exist ・not-exist ・match ・not-match |
| bcc | ・exist ・not-exist ・match ・not-match |
| header:subject | ・exist ・not-exist ・match ・not-match |
| header:<Optional Header Name> | ・header-exist ・header-not-exist ・match ・not-match |
| envelope:to | ・match ・not-match |
| envelope:from | ・match ・not-match ・not-approver |
| body | ・match ・not-match |
| attachment | ・attachment-exist ・attachment-not-exist ・filename-match ・content-type-match ・all-password-protected-data ・has-password-protected-data |
Reference
For an example configuration file, please download the sample file from the "■Rule Group Definition" section in the following article.
[Email DLP] Sample Configuration File for Import