All service packs for Exchange Server are supported.
SecurExchange -
Email Content Control Scenarios and Examples
SecurExchange's Content Control and Data Leak Protection (DLP) products are extremely powerful and flexible to enable any conceivable content control and monitoring requirement, whether real-time (internal, outgoing, or inbound) or via a full mailbox search.
Below are a sampling of general and specific scenarios that are possible with SecurExchange family of products. They are categorized by general functionality sets within SecurExchange.
When a message is triggered by a specific rule (or not by any rules) a Message Action is invoked. Message Actions are categorized in 3 ways, none of which are mutually exclusive of another action. In other words any number of sub-actions may be invoked on a triggered message.
Destination Modification:
The message can be deleted/blocked
The message can be routed to other recipients, distribution lists, public folders, and external contacts
The message can be quarantined, which in a compliance or DLP scenario is more a "Review and Allow" type operation.
Message Modifications:
Attachments in the message (all or specific types) can be removed / stripped from the message. Optionally, these attachments may be copied to a directory for safe keeping
Text (plain or HTML) can be added to the triggered message
The Subject of the message can be altered by adding text to the beginning, end, or completely replacing the subject.
Any number of X-Headers may be added to the triggered message
The triggered message can be digitally signed and/or encrypted using the S/MIME standard.
Auxiliary Actions:
A message may be sent to multiple recipients, distribution list, contacts, and/or public folders
A copy of the message may be sent to multiple recipients, distribution list, contacts, and/or public folders. A convert copy operation prevents Read and Delivery Receipts from being sent.
A message may be sent to the originator, explaining the reason(s) for the trigger.
A triggered message can be archived to a SQL, or ODBC compliant database.
Examples:
Combining actions together with other rules and attributes you can for instance:
Block or prevent outgoing/outbound emails from being delivered to external domains like hotmail, gmail, etc., with a copy being sent to HR and a reply be sent to the originator (can be subset by group(s))
Covertly copy messages sent by internal employees to other internal users or external users.
Do a Review and Allow on all messages from particular user(s) or outgoing to a domain or address.
Content Inspection
Content inspection applies to both message bodies (text, HTML, or RTF) and their attachments and occurs either in real-time (inbound, outbound, or internal) and mailbox searches depending on the particular edition of SecurExchange installed.
Looking for terms like guarantee, rate, and return without the ability to place delimiters on the hit location, can result in high false positives as each keyword may be paragraphs away from each other. You don't want to have a false positive hit on something like this:
I guarantee you will have a great time bungee cording. The return bounce will make your feel light headed. Your heart rate will increase.
Dictionary / Thesaurus Expansion: With 30,000 commonly used words in the English language how are you going to create rules for every possibility?
Using a Spam example that we are all familiar with, locating "free meds".
In a simple rule like "free meds", free can also been inexpensive, cheap, "at least cost", gratis, etc, while meds could be Rx, drugs, pills, etc. In any keyword searching product, you would need 20 rules to cover these specific words. With SecurExchange the simple rule "free meds" would catch them all.
Word Stemming: Stripping prefixes and suffixes to yield the root word. This means that plurals, past tenses, adjectives, adverbs, etc will be found without the need to create specific rules"
Looking for determine, will also find determination, determining, determinations, determines, etc
Positional Analysis: Location of content signifies overall importance
Finding confidential (or it's equivalences) in 17 spots in a word document does not necessarily make the document confidential, but finding Confidential in the title, summary pages, table of contents, header, or footer would strongly suggest the document is confidential
Misspellings: Looking for closeness to a keyword
With the i before e rule, or US / British/Canadian differences you need to be able to handle situations like reciept or receipt, honour or honor, etc
Numeric Equivalences: Locates numerics independent of how they are represented.
Looking for a number greater than 1,000 will find 1234, 1,234, the word million, combinations of numerics and words like 2K, or 58 hundred.
Negative and Multiple Search Terms: Creates tighter rules to prevent false positives, and wider rules to catch more specific content.
You need to a rule to block "guarantee a high, large, or huge rate of return" - One rule -> +guarantee +rate +return @0 high large huge
Missing Content: Looks for the omission of particular content
Trying to make sure that for instance a project number is contained within an email if there is an AutoCad file or Excel spreadsheet attached.
Attachment Handling
Filename or Extension Name: Trigger based on some aspect of the file name or extension.
For instance you want to make sure that *.doc or *.pdf files are blocked from leaving your organization, possibly from only a particular group (include), or from everyone except a particular group (exclude).
Content Type: Looks at the true content of the attachment to determine its type or natural extension.
Using the example above, block or quarantine any messages that contain a Word document, independent of what the extension actually is.
Spoofing: Triggers if the true type of the attachment differs with that of the actual extension assigned to the attachment.
For instance, triggers if a zip file has been renamed to a .txt file.
Omissions: Define what types of attachments are acceptable.
For inbound you want to only allow PDF and Word documents, but for outbound you want to allow only PDF files
Exclusions:
Blocking any zip files (based on actual content or the file extension) from entering your organization except if they are going to your System Admin staff.
See our Solutions and Scenarios section for some real life examples of SecurExchange in action.
Copyright 1996-2007, Nemx Software Corporation, All Rights Reserved. All trademarks used or referred to on this site are the
property of their respective owners. No materials on this site may be reproduced, altered, or further distributed without Nemx's prior written permission.
