International Business Machines Corporation

Stephen Viselli

Shane Bradley Weeden

Jeffrey Owen Kephart

Diana Joyce Hellman

Wayne B Riley

Josephine F Bayang

Simon Gilbert Canning

Valerio Bellizia

James K MacKenzie

Dillon H Ginley

Attila Kollar

Srinivasarao Siddabattini

Michael Gaertner

Neil Ian Readshaw

Scott Anthony Exton

David Paul Moore

Davin J Holmes

A technique to enforce mobile device security policy is based on a 'risk profile' of the individual device, where the risk profile is fine-grained and based on the types of applications installed on the device, the services they are accessing, and the operation(s) the user granted the device authorization to perform. Thus, the approach takes into account not only the actual applications installed on the device (and those actively in use), but also the services those applications are accessing, and the scope of operations the user has granted the device authorization to perform. By combining this information to create the risk profile, a suitable security policy, including one that does not unnecessarily degrade device usability, may then be applied.

Mobile device security policy based on authorized scopes

Power usage is estimated in a computing environment by automatically detecting hardware configuration information by use of a software agent that is translated into power consumption information for implementing a plurality of power estimation models for efficient power consumption and utilization.

Estimating power usage in a computing environment

An approach is provided to access resources at legacy systems. In this approach, a resource request destined to a legacy system is receiving from a requestor with the resource request including an access token and being on behalf of a resource owner. A validation process is performed on the access token. If the access token is valid, the approach identifies the resource owner and one or more legacy access tokens used to access the legacy system. Another request is formed with the new request including the legacy access tokens. The new request is transmitted to the legacy system and a response is received back from the legacy system. The response received from the legacy system is transmitted back to the requestor.

Propagating delegated authorized credentials through legacy systems

An approach is provided where an HTTP request is received and a Request for Security Token (RST) is created. Parameters are selected from the request and mappings are retrieved corresponding to the parameters. Context attributes are created in the RST corresponding to the parameters. A context attribute type value is set based on an HTTP section where the parameter is located within the HTTP request. The RST is sent to a security token service for processing. In another approach, a Request Security Token Response (RSTR) is received and an HTTP response is created. RSTR parameters are selected and parameter mappings are retrieved corresponding to the selected RSTR parameters from a mapping table with a TYPE value being identified based on the retrieved parameter mapping. Context attributes are added to the HTTP response based on the identified TYPE values. The HTTP response is transmitted to a remote computer system.

Transforming HTTP requests into web services trust messages for security processing

Growing community of inventors

Southport, Australia

Stephen Viselli