Systems and methods for identifying data files based on community data

1. A computer-implemented method for using community data to automatically generate rules for identifying files that are suitable for being stored within virtualization layers, at least a portion of the method being performed by a server comprising at least one processor, the method comprising:

receiving file metadata from a plurality of client devices within a community, wherein the file metadata identifies characteristics of files stored on the plurality of client devices;

automatically determining, by analyzing the file metadata received from the plurality of client devices within the community, that a file having a specific file name is frequently present on client devices of users of a specific application within the community;

concluding, based at least in part on the determination, that the file represents a non-data file suitable for being stored within virtualization layers;

automatically generating a rule that:

comprises criteria for identifying the file;

specifies that the file is suitable for being stored within virtualization layers;

providing the rule to at least one of the plurality of client devices within the community to enable the client device to determine that the file is suitable for being stored within a virtualization layer on the client device.

2. The method of claim 1 , further comprising at least one of:

determining that the file is substantially always stored in a location known to be associated with non-data files;

identifying a file extension of the file and determining that file names of files of the file extension do not frequently vary within the community;

determining that the file is frequently present in a specific relative location on client devices of users of the specific application within the community;

determining that the file is widespread within the community;

determining that the file is not shared by users within the community.

3. The method of claim 2 , further comprising assigning weight values to at least one of the determinations.

4. The method of claim 1 , wherein the file metadata comprises data that identifies, for at least one file, at least one of:

the file's name;

the file's pathname;

the file's extension;

the file's creation date;

the file's last-modified date;

a hash of the file;

the number of times the file has been read;

the number of times the file has been modified;

at least one application that has accessed the file;

a list of applications installed on a client device where the file resides;

usage behavior for the file.

5. A computer-implemented method for identifying files that are suitable for being stored within virtualization layers, at least a portion of the method being performed by a client device comprising at least one processor, the method comprising:

identifying a file;

accessing file metadata associated with the file;

accessing a rule that:

comprises criteria for identifying the file based on the file metadata associated with the file;

specifies that the file is suitable for being stored within virtualization layers;

wherein the rule is automatically generated by determining, by analyzing file metadata that identifies characteristics of files stored on a plurality of client devices within a community, that the file is frequently present on client devices of users of a specific application within the community;

determining, by applying the rule to the file metadata associated with the file, that the file is suitable for being stored within a virtualization layer on the client device;

in response to the determination, storing the file within the virtualization layer on the client device.

6. The method of claim 5 , wherein accessing the file metadata associated with the file comprises:

accessing file metadata stored within the file;

accessing file metadata stored outside of the file.

7. The method of claim 5 , wherein accessing the rule comprises:

retrieving the rule from a local storage device;

retrieving the rule from a remote storage device.

8. The method of claim 5 , further comprising determining whether to perform a security operation on the file.

9. The method of claim 5 , wherein the criteria comprises at least one of:

criteria for determining whether the file is of a specific file extension;

criteria for determining whether the file is stored in a specific location;

criteria for determining whether the file has a specific file name;

criteria for determining whether a hash of the file matches a specific file hash.

10. The method of claim 9 , wherein the rule contains a weight value assigned to at least one of the criteria.

11. The method of claim 5 , wherein the file metadata received from the plurality of client devices comprises data that identifies, for at least one file, at least one of:

the file's name;

the file's pathname;

the file's extension;

the file's creation date;

the file's last-modified date;

a hash of the file;

the number of times the file has been read;

the number of times the file has been modified;

at least one application that has accessed the file;

a list of applications installed on a client device where the file resides;

usage behavior for the file.

12. A system for automatically generating rules for identifying files that are suitable for being stored within virtualization layers based on community data, the system comprising:

a communication module programmed to receive file metadata from a plurality of client devices within a community, wherein the file metadata identifies characteristics of files stored on the plurality of client devices;

a criteria-identification module programmed to:

automatically determine, by analyzing the file metadata received from the plurality of client devices within the community, that a file having a specific file name is frequently present on client devices of users of a specific application within the community;

conclude, based at least in part on the determination, that the file represents a non-data file suitable for being stored within virtualization layers;

a rule-generation module programmed to automatically generate a rule that:

comprises criteria for identifying the file;

specifies that the file is suitable for being stored within virtualization layers;

wherein the communication module is further programmed to provide the rule to at least one of the plurality of client devices within the community to enable the client device to determine that the file is suitable for being stored within a virtualization layer on the client device;

at least one processor configured to execute at least one of the communication module, the criteria-identification module, and the rule-generation module.

13. The system of claim 12 , wherein the criteria-identification module is further programmed to at least one of:

determine that the file is substantially always stored in a location known to be associated with non-data files;

identify a file extension of the file and determine that file names of files of the file extension do not frequently vary within the community;

determine that the file is frequently present in a specific relative location on client devices of users of the specific application within the community;

determine that the file is widespread within the community;

determine that the file is not shared by users within the community.

14. The system of claim 13 , wherein the criteria-identification module is further programmed to assign weight values to at least one of the determinations.

15. The system of claim 12 , wherein the file metadata received from the plurality of client devices comprises data that identifies, for at least one file, at least one of:

the file's name;

the file's pathname;

the file's extension;

the file's creation date;

the file's last-modified date;

a hash of the file;

the number of times the file has been read;

the number of times the file has been modified;

at least one application that has accessed the file;

a list of applications installed on a client device where the file resides;

usage behavior for the file.