IP Library Granted Patent US 6,986,058
Granted Patent B1
US 6,986,058 · App. 09/701,154 · Granted Jan 10, 2006

Method and system for providing data security using file spoofing

Assignee: Infraworks Corporation
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 6,986,058
App. No.
09/701,154
Granted
Jan 10, 2006
Kind
B1
Abstract

A method for providing data security in a device driver for accessing data. The device driver detects a file system request, completes the file system request, and receives return information from the file system request. The device driver further determines whether the file system request is for a tag file associated with a secured file; and if so, modifies the return information to reflect a file attribute of the secured file.

Claims (69)

1. A method for providing data security in a device driver for accessing data, the method comprising the steps of:

providing at least one tag file, the tag file comprising a physical file of zero bytes in length;

maintaining the tag file in a part of a file system; and processing file system calls so that the tag file appears as a secured file containing data from the viewpoint of a user, operating system and programs, the method further comprising the steps of:

detecting a file system request;

completing said file system request;

receiving return information from said file system request;

determining whether said file system request is for a tag file associated with a secured file; and

if so, modifying said return information to reflect a file attribute of the secured file.

2. The method of claim 1 wherein said file attribute is file size.

3. The method of claim 1 wherein the step of determining further comprises the steps of:

determining whether said return information identifies a plurality of tag files associated with a plurality of secured files; and

if so, modifying said return information to reflect a file attribute of the plurality of secured files.

4. The method of claim 1 wherein the secured file is stored in encrypted form.

5. The method of claim 1 wherein the secured file is stored in a secure virtual file system.

6. The method of claim 1 wherein the secured file is stored on a remote networked device.

7. The method of claim 1 wherein the file system request is to open a file.

8. The method of claim 1 wherein the file system request is to delete a file.

9. The method of claim 1 wherein the file system request is to rename a file.

10. The method of claim 1 wherein the file system request is to query file information.

11. The method of claim 1 wherein the file system request is to set file information.

12. The method of claim 3 wherein the file system request is to find a first matching file.

13. The method of claim 3 wherein the file system request is to find a next matching file.

14. The method of claim 3 wherein the file system request is directory control.

15. A system for providing data security, the system comprising a device driver for accessing data, the device driver operably installed in an operating system on an electronic computer, the system further comprising at least one tag file, the tag file comprising a physical file of zero bytes in length, the tag file being maintained in a file system location, wherein file system calls are processed so that the tag file appears as a secured file containing data, wherein said device driver:

detects a file system request;

completes said file system request;

receives return information from said file system request;

determines whether said file system request is for a tag file associated with a secured file; and

if so, modifies said return information to reflect a file attribute of the secured file.

16. The system of claim 15 wherein said file attribute is file size.

17. The system of claim 15 wherein said device driver further

determines whether said return information identifies a plurality of tag files associated with a plurality of secured files; and

if so, modifies said return information to reflect a file attribute of the plurality of secured files.

18. The system of claim 15 wherein said first device driver is a file systemmonitor.

19. The system of claim 15 wherein the secured file is stored in encrypted form.

20. The system of claim 15 wherein the secured file is stored in a secure virtual file system.

21. The system of claim 15 wherein the secured file is stored on a remote networked device.

22. The system of claim 15 wherein the file system request is to open a file.

23. The system of claim 15 wherein the file system request is to delete a file.

24. The system of claim 15 wherein the file system request is to rename a file.

25. The system of claim 15 wherein the file system request is to query file information.

26. The system of claim 15 wherein the file system request is to set file information.

27. The system of claim 17 wherein the file system request is to find a first matching file.

28. The system of claim 17 wherein the file system request is to find a next matching file.

29. The system of claim 17 wherein the file system request is directory control.

30. A machine-readable medium comprising a device driver program for accessing data, said device driver program comprising:

computer implemented instructions for providing at least one tag file, the tag file comprising a physical file of zero bytes in length;

computer-implemented instructions for maintaining the tag file in a part of a file system;

computer-implemented instructions for processing file system calls so that the tag file appears as a secured file containing data from the viewpoint of a user;

computer-implemented instructions for detecting a file system request;

computer-implemented instructions for completing said file system request;

computer-implemented instructions for receiving return information from said file system request;

computer-implemented instructions for determining whether said file system request is for a tag file associated with a secured file; and

computer-implemented instructions for modifying said return information to reflect a file attribute of the secured file, if said file system request is for a tag file associated with a secured file.

31. The machine-readable medium of claim 30 wherein the device driver program further comprises:

computer-implemented instructions for determining whether said return information identifies a plurality of tag files associated with a plurality of secured files; and

computer-implemented instructions for modifying said return information to reflect a file attribute of the plurality of secured files, if said return information identifies a plurality of tag files associated with a plurality of secured files.

32. A computer-implemented device driver for accessing data when operably installed in a computer operating system, said device driver comprising:

means for providing at least one tag file, the tag file comprising a physical file of zero bytes in length;

means for maintaining the tag file in a part of a file system;

means for processing file system calls so that the tag file appears as a secured file containing data from the viewpoint of a user; means for detecting a file system request;

means for completing said file system request;

means for receiving return information from said file system request;

means for determining whether said file system request is for a tag file associated with a secured file; and

means for modifying said return information to reflect a file attribute of the secured file, if said file system request is for a tag file associated with a secured file.

33. The computer-implemented device driver of claim 32 wherein said file attribute is file size.

34. The computer-implemented device driver of claim 32 further comprising:

means for determining whether said return information identifies a plurality of tag files associated with a plurality of secured files; and

means for modifying said return information to reflect a file attribute of the plurality of secured files, if said return information identifies a plurality of tag files associated with a plurality of secured files.

Assignments (9)
CORRECTIVE ASSIGNMENT TO CORRECT THE NAME OF CORPORATION PREVIOUSLY RECORDED ON REEL 021147 FRAME 0584. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Aug 21, 2019
From: PINION SOFTWARE, INC.
To: GIGAMEDIA ACCESS CORPORATION
Reel/Frame 050127/0347 →
SECURITY INTEREST Recorded Aug 1, 2019
From: GIGAMEDIA ACCESS CORPORATION
To: CRYSTAL FINANCIAL LLC
Reel/Frame 049931/0858 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 31, 2019
From: JPMORGAN CHASE BANK, N.A.
To: GIGAMEDIA ACCESS CORPORATION
Reel/Frame 049920/0903 →
SECURITY INTEREST Recorded Jan 17, 2019
From: GIGAMEDIA ACCESS CORPORATION
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 048052/0663 →
RELEASE OF SECURITY INTEREST Recorded Oct 5, 2016
From: BRIDGEVIEW BANK GROUP
To: GIGAMEDIA ACCESS CORPORATION
Reel/Frame 039944/0640 →
SECURITY INTEREST Recorded Jun 21, 2016
From: GIGAMEDIA ACCESS CORPORATION
To: BRIDGEVIEW BANK GROUP
Reel/Frame 039109/0686 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 26, 2008
From: PINION SOFTWARE, INC.
To: GIGATRUST
Reel/Frame 021147/0584 →
CHANGE OF NAME Recorded May 5, 2005
From: INFRAWORKS CORPORATION
To: PINION SOFTWARE, INC.
Reel/Frame 016182/0821 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 22, 2000
From: FRIEDMAN, GEORGE; STAREK, ROBERT PHILLIP; MURDOCK, CARLOS A.
To: INFRAWORKS CORPORATION
Reel/Frame 011578/0854 →
Continuity (2)
Provisional Application 6015747200 · Oct 1, 1999
Provisional Application 6020694700 · May 25, 2000