Data classification

Abstract

A method for managing data in an enterprise by identifying data of interest from among a multiplicity of data elements in an enterprise, the method including characterizing data of interest at least by at least one non-content based data identifier thereof and at least one access metric thereof, the at least one access metric being selected from data access permissions and actual data access history and selecting data of interest by considering only data elements from among the multiplicity of data elements which have the at least one non-content based data identifier thereof and the at least one access metric thereof.

Description

FIELD OF THE INVENTION

The present invention relates to improved systems and methodologies for data classification.

BACKGROUND OF THE INVENTION

The following patent publications are believed to represent the current state of the art:

U.S. Pat. Nos. 5,465,387; 5,899,991; 6,338,082; 6,393,468; 6,928,439; 7,031,984; 7,068,592; 7,403,925; 7,421,740; 7,555,482, 7,606,801 and 7,743,420; and

U.S. Published Patent Application Nos.: 2003/0051026; 2004/0249847; 2005/0108206; 2005/0203881; 2005/0086529; 2006/0064313; 2006/0184530; 2006/0184459; 2007/0203872; 2007/0244899; 2008/0271157; 2009/0100058; 2009/0119298 and 2009/0265780.

SUMMARY OF THE INVENTION

The present invention provides improved systems and methodologies for data classification.

There is thus provided in accordance with a preferred embodiment of the present invention a method for managing data in an enterprise by identifying data of interest from among a multiplicity of data elements in an enterprise, the method including characterizing data of interest at least by at least one non-content based data identifier thereof and at least one access metric thereof, the at least one access metric being selected from data access permissions and actual data access history and selecting data of interest by considering only data elements from among the multiplicity of data elements which have the at least one non-content based data identifier thereof and the at least one access metric thereof.

Preferably, the characterizing the data of interest includes characterizing data of interest also by at least one content based data identifier thereof and the selecting data of interest includes considering only data elements which have the at least one content based data identifier thereof.

In accordance with a preferred embodiment of the present invention the considering includes defining a field of search in accordance with the at least one access metric and searching within the field of search based on the at least one non-content based data identifier. Alternatively, the considering includes defining a field of search in accordance with the at least one access metric multiple times and searching within the field of search multiple times, wherein the at least one access metric is different at least some of the multiple times.

Preferably, the at least one access metric is a dynamic metric which changes over time during operation of the enterprise.

In accordance with a preferred embodiment of the present invention the method for managing data in an enterprise by identifying data of interest from among a multiplicity of data elements in an enterprise also includes automatically redefining the field of search in accordance with the at least one access metric multiple times and searching within the field of search multiple times, where the at least one access metric is different at least some of the multiple times. Additionally, the searching includes searching only within those portions of the field of search that have been modified or added as the result of redefining the field of search in accordance with changes in the at least one access metric.

In accordance with a preferred embodiment of the present invention the method for managing data in an enterprise by identifying data of interest from among a multiplicity of data elements in an enterprise also includes noting the current status of data elements that have been modified, added or removed in accordance with changes in the at least one access metric.

Preferably, the searching is prioritized at least in accordance with at least one access metric related prioritization characteristic. Additionally, results of the searching are ordered at least in accordance with at least one access metric related prioritization characteristic.

In accordance with a preferred embodiment of the present invention the selecting the data of interest by considering only data elements which have the at least one non-content based data identifier thereof and the at least one access metric thereof from among the multiplicity of data elements includes searching for data elements which have the at least one non-content based data identifier thereof, separately from the searching for data elements which have the at least one non-content based data identifier thereof, identifying data elements from among the multiplicity of data elements in accordance with the at least one access metric and combining results of the searching and the identifying. In accordance with a preferred embodiment of the present invention, the searching and the identifying are performed by separate entities.

Preferably, the method for managing data in an enterprise by identifying data of interest from among a multiplicity of data elements in an enterprise also includes maintaining an access metrics database. In accordance with a preferred embodiment of the present invention the method for managing data in an enterprise by identifying data of interest from among a multiplicity of data elements in an enterprise also includes maintaining a metadata database.

Preferably, the method for managing data in an enterprise by identifying data of interest from among a multiplicity of data elements in an enterprise also includes, responsive to the identification of data elements of interest, modification of access permissions to at least one of the data elements of interest.

There is also provided in accordance with another preferred embodiment of the present invention a system for managing data in an enterprise by identifying data of interest from among a multiplicity of data elements in an enterprise, the system including query generation functionality operable for characterizing data of interest at least by at least one non-content based data identifier thereof and at least one access metric thereof the at least one access metric being selected from data access permissions and actual data access history and query resolution functionality operable for selecting data of interest by considering only data elements from among the multiplicity of data elements which have the at least one non-content based data identifier thereof and the at least one access metric thereof.

Preferably, the query generation functionality is also operable for characterizing data of interest by at least one content based data identifier thereof and the query resolution functionality is also operable for selecting data of interest by considering only data elements which have the at least one content based data identifier thereof.

In accordance with a preferred embodiment of the present invention the considering includes defining a field of search in accordance with the at least one access metric and searching within the field of search based on the at least one non-content based data identifier. Alternatively, the considering includes defining a field of search in accordance with the at least one access metric multiple times and searching within the field of search multiple times, wherein the at least one access metric is different at least some of the multiple times.

Preferably, the at least one access metric is a dynamic metric which changes over time during operation of the enterprise.

In accordance with a preferred embodiment of the present invention the considering also includes automatically redefining the field of search in accordance with the at least one access metric multiple times and searching within the field of search multiple times, wherein the at least one access metric is different at least some of the multiple times. Additionally, the searching includes searching only within those portions of the field of search that have been modified or added as the result of redefining the field of search in accordance with changes in the at least one access metric.

Preferably, the searching includes noting the current status of data elements that have been modified, added or removed in accordance with changes in the at least one access metric. In accordance with a preferred embodiment of the present invention the searching is prioritized at least in accordance with at least one access metric related prioritization characteristic. Additionally, results of the searching are ordered at least in accordance with at least one access metric related prioritization characteristic.

Preferably, the query resolution functionality is also operable for searching for data elements which have the at least one non-content based data identifier thereof, separately from the searching for data elements which have the at least one non-content based data identifier thereof, identifying data elements from among the multiplicity of data elements in accordance with the at least one access metric and combining results of the searching and the identifying. In accordance with a preferred embodiment of the present invention the searching and the identifying are performed by separate entities.

In accordance with a preferred embodiment of the present invention the system for managing data in an enterprise by identifying data of interest from among a multiplicity of data elements in an enterprise also includes access metrics collection functionality and an access metrics database.

Preferably, the system for managing data in an enterprise by identifying data of interest from among a multiplicity of data elements in an enterprise also includes metadata collection functionality and a metadata database.

In accordance with a preferred embodiment of the present invention the system for managing data in an enterprise by identifying data of interest from among a multiplicity of data elements in an enterprise also includes access permissions modification functionality which is operative, responsive to the identification of data elements of interest, to modify access permissions to at least one of the data elements of interest.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be understood and appreciated more fully from the following detailed description, taken in conjunction with the drawings in which:

FIG. 1 is a simplified pictorial illustration of an example of the operation of a data classification system constructed and operative in accordance with a preferred embodiment of the present invention;

FIG. 2 is a simplified pictorial illustration of another example of the operation of a data classification system;

FIG. 3 is a simplified flowchart indicating steps in the operation of the data classification system of FIGS. 1 & 2; and

FIG. 4 is a simplified block diagram illustration of the data classification system of FIGS. 1-3.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Reference is now made to FIG. 1, which is a simplified pictorial illustration of one example of the operation of a data classification system constructed and operative in accordance with a preferred embodiment of the present invention. The data classification system of FIG. 1 is preferably suitable for operating in an enterprise computer network including multiple disparate clients, data elements, computer hardware resources and computer software resources, and preferably includes data characterization functionality and data selection functionality operative to characterize and select data based on content and non-content based data identifiers and on access metrics.

The operation of the data classification system preferably includes characterizing data of interest at least by at least one non-content based data identifier thereof and at least one access metric thereof, the at least one access metric being selected from data access permissions and actual data access history, and selecting data of interest by considering only data elements from among the multiplicity of data elements which have the at least one non-content based data identifier thereof and the at least one access metric thereof.

The term “non-content based data identifier” is used throughout to refer to metadata associated with a data element. The metadata may include any data element characteristic associated with the data element such as, for example, file type, author, category and language. It is appreciated that the metadata may be predefined characteristics provided by the system which hosts the data elements or user-defined characteristics. It is appreciated that metadata may be manually associated with a data element without having to actually access or modify the content of the data element.

As shown in FIG. 1, the data classification system typically resides on a server 100 which is connected to an enterprise computer network 102 which preferably includes multiple disparate clients 104, servers 106 and data storage resources 108. Typically, data elements such as computer files reside on servers 106 and data storage resources 108 and are accessible to users of network 102 in accordance with access permissions defined by an owner of each data element or each data element folder. It is appreciated that the data elements may reside on any suitable data storage system or platform, such as a file system or a data collaboration system, which may reside on any suitable computer operating system or infrastructure.

Preferably, the system maintains a database of actual access and access permissions of every user to every data element in the enterprise. This functionality is described in U.S. Pat. No. 7,606,801, in U.S. Published Patent Application 2009/0265780 and in U.S. patent application Ser. No. 12/673,691 owned by assignee, the disclosures of which are hereby incorporated by reference. Access permissions and/or actual access are together designated as access metrics and may be used to designate subsets of all of the data elements in the enterprise.

Preferably, the system also crawls over at least a subset of all data elements in the enterprise and maintains a database of metadata associated with each data element of the subset of data elements.

As seen in FIG. 1, on a particular day, such as on Mar. 10, 2008, an IT Security Manager of an enterprise network decides to assign values to metadata fields associated with at least some of the files on the network. For example, the IT Security Manager may choose to assign values to the predefined ‘author’ field and ‘category’ field. It is appreciated that metadata may be assigned to individual files at the time of file creation or at any other time thereafter.

At a later date, such as on Jan. 10, 2011, the HR Manager of the enterprise decides to terminate the employment of John, an enterprise employee, and to give John thirty days notice before the termination will take effect.

In accordance with company policy, the IT Security Manager immediately queries the system in order to ascertain to which of the files having the predefined ‘category’ metadata field set to “legal” John has access permissions. Preferably, the IT Security Manager receives a response from the system to his query in near real time, whereby the response includes a list of legal files to which John has access permissions. The IT Security Manager may then restrict John's access permissions to the legal files, in anticipation of John's termination of employment.

It is appreciated that maintenance by the system of a database of actual access and access permissions of every user to every data element in the enterprise and of a database of metadata associated with each of the data elements in the enterprise is operative to enable the system to provide near real time responses to queries to the system.

Reference is now made to FIG. 2, which is a simplified pictorial illustration of another example of the operation of a data classification system. The data classification system of FIG. 2 is preferably suitable for operating in an enterprise computer network including multiple disparate clients, data elements, computer hardware resources and computer software resources, and preferably includes data characterization functionality and data selection functionality operative to characterize and select data based on content and non-content based data identifiers and on access metrics.

The operation of the data classification system preferably includes characterizing the data of interest at least by at least one non-content based data identifier thereof and at least one access metric thereof, the at least one access metric being selected from data access permissions and actual data access history, and selecting the data of interest by considering only data elements which have the at least one non-content based data identifier thereof and the at least one access metric thereof from among the multiplicity of data elements.

As shown in FIG. 2, the data classification system typically resides on a server 200 which is connected to an enterprise computer network 202 which preferably includes multiple disparate clients 204, servers 206 and data storage resources 208. Typically, data elements such as computer files reside on servers 206 and data storage resources 208 and are accessible to users of network 202 in accordance with access permissions defined by an owner of each data element or each data element folder. It is appreciated that the data elements may reside on any suitable data storage system or platform, such as a file system or a data collaboration system, which may reside on any suitable computer operating system or infrastructure.

Preferably, the system maintains a database of actual access and access permissions of every user to every data element in the enterprise. This functionality is described in U.S. Pat. No. 7,606,801, in U.S. Published Patent Application 2009/0265780 and in U.S. patent application Ser. No. 12/673,691 owned by assignee, the disclosures of which are hereby incorporated by reference. Access permissions and/or actual access are together designated as access metrics and may be used to designate subsets of all of the data elements in the enterprise.

Preferably, the system also crawls over at least a subset of all data elements in the enterprise and maintains a database of metadata associated with each data element of the subset of data elements.

As seen in FIG. 2, on a particular day, such as on Mar. 10, 2008, an IT Security Manager of an enterprise network decides to assign values to metadata fields associated with at least some of the files on the network. For example, the IT Security Manager may choose to assign values to the predefined ‘author’ field and ‘category’ field. Additionally, the IT Security Manager decides to define a new ‘customer profile’ metadata field for all sales related files. It is appreciated that metadata may be assigned to individual files at the time of file creation or at any other time thereafter.

At a later date, such as on Jan. 10, 2011, the HR Manager of the enterprise decides to terminate the employment of Mark, an enterprise employee, and to give Mark thirty days notice before the termination will take effect.

In accordance with company policy, the IT Security Manager immediately queries the system in order to ascertain to which of the files having the predefined ‘category’ metadata field set to “sales” and having the user-defined ‘customer profile’ field set to “high” Mark has access permissions. Preferably, the IT Security Manager receives a response from the system to his query in near real time, whereby the response includes a list of high-profile customer sales-related files to which Mark has access permissions. The IT Security Manager may then restrict Mark's access permissions to the high-profile customer sales-related files, in anticipation of Mark's termination of employment.

It is appreciated that maintenance by the system of a database of actual access and access permissions of every user to every data element in the enterprise and of a database of metadata associated with each of the data elements in the enterprise is operative to enable the system to provide near real time responses to queries to the system.

Reference is now made to FIG. 3, which is a simplified flowchart indicating steps in the operation of the data classification system of FIGS. 1 & 2. As shown in FIG. 3, the system preferably maintains a database of access metrics which include actual access and access permissions of every user to every data element in the enterprise (300). The system also preferably crawls over at least a subset of all data elements in the enterprise and maintains a database of metadata associated with each of the subset of data elements (302).

As shown in FIG. 3, a user of the data classification system composes a file search query to be submitted to the system (304). The search query preferably comprises a request for a list of files having at least one search access metric and at least one search non-content based data identifier associated therewith. The user then submits the query to the system (306). It is appreciated that the search query may be redefined in accordance with the at least one access metric multiple times and executed multiple times, wherein the at least one access metric is different at least some of the multiple times.

Upon receiving the search query from the user, the system utilizes the database of access metrics and the database of metadata to provide to the user a search report which comprises a list of files having the at least one search access metric and the at least one search non-content based data identifier associated therewith (308).

Reference is now made to FIG. 4, which is a simplified block diagram illustration of the data classification system of FIGS. 1-3. As shown in FIG. 4, the system 400 comprises access metrics collection functionality 402 and metadata collection functionality 404. As described hereinabove regarding FIGS. 1-3, access metrics collection functionality 402 preferably stores access metrics in an access metrics database 406 and metadata collection functionality 404 preferably stores file metadata in metadata database 408.

It is appreciated that the system continuously maintains a database of actual access and access permissions of every user to every data element in the enterprise. This functionality is described in U.S. Pat. No. 7,606,801, in U.S. Published Patent Application 2009/0265780 and in U.S. patent application Ser. No. 12/673,691 owned by assignee, the disclosures of which are hereby incorporated by reference. Access permissions and/or actual access are together designated as access metrics and may be used to designate subsets of all of the data elements in the enterprise.

Query generation functionality 410 is preferably provided to allow a user to compose a file search query to be submitted to query resolution functionality 412. As shown in FIG. 4, query resolution functionality 412 is operative to utilize access metrics database 406 and metadata database 408 to execute the file search query and to provide the user with the resulting search report in near real time.

It will be appreciated by persons skilled in the art that the present invention is not limited by what has been particularly shown and described hereinabove. Rather, the invention also includes various combinations and subcombinations of the features described hereinabove as well as modifications and variations thereof, which would occur to persons skilled in the art upon reading the foregoing and which are not in the prior art.

Claims

1. A method for managing data elements in an enterprise file system, said data elements being characterized at least by metadata thereof and by at least one access metric thereof, said at least one access metric including actual access, the method comprising: specifying, by a first human operator, specific metadata and at least one specific access metric to identify data elements of interest from among a multiplicity of said data elements in said enterprise file system; classifying said data elements of interest by considering data elements in said enterprise file system which have said specific metadata and said at least one specific access metric, said at least one specific access metric comprising actual access including at least one of reading, writing, opening, creating and removing said data elements, said classifying including: searching for data elements which have said specific metadata;separately from said searching for data elements which have said specific metadata, identifying data elements from among said multiplicity of data elements in accordance with said at least one specific access metric comprising said actual access; andcombining results of said searching and said identifying; andresponsive to said classifying said data elements of interest, modifying, by a second human operator, access permissions to at least one of said data elements of interest.

2. The method for managing data elements in an enterprise file system according to claim 1 and also comprising: specifying, by said operator, at least one specific content based data identifier; and whereinsaid classifying said data elements of interest includes considering only data elements which have said at least one specific content based data identifier.

3. The method for managing data elements in an enterprise file system according to claim 1 and wherein said considering comprises: defining a field of search in accordance with said at least one specific access metric multiple times and searching within said field of search multiple times, wherein said at least one specific access metric is different at least some of said multiple times.

4. The method for managing data elements in an enterprise file system according to claim 1 and wherein said at least one specific access metric is a dynamic metric which changes over time during operation of the enterprise.

5. The method for managing data elements in an enterprise file system according to claim 1 and wherein said searching comprises searching only within those portions of said field of search that have been modified or added as the result of redefining said field of search in accordance with changes in said at least one specific access metric.

6. The method for managing data elements in an enterprise file system according to claim 1 and also comprising noting the current status of data elements that have been modified, added or removed in accordance with changes in said at least one specific access metric.

7. The method for managing data elements in an enterprise file system according to claim 1 and wherein said searching is prioritized at least in accordance with at least one specific access metric related prioritization characteristic.

8. The method for managing data elements in an enterprise file system according to claim 7 and wherein results of said searching are ordered at least in accordance with at least one specific access metric related prioritization characteristic.

9. The method for managing data elements in an enterprise file system according to claim 1 and wherein said searching and said identifying are performed by separate entities.

10. The method for managing data elements in an enterprise file system according to claim 1 and also comprising maintaining an access metrics database.

11. The method for managing data elements in an enterprise file system according to claim 1 and also comprising maintaining a metadata database.

12. The method for managing data elements in an enterprise file system according to claim 1 and also comprising automatically redefining said field of search in accordance with said at least one specific access metric multiple times and searching within said field of search multiple times, wherein said at least one specific access metric is different at least some of said multiple times.

13. A system for managing data elements in an enterprise file system, said data elements being characterized at least by metadata thereof and by at least one access metric thereof, said at least one access metric including actual access, the system comprising: a computer including: a processor;a memory; anda non-transitory, tangible computer-readable medium in which computer program instructions are stored, which instructions, when read by said computer, cause the computer to enable efficient management of data in said enterprise;query generation functionality operable for facilitating specifying, by a first human operator, specific metadata and at least one specific access metric to identify data elements of interest from among a multiplicity of said data elements in said enterprise file system;query resolution functionality operable for classifying said data elements of interest by considering data elements in said enterprise file system which have said specific metadata and said at least one specific access metric, said at least one specific access metric comprising actual access including at least one of reading, writing, opening, creating and removing said data elements, said classifying including: searching for data elements which have said specific metadata;separately from said searching for data elements which have said specific metadata, identifying data elements from among said multiplicity of data elements in accordance with said at least one specific access metric comprising said actual access; andcombining results of said searching and said identifying; andaccess permissions modification functionality operable, responsive to said classifying data elements of interest, for modifying, responsive to receiving an instruction from a second human operator, access permissions to at least one of said data elements of interest.

14. The system for managing data elements in an enterprise file system, said data elements being characterized at least by metadata thereof and by at least one access metric thereof according to claim 13 and wherein: said query generation functionality is also operable for facilitating specifying, by said operator, at least one specific content based data identifier; andsaid query resolution functionality is also operable for classifying data elements of interest by considering data elements which have said at least one content based data identifier.

15. The system for managing data elements in an enterprise file system, said data elements being characterized at least by metadata thereof and by at least one access metric thereof according to claim 13 and wherein said considering comprises: defining a field of search in accordance with said at least one access metric multiple times and searching within said field of search multiple times, wherein said at least one specific access metric is different at least some of said multiple times.

16. The system for managing data elements in an enterprise file system, said data elements being characterized at least by metadata thereof and by at least one access metric thereof according to claim 13 and wherein said at least one specific access metric is a dynamic metric which changes over time during operation of the enterprise.

17. The system for managing data elements in an enterprise file system, said data elements being characterized at least by metadata thereof and by at least one access metric thereof according to claim 13 and wherein said searching comprises searching only within those portions of said field of search that have been modified or added as the result of redefining said field of search in accordance with changes in said at least one specific access metric.

18. The system for managing data elements in an enterprise file system, said data elements being characterized at least by metadata thereof and by at least one access metric thereof according to claim 13 and wherein said searching comprises noting the current status of data elements that have been modified, added or removed in accordance with changes in said at least one specific access metric.

19. The system for managing data elements in an enterprise file system, said data elements being characterized at least by metadata thereof and by at least one access metric thereof according to claim 13 and wherein said searching is prioritized at least in accordance with at least one specific access metric related prioritization characteristic.

20. The system for managing data elements in an enterprise file system, said data elements being characterized at least by metadata thereof and by at least one access metric thereof according to claim 19 and wherein results of said searching are ordered at least in accordance with at least one specific access metric related prioritization characteristic.

21. The system for managing data elements in an enterprise file system, said data elements being characterized at least by metadata thereof and by at least one access metric thereof according to claim 13 and wherein said searching and said identifying are performed by separate entities.

22. The system for managing data elements in an enterprise file system, said data elements being characterized at least by metadata thereof and by at least one access metric thereof according to claim 13 and also comprising access metrics collection functionality and an access metrics database.

23. The system for managing data elements in an enterprise file system, said data elements being characterized at least by metadata thereof and by at least one access metric thereof according to claim 13 and also comprising metadata collection functionality and a metadata database.

24. The system for managing data elements in an enterprise file system according to claim 13 and wherein said query generation functionality is also operable for automatically redefining said field of search in accordance with said at least one specific access metric multiple times and searching within said field of search multiple times, wherein said at least one specific access metric is different at least some of said multiple times.