Network asset data discovered by Genian NAC becomes a managed asset within the ServiceNow CMDB operational framework.
NAC + CMDB = Asset Lifecycle, Accurate from Day One
An asset on the network that isn’t in the CMDB doesn’t exist as far as operations are concerned. The moment a device connects to the network is the first entry in its Asset Lifecycle.
- Genian NAC: Discovers and identifies every device on the network — without agents, without credential sharing.
- ServiceNow: Asset management tied to owners, services, and operational processes cannot start without network data.
Service Graph Connector (SGC): The moment a device connects, NAC detects it. That data is automatically registered in the CMDB via scheduled Pull — immediately after the initial setup is complete.
Data Mapping Structure
Each NAC node is registered in the CMDB as three linked CIs, following ServiceNow’s IRE (Identification and Reconciliation Engine) rules. This structure ensures data consistency and traceability.
- Base CI: Hardware identity: manufacturer, class, operational status
- Network Adapter CI: Linked to the Base CI via MAC address
- IP Address CI: Linked to the Base CI via IP address
What This Integration Actually Solves
The Service Graph Connector for Genians synchronizes the following fields to the ServiceNow CMDB: IP address, MAC address, active status, hostname (FQDN), domain, node type, Node ID, device ID, platform, OS name, OS version, manufacturer, serial number, CPU speed, RAM, memory capacity, switch name, switch port, Sifname, SSID, and NIC vendor.
When this data is combined with ServiceNow’s operational data — owners, services, change history — the technical context and business context of each asset are unified within a single CI.
| Automation | Reliability | Visibility |
|---|---|---|
| The CMDB stays current without manual input. | Data identified at Layer 2 without agents cannot be tampered with or omitted. | What is connected, where, in what state, and with what vulnerabilities — consolidated in a single CI. |
Early Access Program
Genian NAC SGC is approaching its official release on the ServiceNow Store. Before that release, Genians is running an Early Access Program for a select group of customers and partners.
What Early Access Participants Get
- Validate the connector in your own live network environment before general availability.
- Requirements and improvement feedback are incorporated into the product before official release.
- Priority access to the product roadmap and release timeline.
- At the time of official release, your infrastructure already has a validated connector in place.
- The SGC is provided at no charge.
Participation Requirements
- Eligible participants: Organizations currently subscribed to Genian NAC and holding a ServiceNow Non-production instance.
- Supported versions:
- Cloud-managed Genian NAC V5.0 Enterprise Edition,
- Genian NAC 6.0 Software Enterprise Edition,
- ServiceNow Zurich.
- Supported versions:
- Selection: First-come, first-served. Limited to 10 organizations.
- Test environment: Non-production instance only. Production environments and Federal Customers are excluded.
- Feedback: Submit issues and customization requests directly to your Genians contact via email or Jira ticket.
- Terms: Installing the app constitutes acceptance of the App Terms and Conditions. Separate Early Access Program agreement required — accepted via checkbox at online registration.
How to Apply
Customers and partners wishing to participate in Early Access can reach out below. After confirming your request, Genians will send participation instructions and the agreement link.
During the program, communication and feedback are managed through the following channels:
- Email: direct contact with your Genians program manager
- Jira: issue tracking and feature requests via the shared Genians Jira workspace
- Slack: dedicated channel for real-time Q&A and program updates
FAQ
Pre-Implementation Considerations
1. Do we need to be using both Genian NAC and ServiceNow?
Yes. You must have access to the Genian NAC API Key and a ServiceNow instance.
https://docs.genians.com/nac/5.0/release/en/api.html
2. Which versions of Genian NAC and ServiceNow are supported?
3. Do we need to install an agent?
4. Does this affect existing CMDB data?
Data-Related
5. What data is imported into the CMDB? Will unwanted data be imported as well?
IP Address, MAC Address, Active Status, FQDN, Domain, Node Type, Node ID, Device ID, Platform, OS Name, OS Version information, Manufacturer, Serial Number, CPU Speed, RAM Capacity, Memory Capacity, Switch Name, Switch Port, Sifname, SSID, and NIC Vendor detected by Genian NAC will be synchronized. Unwanted data fields can be excluded during the mapping configuration stage. Conversely, if there is additional data you wish to synchronize, users can extend the fields through separate configurations.
6. Are all devices detected by Genian NAC registered in the CMDB, or can they be filtered?
7. How long does it take for Genian NAC data to be reflected in ServiceNow CMDB as CI?
8. Is there a possibility of conflict or duplicate creation with existing CMDB CIs?
Security & Operations
9. Is there any risk of the Genian NAC API Key being exposed externally?
10. What happens to the existing CMDB data if the integration is stopped?
11. Why must this be tested only in a Non-production instance?
Early Access Program
12. Is there a difference between the Early Access and the official release version?
13. How do I submit issues discovered during the Early Access period?
Discovered issues can be submitted via email to hello@genians.com or by creating a Jira ticket.
