First impression on unpacking the Q702 test unit was the solid feel and clean, minimalist styling.
Titus Labs helps stop e-mail slips
- — 02 June, 2008 08:15
Classified company messages
Message classification is configurable as an optional setting or enforced. If labeling is required and the user attempts to send an e-mail without selecting a label, a default label can be applied automatically without any user intervention or the user can be warned or prevented from sending the e-mail until after they have selected a label (see Figure 3). When a user forwards a labeled message and attempts to reclassify it, a warning can be displayed or the message can be prevented from being sent. Labels can also be signed and verified so that subsequent modification results in a denial message. If Titus Labs' Document Classification product is used, Microsoft Office attachments can have their own data classification labels, which interact with the message data classification features in expected ways.
Forcing users to classify each e-mail can help in providing data sensitivity awareness, but Message Classification can also be used to prevent inadvertent sending to unauthorized parties, enable encryption, or provide policy defined archival. At a very basic level, the classification label text can be interrogated by an Outlook rule, which then controls where and from whom the message can be sent. For example, a message labeled CONFIDENTIAL can be restricted to internal readership only and automatically enable S/MIME protections. Similarly, the data classification labels can be acted upon using e-mail server-side programming (such as Microsoft Exchange event sinks or rules), but Message Classification can also interact with more sophisticated protection products such as Microsoft's Rights Management Service (RMS).
Better security, less coding
RMS (available with Windows Server 2003 or 2008) allows e-mails, documents, and other protected content to be restricted to particular users or groups, and each user can be allowed full access, or forbidden to forward, print, or save. Message Classification allows each data classification level to trigger a particular RMS template (which contains predefined rights for particular users and groups). RMS must be purchased and installed separately, and the involved RMS templates must be distributed to each participating client (as is required even without Message Classification installed). In my testing, Message Classification interacted with RMS perfectly. You can accomplish the same results in RMS without the Message Classification product, but it requires a lot more custom coding. Together, the two are a strong combination, and I'm surprised Microsoft hasn't tried to purchase Titus Labs products and add them to their default RMS offering.
If there is a downside to be found it is in the lack of included reporting. Message Classification reporting is limited to writing events to the normal Windows event log, collecting those events into a central repository, and creating custom reports. Events can be written whenever message classification is used, or writing can be limited to more significant events (failed data classification downgrade). It would better if Titus Labs provided its own data collection and reporting tool with multiple predefined reports.
Titus Labs had made a thoughtful product that can only increase the security awareness of data sensitivity when users rely on Microsoft Office products. Titus Labs has a wide list of satisfied customers, both big and small, including Dow Corning, and multiple state and federal government entities. Titus Labs, and other data classification products like it, should be considered by any mid-level or larger company trying to efficiently place the right level of data protection where it is needed. Pricing starts at US$25.00/user with volume discounts available.