Atlassian

Importer Data Types

• Asset Details Enrichment and Create New in Vantage

  Jira Service Management supplies records including object name, IPs, MAC, OS, owner, object type, schema, status and last-updated timestamp — to enrich existing Vantage assets and create new asset records for endpoints not yet observed on the OT network.

Joint Use Cases

• Correlating Atlassian signals with OT network alerts

  When Nozomi Vantage raises an anomaly alert for a device inside an OT segment, the analyst can pivot to the same asset's Jira Service Management record in Vantage to review CI ownership, environment, location and recent change history, all without leaving the Vantage investigation workflow. This cross-layer correlation surfaces whether a network-layer anomaly coincides with activity observed by Atlassian, reducing the time needed to confirm or dismiss an incident.

• Closing asset inventory gaps across IT and OT

  Devices recorded by Jira Service Management but not yet observed by Nozomi network sensors are automatically created as new asset records in Vantage, populated with CI name, IPs, MAC, manufacturer, model and location drawn from the Atlassian management plane. OT operations teams can audit the resulting unified inventory to identify unmonitored or underprotected assets in industrial and critical infrastructure zones, then prioritize sensor deployment accordingly.

• Aligning CMDB ownership with OT-observed asset reality

  Network-observed assets in Vantage are reconciled against their CMDB CI in Jira Service Management, surfacing devices that exist on the network but not in the CMDB, and vice versa. This supports the asset-governance workflows that ITAM and OT engineering teams need to keep ownership, location and lifecycle data accurate.

Integration Prerequesites