# US 2014/0156711 A1 · Asset model import connector

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0156711 A1
- Document ID: US20140156711A1
- Status: Published application
- Kind: A1
- Application number: 14/233,178
- Filed: 2012-08-01
- Published: 2014-06-05
- Earliest claimed: 2011-08-01
- Assignees: Hewlett Packard Enterprise Development LP
- Inventors: Dhiraj Sharan; Qiang Zeng; Sez-ming Yee
- Web page: https://patentgrep.com/patent/US20140156711A1

## CPC

- G06F 16/212: {with details for data modelling support}
- H04L 41/022: Multivendor or multi-standard integration
- H04L 41/0266: using meta-data, objects or commands for formatting management information, e.g. using eXtensible markup language [XML]
- H04L 41/0631: using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
- H04L 63/1416: {Event detection, e.g. attack signature detection}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

An asset model import connector includes an interface to receive asset data from a data source and a normalize module. The normalize module determines an operation to be performed at a system based on the received asset data and determines code to perform the determined operation. The schema may be populated with attributes from the asset data, and sent to the system.

## Claims

### Claim 1

An asset model import connector comprising:
an interface to receive asset data from a data source, wherein the asset data describes an asset in a computer network; and
a normalizing module executed by at least one processor to determine an operation to be performed at a system based on the received asset data, determine code and asset attributes from a schema to include in the code to instruct the system to perform the operation, generate the code and populate the attributes in the code with values from the received asset data, and send the code with the attribute values to the system.

### Claim 2 (depends on 1)

The asset model import connector of claim 1, comprising data storage to store code templates describing different operations to be performed on asset data stored at the system, and each code template includes different attributes from the schema, wherein the determined code is determined from the code template for the operation.

### Claim 3 (depends on 2)

The asset model import connector of claim 2, wherein the different operations comprise adding an asset, removing an asset, moving an asset from one group to another, adding an asset to a group, removing an asset from a group, moving an asset from one category to another to another, adding an asset to a category, removing an asset from a category, moving an asset from one zone to another, adding an asset to a zone, removing an asset from a zone, and marking an asset as enabled or disabled.

### Claim 4 (depends on 1)

The asset model import connector of claim 1, comprising:
a filter and condition module to identify if the received asset data matches a condition and if the received asset data matches the condition to send the received asset data to the system.

### Claim 5 (depends on 1)

The asset model import connector of claim 1, comprising:
a batch module to control how much asset data is sent to the system and when to send the asset data to the system.

### Claim 6 (depends on 1)

The asset model import connector of claim 1, wherein the selected schema describes the operation.

### Claim 7 (depends on 1)

The asset model import connector of claim 1, wherein the system is external to the asset model import connector and the asset model import connector sends the populated schema to the system via a computer network.

### Claim 8 (depends on 1)

The asset model import connector of claim 1, wherein the system comprises a security information and event management system to correlate event data and asset data.

### Claim 9 (depends on 1)

The asset model import connector of claim 1, wherein the normalize module is to determine the operation from an indication of the operation in the received collection data.

### Claim 10 (depends on 1)

The asset model import connector of claim 1, wherein the normalize module is to determine the operation by determining whether the received asset data includes attributes specified in a rule for determining the operation, and if the received collection data includes the attributes, determining the operation from the rule.

### Claim 11

A non-transitory computer readable medium including machine readable instructions executable by at least one processor to:
store a plurality of different code templates at an asset model import connector, wherein the code templates describe different operations to be performed on asset data stored at a system external to the asset model import connector;
receive asset data from a data source, wherein the asset data described an asset in a computer network;
determine an operation to be performed on the asset data stored at the system based on the received asset data;
select one of the plurality of code templates for the operation; and
generate code from the selected code template, wherein the code includes asset attributes from a schema used to store the asset data at the system.

### Claim 12 (depends on 11)

The non-transitory computer readable medium of claim 11, wherein the machine readable instructions to determine the operation comprise machine readable instructions to:
request information associated h the received asset data from the system; and
determine the operation from the requested information.

### Claim 13 (depends on 11)

The non-transitory computer readable medium of claim 11, wherein the machine readable instructions to determine the operation comprise machine readable instructions to determine the operation from an indication of the operation in the received collection data.

### Claim 14 (depends on 11)

The non-transitory computer readable medium of claim 11, wherein the machine readable instructions to determine the operation comprise machine readable instructions to:
determine whether the received asset data includes attributes specified in a rule for determining the operation; and
if the received collection data includes the attributes, determine the operation from the rule.

### Claim 15

A method of normalizing asset data at an asset model import connector, he method comprising:
receiving asset data from a data source, wherein the asset data describes an asset in a computer network;
determining an operation to be performed at a system based on the received asset data;
generating, by at least one processor, code to instruct the system to perform the operation, wherein the code includes asset attributes from a schema, and the schema is used by the system to store data for assets;
populating the asset attributes in the code with values from the received asset data; and
sending the code with the populated asset values to the system