---
title: "Synchronizing, Grouping, and Scanning Assets of Infoblox IPAM"
canonical: "https://docs.infoblox.com/space/DeploymentGuideIPAMTDwithRapid7/1631813758/Synchronizing%2C%20Grouping%2C%20and%20Scanning%20Assets%20of%20Infoblox%20IPAM"
format: markdown
---
> ℹ️ Only Infoblox objects or IP spaces tagged with **Rapid7_sync** set to true will be synchronized with Rapid7; without this tag, no other tags will be evaluated.

### 1. Tag Configuration on Infoblox IP Space

- The IP Space is tagged with the following values:
  - `Rapid7_sync = true` – Enables asset synchronization
  - `Rapid7_group = Group2` – Assigns the asset to a specific group in Rapid7
  - `Rapid7_scan = true` – Triggers a vulnerability scan
    

> ℹ️ Even if specific objects like address blocks, subnets, or ranges are tagged with `Rapid7_sync = false`, the individual IPs within them may still be synchronized if they inherit tags from a parent object—such as the IP Space—due to Infoblox’s top-down inheritance model.

### 2. Asset Creation in Rapid7

- The tagged IPs are successfully synced from Infoblox to Rapid7 as individual assets.
- Each synced asset appears in the Rapid7 console under the configured site.

### 3. Asset Grouping Verification

- Synced assets are correctly grouped under the specified group name (`Group2`) in Rapid7.
- This confirms that the `Rapid7_group` tag was processed correctly.

### 4. Scan Information Synced Back to Infoblox

- After a scan is completed in Rapid7, scan results are pushed back and reflected in Infoblox as asset tags:
  - `Rapid7_scan_id` – Unique identifier for the scan
  - `Rapid7_scan_time` – Timestamp of when the scan was executed
  - `Rapid7_Vulnerabilities_CVE_Id` – Detected CVEs
  - `Rapid7_Vulnerability_Severity` – Severity of vulnerabilities (e.g., Critical)