Abstract: A system and method for establishing application identities including application runtime properties. A method includes signing at least one artifact of a first application communicating with a second application, wherein each of the at least one artifact includes data used for executing the first application, wherein a signing result of each artifact is a signed cryptographic hash of the artifact; monitoring events related to communications between the first application and the second application to identify a file event; generating at least one runtime hash for the file event, wherein the at least one runtime hash represents runtime properties of the first application; and generating an application identity for the first application, the application identity for the first application including the signed cryptographic hash of each of the at least one artifact and the at least one runtime hash of the file event.

Abstract: A method and system for securing instantiates. The method includes determining at least one signable file among a plurality of files of an instantiate, wherein determining the at least one signable file further comprises classifying each of the plurality of files with respect to whether the file is changed at runtime; signing each of the at least one signable file to create at least one first signature, wherein signing the plurality of files further comprises computing a cryptographic hash for each file, wherein each encrypted hash is signed using a private key; and verifying an identity of the instantiate using the at least one first signature, wherein verifying the identity of the instantiate further comprises comparing the at least one first signature to the at least one second signature, wherein each of the at least one second signature is a signature of one of the at least one signable file at runtime.

Abstract: A system and method for establishing application identities including application runtime properties. A method includes signing at least one artifact of a first application communicating with a second application, wherein each of the at least one artifact includes data used for executing the first application, wherein a signing result of each artifact is a signed cryptographic hash of the artifact; monitoring events related to communications between the first application and the second application to identify a file event; generating at least one runtime hash for the file event, wherein the at least one runtime hash represents runtime properties of the first application; and generating an application identity for the first application, the application identity for the first application including the signed cryptographic hash of each of the at least one artifact and the at least one runtime hash of the file event.

Abstract: A method and system for securing instantiates. The method includes determining at least one signable file among a plurality of files of an instantiate, wherein determining the at least one signable file further comprises classifying each of the plurality of files with respect to whether the file is changed at runtime; signing each of the at least one signable file to create at least one first signature, wherein signing the plurality of files further comprises computing a cryptographic hash for each file, wherein each encrypted hash is signed using a private key; and verifying an identity of the instantiate using the at least one first signature, wherein verifying the identity of the instantiate further comprises comparing the at least one first signature to the at least one second signature, wherein each of the at least one second signature is a signature of one of the at least one signable file at runtime.

Abstract: A method and apparatus for controlling at least one executable on a blade server having a controller, which is accessible to the blade server and to at least one blade having access to a storage device in association with the controller. The controller has access to a source snapshot of at least one executable stored on the storage device An available blade is selected for loading an instance of a running snapshot associated with the source snapshot, and the instance of the running snapshot is loaded to the available blade.