So why did the CertiVox technology come into being?

Well simply put, I was continuously frustrated how presentations and ideas I presented to customers or partners would end up being copied and sometimes shown to me by other customers, received from another company!

So I wanted to achieve two goals;  Firstly, to make my content traceable so that when it turned up somewhere else I had a way to identify where my leak occurred, i.e., classic DLP; Secondly, to have better control on the content as to when it could be viewed and who by, i.e. authentication and authorization.

The first incarnation was Rhapzode, a compiler for PowerPoint.  This helped prove the technology and build in the right content type support.  The Rhapzode technology was extended to handle other content types like Windows Media, MPEG, Flash and PDF.

This was then extended to Document Protector, which we wanted to bring on as an online SaaS based solution which allowed users to manage their content dynamically, tracing access down to slide/page/frame level and added policy based capabilities such as redaction.

CertiVox finally closed the loop on the online solution by utilizing XMPP, a secure messaging system to manage the delivery of authentication data and effectively create a spam free trusted network for publishing secure content.

Incidentally it appears we weren’t alone in becoming fans of XMPP, Google built Wave on top of the XMPP protocol as well (Google Wave Federation Server).

Today, I can feel pretty comfortable believe that CertiVox is the most advanced Web 2.0 security service for document and media content protection.  Not just from a technology standpoint, but from a usability factor as well.  We will see shortly!