Hi,

I am not sure whether this is the truly neutral platform for this case, but let's describe this anyway.

My company is evaluating IRM tools (for pilot use) and currently mostly from a primarily security perspective (keys, external access etc). We also run ECM systems (Sharepoint and Documentum). From my content management point of view, security as applied in IRM systems should always extend and respect the access rules as defined in the ECM system. ECM systems are rather poor in managing content that leaves the repository and -if required- IRM technology seem the most relevant technology in securing content "outside the repository". However as ECM systems manage the  document in its validity (eg is it the right version in the right state, should it still be used, should a particular user be able to access this etc etc), security rules and related capabilities (disable printing/mailing) as defined in IRM technologies are to my opinion not a self-standing subject. This should be ideally steered by ECM systems (lifecycle state, acl rules) that change over time. Some IRM technologies seems to have a rather isolated approach (eg a user sets the IRM permissions on a document themselves).

What is your take on this? Are there any experiences in "real world" implementations? 

regards, Mark

Add a Response

You need to log in to post messages. Click here to login.