Abstract: A solution is proposed for managing each one of a plurality of computing machines. A corresponding method comprises taking one or more snapshots of the computing machine or part thereof, the snapshots being organized in a snapshot tree of nodes representing the snapshots according to a dependency thereof, expanding the snapshot tree of the computing machine according to each sub-tree of the snapshot tree of each other computing machine having the snapshot of a parent node of the sub-tree matching a graft node of the snapshot tree of the computing machine, the sub-tree being appended to the graft node, selecting a snapshot of the other computing machines represented by a selected node of the snapshot tree of the computing machine, and restoring the selected snapshot on the computing machine.

Abstract: A software patch management solution (200) is proposed. The devised solution is based on the idea of automating the installation of the patches through a software distribution infrastructure. For this purpose, an automation engine (225) is added to a distribution server (110). The automation engine interfaces with a patch provider (125) acting as a proxy, which stores a local copy of the patches (210) and of a patch catalogue (215) for detecting corresponding vulnerabilities. The automation engine automatically builds a distribution plan for deploying the patches to the relevant endpoints (115), according to a vulnerability catalogue (230) that stores the actual exposures of the endpoints. The distribution plan arranges the required activities in the correct order, so as to minimize the number of rebooting of the endpoints; the distribution plan ends with an activity for scanning the endpoints, so as to update the vulnerability catalogue accordingly.

Abstract: Mechanisms for securing dynamic discovery of an enterprise computing infrastructure is provided. One implementation involves maintaining enterprise credential information in a secured trust store, receiving an access request through a secure connection for access to a remote infrastructure component, determining the type of the access request, for a root-level type access request, responding to the request via the secure connection with enterprise root credentials from the trust store, and for an unprivileged type access request, responding to the request via the secure connection with unprivileged access enterprise credentials from the trust store.

Abstract: A software patch management solution (200) is proposed. The devised solution is based on the idea of automating the installation of the patches through a software distribution infrastructure. For this purpose, an automation engine (225) is added to a distribution server (110). The automation engine interfaces with a patch provider (125) acting as a proxy, which stores a local copy of the patches (210) and of a patch catalogue (215) for detecting corresponding vulnerabilities. The automation engine automatically builds a distribution plan for deploying the patches to the relevant endpoints (115), according to a vulnerability catalogue (230) that stores the actual exposures of the endpoints. The distribution plan arranges the required activities in the correct order, so as to minimize the number of rebooting of the endpoints; the distribution plan ends with an activity for scanning the endpoints, so as to update the vulnerability catalogue accordingly.

Abstract: A software patch management solution is proposed. The devised solution is based on the idea of automating the installation of the patches through a software distribution infrastructure. An automation engine is added to a distribution server. The automation engine interfaces with a patch provider acting as a proxy, which stores a local copy of the patches and of a patch catalogue for detecting corresponding vulnerabilities. The automation engine automatically builds a distribution plan for deploying the patches to the relevant endpoints, according to a vulnerability catalogue that stores the actual exposures of the endpoints. The distribution plan arranges the required activities in the correct order, to minimize the number of rebooting of the endpoints; the distribution plan ends with an activity for scanning the endpoints, to update the vulnerability catalogue accordingly.

Abstract: A method and system for securing dynamic discovery of an enterprise computing infrastructure is provided. One implementation involves maintaining enterprise credential information in a secured trust store, receiving an access request through a secure connection for access to a remote infrastructure component, determining the type of the access request, for a root-level type access request, responding to the request via the secure connection with enterprise root credentials from the trust store, and for an unprivileged type access request, responding to the request via the secure connection with unprivileged access enterprise credentials from the trust store.

Abstract: A method for keeping synchronized data collected by a first and at least one second software applications from respective information sources and stored in a respective first and second data repositories. The method comprises: a) receiving a request to refresh data stored in the first data repository; b) causing the at least one second software application to collect data from the respective information source; c) receiving the data collected by the first and the at least one second software applications from the respective information sources, and d) uploading the received data to the respective first and second repositories.

Abstract: A software patch management solution (200) is proposed. The devised solution is based on the idea of automating the installation of the patches through a software distribution infrastructure. For this purpose, an automation engine (225) is added to a distribution server (110). The automation engine interfaces with a patch provider (125) acting as a proxy, which stores a local copy of the patches (210) and of a patch catalogue (215) for detecting corresponding vulnerabilities. The automation engine automatically builds a distribution plan for deploying the patches to the relevant endpoints (115), according to a vulnerability catalogue (230) that stores the actual exposures of the endpoints. The distribution plan arranges the required activities in the correct order, so as to minimize the number of rebooting of the endpoints; the distribution plan ends with an activity for scanning the endpoints, so as to update the vulnerability catalogue accordingly.

Abstract: A method for transmitting information (from a source computer to one or more target computers) is proposed. The solution of the invention applies to a message (300o) that includes a main body (310) with possible attachments (315), each one identified by a corresponding internal link (320i) The attachments including bulk data are removed and placed onto a location (125s) of a distribution service wherein they are available for downloading; at the same time, the internal links of the removed attachments are replaced with external links (320e), which point to the corresponding downloading locations. The resulting compacted message (300c) is transmitted to each target computer directly. The target computer downloads the desired removed attachments (from the locations pointed by the corresponding external links); the message can then be reconstructed by restoring the downloaded attachments.