METHOD AND APPARATUS FOR FILE ASSURANCE

• US 20120317145A1
• Filed: 06/08/2012
• Published: 12/13/2012
• Est. Priority Date: 06/10/2011
• Status: Abandoned Application

• Current Assignee: M.E.P. Cad, Incorporated
• Original Assignee: M.E.P. Cad, Incorporated
• Inventors: Reghetti, Joseph P., Conte, Anthony M.
• Application Number:
  US13/492,689
• Publication Number:
  US 20120317145A1
• Time in Patent Office: Days
• US Class Current: 707/781
• CPC Class Codes: G06F 21/6209 to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself

Abstract

A system and associated processes for file assurance. A user may use the system to maintain control over a file that is distributed to another user. The user may specify a number of file access options, such as read-only, report distribution, or track edits. The system may encrypt the file with the file access options included. The file may be altered so as to make the file no longer readable by an application designed to read the file without the system, or a corresponding system associated with the recipient user. The system or corresponding system may enforce the file access options selected by the user. Further, in some embodiments, the system may report the occurrence of file access or the performance of specific operations on the file to the user.

Claims

1. A system for facilitating file assurance, the system comprising:

a data inserter configured to insert data into a native file to create a modified native file, wherein an application associated with the native file may read the native file and is unable to read the modified native file;

a tracker configured to access tracking information associated with a secure file;

a file access module configured to associate one or more file access restrictions that restrict access to the secure file;

a secure file creator configured to create the secure file based, at least in part, on the modified native file, the tracking information, and the one or more file access restrictions; and

a file distributor configured to distribute the secure file to a computing system.

2. The system as recited in claim 1, wherein the data inserted into the native file to create a modified native file is based on the application.

3. The system as recited in claim 2, wherein the data inserted into the native file is based on a file type associated with the native file.

4. The system as recited in claim 1, wherein the data inserted into the native file to create a modified native file is based on a file type associated with the native file.

5. The system as recited in claim 1, wherein the data includes one or more special characters having one or more insertion points within the modified native file based on an insertion factor.

6. The system as recited in claim 5, wherein the insertion factor is based on one or more of a size of the native file, a date, a time, a random number and a pseudo-random number.

7. The system as recited in claim 5, wherein the insertion factor is based on a globally or universally unique identifier value.

8. The system as recited in claim 5, wherein the one or more insertion points are based on one or more of a size of the native file and the insertion factor.

9. The system as recited in claim 5, wherein the one or more insertion points are in content of the modified native file, a header of the modified native file or both the content of the modified native file and the header of the modified native file.

10. The system as recited in claim 1, further comprising a file compressor for compressing the native file prior to creation of the modified native file.

11. The system as recited in claim 1, further comprising a file compressor for compressing the modified native file.

12. A system for facilitating file assurance, the system comprising:

a file access control system configured to receive a secure file from a first user and to regulate a second user'"'"'s access to the secure file, the file access control system comprising;

a native file extractor configured to extract a native file from the secure file;

a file access module configured to restrict the second user'"'"'s access to the native file based on a set of file access restrictions associated with the secure file and to access the native file when authorized by the file access restrictions using an application associated with the native file; and

a tracker configured to provide an alert the first user in response to the second user accessing the secure file or the native file.

13. The system as recited in claim 12, wherein the file access restrictions include one or more file access actions of viewing, opening, editing, altering, moving, transferring, sharing, appending data to, printing, imaging, copying the native file.

14. The system as recited in claim 13, wherein the alerts are provided in response to at least one but not all of the one or more file access actions.

15. The system as recited in claim 14, further comprising a tracking repository for storing at least the file access restrictions, the file access actions, and the alerts.

16. The system as recited in claim 12, wherein the secure file includes a modified native file that includes one or more special characters inserted within the modified native file that render the modified native file unreadable by an application associated with the native file, and wherein the native file extractor is configured to remove the one or more special characters to extract the native file.

17. A method for facilitating file assurance, comprising the steps of:

receiving a native file;

receiving one or more file access restrictions;

receiving one or more tracking options;

creating an inaccessible native file by rendering the native file inaccessible to an application associated with the native file;

generating a composite file based on the inaccessible native file, the one or more tracking options, and the one or more file access restrictions; and

encrypting the composite file.

18. The method as recited in claim 17, further comprising the step of compressing the inaccessible native file prior to generating the composite file.

19. The method as recited in claim 17, further comprising the step of compressing the composite file prior to encrypting the composite file.

20. The method as recited in claim 17, wherein the step of creating an inaccessible native file includes the step of inserting data into the native file that results in the inaccessible native file being unreadable by the application.

21. The method as recited in claim 20, wherein the data inserted into the native file is based on the application.

22. The method as recited in claim 21, wherein the data inserted into the native file is based on a file type associated with the native file.

23. The method as recited in claim 20, wherein the data includes one or more special characters and wherein the one or more special characters are inserted at one or more insertion points based on an insertion factor.

24. The method as recited in claim 23, wherein the insertion factor is based on one or more of a size of the native file, a date, a time, a random number and a pseudo-random number.

25. The method as recited in claim 23, wherein the insertion factor is based on a globally or universally unique identifier value.

26. The method as recited in claim 23, wherein the one or more insertion points are based on one or more of a size of the native file and the insertion factor.

27. A method for facilitating file assurance, comprising the steps of:

receiving a secure file;

decrypting the secure file to create a composite file;

accessing a set of tracking restrictions associated with the composite file;

alerting a first user of access by a second user of the composite file based, at least in part, on the set of tracking restrictions;

receiving a file access command from the second user;

accessing a set of file access restrictions associated with the composite file;

determining if the file access command is permitted based on the set of file access restrictions;

rejecting the file access command if the file access command is not permitted; and

extracting a modified native file from the secure file if the file access command is permitted, wherein the modified native file is based on a native file configured to be read by an application, and wherein the modified native file is unreadable by the application;

converting the modified native file to a readable native file capable of being read by the application; and

executing the file access command on the readable native file using the application.

28. The method as recited in claim 27, wherein the set of tracking restrictions are contained within the composite file.

29. The method as recited in claim 27, wherein the set of file access restrictions are contained within the composite file.

30. The method as recited in claim 27, wherein the step of accessing the set of tracking restrictions includes the step of obtaining the set of tracking restrictions from a server through a network connection.

31. The method as recited in claim 27, wherein the step of accessing the set of file access restrictions includes the step of obtaining the set of file access restrictions from a server through a network connection.

32. The method as recited in claim 27, wherein the step of converting the modified native file to the readable native file includes the step of removing data inserted into the native file, wherein the data inserted into the native file made the modified native file unreadable by the application.

33. The method as recited in claim 32, wherein the data inserted into the native file includes one or more special characters, and wherein the step of removing data includes the step of removing the one or more special characters from one or more insertion points in the native file.

34. The method as recited in claim 33, wherein the one or more insertion points are identified based on an insertion factor.

35. The method as recited in claim 34, wherein the insertion factor is contained in the composite file.

36. The method as recited in claim 34, wherein the insertion factor is obtained from a server through a network connection.

37. A method for facilitating file assurance, comprising the steps of:

receiving a secure file including a native file from a first user;

receiving an access request from a second user to access the secure file;

alerting the first user of the access request by the second user;

determining if the access request is permitted based on a set of file access restrictions associated with the secure file; and

if the file access command is permitted;

extracting a copy of the native file from the secure file without opening or modifying the native file with an application for accessing the native file; and

executing a file access command on the copy of the native file using the application.

38. The method as recited in claim 37, wherein the step of extracting a copy of the native file includes the steps of:

extracting a modified native file from the secure file, wherein the modified native file is unreadable by the application;

converting the modified native file to the copy of the native file by removing data inserted into the modified native file, wherein the data inserted into the modified native file made the modified native file unreadable by the application.

39. The method as recited in claim 38, wherein the data inserted into the native file includes one or more special characters, and wherein the step of removing data includes the step of removing the one or more special characters from one or more insertion points in the native file.

40. The method as recited in claim 39, wherein the one or more insertion points are identified based on an insertion factor.