Bladelogic, Inc.

Emc IP Holding Company LLC

Emc Corporation

Denis Knjazihhin

Chet Birger

Paul A Reilly

David Allen Solin

Dan Uwe Zehme

David Shapiro

Joseph Xavier Lawrence, Jr

Carl Adams

A key manager provides a way to separate out the management of encryption keys and policies from application domains. The key manager may create cipher objects that may be used by the domains to perform encryption or decryption, without exposing the keys or encryption/decryption algorithms to the domains. A master key managed by the key manager may be used to encrypt and decrypt the domain keys that are stored under the control of the key manager. The key manager supports the rekeying of both the master key and the domain keys based on policy. Multiple versions of domain keys may be supported, allowing domains to access data encrypted with a previous version of a domain key after a rekeying.

Multi-level key management

An improved technique involves setting an administrator password in a server to a temporary password upon receipt of a request for administrator access to the server. Along these lines, when a support engineer receives a support ticket from a customer, the support engineer sends a request to obtain administrator access to the customer's server to an access control computer. The access control computer, upon receipt of the request, generates a temporary password that grants the support engineer a one-time administrator access to the server. The access control computer then changes the administrator password on the server to the temporary password and reveals the temporary password to the support engineer. At some time either after the engineer obtains administrator access to the server or after some specified time has passed, the access control computer invalidates the temporary password by changing the administrator password to a different password.

Managing support access in software-as-a-service systems

Systems and methods for stateless system management are described. Examples include a method wherein a user sends the management system a request to act upon a managed system. The management system determines whether the user is authorized for the requested action. Upon authorization, the management system looks up an automation principal, which is a security principal native to the managed system. The management system retrieves connecting credentials for the automation principal, and connects to the managed system using the retrieved credentials. Once the managed system is connected, the management system performs the requested action on the managed system, and sends the result back to the user.

Security context passing for stateless system management

Improved techniques involve marking each test case routine written in the source code with test case identifiers that describe that test case routine. Software in a development system parses source code to locate such identifiers and, upon compilation of the source code, generates a report based on those identifiers. Advantageously, the improved techniques ensure that test cases remain current with the source code.

Growing community of inventors

Brighton, MA, United States of America

Denis Knjazihhin