CSSCurrent en:Import and Export of Policy Rules
Exporting Policy Rules as CSV File
You can export existing policy rules as a CSV file to make more extensive changes or to obtain a tabular overview of all settings. The format of the CSV file is identical for export and import, see CSV File Format. This allows you to export individual or all policy rules, edit them in the exported file and then import them again to apply the changes.
Exporting Single Policy Rules
To get an export of a single policy rule, click on the export icon to the right side of a policy rule:
Apart from the header line, the generated CSV file contains only a single line that corresponds to the selected rule.
Exporting all policy rules
To export all existing policy rules, click on "Start Export" button above the policy rules table:
Importing Policy Rules from a CSV File
In addition to using the "Create default rule" and "Create custom rule" buttons, you can create policy rules by importing a CSV file. It is also possible to update existing policy rules this way.
Option 'Update existing rules'
When changes to existing rules are necessary, you are able to 'update existing rules' by using the option with the same name. By using the same name as the existing policy rules you define which rules should be updated. By not selecting the option 'Update existing rules' for each rule it is checked if there is already a rule with the same name. When there is no rule with the same name, the name is used as it was defined. When there is is a rule with the defined name, a new rule is created with a policy name extended with a suffix, e.g. 'rule name (2)'. By specifying a blank value for a column, no changes to this setting are performed. An exception to this are sender and recipient patterns. These patterns are added to existing entries instead of overwriting them.
CSV File Format
File Size Limitation
The CSV file may not be larger than 1 megabytes.
Optional delimiter definition
If the policies are written using a different delimiter than a semicolon, you need to define which delimiter was used for the file by adding a first line with the following definition:
Example: sep=,
Optional definition of strings
In order to prevent splitting values into multiple column values that contain the delimiter, you are able to use double quotation marks to define a string.
Example: "Sending mails from external senders to the departments Marketing, Distribution, and Support"
By using double double quotation marks inside of strings, you are able to escape and add double quotation marks into the string.
Required definition of headers
For easier understanding of the individual columns, it is necessary to specify a header line definition after the optional separator definition and before the policy rule lines. This header is also used to transparently display changes to the CSV import. Copy this header line into your csv file to get a valid csv file. Please note, if you use a separator other than the default semicolon, replace it with your custom separator in the header definition.
For versions prior or equal to 6.2.0:
Defining policy rules
Each policy has to be defined in a separate line with 44 columns each. Each column represents an own setting. Based on creating or modifying a rule, a blank value for a column has different results:
- When a new rule is created, the defined default value is used, see below.
- When updating an existing rule, the already set setting is used.
| Column number | Settings | Allowed values | Default value for new rules when a blank value is given | Remarks for creating a new rule | Remarks for updating existing rules |
|---|---|---|---|---|---|
| 1 | Rule name | Arbitrary string (maximum 4000 characters) | <Index> - <Date> - | When there are already rules with the same name, the given name is appended with a generated suffix, e.g. 'Rule name (2)'. | The rule name is used to determine which existing rules should be updated. |
| 2 | Rule type |
Allow, Deny |
Allow |
Define an 'allow' or 'deny' rule. | |
| 3 1, 3 | Sender pattern | A comma, semicolon, or space separated list of email addresses, domains and regexes. |
.* |
Entries are assigned to the correct input field in the policy table automatically.
It is not possible, to define a rule where neither the sender pattern nor the recipient pattern is defined. |
Defined email addresses, domains, and regexes are added and classified automatically to the existing list of sender patterns.
Already existing email address, domains, and regexes have to be deleted using the "current policy rules" table or the wizard. It is not possible, to define a rule where neither the sender pattern nor the recipient pattern is defined. |
| 4 1, 3 | LDAP for sender pattern | A string which resolves to a unique LDAP entry
eg: CN=John ,OU=CSS,DC=cs4qa,DC=com |
|||
| 5 | Sender network IPV4 pattern | A string that matches IPv4 with subnet mask (eg. 123.123.123.121/10) | |||
| 6 | Sender network IPV6 pattern | A string that matches IPv6 with subnet mask (eg: 2001:0db8:85a3:0000:0000:8a2e:0370:7334/23 ) | |||
| 7 2, 3 | Recipient pattern | A comma, semicolon, or space separated list of email addresses, domains and regexes. |
.* |
Entries are assigned to the correct input field in the policy table automatically.
It is not possible, to define a rule where neither the sender pattern nor the recipient pattern is defined. |
Defined email addresses, domains, and regexes are added and classified automatically to the existing list of recipient patterns.
Already existing email address, domains, and regexes have to be deleted using the "current policy rules" table or the wizard. It is not possible, to define a rule where neither the sender pattern nor the recipient pattern is defined. |
| 8 2, 3 | LDAP for recipient pattern | A valid string which resolves to unique LDAP entry
eg: CN=John ,OU=CSS,DC=cs4qa,DC=com |
|||
| 9 | Transfer size | Positive numbers (> 10) | The value specified in Transfer Settings for maximum transfer size in megabytes. | ||
| 10 | Storage duration | Positive numbers (>1) | The value specified in Transfer Settings for storage duration in days. | ||
| 11 | Show filenames | Boolean value (0 - false, 1 - true) | The value specified in Mail Settings for show filenames in transfers. | ||
| 12 | Show filenames changeable | Boolean value (0 - false, 1 - true) | The value specified in Mail Settings for show filenames in transfers changeable. | ||
| 13 | Download notification | Boolean value (0 - false, 1 - true) | The value specified in Mail Settings for download notification on file retrieval. | ||
| 14 | Download notification changeable | Boolean value (0 - false, 1 - true) | The value specified in Mail Settings for download notification on file retrieval changeable. | ||
| 15 | Show zip content | Boolean value (0 - false, 1 - true) | The value specified in Mail Settings for show zip contents. | ||
| 16 | Allow confidential message | Boolean value (0 - false, 1 - true) | The value specified in Mail Settings for allow confidential message. | ||
| 17 | Force confidential message | Boolean value (0 - false, 1 - true) | The value specified in Mail Settings for force confidential message. | ||
| 18 | Allow notification editable | Boolean value (0 - false, 1 - true) | The value specified in Mail Settings for allow edit recipient notification. | ||
| 19 | Standard password modes | A comma, semicolon, or space separated list of "none", "generated" or "manual. | The value specified in Password Policy for standard password modes. | ||
| 20 | Quick password modes | A comma, semicolon, or space separated list of "none", "generated" or "manual. | The value specified in Password Policy for Quick password modes. | ||
| 21 | Access protection | lock, delete | The value specified in Download Security for access protection. | ||
| 22 | Available security modes | A comma, semicolon, or space separated list of "password", "quick" or "id_provider". | The value in the security settings for activated security modes.
The first listed security mode will be used as default security mode. id_provider is only selectable when the installed licence allows the use of id providers. |
||
| 23 | QUICK default only if established | Boolean value (0 - false, 1 - true) | The value in the security settings if QUICK should be default if a quick connection is already established.
This setting can only be selected with true if
|
||
| 24 | Signature | The name of a pre-configured signature (can be empty) | |||
| 25 | Sender address | Valid mail address (maximum 320 characters) | The value specified in Mail Server Settings for sender address | ||
| 26 | Sender name | Arbitrary string (maximum 4000 characters) | The value specified in Mail Server Settings for sender name | ||
| 27 | Subject | The label of a pre-configured subject (can be empty) | |||
| 28 | Mail format | mixed, multipart, html, plain | The value specified in Mail Server Settings for mail format | ||
| 29 | Mail encoding | binary, 7bit, 8bit, base64, quoted-printable | The value specified in Mail Server Settings for mail encoding | ||
| 30 | Mail image handling | external, embedded, multipart, hidden | The value specified in Mail Server Settings for images | ||
| 31 | Log messages and subjects | Boolean value (0 - false, 1 - true) | The value specified in Log Settings for log messages and subjects | ||
| 32 | Log filenames | Boolean value (0 - false, 1 - true) | The value specified in Log Settings for log filenames | ||
| 33 | Log zip content | Boolean value (0 - false, 1 - true) | The value specified in Log Settings for log zip content | ||
| 34 | Pre-processing exit code | A valid Integer within range (-2147483648 to 2147483647) | 0 | ||
| 35 4 | Pre-processing command | Arbitrary string (maximum 4000 characters) (can be empty) | |||
| 36 4 | Pre-processing additional command arguments | Comma separated strings (maximum 4000 characters for each item) (can be empty) | |||
| 37 4 | Pre-processing error output source | none, stdout, stderr, combined | none | ||
| 38 | Pre-processing search pattern | Arbitrary string (maximum 4000 characters) (can be empty) | |||
| 39 5 | Pre-processing replacement pattern | Arbitrary string (maximum 4000 characters) (can be empty) | |||
| 40 | Pre-processing file size limit behavior | skip, remove | skip | ||
| 41 | Pre-processing file size limit | A valid Integer within range
(0 and 10000000) |
0 | ||
| 42 | Pre-processing inform admin on failure | Boolean value (0 - false, 1 - true) | 0 | ||
| 43 | Archiving active | Boolean value (0 - false, 1 - true) | The value specified in Archiving Connection Settings for enabling archiving for new policy rules | ||
| 44 6 | File type filter list | Name of an existing file type list (can be empty) | If not specified no file type list will be assigned to the policy | If the imported value is empty any existing file type list assignment of the policy will be overwritten with an empty assignment. |
1 - This is mutually exclusive. Only one of these should have value at a time.
2 - This is mutually exclusive. Only one of these should have value at a time.
3 - At least one of these four colums has to be set for a valid policy rule. The other values can be left empty (but it is necessary to specify the correct amount of separators).
4 - These fields cannot have a value if the field 'Pre-processing exit code' is empty.
5 - Cannot have a value if the field 'Pre-processing search pattern' is empty.
6 - This field can only contain a value if the associated feature is licensed. If not an error message will be shown.
Example
Below is an example of the contents of a CSV file including two policies.