---
title: "Best Recommended Practices for Infoblox + Rapid7 Integration"
canonical: "https://docs.infoblox.com/space/DeploymentGuideIPAMTDwithRapid7/1631846502/Best%20Recommended%20Practices%20for%20Infoblox%20%2B%20Rapid7%20Integration"
format: markdown
---
### **1. Delay Script Activation for Stability**

**Recommendation:**  
Enable the **Event Handler** and **Scheduler (Fetch Scan Results)** scripts only **after 24 hours** from the initial sync.  
**Why:**  
This allows full and stable asset synchronization before initiating scan workflows.


### **2. Use **`restrictToUsedIps`** to Focus on Active Assets**

**Recommendation:**  
Enable the `restrictToUsedIps` parameter to sync and scan only IPs that are currently in use (e.g., those with MAC addresses).  
**Why:**  
This minimizes unnecessary scanning and improves operational efficiency by targeting real, active endpoints.


### **3. Customize Rapid7 Site Name if Needed**

**Recommendation:**  
Use the default site name `"Infoblox Assets Site"` unless your organization has a specific grouping or site naming strategy.  
**Why:**  
Ensures easy setup and consistent reporting, with the flexibility to support custom scan zones.


### **4. Avoid Tagging at the IP Space Level**

**Recommendation:**  
Avoid applying tags at the IP Space level, as it can significantly increase the number of objects in the system.

**Why:**  
Tagging at this level may lead to performance degradation or exceed system object limits.

**Best Practice:**  
Apply tags at a more granular level—such as individual IP addresses or subnets—for better scalability and system stability.