Browse Prior Art Database

Document chameleon for sensitive object protect

IP.com Disclosure Number: IPCOM000238596D
Publication Date: 2014-Sep-05
Document File: 3 page(s) / 166K

Publishing Venue

The IP.com Prior Art Database

Abstract

In daily, there are lots of files and information. Some of the files might be sensitive, we would not let others recognize the type of the files. The file might be shown as a sensitive document. So these risky people would ignore this file.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 77% of the total text.

Page 01 of 3

Document chameleon for sensitive object protect

In daily, there are lots of files and information. Some of the files might be sensitive, we would not let others recognize the type of the files. For example, we put our PPT in the sever, and we would not let all the people know that, so the file might be shown as a draw 'Mona Lisa'. So these people would not treat it as sensitive file.

When a file is marked as sensitive, the file would have the ability to imitate the file around it. For example, if all the file around it is *.txt, the file would disguise itself as *.txt; if all the file around it is *.jpg, the file would disguise itself as *.jpg. We could also use different strategies for different setting.

If we mark the document as sensitive, the document would disguise itself depending on the environment such the document types in the file folder, user name of the system, and key setting.

As shown in the following graph, there is a sensitive document in server as S.PPT. If the destination user downloads the document, it is shown as normal, S.PPT; If the risky user downloads the document, it is shown as file just like the file around it, X.txt.

1



Page 02 of 3

There are also several rules which could be considered.


1. The file could change into a defined file type such as TXT.

2. The file could also change as the file around it. For example, if there are more *.JPG, it would be shown as image.

3. To be more reasonable, if the file is very big and could not disgui...