Data security system and method with editor

• US 8,176,563 B2
• Filed: 11/26/2004
• Issued: 05/08/2012
• Est. Priority Date: 11/13/2000
• Status: Active Grant

• Current Assignee: DigitalDoors, Inc.
• Original Assignee: DigitalDoors, Inc.
• Inventors: Redlich, Ron M., Nemzow, Martin A.
• Primary Examiner(s): PYZOCHA, MICHAEL J
• Application Number:
  US10/998,363
• Publication Number:
  US 20050132070A1
• Time in Patent Office: 2,720 Days
• Field of Search: 726/27, 713/166, 713/193, 715/234, 715/255
• US Class Current: 726/27
• 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
• CPC Class Codes: G06F 2221/2113 Multi-level security, e.g. mandatory access control

Abstract

The method, program and system secures sensitive data/objects found in a data source document with an editor. The simple editor identifies and displays, in situ, the sensitive words/objects per each security level. Level tags are inserted and adjunctive words/objects are marked/displayed per the level'"'"'s protocol. The precursor document is processed to extract sensitive and adjunctive words/objects. The stripped data is either separately stored or partial versions of the secured document are stored per protocol. A comprehensive editor secures content data and meta data contained in a data document object model (DOM). The editor maps the source document root, branch and leaf components as binary files populated with content data and meta data. Security introns, earlier identified based upon the level'"'"'s informational attributes, are excluded. Security exons are copied from the source content and meta data binary files into a security safe document (template). Filtration, extraction, dispersal and storage follow.

Claims

1. A method of securing content data and meta data contained in a document formatted as a document object model, said document having one or more security sensitive words, characters or data objects, said security sensitive words, characters or data objects grouped into subsets corresponding to respective ones of a plurality of security levels without regard to said document, said document object model having a blueprint and root, branch and leaf components, said method operable on said data in said document in a computer system, comprising:

mapping said root, branch and leaf components of said document as binary files populated with content data and meta data representing subsets of said document object model blueprint;

excluding security introns and associated content data and meta data based upon predetermined informational attributes relative to said document object model;

providing a security safe document formatted as a safe document object model, the security safe document is a template formatted as a document object model with root, branch and leaf components wherein each root, branch and leaf component is a vendor standard template or a non-standard clean template with only security introns previously identified with respect to the vendor standard template based upon predetermined informational attributes relative to the document object model;

copying security exons from said content data and meta data binary files into said security safe document formatted as said safe document object model;

extracting said security sensitive words, characters or data objects from the copied content data and meta data; and

either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data based upon security levels unique to each partial version.

2. A method of securing content and meta data as claimed in claim 1 wherein said extracting occurs on each said root, branch and leaf components of said security safe document.

3. A method of securing content and meta data as claimed in claim 1 wherein excluding security introns and providing a security safe document and copying security exons are non-sequential acts.

4. A method of securing content and meta data as claimed in claim 1 wherein either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data includes mapping extracted data to said root, branch and leaf components of said security safe document.

5. A method of securing content and meta data as claimed in claim 2 wherein excluding security introns and providing a security safe document and copying security exons are non-sequential acts.

6. A method of securing content and meta data as claimed in claim 5 wherein either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data includes mapping extracted data to said root, branch and leaf components of said security safe document.

7. A method of securing content data and meta data contained in a document formatted as a document object model, said document having one or more security sensitive words, characters or data objects, said security sensitive words, characters or data objects grouped into subsets corresponding to respective ones of a plurality of security levels without regard to said document, said document object model having a blueprint and root, branch and leaf components, said method operable on said data in said document in a computer system, comprising:

mapping said root, branch and leaf components of said document as binary files populated with content data and meta data representing subsets of said document object model blueprint;

providing a security safe document formatted as a safe document object model, the security safe document is a template formatted as a document object model with root, branch and leaf components wherein each root, branch and leaf component is a vendor standard template or a non-standard clean template with only security introns previously identified with respect to the vendor standard template based upon predetermined informational attributes relative to the document object model;

copying security exons from said content data and meta data binary files into said security safe document formatted as said safe document object model, said safe document object model consisting of security exons and excluding security introns, and the respective associated content data and meta data relative thereto, which exons and introns being previously identified based upon predetermined informational attributes relative to said document object model;

extracting said security sensitive words, characters or data objects from the copied content data and meta data; and

either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data based upon security levels unique to each partial version.

8. A method of securing content and meta data as claimed in claim 7 wherein said extracting occurs on each said root, branch and leaf components of said security safe document.

9. A method of securing content and meta data as claimed in claim 7 wherein excluding security introns and providing a security safe document and copying security exons are non-sequential acts.

10. A method of securing content and meta data as claimed in claim 7 wherein either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data includes mapping extracted data to said root, branch and leaf components of said security safe document.

11. A method of securing content and meta data as claimed in claim 8 wherein excluding security introns and providing a security safe document and copying security exons are non-sequential acts.

12. A method of securing content and meta data as claimed in claim 11 wherein either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data includes mapping extracted data to said root, branch and leaf components of said security safe document.

13. A method of securing content data and meta data contained in a document formatted as a document object model, said document having one or more security sensitive words, characters or data objects, said security sensitive words, characters or data objects grouped into subsets corresponding to respective ones of a plurality of security levels without regard to said document, said document object model having a blueprint and root, branch and leaf components, said safe document object model consisting of security exons and excluding security introns, and the respective associated content data and meta data relative thereto, said exons and introns being identified based upon predetermined informational attributes relative to said document object model, said method operable on said data in said document in a computer system, comprising:

mapping said root, branch and leaf components of said document as binary files populated with content data and meta data representing subsets of said document object model blueprint;

providing a security safe document formatted as a safe document object model, the security safe document is a template formatted as a document object model with root, branch and leaf components wherein each root, branch and leaf component is a vendor standard template or a non-standard clean template with only security introns previously identified with respect to the vendor standard template based upon predetermined informational attributes relative to the document object model;

copying security exons from said content data and meta data binary files into said security safe document formatted as said safe document object model;

extracting said security sensitive words, characters or data objects from the copied content data and meta data; and

either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data based upon security levels unique to each partial version.

14. A method of securing content and meta data as claimed in claim 13 wherein said extracting occurs on each said root, branch and leaf components of said security safe document.

15. A method of securing content and meta data as claimed in claim 13 wherein providing a security safe document and copying security exons are non-sequential acts.

16. A method of securing content and meta data as claimed in claim 13 wherein either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data includes mapping extracted data to said root, branch and leaf components of said security safe document.

17. A method of securing content and meta data as claimed in claim 14 providing a security safe document and copying security exons are non-sequential acts.

18. A method of securing content and meta data as claimed in claim 17 wherein either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data includes mapping extracted data to said root, branch and leaf components of said security safe document.

19. A non-transitory computer readable storage medium having stored thereon programming instructions for securing content data and meta data contained in a document formatted as a document object model, said document having one or more security sensitive words, characters or data objects, said security sensitive words, characters or data objects grouped into subsets corresponding to respective ones of a plurality of security levels without regard to said document, said document object model having a blueprint and root, branch and leaf components, said method operable on said data in said document in a computer system, comprising:

mapping said root, branch and leaf components of said document as binary files populated with content data and meta data representing subsets of said document object model blueprint;

excluding security introns and associated content data and meta data based upon predetermined informational attributes relative to said document object model;

providing a security safe document formatted as a safe document object model, the security safe document is a template formatted as a document object model with root, branch and leaf components wherein each root, branch and leaf component is a vendor standard template or a non-standard clean template with only security introns previously identified with respect to the vendor standard template based upon predetermined informational attributes relative to the document object model;

copying security exons from said content data and meta data binary files into said security safe document formatted as said safe document object model;

extracting said security sensitive words, characters or data objects from the copied content data and meta data; and

either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data based upon security levels unique to each partial version.

20. A computer readable medium with programming instructions for securing data as claimed in claim 19 wherein said extracting occurs on each said root, branch and leaf components of said security safe document.

21. A computer readable medium with programming instructions for securing data as claimed in claim 19 wherein excluding security introns and providing a security safe document and copying security exons are non-sequential acts.

22. A computer readable medium with programming instructions for securing data as claimed in claim 19 wherein either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data includes mapping extracted data to said root, branch and leaf components of said security safe document.

23. A computer readable medium with programming instructions for securing data as claimed in claim 20 wherein excluding security introns and providing a security safe document and copying security exons are non-sequential acts.

24. A computer readable medium with programming instructions for securing data as claimed in claim 23 wherein either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data includes mapping extracted data to said root, branch and leaf components of said security safe document.

25. A non-transitory computer readable storage medium having stored thereon programming instructions for securing content data and meta data contained in a document formatted as a document object model, said document having one or more security sensitive words, characters or data objects, said security sensitive words, characters or data objects grouped into subsets corresponding to respective ones of a plurality of security levels without regard to said document, said document object model having a blueprint and root, branch and leaf components, said method operable on said data in said document in a computer system, comprising:

mapping said root, branch and leaf components of said document as binary files populated with content data and meta data representing subsets of said document object model blueprint;

providing a security safe document formatted as a safe document object model, the security safe document is a template formatted as a document object model with root, branch and leaf components wherein each root, branch and leaf component is a vendor standard template or a non-standard clean template with only security introns previously identified with respect to the vendor standard template based upon predetermined informational attributes relative to the document object model;

copying security exons from said content data and meta data binary files into said security safe document formatted as said safe document object model, said safe document object model consisting of security exons and excluding security introns, and the respective associated content data and meta data relative thereto, which exons and introns being previously identified based upon predetermined informational attributes relative to said document object model;

extracting said security sensitive words, characters or data objects from the copied content data and meta data; and

either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data based upon security levels unique to each partial version.

26. A computer readable medium with programming instructions for securing data as claimed in claim 25 wherein said extracting occurs on each said root, branch and leaf components of said security safe document.

27. A computer readable medium with programming instructions for securing data as claimed in claim 25 wherein excluding security introns and providing a security safe document and copying security exons are non-sequential acts.

28. A computer readable medium with programming instructions for securing data as claimed in claim 25 wherein either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data includes mapping extracted data to said root, branch and leaf components of said security safe document.

29. A computer readable medium with programming instructions for securing data as claimed in claim 26 wherein excluding security introns and providing a security safe document and copying security exons are non-sequential acts.

30. A computer readable medium with programming instructions for securing data as claimed in claim 29 wherein either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data includes mapping extracted data to said root, branch and leaf components of said security safe document.

31. A non-transitory computer readable storage medium having stored thereon programming instructions for securing content data and meta data contained in a document formatted as a document object model, said document having one or more security sensitive words, characters or data objects, said security sensitive words, characters or data objects grouped into subsets corresponding to respective ones of a plurality of security levels without regard to said document, said document object model having a blueprint and root, branch and leaf components, said safe document object model consisting of security exons and excluding security introns, and the respective associated content data and meta data relative thereto, said exons and introns being identified based upon predetermined informational attributes relative to said document object model, said method operable on said data in said document in a computer system, comprising:

mapping said root, branch and leaf components of said document as binary files populated with content data and meta data representing subsets of said document object model blueprint;

providing a security safe document formatted as a safe document object model, the security safe document is a template formatted as a document object model with root, branch and leaf components wherein each root, branch and leaf component is a vendor standard template or a non-standard clean template with only security introns previously identified with respect to the vendor standard template based upon predetermined informational attributes relative to the document object model;

copying security exons from said content data and meta data binary files into said security safe document formatted as said safe document object model;

extracting said security sensitive words, characters or data objects from the copied content data and meta data; and

either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data based upon security levels unique to each partial version.

32. A computer readable medium with programming instructions for securing data as claimed in claim 31 wherein said extracting occurs on each said root, branch and leaf components of said security safe document.

33. A computer readable medium with programming instructions for securing data as claimed in claim 31 wherein providing a security safe document and copying security exons are non-sequential acts.

34. A computer readable medium with programming instructions for securing data as claimed in claim 31 wherein either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data includes mapping extracted data to said root, branch and leaf components of said security safe document.

35. A computer readable medium with programming instructions for securing data as claimed in claim 32 providing a security safe document and copying security exons are non-sequential acts.

36. A computer readable medium with programming instructions for securing data as claimed in claim 35 wherein either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data includes mapping extracted data to said root, branch and leaf components of said security safe document.

37. An information processing system for securing content data and meta data contained in a document formatted as a document object model, said document having one or more security sensitive words, characters or data objects, said security sensitive words, characters or data objects grouped into subsets corresponding to respective ones of a plurality of security levels without regard to said document, said document object model having a blueprint and root, branch and leaf components, said method operable on said data in said document in a computer system, comprising:

a mapper to map said root, branch and leaf components of said document as binary files populated with content data and meta data representing subsets of said document object model blueprint;

means for excluding security introns and associated content data and meta data based upon predetermined informational attributes relative to said document object model;

a security safe document formatted as a safe document object model, the security safe document is a template formatted as a document object model with root, branch and leaf components wherein each root, branch and leaf component is a vendor standard template or a non-standard clean template with only security introns previously identified with respect to the vendor standard template based upon predetermined informational attributes relative to the document object model;

a copier for copying security exons from said content data and meta data binary files into said security safe document formatted as said safe document object model;

extractor for extracting said security sensitive words, characters or data objects from the copied content data and meta data; and

means for either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data based upon security levels unique to each partial version.

38. An information processing system for securing content and meta data as claimed in claim 37 wherein said extractor operates on each said root, branch and leaf components of said security safe document.

39. An information processing system as claimed in claim 37 wherein said means for excluding security introns operates concurrently with said security safe document and copier for said security exons.

40. An information processing system as claimed in claim 37 wherein said means for storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data includes a supplemental mapper for mapping said extracted data to said root, branch and leaf components of said security safe document.

41. An information processing system as claimed in claim 38 wherein said means for excluding said security introns operates concurrently with said security safe document and said copier for said security exons.

42. An information processing system as claimed in claim 41 wherein said means for storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data includes a supplemental mapper for mapping extracted data to said root, branch and leaf components of said security safe document.

43. An information processing system for securing content data and meta data contained in a document formatted as a document object model, said document having one or more security sensitive words, characters or data objects, said security sensitive words, characters or data objects grouped into subsets corresponding to respective ones of a plurality of security levels without regard to said document, said document object model having a blueprint and root, branch and leaf components, said method operable on said data in said document in a computer system, comprising:

a mapper for mapping said root, branch and leaf components of said document as binary files populated with content data and meta data representing subsets of said document object model blueprint;

a security safe document formatted as a safe document object model, the security safe document is a template formatted as a document object model with root, branch and leaf components wherein each root, branch and leaf component is a vendor standard template or a non-standard clean template with only security introns previously identified with respect to the vendor standard template based upon predetermined informational attributes relative to the document object model;

a copier for copying security exons from said content data and meta data binary files into said security safe document formatted as said safe document object model, said safe document object model consisting of security exons and excluding security introns, and the respective associated content data and meta data relative thereto, which exons and introns being previously identified based upon predetermined informational attributes relative to said document object model;

an extractor for extracting said security sensitive words, characters or data objects from the copied content data and meta data; and

means for storing either the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data based upon security levels unique to each partial version.

44. An information processing system as claimed in claim 43 wherein said extractor operates on each said root, branch and leaf components of said security safe document.

45. An information processing system as claimed in claim 43 wherein said means for excluding said security introns operates concurrently with said security safe document and said copier of said security exons.

46. An information processing system as claimed in claim 43 wherein said means for storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data includes a supplemental mapper for mapping extracted data to said root, branch and leaf components of said security safe document.

47. An information processing system as claimed in claim 44 wherein said means for excluding said security introns operates concurrently with said security safe document and said copier for said security exons.

48. An information processing system as claimed in claim 47 wherein said means for storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data includes a supplemental mapper for mapping extracted data to said root, branch and leaf components of said security safe document.

49. An information processing system for securing content data and meta data contained in a document formatted as a document object model, said document having one or more security sensitive words, characters or data objects, said security sensitive words, characters or data objects grouped into subsets corresponding to respective ones of a plurality of security levels without regard to said document, said document object model having a blueprint and root, branch and leaf components, said safe document object model consisting of security exons and excluding security introns, and the respective associated content data and meta data relative thereto, said exons and introns being identified based upon predetermined informational attributes relative to said document object model, said method operable on said data in said document in a computer system, comprising:

a mapper for mapping said root, branch and leaf components of said document as binary files populated with content data and meta data representing subsets of said document object model blueprint;

a security safe document formatted as a safe document object model, the security safe document is a template formatted as a document object model with root, branch and leaf components wherein each root, branch and leaf component is a vendor standard template or a non-standard clean template with only security introns previously identified with respect to the vendor standard template based upon predetermined informational attributes relative to the document object model;

a copier for copying said security exons from said content data and meta data binary files into said security safe document formatted as said safe document object model;

extractor for extracting said security sensitive words, characters or data objects from the copied content data and meta data; and

means for either storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data based upon security levels unique to each partial version.

50. An information processing system as claimed in claim 49 wherein said extractor operates on each said root, branch and leaf components of said security safe document.

51. An information processing system as claimed in claim 49 wherein said security safe document is used concurrently with said copier for said security exons.

52. An information processing system as claimed in claim 49 wherein said means for storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data includes mapping extracted data to said root, branch and leaf components of said security safe document.

53. An information processing system as claimed in claim 50 wherein said security safe document is employed by said copier for said security exons.

54. An information processing system as claimed in claim 53 wherein said means for storing the extracted data separately from remainder data or storing partial versions of said extracted data with said remainder data includes a supplemental mapper for mapping extracted data to said root, branch and leaf components of said security safe document.