METADATA-BASED ACCESS, SECURITY, AND COMPLIANCE CONTROL OF SOFTWARE GENERATED FILES
In embodiments of the present invention improved capabilities are described for an extensible, file-based, security system that may be used for recording, analyzing, storing, updating and evaluating metadata, such as file reputation metadata, in order to determine an appropriate access control or security control measure to implement in association with a file. In response to the generation of a file from a software program, metadata that defines access, security, and compliance reporting parameters of the generated file may be created that conform to and/or implement a corporate policy. The metadata may be used to control the access, security, and/or compliance reporting settings of the file and to require that only an approved method of using the file, or any of the file's contents, is used, and that the method and use of the file is in accord with the access, security, and/or compliance reporting parameter definitions in the metadata which embody the corporate policy.
1 . A computer program product embodied in a computer readable medium that, when executing on one or more computers, performs the steps of:
a. In response to generation of a file from a software program, automatically generating metadata that defines access parameters of the file in accordance with a corporate policy and a user's input; and
b. Appending the metadata to the file, the metadata controlling access of the file such that only approved method of gaining access to the file or any of the file's contents is to meet the access parameters definitions in the metadata.
2 . A computer program product embodied in a computer readable medium that, when executing on one or more computers, performs the steps of:
a. In response to generation of a file from a software program, automatically generating metadata that defines security parameters of the file in accordance with a corporate policy and a user's input; and
b. Appending the metadata to the file, the metadata controlling security of the file such that only approved method of using the file or any of the file's contents is to meet the security parameters definitions in the metadata.
3 . A computer program product embodied in a computer readable medium that, when executing on one or more computers, performs the steps of:
a. In response to generation of a file from a software program, automatically generating metadata that defines compliance reporting parameters of the file in accordance with a corporate policy and a user's input; and
b. Appending the metadata to the file, the metadata controlling compliance reporting associated with the file such that only approved method of compliance reporting relating to the use of the file or any of the file's contents is to meet the compliance reporting parameters definitions in the metadata.
4 . The method of claim 3 , wherein the compliance reporting includes, at least in part, audit tracking.
5 . The method of claim 4 , wherein the audit tracking includes, at least in part, auditing access of a file.
6 . A computer program product embodied in a computer readable medium that, when executing on one or more computers, performs the steps of:
a. In response to generation of a file from a software program, automatically generating metadata that defines access, security, and compliance reporting parameters of the file in accordance with a corporate policy and a user's input; and
b. Appending the metadata to the file, the metadata controlling access, security, and compliance reporting of the file such that only approved method of using the file or any of the file's contents is to meet the access, security, and compliance reporting parameters definitions in the metadata.
7 . The method of claim 6 , wherein the step of automatically generating metadata in accordance with the corporate policy involves automatically categorizing the file as a type of file based on a software application type that produced the file and generating metadata in accordance with how the policy dictates how such file types should be treated.
8 . The method of claim 7 , wherein the type of file is an accounting file.
9 . The method of claim 7 , wherein the type of file is an engineering file.
10 . The method of claim 7 , wherein the type of file is a marketing file.
11 . The method of claim 7 , wherein the type of file is a confidential file.
12 . The method of claim 7 , wherein the type of file is a non-confidential file.
13 . The method of claim 7 , wherein the type of file is an Internet file.
14 . The method of claim 7 , wherein the type of file is an Intranet file.
15 . The method of claim 6 , wherein the step of automatically generating metadata in accordance with the user's input involves soliciting input from the user.
16 . The method of claim 6 , wherein the step of automatically generating the metadata in accordance with the user's input involves assessing the user's input based on the file's storage location.
17 . The method of claim 6 , wherein the step of appending the metadata to the file, comprises associating the metadata with the file and storing the metadata separately from the file.
18 . The method of claim 6 , wherein the metadata defines access and security parameters of individual components within the file.
19 . The method of claim 6 , wherein the step of automatically generating the metadata further involves scanning the contents of the file to determine a file type and then producing metadata in accordance with how the policy dictates how such file types should be treated.
20 . The method of claim 6 , wherein the step of automatically generating the metadata further involves scanning the contents of the file to determine what sections are included within the file, determining the types of data in each section, and developing metadata for each section; and wherein the step of controlling access and security involves controlling access and security to each section.
21 . The method of claim 6 , wherein the metadata is a reputation datum.
22 . The method of claim 21 , wherein the reputation datum relates to a file format.
23 . The method of claim 21 , wherein the reputation datum relates to an originating location of the file.
24 . The method of claim 23 , wherein the originating location is an Internet URL.
25 . The method of claim 23 , wherein the originating location is an intranet.
26 . The method of claim 23 , wherein the originating location is a server address.
27 . The method of claim 23 , wherein the originating location is an IP address.
28 . The method of claim 23 , wherein the originating location is a CPU.
29 . The method of claim 23 , wherein the originating location is a plurality of locations.
30 . The method of claim 29 , wherein the plurality of locations are prior locations in which the received file has been located.
31 . The method of claim 21 , wherein the reputation datum relates to an application that is used to open the file.