USB Switches- CMDB

[Tina Bowers]

For the first time, I received a request to add USB Switches as a CI record.  They will be accompanied by license keys.  I have done some research online and everything says netgear, ip device, or computer and non of those seem to be an appropriate class.  I am not even sure that they should be in the CMDB.  They have their own IP address so I am struggling with not putting them in.   Any advice would be greatly appreciated! 

[L_H]

This is a question which everyone responsible for a CMDB has to deal with quite regularly.
Before deciding if, and to which CI-Class, these USB Switches should be added, consider which processes require this CI data.
If for example the USB Switches are supported (Incident Management), or if there is an Operating System running on them which could theoretically be relevant for Vulnerability Management, then it is quite likely that they should be added to the CMDB.
Once you know the process dependencies, you can start considering which of the available possible CI Classes are best used for the processes requiring theses CIs.
That still might not give you an easy answer, but understanding process requirements is never a bad way to tackle a difficult question.

[MaxMixali]

ServiceNow CMDB – How to Handle USB Switches as Configuration Items (CIs)

Scenario
You received a request to add USB Switches as Configuration Items (CIs), each accompanied by a license key. These devices have their own IP address, so you’re uncertain whether they belong in the CMDB and under which class.

Analysis
------------------------------------------------------------
USB switches are typically small network-attached or peripheral control devices that allow sharing of USB peripherals (e.g., keyboards, storage, cameras) across multiple systems. They are *not* core IT infrastructure, but they may have an IP address for management (e.g., network-based USB hubs).

Key considerations before adding them to CMDB:
1. **Purpose of inclusion**
- CMDB should reflect assets that have operational, security, or support impact.
- If the switch is business-critical (e.g., used in labs, monitoring environments, or production control systems), inclusion can be justified.
- If it’s a basic office utility (like a USB sharing hub), it may belong in the asset repository, not the CMDB.

2. **License association**
- If license tracking is required for compliance or maintenance, create a Software Model and associate the license to a hardware asset record rather than a full CI.

3. **Network accessibility**
- Since the device has an IP address, it could be discovered through Discovery. However, Discovery would likely classify it as an “Unknown IP Device” unless manually categorized.

Recommended Classification Options
------------------------------------------------------------
Option A – If the device is managed or monitored
- Class: **cmdb_ci_network_adapter** or **cmdb_ci_network_device** (if manageable via SNMP or similar protocols)
- Attributes to maintain:
- Name, serial number, IP address, location, and associated licenses
- Link to a parent CI (e.g., workstation, lab controller)

Option B – If the device is unmanaged or peripheral
- Class: **cmdb_ci_peripheral** or **cmdb_ci_computer_peripheral**
- These classes represent auxiliary equipment like docking stations, KVMs, or USB hubs.
- Use this if the device supports business operations but is not monitored.

Option C – If tracking only for asset/license compliance
- Do not include it in CMDB; instead, manage it in **alm_asset** with a related **Software License [alm_license]** record.
- Create a simple asset entry: Model category “Peripheral / Network Accessory.”
- Link license keys under associated contracts.

Best Practice Decision Tree
------------------------------------------------------------
1. Does the USB switch affect production service delivery or monitoring?
- Yes → CMDB (Network Device or Peripheral)
- No → Asset table only

2. Is it monitored or discoverable via IP?
- Yes → CMDB as a lightweight network device (custom class under cmdb_ci_network)
- No → Asset management only

3. Do you need to track licenses for compliance?
- Yes → Create License Model and link to Asset.
- No → Treat as consumable or peripheral inventory.

Recommended Configuration Example
------------------------------------------------------------
If added to CMDB:
- Class: cmdb_ci_peripheral (OOB)
- Key fields:
- Name: USB Switch [Model Name]
- IP Address: [Device IP]
- Serial Number
- Location / Assigned To
- Related Software / License record (relationship type: “Depends on”)
- Relationship: Connected to → Host Computer / Service

If asset-only:
- Table: alm_asset
- Model Category: Peripheral
- Track license in alm_license and link to asset.

Summary
------------------------------------------------------------
- USB switches are borderline CI candidates. Only include them in CMDB if they’re network-managed or critical.
- Otherwise, record them in **alm_asset** for inventory and license tracking.
- Use cmdb_ci_peripheral for CIs, or alm_asset for non-critical hardware.
- Keep license association in asset/license management modules, not in CMDB directly.

Decision: Unless part of critical monitored infrastructure, manage as **assets** rather than **CIs**.

[MaxMixali]

ServiceNow – How to Classify USB Switches in the CMDB

Scenario:
You’ve received a request to add USB Switches as CI (Configuration Item) records. These devices have IP addresses and are associated with license keys. The question is whether they belong in the CMDB and, if so, under which CI class.

--------------------------------------------------
1. Determine if the USB Switch Qualifies as a CI
--------------------------------------------------
Use the following criteria to decide if the USB switch should be tracked in CMDB:
- **Configuration impact:** Does the switch have configurable settings (e.g., IP management, firmware updates, monitoring)?
- **Dependency impact:** Does its failure affect other tracked services, assets, or endpoints?
- **Asset tracking requirement:** Is it managed, licensed, or monitored via asset/inventory systems?
- **Compliance requirement:** Does it require patching, audits, or license key control?

If at least two of the above apply → it qualifies as a Configuration Item.

If the device is merely a simple USB splitter or unmanaged peripheral, it is better tracked as an **Asset** rather than a CI.

--------------------------------------------------
2. Recommended CMDB Class
--------------------------------------------------
If the device has network connectivity (an IP address) and participates in infrastructure, use one of the following CMDB classes based on its capabilities:

| Use Case | Suggested Class | Table |
|-----------|------------------|--------|
| Network-managed USB switch (with IP, firmware) | **cmdb_ci_network_device** | Network Gear |
| Unmanaged, peripheral-type device | **cmdb_ci_peripheral** | Peripheral |
| Specialized industrial or OT environment USB hub | **cmdb_ci_computer_peripheral** or custom subclass | Peripheral/Custom |

**Tip:** Avoid placing it under `cmdb_ci_computer` unless the switch runs an OS or hosts software directly.

--------------------------------------------------
3. License Key Tracking
--------------------------------------------------
- If each USB switch includes an associated license, track it in **Software Entitlements [cmdb_software_product_model]** and relate it to the hardware CI via **Installed on::Installs** relationship.
- Alternatively, create a **Custom Relationship** (“Licensed by”) between the USB switch CI and its license record.

--------------------------------------------------
4. Best Practice Recommendation
--------------------------------------------------
- Only add to CMDB if the device is managed, monitored, or critical to operations.
- For small peripherals (e.g., USB docking switches, KVM hubs), manage them in the **Asset table [alm_asset]** instead. You can still link to the CMDB through the **Asset-CI Relationship** if necessary.
- Maintain accurate relationships using the **Dependency Views** feature to visualize impact.

--------------------------------------------------
5. Optional Customization
--------------------------------------------------
If none of the OOB CI classes properly fit your organization’s taxonomy:
1. Create a subclass of **cmdb_ci_peripheral** called **cmdb_ci_usb_switch**.
2. Extend with relevant fields (License Key, Firmware Version, IP Address, etc.).
3. Update Discovery Patterns or Import Sets to map data automatically.

--------------------------------------------------
6. Decision Matrix Summary

| Characteristic | Recommendation |
|----------------|----------------|
| No IP / unmanaged USB hub | Track as Asset only |
| Managed device with IP, SNMP, or firmware | CI in cmdb_ci_network_device |
| Specialized USB controller / KVM hub | Custom subclass of cmdb_ci_peripheral |
| Includes license management | Link to Software Model or License table |

--------------------------------------------------
7. Conclusion
--------------------------------------------------
✔ If the USB switches are IP-enabled and managed, add them as CIs under **cmdb_ci_network_device** or create a custom **USB Switch** subclass.
✔ If they are simple USB hubs without management capabilities, track them in **Asset Management** instead of CMDB.
✔ Link any license key via a **relationship or entitlement record** for audit and compliance tracking.

By applying these rules, your CMDB remains accurate, lean, and aligned with ITIL best practices.