Microsoft Technology Licensing, LLC

Sunil Kadam

Sanjeev Dwivedi

Ariye M Cohen

Thomas C Jones

Meir Baruch Blachman

Ziquan Li

Sunil P Gottumukkala

Tomer Cherni

George Li

Nitzan Frogel

Aravind Aluri

Alwin Vyhmeister

Yibing Chen

Mark-Gil Parayno

Varun Eda Naarayana Kulothungan

Saurabh Boyed

Amy Hariharan Dang

Hassan Almandil

Automated and semi-automated document redaction technology is disclosed herein. In certain example embodiments, 'context-aware' redaction is provided. Automated techniques are used to identify a set of potentially sensitive item(s) within a document. The potentially sensitive item(s) are filtered based on contextual information, such an entity identifier (e.g. person identifier, person group identifier identifying a group of multiple people, organization identifier etc.), resulting in a filtered set of redaction candidate(s). The filtered redaction candidate(s) may, for example, be redacted from the document automatically, or outputted as suggestions in an assisted redaction tool, e.g. via a document redaction graphical user interface. Other example embodiments consider selective redaction when uploading and/or downloading documents via a proxy server, to prevent intended or unintended release of potentially sensitive information, e.g. in a web browsing context.

Detection and removal of predefined sensitive information types from electronic documents

A master license entry that links a software application to a user identification can be made. Application licenses to use the software application can be roamed to multiple computing machines. Feature licenses for added features of the software application can be roamed to those computing machines as well. Multiple overlapping license rights for the software application may be linked to the master license entry. A count of how many license rights for the software application are linked to the master license entry can be maintained. Requests for licenses may be refused if the count of license rights has reached zero.

Software application license roaming

For a particular request to access a resource, both a user associated with the request and a service through which the request is made are identified. Whether requested access to a resource is permitted is determined based on a user associated with the requested access and a service through which the access is requested. This determination can be made based on an access control entry of an access control list corresponding to the resource, the access control entry identifying access to the resource that is permitted to the user when accessing the resource through the service.

Access control based on user and service

Techniques involving detection of misuse of digital licenses pertaining to application use. An identification of unsigned applications or other use-protected applications enabled for use at a user device is obtained. The identification of such applications is directed to a licensing authority to seek digital license renewal for using the applications. A renewed digital license is received if the provided identification of use-protected applications corresponds to what is authorized by the licensing authority for use at the user device. In other embodiments, verification information may be provided to protect the identification of unsigned applications from tampering, such as information indicative of whether the identification of unsigned applications originated at the user device in which the use-protected applications are used, and indicative of whether the identification of the unsigned applications is a copy of a previous identification of the unsigned applications.

Licensing verification for application use

One or more techniques and/or systems are disclosed for generating a developer license that allows a developer application to run on developer machine. A user identification (userID) used to register a user can be used by the user to register as a developer. The userID can be authenticated for the registered developer. Further, a machine used by the developer for the developer application can be registered, and a resulting hardware identification (hardwareID) can be authenticated for the registered developer machine. Additionally, a developer certificate can be generated for the registered developer. The developer certificate can be authenticated and used to sign the developer application. The developer license can be generated for the developer, allowing the developer machine to execute the developer application, based at least upon the authenticated userID, the authenticated hardwareID, and the authenticated developer certificate.

Generating developer license to execute developer application

Growing community of inventors

Redmond, WA, United States of America

Sunil Kadam