Abstract: Embodiments provide systems and methods configured to mine information available from informal sources (e.g., social media, blogs, and forums) regarding security vulnerabilities. Particular embodiments may comprise engine(s) of a backend in communication with a user through an interface of a frontend, and also in communication with an underlying database to store security information and related information (e.g. search parameters). Embodiments may allow creation of user-specific search phrases for searching information in one or more informal social media information sources. Search results may be consolidated, and users such as system administrators quickly alerted to possible security issues. Embodiments may refine data mining over time by tracking the reputation (e.g. for data accuracy, freshness) of various sources. Embodiments may also reference formal official and third party sources of security information.

Abstract: The embodiments provide a data processing apparatus including a runtime check identifier configured to determine, in response to a request to execute a function of the application, whether a runtime check descriptor corresponding to the function is stored in a database and select the runtime check descriptor if the runtime check descriptor is determined as stored in the database. The selected runtime check descriptor provides, in part, at least one configuration check of a component related to an execution of the function. The data processing apparatus also includes a system component configured to invoke a system management tool to perform the at least one configuration check, and a runtime check controller configured to receive results of the at least one configuration check and perform at least one action specified in the selected runtime check descriptor based on the received results.

Abstract: Embodiments include a system for tracing a collaborative workflow. The system includes an event collector and a transition engine. The event collector may be configured to receive data that represents an event of the collaborative workflow. The collaborative workflow has a local workflow part and a global workflow part. The transition engine may be configured to compute a new instance state of a model of the collaborative workflow. The new instance state represents an instance of the collaborative workflow obtained through the event of the collaborative workflow. The new instance state complies with rules of a local model of the local workflow part and with rules of a global model of the global workflow part.

Abstract: Implementations of the present disclosure include methods for generating a configuration checklist template. In some implementations, methods include retrieving one or more source code files, each of the one or more source code files corresponding to a software product, scanning the one or more source code files to generate one or more configuration check building blocks, receiving first user input, processing the one or more configuration check building blocks and the first user input to generate one or more check definitions, receiving second user input, processing the one or more check definitions and the second user input to generate the configuration checklist template, electronically storing the configuration checklist template, and transmitting the configuration checklist template to one or more computing devices associated with a customer entity over a network.

Abstract: The present disclosure is directed to comparing a first structured data document to a second structured data document, including receiving the first and second structured data documents as first and second encrypted documents, respectively, comparing nodes of the first encrypted document to nodes of the second encrypted document, a content and a location of each of the nodes remaining confidential during the comparing, generating matched pairs of nodes based on the comparing, and storing the matched pairs in computer memory, each matched pair comprising a node of the first encrypted document and a corresponding node of the second encrypted document, determining one or more edit operations based on the matched pairs, and generating an edit script comprising the one or more edit operations, the edit script being executable to transform the first encrypted document to provide a transformed encrypted document that is isomorphic to the second encrypted document.

Abstract: The embodiments provide a data processing apparatus including a runtime check identifier configured to determine, in response to a request to execute a function of the application, whether a runtime check descriptor corresponding to the function is stored in a database and select the runtime check descriptor if the runtime check descriptor is determined as stored in the database. The selected runtime check descriptor provides, in part, at least one configuration check of a component related to an execution of the function.

Abstract: Implementations of the present disclosure include methods for generating a configuration checklist template. In some implementations, methods include retrieving one or more source code files, each of the one or more source code files corresponding to a software product, scanning the one or more source code files to generate one or more configuration check building blocks, receiving first user input, processing the one or more configuration check building blocks and the first user input to generate one or more check definitions, receiving second user input, processing the one or more check definitions and the second user input to generate the configuration checklist template, electronically storing the configuration checklist template, and transmitting the configuration checklist template to one or more computing devices associated with a customer entity over a network.

Abstract: The present disclosure is directed to comparing a first structured data document to a second structured data document, including receiving the first and second structured data documents as first and second encrypted documents, respectively, comparing nodes of the first encrypted document to nodes of the second encrypted document, a content and a location of each of the nodes remaining confidential during the comparing, generating matched pairs of nodes based on the comparing, and storing the matched pairs in computer memory, each matched pair comprising a node of the first encrypted document and a corresponding node of the second encrypted document, determining one or more edit operations based on the matched pairs, and generating an edit script comprising the one or more edit operations, the edit script being executable to transform the first encrypted document to provide a transformed encrypted document that is isomorphic to the second encrypted document.

Abstract: Embodiments include a system for tracing a collaborative workflow. The system includes an event collector and a transition engine. The event collector may be configured to receive data that represents an event of the collaborative workflow. The collaborative workflow has a local workflow part and a global workflow part. The transition engine may be configured to compute a new instance state of a model of the collaborative workflow. The new instance state represents an instance of the collaborative workflow obtained through the event of the collaborative workflow. The new instance state complies with rules of a local model of the local workflow part and with rules of a global model of the global workflow part.