What areas must be addressed for ILP solutions to be succesful?
1. Document searches must be easy. This sounds contrite, but is acutally a big challenge. It is hard to know how to distinguish one document from another unless you know what you are looking for. Knowing what to be looking for becomes increasingly difficult as the number of documents outnumbers what can be expected to be read by a person, or team of persons. The standard approach has been to search for regulatory compliance, or terms that one accociate with sensitive information. What has not been done yet, is to understand how these documents are related to other documents. If this relationship was understood, then automation could be used to find groups of documents and assign sensitivity to these documents by assigning "social" values (such as documents created in a finance group) etc. The problem is to establish a hierarchy of documents based on sensitivity. This cannot be achieved by just looking for syntax, context, and keywords or regular expressions. This combination will catch a subset of documents that look like what you are afraid of, but cannot tell you about documents you dont know needs to be protected, but you dont know how these documents looks like yet. Without understanding the cronologie of how these documents are created, and by who(m), it will not be solved. Most of the documents I create, are either created from a template, or use text from other documents, or downloaded information from either websites or data bases. I also rely on prior knowledge obtained through reading. It is easy to see that a strict hierarchy is impossible to create unless the origin of the information is understood. I believe that the best approach is to create meta data that follows the documents as they are incorporated into other documents, and as information is created. The only one who can do this, is the user(s) themselves. Today's document creation tools allows for some of this, but it is not allowing for assigning sensitivity.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment