Patent Application
20200257826
The evolution of the web has brought content submissions to the forefront of public online services. User submissions including comments, status updates, images, and the like are now commonplace in virtually all public online services, including social networking sites, online news articles, and blogs. A vast majority of material is now provided by end-users rather than webmasters. As a webmaster, one has the ability to modify or remove content at will, or to reserve access to a select community of viewers. An end-user user posting into a web service, however, normally gives up all these rights as soon as the content is uploaded.
Users of a public online service who share content on the site can create serious risks to their own privacy. Not only do social networking site users face privacy concerns with respect to the social network site itself having access to, and possibly ownership of, content posted by its users, but third party applications and advertisers integrated/linked into the social networking site may also have access to such content. Social networking site APIs can allow integration of third-party software and give third-party developers access to user data. While these open interfaces enable site enhancements, there is an important privacy trade off, which many site users do not appreciate. Thus, social networking sites can pose serious privacy risks to their users by exposing user data to third-party developers and advertisers. To allay fears of privacy violations, some social networking sites provide users with some access control settings to place restrictions on who may view their personal information. The introduction of open APIs to social networks, however, enables such access control preferences to be circumvented, thus making user data vulnerable to data mining and other privacy issues.
Systems and methods may be provided in which end-users may encode (e.g. encrypt, mask, transform) content posted to a public Internet service. The systems and methods may enable end-users to control a policy that governs access to that content. Private data posted by end-users on public networks, such as social networking sites or publishing sites that allow end-users to post comments, may be encoded by the posting end-user. A browser plugin may be provided on a client system to encode the posted data before it is available online and automatically decode the encoded posts into clear text for those viewers that are granted the key. In this way, data security and data control may be provided for end-user posting online. Access to the posted data may be restricted to a select group of viewers. Data that has already been posted may be destroyed, for example, by deleting the decryption key.
Content, such as a written post or image, is often submitted through a form hosted in a tool such as a web browser. Examples include the comment forms made available with most blogs, the Google Gmail web interface or Facebook.
A privacy agent (or software plugin/client or engine) may be provided to intercept a post prior to the post being posted/effectuated. In this way, the content to be posted can be intercepted and then encoded/encrypted before it is uploaded and, then decoded/decrypted, according to a given policy, prior to being rendered. No changes are introduced to the network infrastructure or the hosted web service
An end-user equipped with the privacy agent may select to encrypt the contents of a specified form field after supplying the content, but before instructing the hosting tool (such as a web browser) to deliver the content to the web service. Along with the instruction to encrypt, the end-user may identify the policy server and policy that will govern the content to be posted. The end-user may have an account with the policy server where he or she may establish, and later modify, content access policies.
The privacy agent may contact the policy server and log in, given the end-user credentials. The indicated policy may be fetched and along with it, the content encryption key. This communication may be cached for re-use or made automatic with device identity as is common in phones.
The privacy agent may encrypt the content and tag it with a recognizable identifier, the address of the policy server, and the policy identifier. This encrypted package may be prepared in a manner that is likely to be accepted by the server. For example, textual content could be rendered into hexadecimal ASCII code surrounded by a header structure. The encrypted content may then be delivered to the web service.
The web service may deliver the encrypted content to a rendering environment likely with no knowledge that it has been altered or needs further processing. However, the same privacy agent running in the rendering environment may parse the content prior to display and identify segments that are to be decrypted by means of the recognizable identifier.
The policy server and policy identifier may be extracted from the content. The policy server may be contacted to request a decryption key. If terms of the policy are satisfied, the decryption key may be delivered to the privacy agent, which may then decrypt the content and replace the encrypted blog with the cleartext. To the end-user rendering the content, this process can be invisible.
Systems, methods and computer apparatuses for controlling digital content may be provided that use an external or third party key server to control access to decoding keys. The third party key node may be controlled by an independent entity that has sovereign control over access to the decoding keys. An encoded version of input field content in an electronic document may be decoded at, for example, a node attempting to view a decoded version of the input field content. A decoding key to facilitate decoding of at least portions of the encoded version of the input field content in the electronic document may be requested. A universal resource identifier (URI) reference to the decoding key may be received from a policy node. The URI reference to the decoding key may be used to request access to the decoding key from a third party key node to facilitate replacement of at least portions of the encoded version of the input field content with a decoded version of the input field content.
The encoded version of the input field content may be an encoded form of input, which is received at an input field in the electronic document. The electronic document may be a webpage.
The URI reference to the decoding key may be transmitted from the policy node in response to a request from the viewing node to access the decoded version of the input field content in the electronic document. The policy node may receive the viewing node's request to access the decoded version of the input field content. The policy node may process session attributes about the viewing node to verify its credentials to determine whether it is authorized to view the decoded version of the input field content. The policy node may respond to the viewing node's request to access the decoded version of the input field content by transmitting a message to the viewing node, including the URI reference to the decoding key at the third party key node. The message, which includes the URI reference to the decoding key, is transmitted to the viewing node in response to the policy node verifying the credentials of the viewing node and determining that the viewing node satisfies the terms of a decoding policy associated with the input field content. The decoding policy may specify at least one group having one or more users that is permitted to access the decoded version of the encoded input field content.
The URI reference to the decoding key may enable decoding at the viewing node of only a portion of the encoded input field content, while other portions of the input field content can remain encoded. The URI reference to the decoding key may be a link to the decoding key at the third party key node. The URI reference to the decoding key may permit only the viewing node to access the decoding key at the third party key node.
A client application, such as a privacy agent, that is executing at the viewing node may respond to receipt of the decoding key by: (1) accessing a document object model (DOM) tree associated with the electronic document to modify and replace instances of the encoded version of the input field content with the decoded version of the input field content; and (2) directing a browser to draw the modified electronic document at the viewing node.
The systems/apparatuses/methods for controlling digital content may include a viewing node that has one or more processors configured to process an electronic document having an encoded version of input field content. The system may include a policy node that is in communication with the viewing node. The policy node may have one or more processors configured to facilitate determining whether the viewing node satisfies terms of a decoding policy associated with the encoded version of the input field content in the electronic document. The system may include a third party key node that is in communication with the policy node and the viewing node. The third party key node may have one or more processors configured to respond to a request from the viewing node to access a decoding key that decodes the encoded version of the input field content if the viewing node satisfies terms of a decoding policy.
A policy node system may receive, from the viewing node, a request for a decoding key to facilitate decoding of at least portions of an encoded version of the input field content in the electronic document. The policy node may respond to the request by the viewing node by transmitting a universal resource identifier (URI) reference to the decoding key. The URI reference may be used by the viewing node to access the decoding key, which facilitates decoding of at least portions of the encoded version of the input field content.
A third party key node system may receive, from a viewing node, a request for a decoding key to facilitate decoding of at least portions of an encoded version of the input field content in the electronic document. The third party key node system may respond to the request by forwarding, to the viewing node, the decoding key to facilitate decoding of at least portions of the encoded version of the input field content.
Systems, computer apparatuses, and methods may be provided to identify and encode accordingly portions of digital content, while other portions of the digital content remain in the clear. Input field content in an electronic document may be processed. A request to encode portions of the input field content in the electronic document may be detected if, for instance, an encoding marker (e.g. tag) is detected in the input field content. The encoding marker may define the portions of the input field content, which should be encoded. The encoding marker may be a string of characters. The string of characters may be any string of characters, for example, “@@”. The encoding marker in the input field content may defines which portions of the input field content are to be encoded via a start encoding tag and an end encoding tag. The portion of the content to be encoded may be the content in between the start encoding tag and the end encoding tag. The content outside of the start encoding tag and the end encoding tag may be ignored, and thus, not encoded.
The system for encoding portions of digital content may include a privacy agent that is executing on a client machine. The privacy agent may process input field content to try to detect the encoding markers, which defines the portions of the input field content that are to be encoded. The portions of the input field content defined by the encoding marker(s) may be encoded by the privacy agent.
The foregoing will be apparent from the following more particular description of example embodiments of the invention, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating embodiments of the present invention.
A description of example embodiments follows.
The teachings of all patents, published applications and references cited herein are incorporated by reference in their entirety.
Example features of embodiments disclosed herein may be implemented in a software or hardware environment. One such environment is shown in
When the webpage is requested from the service provider 104, the browser typically collects all the images (including the page structure) and stores this data in the browser cache. The browser renders the webpage and, before the browser draws the page such that it would be visible on the display of the publisher node 102, it raises an event indicating that the browser is about to draw the page. The inventive system 100 includes a client application (browser plugin) 300 that provides a listener, which listens for this event to detect when the browser is about to draw the page.
Referring to
The client 300 assigns a unique post ID and an event handler (e.g. an onChange event/blur event handler) to each input field identified. The onChange event can be fired when the content of an input field changes. The handlers that are assigned to each input field are added to the webpage's DOM. Once the unique post IDs and event handlers have been assigned to the input fields, control is then passed back from the client 300 over to the browser and, the webpage is allowed to be drawn by the browser. Once the browser has resumed control over the webpage, the client 300 monitors the webpage and its associated contents in the background, waiting for the onChange events to be fired. The client 300 monitors the page to detect the situation where the publisher 102 inputs digital content into an input field on the webpage and then the system 100 responds by encoding/encrypting the input. The encoded content is then forwarded to the service provider 104 for posting/loading on the page.
At 622, the onChange event is fired when the content of an input field changes (e.g. the field blurs). Specifically, once the client detects that the publisher's curser exits the field (e.g. loses focus/blurs), the onChange event is fired and detected by the event handler. In response to detecting an onChange event, at 626 components of the system 100 determine an active policy associated with the input field. In one example implementation, the policy server 108-1 receives the unique identifier and the viewing node's 110 credentials/session information, and in response three pieces of information are generated (ID for post 628, decoding key or a URI to the key, and a link to a preexisting policy for decryption). The policy is a collection of terms that need to be satisfied. While the example of
At 630 and 632, the policy server 108-1 stores the assigned key and the post ID associated with that input field. At 636-640, the digital content (e.g. cleartext) is replaced in the webpage's DOM-tree with the encrypted content and the post ID. The browser is then instructed to draw that portion of the page (at the location of the input field) with the encrypted text and post ID. The user(s), e.g. the publisher 102 (and any viewer(s) 110), will see encrypted text once it is posted. In this way, each input field detected represents a unique postable item and, for each input field detected, a unique identifier/tag is assigned and a key is generated that is associated with that identifier, which can enable the system 100 to identify that field and encrypt digital content that has been input into the page through that input field.
With publishing (encrypting text/image/video content), the browser fires the event and the listener detects the event. With viewing the page at, for example, a viewing node 110, this process occurs in reverse in that the listener is fired before the page is drawn/rendered by the browser. Instead of searching for input fields as described in
In
Preferably, the encoded content tag 1306-4 and the post ID 1306-3 are strings of characters that do not include browser instructions or code (e.g. any markup or scripting code for displaying web pages). The encoded content tag 1306-4 and the post ID 1306-3 can be inserted by the client 300 into the webpage source code as text content during the publishing/posting process. During the rendering/viewing phase, the encoded content tag 1306-4 and the postID 1306-3 are processed and displayed in the webpage as text. Because the encoded content tag 1306-4 and the postID 1306-3 do not include any HTML/scripting instructions, the encoded content tag 1306-4 and the postID 1306-3 are ignored by the browser engine and, processed by the browser as text elements appearing on the webpage.
The post ID 1306-3 provides instructions for the client 300 regarding the protocol that should be used to interpret/handle the encoded digital content that follows the post ID 1306-3. For example, the post ID 1306-3 may be used to look up the policy associated with the encoded content 1306-2, or may be used to inform the client application 300 that there are Unicode characters in the encoded post.
Referring back to
If the terms of the policy are satisfied at 814, then the decoding key or the universal resource identifier (URI) to the key is sent to the viewing node 110 so that the encoded item may be decoded at 818. At 820, the encoded content (cloaked text or tag) is replaced with the decoded content and the page is displayed by the viewing node 110 at 822. If the terms of the policy are not satisfied, then at 814 the error text is displayed. Specifically, at 816 the cloaked item is replaced with the error text. The error text may be any kind of content. For example, the error text may be content that is displayed as unreadable; it can be advertisements, an image, a URL, or defined text, e.g. “I do not like you.” The error text may be customized content specified in the policy terms.
It should be noted that in one example of the tokenized embodiment, instead of displaying the error text, the body of the element (or a pointer to it) is returned since the page contains the id of the cloaked item.
By introducing third party nodes in the system 100, the policy server 108-1 may defer to an external system (e.g. other third party policy node for further handling/processing). The third party node may customize the policy terms and/or perform key management to address privacy laws and/or as privacy concerns of any entity (e.g. governments, organizations, or businesses) who may have an interest in maintaining control of policy terms and/or keys for the content that is posted, uploaded or transmitted. In this way, a sovereign third party policy server can be used to control access/define access terms to the encoded content, and a sovereign third party key factory can be used to provide independent control of key issuance and/or maintenance.
A user can define a policy that defers to an external policy or key server. In defining this policy, the user can specify the URI of the external server(s) to which they want the policy server 108-1 to redirect. This URI redirection to an external node can become a term of the policy by which encoding/decoding decisions may be controlled.
When an encoded content tag is identified, the client application 300 extracts the post ID and passes it to the policy server 108-1. The policy server 108-1 looks-up the policy associated with the post ID. The policy server 108-1 processes the policy terms to determine if the policy conditions have been met. For example, the policy server 108-1 may process the viewing node's 110 login credentials (login/password), geographical location of the viewing node 110, session variables, cookies, etc., and it may use any of this information to test against the policy terms.
In the example of
Based on the results of the policy test, the third party policy server 108-2 may transmit a message to the policy server 108-1 regarding its decision as to whether the encoded post can be viewed in its decoded state at the viewing node 110. The third party policy server 108-2, for example, may send a pass or fail message indicating its decision. Depending on the instructions received from the third party policy server 108-2, the policy server 108-1 may transmit to the client 300 the key/cipher/token to enable the client 300 to decode the encoded content. If the client 300 satisfies the policy terms, the client may then receive or generate the decoding key. Once the client has the key, the client 300 decodes the encoded content and traverses the webpage's DOM tree to replace the encoded content with the decoded content, which enables the browser to display the decoded content at the viewer node 110. In another optional implementation, instead of having the client 300 interface with the policy server 108-1 alone, the policy terms may have policy server 108-1 instruct the client 300 to redirect the session so that the client 300 can interface directly with the third party policy server 108-2.
When the client 300 detects that publishing node 102 has entered one of the editable input fields in the webpage, the client 300 determines an active policy associated with the page, and transmits the post ID associated with the input field and requests a key from an external key node (e.g. keyfactory) 108-3. The key node 108-3 returns a uniform resource identifier (URI) to the policy server 108-1, which is registered at the policy server 108-1. The key URI may include a string of characters that can be used to identify/locate the key at the external key node 108-1. In this way, the key/cipher/token itself does not pass through the policy server 108-1. Rather, the URI to the key is registered at the policy server. With this arrangement of
The key URI may include a uniform resource name (URN) and/or a uniform resource locator (URL) associated with the key at the external key node 108-3. If the publishing node 102 (now operating as a viewing node 110) satisfies the terms of the policy, the policy server 108-1 sends the key URI and an authorization/access signature (unique one time token), which authorizes the viewing node 110 to access the external key server 108-3 through the key URI. With the external key node 108-2, instead of the client generating its own key or the policy server 108-1 generating the key (which are other possible optional implementations), the third party key node 108-2 generates the key, and a URI reference to the key is stored at the policy server 108-1.
While
The client 300 may include a parser 312, an extension manifest component 314, a transformation engine 318, and a preference settings component 316. The parser 312 may be used to process a webpage to detect any unique postable item (e.g. text input fields or other image/video content for encoding—publishing) and to parse the webpage for encrypted/encoded/tagged text (viewing). The unique postable item/content may be any user-entered and user-controlled text/image/video content that is to be cloaked/encrypted/encoded.
The extension manifest 314 may provide a specific structure for the browser that enables events to be declared. For example, an onload event handler can be defined that detects when the electronic document/webpage is loaded (e.g. detects when an onload event is fired); in this way, the client 300 can detect when the webpage is being loaded so that it can process the page for text input fields or other fields that allow for the creation of unique postable items. The transformation engine 318 may facilitate changing cleartext into encrypted/encoded/tagged text (or unencoded content into encoded content).
The client 300 may include a toolbar interface for a browser.
The toolbar interface may be provided to facilitate encoding/decoding for the user environment (e.g. publishing/viewing). The publishing/viewing nodes may interact with a policy server environment to facilitate encryption/decryption of content by processing the terms of the policy.
The ecommerce gateway 220 may provide billing and invoicing services for the publisher 102 and viewer 110. The post tracker 250 records or tracks posts made by the publisher 102. The analytics 260 component facilitates analysis/reporting of the records recorded by the post tracker.
The directory interpreter 412 can interface with other external components/directories to configure policy access terms for a post. The policy may be defined to deliver access to specific users identified in some third party system, such as a corporate directory or online contacts list and, the directory interpreter can be used to interface with these third party systems. For example, the publisher may want to restrict viewing access to the publisher's Facebook friends. The directory interpreter 412 may be used to help implement this portion of the policy by inputting (importing) the publisher's Facebook friends. In this way, group access can be created.
The policy enforcement interface 416 may be used to interface with the client 300 at the viewing/publishing node(s). For example, if a publishing node is attempting to encode a post, the client 300 may pass a post, an ID for the post, and a key to the policy enforcement interface 416 for processing at the policy node 108. In one example embodiment, the policy node 108 may be an automated key management server.
The policy node 108 may also confirm that a viewing node attempting to access contents of an encoded post meets the terms for the post ID associated with that item. If the terms are met, then the policy node 108 may return the key. If the terms are not met, then the request for the key may be denied. If the key is returned, then the encoded posts are swapped out for the cleartext at the viewing node. The encrypted text is therefore transformed into cleartext.
The policy may be configured so that viewer access is limited to viewers having a rendering environment that is a trustworthy. For example, if the policy node 107 is able to confirm that the viewing node is trustworthy, the policy node 107 can ensure that the decryption key is likely not to be compromised, stored or redistributed. For example, the viewing node may be considered trustworthy if it has a trusted hardware environment, such as a trusted platform module.
An end user's account may be configured so that it is associated with another user's account (e.g. cosigned/guardian/parental account). The cosigned account may be arranged so that it has preemptive rights to override posting decisions or policy configuration decisions made by the end user. These preemptive rights associated with the cosigned account may be hidden from other users and from the end user. For example, an end user's account may be configured so that additional user(s), such as a parent or co-signatory have override control over the encoding/decoding status of content. The parent/co-signatory may have the ability to override the policy associated with a post made by, for example, an end user who is a minor. The parent/co-signatory may have control over whether the minor user can published certain content and, whether such content is encoded/decoded for a group of users. This feature may uniquely allow, for example, a co-signatory/parent to have control over whether his/her child's social networking posts are encoded or decoded.
The system may have a setting enabling the cosignatory/parent to specify that all posts made by the child online are to be encoded. The system may enable the cosignatory/parent to control which users are granted key access to view the encoded posts as cleartext. For example, the cosignatory/parent may be able to preemptively specify that all posts made by the minor user may only be decoded by a closed group. This preemptive cosignatory/parent account may facilitate compliance with Child Online Protection Act (COPA) requirements.
Further, the parent/cosignatory may be able to configure the minor user's account so that it is not apparent to the group (or any other users) that the policy decisions associated with the minor's account are controlled by a parent/cosignatory. This hidden status associated with the parent/cosignatory account may be a feature that can be enabled so that it appears as though the minor user is operating independently without any preemptive control by another user. In this way, the parent/cosignatory may have rights that supersede the rights of the minor user, while the parent/cosignatory operates in a manner that appears invisible to other users.
Accounts associated with the system may be configured so that a second party, such as an enterprise or other controlling entity, has control over the publishing status of posts made by users from within its domain. A domain of accounts may be determined based on the identity of the account. For example, if the domain is “wave.com”, then users with an @wave.com address fall into the domain automatically.
While being in a domain does not necessarily equate to being in a group, by default, a new enterprise account may have an associated group defined which matches that of the domain. If, for instance, an enterprise account is “EndUser@wave.com”, the account settings may be configured such that all users from the same domain, i.e. “from @wave.com” are granted access to decoding keys to view EndUser@wave.com's posts in the clear.
While the embodiment of
In one embodiment, the plug-in 300 can be configured so that it is always on. In this way, for example, any publishing activity by a user node can be subject to the policies defined by controlling entity, e.g. enterprise, employer, or guardian. The enterprise/employer/guardian can configure a user's account with a failsafe to ensure that the plug-in is always on when the user is logged-in to the system 100 or when a certain computer system is used by the user.
In an example enterprise/employer implementation, the controlling entity may configure the policy so that the plug-in 300 executes and cannot be turned off during a specific timeframe. For example, the controlling entity may specify that all posts made by a user to external sites are encoded during working hours (e.g. from 9 AM-5 PM). While during non-working hours, the encoding status of posts may be defined by the user. This time sensitivity configuration may be useful if the user has a company laptop, for example, that they are permitted to take home after working hours.
In the conventional online publishing environment, a user at a publishing node 102 who posts a comment to a third party site 104 is typically unable to obtain analytics information concerning the post. For example, the publishing user may be unable to find out information concerning other users who have viewed the post, where the other users are located, where the click path taken by the other users after viewing the post. Such analytics information is typically unavailable to the posting user unless, for example, the third party site provides the information.
With the present disclosure, a system 100 may be provided that may enable a user who publishes a post on a third party site 104 to control who has access a decoded version of the post and determine analytics data associated with the those viewers who accessed the decoded version of the post. The publishing user (e.g. author of a post/comment on a third party site) may be provided with analytics information concerning the viewers of its post, without the third party site's knowledge or control. An aggregate view of traffic accessing/viewing the post may be provided to the publisher. With the present system 100, for example, the publisher may be provided with analytics information concerning the number of viewers that rolled over the post, the number of viewers that successfully view the post, and the number of viewers that were rejected and thus, unable to view the post. In this way, if the publisher/user encodes his or her post/comment when it is published at a third party site, the user is able to monitor traffic accessing the post/comment, including information about who are the visitors, IP geolocation of the visitors, and the number of views. Access to this information helps gauge traffic and popularity trends which is useful information previously unavailable to most users who post on third party sites 104.
The publishing user may configure the policy associated with an encoded post to specify that analytics data should be gathered. The policy, for instance, may be configured so that if the encoded post is decoded by a viewing node 110, an alert may be generated to notify the publishing user about the analytics details concerning the viewing node who viewed the decoded post.
Portions of posted content may be encoded. For example, portions of a body of text in posts/messages may be encoded, while other portions of are intentionally left in the clear. One such example is shown in
Further, a policy associated with the post may be configured to allow tiered access for user(s)/group(s) to the decoding keys for the post. In particular, certain user(s)/group(s) may be granted access to a decoding key to reveal subsets of the encoded content, while other user(s)/group(s) may be granted access to a decoding key that decodes all of the encoded content.
Users that post at a third party site 104 typically do not have a mechanism enabling them to charge users to view the post. With aspects of the present disclosure, a monetization scheme may be provided to such a user by allowing the user to define a policy associated with the post that requires prospective viewers to pay a fee for decoding key access. Users that desire to view decoded posts/comments published at a third party site, may be required to pay a fee for the decoding key. For example, a user having a Facebook or Twitter page, may define a policy that requires viewers to pay for key access so that the viewers may view decode a post. This monetization scheme may be further enhanced by the technology described herein, which encodes portions of a post. In this way, if a publishing user encodes a portion of their post and uses the unecoded portion of the post as a teaser to entice viewers to request/pay for access to view the entire post in the clear. A viewer interested in viewing the entire post may, for example, click on the encoded portion to create an account through the account manager 500 and/or login to the system 100, and then execute a payment transaction in exchange for a token (key/cipher) to view the encoded portion of the post. The transaction may be processed by components of the system 100 using a communications network (credit card network, debit card network, or private label network).
There are a plurality of potential approaches to encoding the data. One example approach is transformation, which involves encoding the content prior to its posting to a third-party web service (service provider 104). In one embodiment, the client 300 may be designed with an open architecture platform so that third parties have the ability to insert their own transformation engine 318. Another potential approach is tokenization, which involves posting a pointer to the content and keep the content on the, for example, policy nodes/servers (or somewhere else).
With transformation, one uses a scheme which can be resilient as the external web service 104 will handle the data like normal text and try to format it. One benefit to transformation is that policy server (or other system) may be configured so that it is not responsible for storing the post and, therefore, it is not responsible for all the data storage.
With tokenization, an external site receives an id, and that id provides a pointer to the encoded (tokenized) content, which can be stored at another node (e.g. a storage node, the policy server node, or on another system, such as a peer-to-peer network). One example benefit with tokenization is that the content may be individually managed; for example, an unwanted post may be easily removed by deleting the pointer (token). In one example preferred implementation, one would apply encryption to the content before it is uploaded to another node to provide additional safeguards to protect the data.
In some implementations, tokenization may be more resistant to cryptanalysis, such as to attacks. For example, the crypto may be more difficult to guess since one would not need to maintain size and word structure. Further, the integrity of the content would likely be complete (e.g. provided that the external server returns back the entire ID, since half an ID string may be inefficient.)
Further, with tokenization, implementation may be provided without modifying existing browser systems. Therefore, browsers can encode/decode using the tokenization approach with or without a plug-in interface.
A variation on tokenization may involve embedding an ID in English. A paragraph long sequence of real words, for example, may provide enough variation to represent a unique ID. With this configuration, it is possible that the token may be undetectable by external servers.
Users may be use the system 100 to ensure that they are able to uncloak content after the encoded version of the content has been posted to a web service 104.
A mobile agent implementation of the invention may be provided. A client server environment on which to enable mobile security services may be implemented including features of the invention. It uses, for example, the XMPP protocol to tether a background cloaking agent/client on the device to a server (e.g. 108-1, 108-2, 108-3). The server can then issue commands to the phone on request.
Embodiments of the security/cloaking schemes of the inventions may be implemented using self-encrypting drives. Such security schemes may be used to help protect against data loss due to a lost or stolen PC. The Trusted Drive Manager software activates the security that distinguishes a self-encrypting drive from a standard hard drive. Examples of such technology are described in, for example, U.S. Pat. Nos. 7,036,020 and 7,426,747, the entire contents of which are incorporated herein by reference.
Continuing from
In one embodiment, the processor routines 92 and data 94 are a computer program product (generally referenced 92), including a computer readable medium (e.g., a removable storage medium such as one or more DVD-ROM's, CD-ROM's, diskettes, tapes, etc.) that provides at least a portion of the software instructions for the invention system. Computer program product 92 can be installed by any suitable software installation procedure, as is well known in the art. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In another embodiment, at least a portion of the software instructions may also be downloaded over a cable, communication and/or wireless connection. In other embodiments, the invention programs are a computer program propagated signal product 107 embodied on a propagated signal on a propagation medium (e.g., a radio wave, an infrared wave, a laser wave, a sound wave, or an electrical wave propagated over a global network such as the Internet, or other network(s)). Such carrier medium or signals provide at least a portion of the software instructions for the present invention routines/program 92.
In alternate embodiments, the propagated signal is an analog carrier wave or digital signal carried on the propagated medium. For example, the propagated signal may be a digitized signal propagated over a global network (e.g., the Internet), a telecommunications network, or other network. In one embodiment, the propagated signal is a signal that is transmitted over the propagation medium over a period of time, such as the instructions for a software application sent in packets over a network over a period of milliseconds, seconds, minutes, or longer. In another embodiment, the computer readable medium of computer program product 92 is a propagation medium that the computer system 50 may receive and read, such as by receiving the propagation medium and identifying a propagated signal embodied in the propagation medium, as described above for computer program propagated signal product.
Generally speaking, the term “carrier medium” or transient carrier encompasses the foregoing transient signals, propagated signals, propagated medium, storage medium and the like.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including JavaScript, XML, Java, Smalltalk, C++, C# or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer as a browser plugin, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed.
While this invention has been particularly shown and described with references to example embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the invention encompassed by the appended claims. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein. For example, the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
Further, although Unified Modeling Language (UML) drawings (e.g. use case diagrams, etc.) have been used in some of the figures to model and/or describe example features of the inventions described herein, these drawings are for purposes of illustration and do not constrain the implementation of the inventions to any particular hardware or software implementations.
The service provider 104 can be, for example, any type of service provider that hosts electronic documents. Example service providers may include news/media service providers, such as CNET, or any social networking service providers, such as Facebook, Twitter, LinkedIn, and the like. Further, although certain embodiments herein use encryption keys/ciphers, one skilled in the art of cryptology would understand that other forms of encryption processes can be used, such as codebook based encryption. Further, it should be understood that content encoded using the systems of the present disclosure may be “nested” in that they may be encoded again to provide for additional protection.
Furthermore, although some figures have been described with reference to the viewer 110 and the publisher 102, one skilled in the art would understand that in some situations, the viewer 110 and the publisher 102 nodes may be operated by the same user.
This application is a continuation-in-part of U.S. application Ser. No. 13/295,686, filed Nov. 14, 2011. This application is related to U.S. patent application Ser. No. ______, entitled “Security Systems and Methods for Encoding and Decoding Digital Content” by Steven Sprague and Michael Sprague, filed Sep. 11, 2012. The entire teachings of the above applications are incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15954089 | Apr 2018 | US |
| Child | 16806304 | US | |
| Parent | 14689965 | Apr 2015 | US |
| Child | 15954089 | US | |
| Parent | 13610657 | Sep 2012 | US |
| Child | 14689965 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13295686 | Nov 2011 | US |
| Child | 13610657 | US |
