BACKGROUND

Electronic documents (EDs) are commonly used for storing and disseminating information. This information may include sensitive data items such as, for example, social security numbers, credit card information, income information, or any type of confidential information, etc. EDs may be defined using a document markup language to provide features such as complex formatting, document comments, tracking of changes, etc. The document markup language may include multiple instances of the sensitive data items.

An ED may be distributed to many users. Some users might be authorized to view the sensitive data items. Some users might not be authorized to view the sensitive data items. Accordingly, it may be necessary to encrypt the sensitive data items. However, encrypting the displayed instances of a sensitive data item in the ED might not encrypt all instances (e.g., non-displayed instances or non-printed instances) of the sensitive data item found within the markup of the ED. An unauthorized user might still be able to view the sensitive data items by accessing the markup of the document. Accordingly, encryption of all instances of the sensitive data items in the ED is desirable. It is also desirable to maintain the overall layout of the ED even when the user is not authorized to view the sensitive data items.

SUMMARY

In general, in one aspect, the invention relates to a method for redacting an electronic document (ED) having a file format. The method comprises: obtaining a request to redact a sensitive data item in the ED; identifying a first instance and a second instance of the sensitive data item in a markup of the ED, wherein the second instance of the sensitive data item is not visible in a rendered version of the ED; and generating a redacted ED having the file format by: replacing the first instance of the sensitive data item and the second instance of the sensitive data item with a neutral data item, and inserting, into the markup, an encrypted version of the sensitive data item at a first location.

In general, in one aspect, the invention relates to a system for redacting an electronic document (ED) having a file format. The system comprises: a computer processor; a user interface (UI) configured to obtain a request to redact a sensitive data item in the ED; an identification engine (IE) configured to identify a first and a second instance of the sensitive data item in a markup of the ED, wherein the second instance of the sensitive data item is not visible in a rendered version of the ED; and a redaction engine (RE), executing on the computer processor, and configured to generate a redacted ED having the file format by: replacing the first instance of the sensitive data item and the second instance of the sensitive data item with a neutral data item, and inserting, into the markup, an encrypted version of the sensitive data item at a first location.

In general, in one aspect, the invention relates to a non-transitory computer readable medium (CRM) storing instructions for redacting an electronic document (ED) having a file format. The instructions comprise functionality for: obtaining a request to redact a sensitive data item in the ED; identifying a first instance and a second instance of the sensitive data item in a markup of the ED, wherein the second instance of the sensitive data item is not visible in a rendered version of the ED; and generating a redacted ED having the file format by: replacing the first instance of the sensitive data item and the second instance of the sensitive data item with a neutral data item, and inserting, into the markup, an encrypted version of the sensitive data item at a first location.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 shows a schematic diagram of a system in accordance with one or more embodiments of the invention.

FIG. 2 shows a flowchart in accordance with one or more embodiments of the invention.

FIG. 3 shows a flowchart in accordance with one or more embodiments of the invention.

FIG. 4, FIG. 5A, and FIG. 5B show examples in accordance with one or more embodiments of the invention.

FIG. 6 shows a computer system in accordance with one or more embodiments of the invention.

DETAILED DESCRIPTION

Specific embodiments of the invention will now be described in detail with reference to the accompanying figures. Like elements in the various figures are denoted by like reference numerals for consistency.

In the following detailed description of embodiments of the invention, numerous specific details are set forth in order to provide a more thorough understanding of the invention. However, it will be apparent to one of ordinary skill in the art that the invention may be practiced without these specific details. In other instances, well-known features have not been described in detail to avoid unnecessarily complicating the description.

In general, embodiments of the invention provide a method, a system, and a non-transitory computer readable medium (CRM) for redacting an ED comprising a sensitive data item. Specifically, an encrypted version of the sensitive data item is inserted into the markup of the ED and all instances of the sensitive data item within the markup are replaced with a neutral data item. The redacted ED may be in the same file format as the original ED. This redacted ED may be sent to any number of users.

If the redacted ED is rendered for a user authorized to view the sensitive data item, the encrypted sensitive data item is decrypted, and the rendered version of the redacted ED includes the sensitive data item in plaintext. A user may be authenticated by providing the correct password, by providing the matching fingerprint scan, by providing the correct answers to a series of questions, by providing the correct encryption key, etc. to the rendering engine or authorization engine connected to the rendering engine. If the redacted ED is rendered for a user that is not authorized to view the sensitive data item, the encrypted sensitive data item remains encrypted, and the rendered version of the ED includes the neutral data item in lieu of the sensitive data item.

In one or more embodiments of the invention, the ED may be defined using a document markup language. A document markup language is a system for annotating the body text of an ED in order to provide, for example, formatting instructions. In one or more embodiments of the invention, the document markup language may be Extensible Markup Language (XML). XML is a markup language that defines a set of rules for encoding documents in a format which is both human-readable and machine-readable. Examples of ED file formats that use XML to annotate the body text of the ED include Office Open XML (OOXML), and Open Document Format (ODF), among others. These file formats enable a user to compose EDs. Rendering engines interpret the markup language instructions affiliated with the body text of the ED in order to display the body text with the desired formatting.

In one or more embodiments of the invention, the markup of the ED may include tags that represent markup language instructions. A tag, in accordance with one or more embodiments of the invention, may be inserted in the markup of the ED to annotate a word, sentence, or paragraph, for example. Other tags may provide support for the tracking of changes and/or the insertion of footnotes, endnotes, headers and footers, linked text, watermarks, and/or other functionality provided by the markup language. Tags may therefore link additional content to the body text of the ED. This additional content might or might not be displayed to the user. Moreover, the user might or might not be aware that the additional content exists.

In one or more embodiments of the invention, the additional content linked to the body text of the ED may be stored in the same file, along with the body text and the tags of the ED, or in a separate or in multiple separate files. The ED file format may use, for example, separate files for the body text of the document, the document settings, footnotes, comments, etc. Further, in accordance with one or more embodiment of the invention, these separate files may be stored in a single container file, thus enabling the user to manipulate the single container file only, rather than having to manipulate multiple individual files.

In one or more embodiments of the invention, the ED may include a sensitive data item. Sensitive data items may include, for example, social security numbers, credit card information, income information, or other confidential information. Not all instances of the sensitive data item may be visible in the displayed (i.e., rendered) ED. A user of the ED may want to encrypt a sensitive data item in the document, for example, before sharing the ED with other users. As previously described, additional content may be linked to the body text of the ED via tags. This additional linked content may include additional instances of the sensitive data item. For example, the same user (or a different user) may have added a comment including the sensitive data item. In another example, the ED may include tracked changes made to the ED, where earlier revisions of the ED may also include the sensitive data item.

One or more embodiments of the invention enable a user to generate a redacted ED from the original ED. In one or more embodiments of the invention, the user may select the sensitive data item to be redacted, for example, by highlighting the sensitive data item in the displayed document, and subsequently the ED may be searched for instances of the sensitive data item. Next, the detected instances of the sensitive data item may be removed from the ED, and may be replaced by a neutral data item. An encrypted version of the sensitive data item may also be added to the ED. In one or more embodiments of the invention, the encrypted version of the sensitive data item is added at each location in the markup corresponding to an instance of the sensitive data item. Additionally or alternatively, the encrypted version of the sensitive data item may be added to newly generated sections or blocks within the markup that are accessed by the rendering engine operated by the end-user.

In one or more embodiments of the invention, all instances of the sensitive data item, including rendered instances (i.e., instances that are visible to the user of the ED), instances that are not rendered in the ED but may be rendered under certain circumstances, and instances that are never rendered, may be removed and replaced (i.e., redacted) by neutral data items and encrypted instances of the sensitive data item.

In one or more embodiments of the invention, the redacted ED may have the same file format as the original ED. Accordingly, the redacted ED remains fully editable and provides all features and functionality of the original ED. For example, interactive content such as macros may be retained, and tables and/or charts may remain fully editable. In addition, the layout and formatting of the original ED may be fully maintained such that the perceivable differences between the original ED and the redacted ED are limited to the neutral data items that are displayed to a non-authorized user. There are no perceivable differences between the original ED and the redacted ED when the encrypted data items, after decryption, are displayed to an authorized user.

FIG. 1 shows a system (102) in accordance with one or more embodiments of the invention. As shown in FIG. 1, the system (102) has multiple components, including a user interface (106), an identification engine (108), and a redaction engine (110). Each of these components may be located on the same computing device (e.g., desktop computer, server, laptop computer, tablet computer, smart phone, etc.) or may be located on different computing devices connected by a network having wired and/or wireless segments.

In one or more embodiments, the system (102) includes the user interface (106). The user interface (106) is configured to receive user requests to open, display, and redact EDs (e.g., ED (112)). The user interface (106) may also be configured to display the redacted ED (114). For example, the user interface may be a graphical user interface (GUI) with multiple widgets (e.g., dropdown boxes, buttons, radio buttons, etc.) that can be manipulated by the user. In one or more embodiments of the invention, the user identifies/specifies a sensitive data item to be redacted within the ED (112) by highlighting an instance of the sensitive data item within the displayed (i.e., rendered) ED (112). Additionally or alternatively, the user could enter the sensitive data item in a â€œsearch boxâ€ from the GUI. In one or more embodiments of the invention, the user interface prompts the user every time an instance of a sensitive data item is identified within the ED (112). By responding to the prompt, the user can choose to redact or not redact instances of the sensitive data item on an instance-by-instance basis (discussed below). Alternatively, the user could select to redact all instances of the sensitive data item.

In one or more embodiments of the invention, the GUI is used to collect credentials (e.g., passwords, encryption keys, answers to a set of security questions, fingerprints, etc.) of authorized end-users. In other words, the user requesting that the redacted ED be generated may also set the credentials required by an end-user to view/print the redacted ED with the sensitive data items in plaintext. End-users having these credentials are considered authorized.

In one or more embodiments of the invention, the system (102) includes the identification engine (108). The identification engine (108) is configured to search the markup of the ED (112) for instances of the sensitive data item. This may include parsing the body of the ED (112) for tags, and then parsing the additional non-rendered content linked using the tags for instances of the sensitive data item. This searching operation may be executed on the entire markup, or only a portion of the markup that surrounds the visible instance of the sensitive data item that has been highlighted by the user. This searching operation may extend into one, multiple, or all files that define the ED (112).

In one or more embodiments of the invention, the system (102) includes the redaction engine (110). The redaction engine (110) is configured to generate the redacted ED (114). Specifically, the redaction engine (110) is configured to replace each identified instance of the sensitive data item in the ED (112) with a neutral data item (e.g., a random number, a random alphanumeric string, a box or other shape, an image, etc.) and an encrypted version of the sensitive data item. The redaction engine (110) may utilize any type of encryption (e.g., symmetric key encryption schemes, public key encryption schemes, etc.) and any encryption algorithm to encrypt the sensitive data item. The redaction engine (110) may utilize some or all of the credentials (i.e., passwords, keys, etc.) provided by the user to generate the encrypted version of the sensitive data time.

If the redacted ED is rendered for a user authorized to view/print the sensitive data item (i.e., a user having the required credentials), the encrypted sensitive data item is decrypted, and the rendered version of the redacted ED includes the sensitive data item in plaintext (i.e., the sensitive data item is visible in plaintext in the rendered ED, while the neutral data item is not visible in the rendered ED). If the redacted ED is rendered for a user that is not authorized to view/print the sensitive data item, the encrypted sensitive data item remains encrypted, and the rendered version of the ED includes the neutral data item in lieu of the sensitive data item (i.e., the neutral data item is visible in the rendered version of the ED).

In one or more embodiments of the invention, the same neutral data item may be used to replace all instances of the sensitive data item. Additionally or alternatively, different neutral data items may be used to replace different instances of the sensitive data item. In one or more embodiments of the invention, a bounding box is determined for each instance of the sensitive data item. The bounding box provides the size of the sensitive data item in the displayed (i.e., rendered) ED (112). The redaction engine (110) may remove each identified instance of the sensitive data item and insert a neutral data item having the same size of the bounding box in its place.

In one or more embodiments of the invention, a single encrypted instance of the sensitive data item may be added to the markup of the document. All instances of the sensitive data item may be restored by decrypting this single instance of the encrypted sensitive data item. Alternatively, in one or more embodiments of the invention, a separate encrypted instance of the sensitive data item may be added for each instance of the sensitive data item.

Those skilled in the art, having the benefit of this detailed description, will appreciate that the ED (112) may have multiple instances of the sensitive data item. When the ED (112) is eventually rendered (e.g., printed, displayed) by a rendering engine, some instances of the sensitive data item are visible in the rendered version of the ED, while other instances of the sensitive data item might not be visible in the rendered version of the ED. Different rendering engines (i.e., rendering engines executing different software versions, having different settings, having different configurations, etc.) may render the ED differently. Accordingly, the instances of the sensitive data item that are visible vs. invisible may vary between different rendered versions of the ED. However, all instances of the sensitive data item may be still be seen by viewing the markup of the ED.

Those skilled in the art, having the benefit of this detailed description, will appreciate that by replacing all instances of the sensitive data item with the neutral and the encrypted data item in the markup of the ED, regardless of whether the instance is eventually rendered, it will no longer be possible for an end user to view, in plaintext, the sensitive data item in the markup of the redacted ED. In other words, not only will visible instances of the sensitive data item be replaced with the neutral and the encrypted version of data item, but even the instances of the sensitive data item that are not rendered but are in the markup will be replaced.

While FIG. 1 shows a configuration of components, other configuration may be used without departing from the scope of the invention. For example, various components may be combined to create a single component. As another example, the functionality performed by a single component may be performed by two or more components.

FIG. 2 shows a flowchart in accordance with one or more embodiments of the invention. The process depicted in FIG. 2 may be used to redact an ED. One or more of the steps in FIG. 2 may be performed by the components of the system (102), discussed above in reference to FIG. 1. In one or more embodiments of the invention, one or more of the steps shown in FIG. 2 may be omitted, repeated, and/or performed in a different order than the order shown in FIG. 2. Accordingly, the scope of the invention should not be considered limited to the specific arrangement of steps shown in FIG. 2.

Initially, an ED is opened (Step 202). The user may select the ED to open using a GUI. The ED may be stored on a local storage device or on a network storage device. The ED may be defined using a markup language (e.g., OOXML, ODF). In response to the open request, the ED may be rendered and displayed to the user. Within the displayed ED, there may be one or more instances of one or more sensitive data items (e.g., salary information, social security numbers, etc.). These might or might not be the only instances of the sensitive data items within the ED (i.e., other instances of the sensitive data items may be in the ED, but not visible).

In Step 204, the user identifies a sensitive data item(s) in the ED and submits a request for redaction of the sensitive data item(s). Specifically, the user may specify the sensitive data item(s) by highlighting an instance(s) of the sensitive data item in the displayed ED. Additionally or alternatively, the user may input (e.g., type in, or speak) the sensitive data item(s). For example, the user may enter the detected sensitive data item(s) in a dialog box or use other means (e.g., microphone) to specify the sensitive data item(s).

In one or more embodiments of the invention, the user provides the credentials needed to render the redacted ED with the sensitive data items in plaintext. These credentials distinguish authorized end-users from unauthorized end-users. As discussed above, the credentials may include passwords, fingerprints, answers to a series of security questions, keys, etc.

In Step 206, instances of the sensitive data item(s) in the ED are identified. In one or more embodiments of the invention, identifying the instances of the sensitive data item(s) includes searching for additional instances of the sensitive data item(s) in the body text and in other areas of the markup or files of the ED. The searching may cover the entire ED. Additionally or alternatively, the searching may be restricted to a predefined portion of the ED that includes the visible instance of the sensitive data item. The predetermined portion may be, for example, the paragraph of the body text that contains the instance of sensitive data item(s) identified by the user. In one or more embodiments of the invention, the boundaries of the predetermined portion may be configurable. For example, the predetermined portion may be limited to the sentence or paragraph of the body text that contains the instance of sensitive data item(s) identified by the user.

In one or more embodiments of the invention, identifying the instances of the sensitive data item(s) includes parsing the predetermined region for possibly non-rendered tags that may link additional content of the ED to the body text of the ED. As described above, this additional content may be, for example, comments, prior versions of the document, footnotes, etc. In one or more embodiments of the invention, the additional content may be searched to locate additional instances of the sensitive data item(s). In one or more embodiments of the invention, the type of additional content to be searched may be configurable. For example, only comments, or only prior versions of the document may be searched, or all types of additional content may be searched. In one or more embodiments of the invention, the additional content to be searched may be distributed over multiple files. For example, separate files may exist for comments, prior versions of the document, footnotes, etc.

In one or more embodiments of the invention, each identified instance of a sensitive data item may be presented to the user. If the instance is visible in the displayed (i.e., rendered) ED, presenting the instance may include positioning the displayed ED such that the instance is in center of the screen and/or has a different appearance (e.g., different font size, different color, highlighting, etc.) than the rest of the displayed ED. If the instance is not visible in the displayed (i.e., rendered) ED, presenting the instance may include displaying via the GUI the instance and within what context the instance was found. For example, if the instance was found in a non-visible comment, then a dialogue box could be presented to the user explaining that the sentence containing the instance has a comment that also contains the instance. Alternatively, if the instance was found in document history, then a dialogue box would be presented to the user with the list of prior versions that contain the instance. The user may approve or reject the redaction of the presented instance. This enables the user to approve or reject the redaction of an instance on an instance-by-instance basis.

In one or more embodiments of the invention, artificial intelligence or machine learning techniques may be implemented to suggest additional sensitive data items. For example, these suggestions may include misspellings of redacted words or analyzing the type of content that is deemed to be a sensitive data item and finding similar content in the document the user may have overlooked.

In one or more embodiments of the invention, images and other non-text content in the ED may also be scanned for sensitive data items. Using optical character recognition (OCR), the image could be analyzed for sensitive data items and a message may be presented to the user warning that the image also contains sensitive data item.

In Step 208, a redacted ED is generated. The redacted ED is generated by replacing each instance (or each user approved instance) of the sensitive data item(s) with a neutral data item (e.g., random number, random alphanumeric string, a box or other graphic or clipart, an image, etc.) and an encrypted sensitive data item. FIG. 3 provides additional details regarding Step 208.

In Step 210, the redacted ED is saved. The redacted ED has the same file format as the original (i.e., non-redacted) ED. The markup of the redacted ED does not have the sensitive data item in plaintext. The redacted ED may be distributed/transmitted to any number of users. Some users may be authorized users, while other users may be unauthorized users. The rendering engine operated by each user is responsible for generating a rendered version of the redacted ED. These rendering engines may be responsible for enforcing access rights by checking the credentials of the users to ensure that only authorized users can view/print rendered versions of the redacted ED having the sensitive data item in plaintext. Unauthorized users can only view/print rendered versions of the redacted ED in which the neutral data item is visible instead of the sensitive data item.

FIG. 3 shows a flowchart in accordance with one or more embodiments of the invention. The process depicted in FIG. 3 may be used to generate a redacted ED. Specifically, the process depicted in FIG. 3 may correspond to Step 208, discussed above in reference to FIG. 2. Accordingly, the process depicted in FIG. 3 may be repeated for each instance of a sensitive data item. One or more of the steps in FIG. 3 may be performed by the components of the system (102), discussed above in reference to FIG. 1. In one or more embodiments of the invention, one or more of the steps shown in FIG. 3 may be omitted, repeated, and/or performed in a different order than the order shown in FIG. 3. Accordingly, the scope of the invention should not be considered limited to the specific arrangement of steps shown in FIG. 3.

In Step 302, a bounding box for the instance of the sensitive data item is determined. The bounding box provides the size, in the rendered ED, of the instance of the sensitive data item. For example, a sensitive data item displayed using a 12pt font size may result in a smaller bounding box than the same sensitive data item displayed using a 16pt font size.

In Step 304, the instance of the sensitive data item is removed from the markup of the ED. In Step 306, a neutral data item is inserted into the ED. The neutral data item has the size specified by the bounding box. Sizing the neutral data item according to the geometry of the bounding box ensures that the inserted neutral data item occupies an amount of space similar to the amount of space occupied by the now-deleted instance of sensitive data item, thus ensuring that the layout of the ED is not altered by the replacement. The redacted ED, in accordance with one or more embodiments of the invention, may therefore have a layout that is indistinguishable or almost indistinguishable from the layout of the original ED. In one or more embodiments of the invention, the neutral data item may be a geometrical object, such as, for example, a solid black rectangle, or any other geometrical object suitable to fill the space in the ED where the instance of the sensitive data item was removed. Replacement of the instance of the sensitive data item with a neutral data item that is a geometrical object may require additional segmentation of the body text and the insertion of additional markup language instructions, discussed below in reference to FIG. 4 and FIG. 5.

In one or more embodiments of the invention, the neutral data item may consist of a string, such as, for example, â€œ%%%â€ , â€œ$$$â€ , â€œ***â€ , or it may consist of characters that form a geometrical object, such as for example â€œî¢ â€ . In such embodiments, replacing an instance of the sensitive data item with a neutral data item that consists of characters may require determining the appropriate font size and the number of characters to be inserted in lieu of the sensitive data item.

In Step 308, an encrypted version of the sensitive data item is generated. The encrypted version may be generated using any type of encryption and/or any encryption algorithm. Moreover, the encrypted version may be generated using one or more credentials provided by the user who requested the redacted ED be generated. Those skilled in the art, having the benefit of this detailed description will appreciate that the encrypted version of the sensitive data item is an illegible string of characters (i.e. ciphertext). In one or more embodiments of the invention, the encrypted version of the sensitive data item consists solely of the sensitive data item in ciphertext (i.e., not plaintext). Alternatively, in one or more embodiments of the invention, the encrypted version of the sensitive data item includes the sensitive data item, words surrounding the sensitive data item, and the tags of the markup delimiting the sensitive data item and the words surrounding the sensitive data item.

In Step 310, the encrypted instance of the sensitive data item (i.e., the illegible string of characters) is inserted into the markup of the redacted ED. Moreover, the markup is further modified such that either the plaintext of the sensitive data item or the neutral data item is displayed/printed following a rendering of the redacted ED, depending on the credentials of the end-user.

In one or more embodiments of the invention, the markup may be modified to include alternate content sections/blocks for each instance of the sensitive data item. In such scenarios, one alternative content section/block may have the neutral data item for the sensitive data item, while another alternative content section/block may have the encrypted version of the sensitive data item. When the redacted ED is rendered, only the content from one of the alternative sections/blocks will appear in the rendered version of the redacted ED, depending on the credentials of the end user.

In one or more embodiments of the invention, the markup may be modified to include a content extension section. In such embodiments, the content extension section includes the encrypted version of the sensitive data item. Those skilled in the art, having the benefit of this detailed description, will appreciate that content extension sections may be used to augment existing schemas (e.g., to refine the semantics of existing constructs). Content extension sections may augment existing schemas without overriding the existing schemas and are therefore designed such that they do not overlap with the semantics of the existing schemas.

Alternate content sections or blocks and content extension sections or blocks are OOXML constructs that are described by the ISO/IEC document 29500-1, third edition, 2012-09-01. ISO/IEC 29500-1, third edition, 2012-09-01 is hereby incorporated by reference in its entirety.

FIG. 4, FIG. 5A and FIG. 5B show examples in accordance with one or more embodiments of the invention. FIG. 4 shows an original ED (402), and FIG. 5A shows the redacted ED (502) derived from the original ED (402), when accessed by a user that is not authorized to view the sensitive data items. FIG. 5B shows the redacted ED (502), when accessed by a user that is authorized to view the sensitive data items. The following example is for explanatory purposes only and is not intended to limit the scope of the invention.

Turning to FIG. 4, assume the ED (402) includes a text box that displays sensitive data items: a social security number and an annual salary. Further, assume the ED (402) includes the document xml file having the body text of the ED. Further still, assume the ED is compatible with different versions of rendering software. Accordingly, the document xml file may have substantially redundant portions, with different portions being used by different versions of the rendering software to display or print the ED. As a result of the multiple portions, two instances of each sensitive data item appear in the document xml file (e.g., one instance per portion).

The ED also includes the comments xml file having a comment referring to the body text of the ED. The comment may have been made by a third-party user who viewed the ED. This comment includes an instance of one sensitive data item (i.e., the annual salary). Moreover, each portion of the document.xml file includes a tag â€œCommentReferenceâ€ indicating that a comment was added to the text box (i.e., a comment exists).

In the example, a user decides to create the redacted ED (502). Specifically, the user wants the social security number and the annual salary in plaintext to be only visible to authorized users. Moreover, the user wants the neutral data items, instead of the plaintext social security number and annual salary, to be displayed to unauthorized users. Accordingly, when inspecting the ED as displayed (404), the user highlights â€œ123-45-6789â€ and â€œ$1,000,000â€ to specify an instance of a sensitive data item. Multiple instances of the sensitive data items are then identified in the ED. Specifically, two instances of â€œ123-45-6789â€ and two instances of â€œ$1,000,000â€ in the document.xml file are identified. During the parsing of the ED, the tag â€œCommentReferenceâ€ is identified/encountered. This triggers a parsing of the comments.xml file where yet another instance of the â€œ$1,000,000â€ is identified.

For each instance of the sensitive data item, the height and width of its bounding box in view of the of the font size and other formatting applied is determined. For this example, it is determined that the bounding box for one instance of â€œ$1,000,000â€ is 22 mmÃ—5 mm. It is also determined that the bounding box for one instance of â€œ123-45-6789â€ is 18 mmÃ—5 mm. Further, for each instance or one or more instances of the sensitive data item, an encrypted version is generated. The encrypted version includes, in ciphertext (i.e., not plaintext), the sensitive data item, words surrounding the sensitive data item, and the tags of the markup delimiting the sensitive data item and the words surrounding the sensitive data item. The redacted ED is generated by modifying the markup of the ED to include alternate content blocks for each instance of the sensitive data item. One of the alternate section blocks includes the neutral data item, while another one of the alternate content blocks includes the encrypted version of the sensitive data item.

FIG. 5A shows the redacted ED, as displayed to a user not authorized to view the sensitive data items (504A). FIG. 5A also shows an example of the modified markup (506) which has been simplified for clarity. The modified markup (506) corresponds to a segment of the markup (406) that is enclosed by a box having a dashed perimeter. The modified markup (506) includes two alternate content sections. The first alternate content section, delimited by the OOXML tags <Choice Requires=â€œdecryptionâ€ > and </Choice>, contains an encrypted version of the sensitive data item. The second alternate content section, delimited by the OOXML tags <Fallback> and </Fallback>, contains the neutral data items (i.e., rectangles) replacing the sensitive data items. Because the user is not authorized to view the sensitive data items, only the content between the <Fallback> and the </Fallback> OOXML tags is rendered, resulting in the display of black rectangles in lieu of the sensitive data items (504A). As shown in the modified markup (506), the sentence â€œMy social security number is 123-45-6789 and I make $1,000,000 per year,â€ after redaction, is segmented into multiple sentence fragments separated by the inserted rectangles. As mentioned previously, the redacted content could also have been replaced with alternate neutral content such as â€œî¢ â€ . A similar sentence segmentation (not shown) is performed to redact the comment â€œI can't believe you make $1,000,000 per year!â€ stored in the comments.xml file.

FIG. 5B shows the redacted ED, as displayed to a user authorized to view the sensitive data items (504B). Because the user is authorized to view the sensitive data items, only the content between the <Choice Requires=â€œdecryptionâ€ > and </Choice> OOXML tags is rendered. Accordingly, during the rendering, the encrypted version (shown as <<ENCRYPTED DATA STREAM>> in FIG. 5A, 506) is decrypted to produce the sensitive data item in plaintext, which appears in the rendered version of the redacted ED. Note that the decrypted markup language content (508) is identical to the original markup language content of the original ED, as shown in FIG. 4, (406), enclosed by the box having a dashed perimeter.

Various embodiments of the invention have one or more of the following advantages: the ability to generate redacted EDs where all instances of sensitive data items have been replaced with neutral data items and an encrypted version of the sensitive data items; the ability to render the redacted ED different ways for different users, where sensitive data items are displayed in plaintext to authorized users while the neutral data item is displayed to non-authorized users; the ability to generate a redacted ED that is in the same file format as the original ED; the ability for users to redact an ED without any knowledge of the markup language used in the ED; the ability to maintain the layout of the ED even though the sensitive data items are replaced with neutral data items; the ability to fragment displayed text in order to accommodate the inserted neutral data items; the ability to replace sensitive data items in files or portions of the ED other than the main body text (e.g., comments, etc.); the ability to redact sensitive data items in an ED that is compatible with multiple versions of one or more rendering engines and thus has redundant portions; etc.

Embodiments of the invention may be implemented on virtually any type of computing system, regardless of the platform being used. For example, the computing system may be one or more mobile devices (e.g., laptop computer, smart phone, personal digital assistant, tablet computer, or other mobile device), desktop computers, servers, blades in a server chassis, or any other type of computing device or devices that includes at least the minimum processing power, memory, and input and output device(s) to perform one or more embodiments of the invention. For example, as shown in FIG. 6, the computing system (600) may include one or more computer processor(s) (602), associated memory (604) (e.g., random access memory (RAM), cache memory, flash memory, etc.), one or more storage device(s) (606) (e.g., a hard disk, an optical drive such as a compact disk (CD) drive or digital versatile disk (DVD) drive, a flash memory stick, etc.), and numerous other elements and functionalities. The computer processor(s) (602) may be an integrated circuit for processing instructions. For example, the computer processor(s) may be one or more cores, or micro-cores of a processor. The computing system (600) may also include one or more input device(s) (610), such as a touchscreen, keyboard, mouse, microphone, touchpad, electronic pen, or any other type of input device. Further, the computing system (600) may include one or more output device(s) (608), such as a screen (e.g., a liquid crystal display (LCD), a plasma display, touchscreen, cathode ray tube (CRT) monitor, projector, or other display device), a printer, external storage, or any other output device. One or more of the output device(s) may be the same or different from the input device(s). The computing system (600) may be connected to a network (612) (e.g., a local area network (LAN), a wide area network (WAN) such as the Internet, mobile network, or any other type of network) via a network interface connection (not shown). The input and output device(s) may be locally or remotely (e.g., via the network (612)) connected to the computer processor(s) (602), memory (604), and storage device(s) (606). Many different types of computing systems exist, and the aforementioned input and output device(s) may take other forms.

Software instructions in the form of computer readable program code to perform embodiments of the invention may be stored, in whole or in part, temporarily or permanently, on a non-transitory computer readable medium such as a CD, DVD, storage device, a diskette, a tape, flash memory, physical memory, or any other computer readable storage medium. Specifically, the software instructions may correspond to computer readable program code that when executed by a processor(s), is configured to perform embodiments of the invention.

Further, one or more elements of the aforementioned computing system (600) may be located at a remote location and connected to the other elements over a network (612). Further, one or more embodiments of the invention may be implemented on a distributed system having a plurality of nodes, where each portion of the invention may be located on a different node within the distributed system. In one embodiment of the invention, the node corresponds to a distinct computing device. Alternatively, the node may correspond to a computer processor with associated physical memory. The node may alternatively correspond to a computer processor or micro-core of a computer processor with shared memory and/or resources.

While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of this disclosure, will appreciate that other embodiments can be devised which do not depart from the scope of the invention as disclosed herein. Accordingly, the scope of the invention should be limited only by the attached claims.