Bmc Software, Inc.

Bladelogic, Inc.

Bmc Helix, Inc.

Ajoy Kumar

Douglas Mueller

Govindarajan Rangarajan

Narayan Kumar

Darius Wallace

Josie George

Eric Michael Anderson

Matthew Dennis Connors

Mantinder Jit Singh

G S Narayan Iyer

Atanu Neogi

Duncan Paul Grisby

Manish Jain

Smijith Pichappan

Amit Gupta

Priya Saurabh Talwalkar

Somesh Kumar Srivastava

Soumee Phatak

Himanshu Singhvi

Matthew Conners

Brendan Farrell

Saifuddin Fazlehusen Rangwala

Siddharth Sukumar Burle

Information technology service management (ITSM) incident reports are converted from textual data to multiple vectors using an encoder and parameters are selected, where the parameters include a base cluster number and a threshold value. A base group of clusters is generated using an unsupervised machine learning clustering algorithm with the vectors and the parameters as input. A cluster quality score is computed for each of the base group of clusters. Each cluster from the base group of clusters with the cluster quality score above the threshold value is recursively split into new clusters until the cluster quality score for each cluster in the new clusters is below the threshold value. A final group of clusters is output, where each cluster from the final group of clusters represents ITSM incident reports related to a same problem.

Self-optimizing context-aware problem identification from information technology incident reports

A plurality of resolved incident tickets may each include a worklog providing a history of actions taken during attempts to resolve a corresponding resolved incident and a resolution having at least one resolution statement. An iterative processing of the plurality of resolved incident tickets may include processing each resolution statement of the resolution with at least one domain-specific statement classifier specific to the incident domain to either discard or retain a classified resolution statement; processing each retained classified resolution statement in conjunction with the worklog to determine whether to discard or retain the resolved incident; providing an updated resolution for the resolved incident when the resolved incident is retained, and adding the resolved incident with the updated resolution to the processed incident tickets. Then, at least one machine learning model may be trained to process a new incident ticket, using the processed incident tickets.

Domain-specific generative machine learning models

Described systems and techniques enable prediction of a state of an application at a future time, with high levels of accuracy and specificity. Accordingly, operators may be provided with sufficient warning to avert poor user experiences. Unsupervised machine learning techniques may be used to characterize current states of applications and underlying components in a standardized manner. The resulting data effectively provides labelled training data that may then be used by supervised machine learning algorithms to build state prediction models. Resulting state prediction models may then be deployed and used to predict an application state of an application at a specified future time.

Application state prediction using component state

A method for securing a service implemented on a computer network includes identifying network assets in the computer network used by the service. The method further includes identifying vulnerabilities in one or more of the network assets, determining an asset risk score for each of the network assets, and determining a service risk score for the service. The method involves implementing one or more vulnerability remediation actions on the computer network to reduce the service risk score and secure the service.

Prioritized remediation of information security vulnerabilities based on service model aware multi-dimensional security risk scoring

A method for securing a networked computer system executing an application includes identifying a vulnerable computer resource in the networked computer system, determining all computer resources in the networked computer system that are accessible from, or are accessed by, the vulnerable computer resource, and prioritizing implementation of a remediation action to secure the vulnerable computer resource if a vulnerability path extends from the vulnerable computer resource to a critical computer resource that contains sensitive information. The remediation action to secure the vulnerable computer resource is a safe remediation action that does not impact availability of the application executing on the networked computer system.

Reachability graph-based safe remediations for security of on-premise and cloud computing environments

A cloud-native proxy gateway is reachable from a central server and from an isolated cloud VM. A method allows legacy (non-cloud native) solutions to establish a secure connection to the isolated cloud VM, even when incoming port flows are not enabled. The method involves transforming a TCP/IP network connection request into a cloud API call, ignoring IP addresses, and instead using a unique cloud resource identifier as the primary network routing methodology. In response to a communication connection request by the central server, the isolated VM establishes a reverse tunnel to the cloud-native proxy gateway. Communication flow initiated by the central server proceeds through the reverse tunnel to the isolated VM, avoiding an issue of duplicate IP addresses in the cloud.

Cloud-native proxy gateway to cloud resources

A data management system includes a data reconciliation engine that identifies data sources that contain data records referencing a resource and determines whether each of the identified data sources is a creative data source or an additive data source. When all of the identified data sources are additive data sources, the reconciliation engine terminates a data reconciliation process. When all of the identified data sources are not additive data sources, the reconciliation engine finds a first creative data source from among the identified data sources, and initiates the data reconciliation process by merging data from the identified data sources including the first creative data source, one data source-by-one data source, into a reconciled data record.

Creative and additive reconciliation of data records

A first datastore discovers a configuration item (CI), without a persistent unique identifier in a distributed datastores environment. When the first datastore has authoritative naming rights, it determines an authoritative identification for the CI. When the first datastore has advisory naming rights, it suggests a name for the CI to a second datastore having authoritative naming rights. The second datastore determines that a pre-existing identification for the CI in the second datastore is the authoritative identification for the CI. If there is no pre-existing identification for the CI in the second data store, the second data store accepts the suggested name as the authoritative identification for the CI. When the first datastore has no naming rights for the CI, it sends the CI to a third data store having authoritative naming rights for the CI to get an authoritative identification for the CI.

Cooperative naming for configuration items in a distributed configuration management database environment

A content engine may utilize a configuration management database (CMDB) to manage a configuration of a technology landscape. A curation managermay utilize a plurality of article sources to provide, in collaboration with the content engine, a plurality of enriched articles that are specific to the technology landscape. The enriched articles enable an IT administrator using the content engine to execute IT administration duties in a fast, efficient, reliable, and timely manner.

Search data curation and enrichment for deployed technology

In accordance with aspects of the disclosure, systems and methods are provided for normalizing data representing entities and relationships linking the entities including defining one or more graph rules describing searchable characteristics for the data representing the entities and relationships linking the entities, applying the one or more graph rules to the data representing the entities and the relationships linking the entities, identifying one or more matching instances between the one or more graph rules and the data representing the entities and the relationships linking the entities, and performing one or more actions to update the one or more matching instances between the one or more graph rules and the data representing the entities and the relationships linking the entities.

Multi-entity normalization

Disclosed are methods and systems to provide coordinated identification of data items across a plurality of distributed data storage repositories (datastores). In one disclosed embodiment, a single configuration management database (CMDB) controls identification rights for all CIs as they are first identified in a master/slave relationship with all other CMDBs in the distributed environment. In a second embodiment, a plurality of CMDBs divide identification rights based upon coordination identification rules where certain CMDBs are assigned authoritative identification rights for CIs matching the rules of a particular CMDB in the distributed environment. In a third embodiment, one or more of the plurality of CMDBs may also have advisory identification rights for CIs which do not already have an identifiable unique identity and can coordinate with an authoritative CMDB to establish an identity for CIs.

In a general aspect, a computer-implemented method can include receiving a request to provision a plurality of containers of an application across a plurality of data center hosts and iteratively placing the plurality of containers on the plurality of data center hosts. The containers can be selected for placement based on one of a locality constraint and an association with previously-placed containers. Placement of a selected container can be based on, at least, compute requirements of the selected container, network requirements of the selected container, configuration of the plurality of data center hosts, and performance metrics for the plurality of data center hosts.

Growing community of inventors

Santa Clara, CA, United States of America

Ajoy Kumar