Archive | Search RSS feed for this section

Dysfunctional Search and the FBI, any of it sound familiar?

I think dysfunctional search is a great name. Unfortunately, it appears that the FBI wins the prize, but I am sure there are many organizations that also feel that their search is dysfunctional. An article in techdirt, ‘How The FBI’s Dysfunctional Search Systems Keep Information Out Of FOIA Requesters’ Hands’, did provide a chuckle, simply because it is just too late to take the US government seriously anymore.

To try to make this short, Trentadue versus the FBI, deals with a requested release of videotapes containing footage of the Oklahoma City bombing. Somehow during the first four days of testimony it was revealed that the FBI has ‘convenient’ information silos, instead of a cohesive repository for search. The problem is the person requesting the information must specify the correct records system for a comprehensive search to take place. The FBI typically only searches the main repository. In addition, the requester must specify in their request a ‘cross-reference’ check, which may mention the subject, but is not stored in the main repository. Again, the now beleaguered requester, must also send a request to the field offices involved, because the FBI ‘Records Information Dissemination’ has no cross-links to other than the original field office.

What about internal search at the FBI? The Central Records System (CRS), as it turns out, is not really a central repository and will accept three different methods of search, which will return three different sets of documents. One of the search methods, Automated Case Support (ACS) is used to search the CRS, but that search isn’t unified. To make matters worse the ACS is then split into three components. And, I think I’ll stop there as it just gets worse and worse, really it does. Oh, one more tidbit, the FBI decides what keywords to use.

I would imagine, or sincerely hope most organizations do not have a search environment such as the FBI. But enterprises do have silos of information and many have no integrated way to search across multiple repositories either via a software product that crosses repositories or through federated search. This should be a basic function. According to an AIIM study, only 18% of organizations have cross repository search capabilities. Maybe the FBI should provide training lessons.

Does your organization have cross repository search capabilities or federated search?

Comments are closed

Office 365 Compliance Search for eMail and Content -Good but not Good Enough

According to our third annual Microsoft Survey, the use of Exchange is almost a given. So is the rise of data breaches, which is most likely caused by your own employees. Security in Exchange for the identification of potential exposure can be done through the use of Compliance Search. This will enable administrators to search for common strings such as social security number, credit card numbers, or account numbers. The searches can be saved and re-executed. Concept Searching adds value to the identification of data privacy or confidential information, regardless of where it resides because it is not limited to defined descriptors such as a social security number, but can contain any descriptor and verbiage that you want secured.

Most security products, including Office 365 Compliance Search will identify the most likely, and standard descriptors typically used by most organizations. Sometimes that doesn’t always work. Confidential information, For Official Use Only (FOUO), new product information, competitive information, intellectual property, patents, or specific customer information may all contain confidential information, but it’s not easy as each subject may not have a common denominator to use as a rule. What to do then?

Concept Searching lets the organization quickly define rules that contain descriptors (social security number) and/or associated verbiage. Since we generate multi-term metadata that forms a concept the organization has no limit or bottlenecks trying to secure specific information. Once found, using Office 365 or SharePoint tools the content can be redirected to a secure repository, removed from search, and portability is prevented. Pretty cool. The rules are easily added, deleted if no longer necessary, and can be changed as the content the organization considers confidential may also change. In SharePoint, taxonomies can be deployed and when a document is found to have a data breach, the content type is automatically changed and classified against the taxonomy. Works when content is created or ingested, and in real-time. It works with diverse repositories, SharePoint, Office 365, You name it, you’re totally covered.

Comments are closed