Here is a quick look at the IRM product suite. IRM can be deployed either stand-alone, or integrated with yourDocumentum Content Server or eRoom installation. We offer client plug-ins for Microsoft Office, Open Office, Adobe Acrobat, Outlook and Lotus Notes email, RIM BlackBerry and html. {Note :  “clients” are plug-ins and not a full separate client. Users still use the native business applications to view their content. }

• ECM Documentum IRM Server (Policy Server)
    - ECM Documentum IRM Client for Microsoft Office
    - Master Concept Documentum IRM Client for OpenOffice
    - ECM Documentum IRM Client for Adobe Acrobat
    - ECM Documentum IRM Client for Lotus Notes
    - ECM Documentum IRM Client for RIM BlackBerry
    - ECM Documentum IRM Client for E-mail


• ECM Documentum IRM Services for Documentum
    - ECM Documentum IRM Client Bundle
            (For Microsoft Office and Adobe Acrobat)

• ECM Documentum IRM Services for eRoom
    - ECM Documentum IRM Client Bundle
            (For Microsoft Office and Adobe Acrobat)
• ECM Documentum IRM SDK
• Products with embedded IRM
    - EMC Infoscape
    - EMC Documentum Records Manager

IRM Server Key and Policy Management

At it’s simplest, here is how IRM works.

1. When IRM is applied, the document is encrypted and the encryption key, along with the rights policy, is stored on the IRM Policy Server.
2. The document may be shared with another user, or checked into a repository, such as a File Share, Documentum Content Server or eRoom.
3. When a user tries to open the protected document, the IRM plug-in retrieves the policy and encryption key from the Policy Server and allows the user to open the document (assuming they have permission) with what ever privileges have been assigned.
4. It’s important to note that content is never stored on the Policy Server, so keys and content are always stored separately, and local keys are always destroyed immediately after use. No encryption key is ever stored locally.

IRM Architecture

1. The IRM Server manages encryption, auditing, policy management etc.

2. Authentication can be handled externally through, say an LDAP integration with Directory Services or your existing Documentum or RSA infrastructure. This allows you to more quickly deploy IRM and reduce impact to administration.

3. And finally, we have our client layer. Documentum IRM works with numerous different types of business content, such as MS Office docs and PDFs, and is also integrated with a number of different Documentum products.