How to Upload Html Email Into Esafesend

VIPRE SafeSend can prevent sensitive information from existence sent out to the incorrect client.

It can scan emails and attachments for specific customer keywords or regular expressions and require amanuensis confirmation.

Customer Keyword and Domain Scanning

Define Client Data

The client keyword/domain data is configured in Edit Settings,under the Data Loss Prevention (DLP) tab, and stored in the setting SS_ClientKeywordDomainList; information technology tin contain thousands of lines of client/customer data. The principle is that you can identify a ready of client keywords or regular expressions and associate those with a set of customer domains. Instead of domains, it is likewise possible to specify individual email addresses as approved recipients.

Syntax:
Client1Keyword1,Client1Keyword2,…:Client1Domain1,Client1Domain2,… Client2Keyword1,Client2Keyword2,…:Client2Domain1,Client2Domain2,…

Example:
Apple tree,AAPL:apple.com Microsoft,MSFT:microsoft.com

Display Popup only when Client Information is Found

Information technology is possible to apply the setting OnlyPopupForDLPMatch to configure SafeSend to brandish its confirmation window but when client data has been found in the electronic mail.

Supported Attachment File Types

Text: csv, txt
PDF: pdf
HTML: html, xhtml
Word: md, docx
PowerPoint: pptx, ppsx, pptm, ppt, pot, pps
Excel: xls, xlsx, xlsm, xlt, xltx, xltm
RTF: rtf
Nada: zip (recursively)

Sending to Not-client Recipients

The user is required to type "CONFIRM" in order to send client data to a not-client external domain.

Sending to Approved Recipients

No additional confirmation is required except confirming the external recipient.

Sending Non-client Data Externally

What happens, in this case, depends on the OnlyPopupForDLPMatch setting. If information technology is enabled and so the SafeSend confirmation window will not exist displayed. If it is disabled, which is the default behavior, then SafeSend will still show its normal confirmation window. The below screenshot is thus displayed just if OnlyPopupForDLPMatch = 0.

Password protected files or invalid files

SafeSend displays countersign protected files or invalid files in the DLP output tabular array. Countersign protection is detected on Word, Excel, PowerPoint, PDF, and Naught files.

The scanning email notification

The Scanning Email notification is displayed when OnlyPopupForDLPMatch is enabled, and SafeSend is busy scanning big files. The default time-out for large files is 10 seconds (see ContentScanningTimeoutMS), whereby SafeSend will post an mistake message in the dialog, saying that the content scan timed out.

DLP Content Scanning

Sensitive content is presented to the user, and yous can define if the email should be blocked, or if the user tin send the e-mail afterwards an additional confirmation.

Here you can see that SafeSend scanned an electronic mail's content and attachments finding potential Social Security and Credit Card numbers.

Sensitive Content

When you lot use DLP with VIPRE SafeSend, this is the type of content information technology looks for within your emails:

Strings such as 'Confidential', 'Internal', 'Restricted' and 'Sensitive'.
US Social Security Number (SSN)
Credit Card number (VISA, MasterCard, American Express, Diners Club, …)
Standard health identification card number (NPI)
Vehicle Identification Number (VIN)
UK health identification number (NHS, CHI)
United kingdom of great britain and northern ireland national insurance number (NINO)

SafeSend Actions

Once VIPRE SafeSend finds what information technology's looking for, it performs the following actions:

Inform the user
Require confirmation from the user in the grade of a checkbox
Require confirmation from the user by the text "CONFIRM"
Deny sending the email

Supported Content Types

VIPRE SafeSend supports the post-obit types of documents and attachments:

Email content (body)
Email field of study
Attachment file name
Zipper file types (scans inside attachments)
- Text: csv, txt
- PDF: pdf
- HTML: html, hxtml
- Discussion: doc, docx
- PowerPoint: pptx, ppsx, pptm, ppt, pot, pps
- Excel: xls, xlsx, xlsm, xlt, xltx, xltm
- RTF: rtf
- ZIP: zip (fully recursive)
- MSG: msg (fully recursive)

DLP Policy

Policy Syntax

The DLP policies are defined using the post-obit syntax:

[policy_name]:[file_types_to_scan]:[action_upon_match]:[regular_expression]

Options for 'file_types_to_scan':

"all"
"all_excl_pdf"
"email_content"
"email_subject"
"file_name"
"csv", "txt", "pdf", "html", "hxtml", "doc", "docx", "rtf", "xls", "xlsx", "xlsm", "xlt", "xltx", "xltm", "pptx", "ppsx", "pptm", "ppt", "pot", "pps"

Options for 'action_upon_match':

"inform"
"ostend"
"confirm_text"
"deny"

If you'd like to skip the policy examples and get straight to the configuration of DLP, we can skip past information technology and come back if necessary.

Policy Examples

Case-insensitive detection of the string "confidential" in all content types that require user confirmation. The policy is named "Confidential".

Confidential:all:confirm:(?i)confidential

Case-insensitive detection of the string "confidential" in specific content types. The results are displayed to the user and require no confirmation. The policy is named "Confidential".

Confidential:email_subject,email_content,doc,docx:inform:(?i)confidential

VISA credit card rule that requires a user confirmation for all content types. The policy is named "VISA".

VISA:all:confirm:4(?<=\b(?<!\.)4)\d{3}[\West\southward]?\d{4}[\West\s]?\d{4}[\W\due south]?\d{four}\b

Regular Expressions (regex)

Generic:

Confidential:all:ostend:(?i)confidential
Internal:all:confirm:(?i)internal
Restricted:all:confirm:(?i)restricted
Sensitive:all:ostend:(?i)sensitive

Credit cards:

Visa: four(?<=\b(?<!\.)4)\d{three}[\Due west\due south]?\d{iv}[\W\s]?\d{iv}[\W\south]?\d{iv}\b
Mastercard 1: 5(?<=\b(?<!\.)5)[ane-5]\d{two}[\W\s]?\d{4}[\W\s]?\d{iv}[\West\due south]?\d{4}\b
Mastercard ii: 5(?<=\b(?<!\.)v)([\Due west\s][ane-5])([\W\s]\d){14}\b
American Express one: iii(?<=\b(?<!\.)3)(4|7)\d{two}[\W\s]?\d{two}[\Due west\south]?\d{4}[\Due west\s]?\d{5}\b
American Limited 2: 3(?<=\b(?<!\.)3)([\W\s](four|seven))([\W\due south]\d){13}\b
Diners Guild 1: three(?<=\b(?<!\.)three)(0[0-5]|[68]\d{1})\d{one}[\W\s]?\d{4}[\W\due south]?\d{4}[\W\south]?\d{2}\b
Diners Social club ii: 3(?<=\b(?<!\.)3)[\W\s](0[\Westward\south][0-v]|[68][\W\southward]\d{one})([\Westward\due south]\d){11}\b
Discover carte 1: 6(?<=\b(?<!\.)6)(011|5[0-nine]{2})[\W\southward]?\d{4}[\W\due south]?\d{4}[\Westward\due south]?\d{4}[\W\southward]?\b
Find card 2: 6(?<=\b(?<!\.)half-dozen)[\W\s](0[\West\s](1[\W\s]){two}|5[\W\s](\d[\Due west\s]){two})(\d[\W\southward]){eleven}\d\b
JCB cards ane: (?=[21|xviii])(2131|1800)[\Westward\due south]?(\d{4}[\W\southward]?){two}\d{three}\b
JCB cards 2: (?=[2|1])(2[\Westward\due south]?ane[\W\s]?3[\W\s]?1|1[\W\s]?8[\W\s]?0[\W\south]?0)([\Westward\s]?\d){x}\b
JCB cards 3: 35(?<=\b(?<!\.)35)\d{2}[\W\s]?(\d{4}[\W\southward]?){3}\b
JCB cards 4: 3(?<=\b(?<!\.)three)[\W\s]?five[\Due west\s]?(\d[\W\south]?){13}\d\b

Standard health identification carte number (NPI):

(?<!\\d)\\d{10}(?!\\d)|80840\\d{10}(?!\\d)

Vehicle Identification Number (VIN):

[0-9A-HJ-NPR-Z]{17}

Us Social Security Number (SSN):

([^0-9-]|^)([0-ix]{3}-[0-9]{2}-[0-9]{4})([^0-9-]|$)

United kingdom wellness identification number (NHS, CHI):

b([ane-9]{1}[0-9]{2}s?-?[0-9]{3}s?-?[0-ix]{4})b
(([^wt]?s)?(-)?d){10}
(([^wt]?s)?(_)?d){10}
(([^wt]?south)?d){x}

UK national insurance number (NINO):

[A-CEGHJ-NOPR-TW-Z]{two}[0-9]{6}[ABCDs]{one}

Irish PPS number:

W?d{seven}[a-zA-Z]{1,2}Westward

Other

SSNorHSA:all:confirm:([^0-9-]|^)([0-ix]{three}[0-9]{ii}[0-9]{four})([^0-9-]|$)
DDAorSAV7:all:confirm:([^0-9-]|^)([0-9]{7})([^0-9-]|$)
DDAorSAV8:all:confirm:([^0-9-]|^)([0-ix]{eight})([^0-9-]|$)
HSA:all:confirm:([^0-nine-]|^)([0-9]{10})([^0-9-]|$)

Health

Configuring DLP Content Scanning

VIPRE recommends that y'all exam your DLP rules earlier deployment using the live testing window. To exercise this, follow the steps below.

Access the live testing window at File > Options > Add together-ins > Add together-In Options > SafeSend > Edit Settings
Use the setting ContentScanningRules in the ADMX/ADML files for configuration via Group Policy; This setting can exist used to push out new rules to all client machines. This setting is named SS_ContentScanningRules in the registry which can also exist used for testing settings locally:

HKEY_LOCAL_MACHINE/SOFTWARE/{WOW6432Node}/SafeSend/SS_ContentScanningRules

The ContentScanningLicenseKey needs to be set to a valid license key in a product deployment (non in a trial or POC).

Screenshots

Sending client data to non-client recipients

Sending non-client data externally

Password protected files or invalid files

jacksonsmisprome1960.blogspot.com

Source: https://success.vipre.com/safesend-manage-pc-addin/safesend-pc-data-loss-prevention-settings