Skip to main content

Cisco NX-OS

The Cisco NX-OS integration reads Nexus switches through NX-API, the switch's HTTPS management API. It runs on an Integrator inside your network, so no switch is exposed to the CyberOptix CTEM Platform. It is listed under Network beside the other switching integrations; Catalyst switches and routers connect through Cisco IOS / IOS-XE.

It is read-only: the integration sends show commands through NX-API and never enters configuration mode.

What it collects​

SyncCollects
Configuration backupshow running-config, with secrets stripped on the Integrator before it leaves your network, versioned whenever it changes
Configuration reviewEvery configuration backup is reviewed against the configuration review checks, and what they find is raised as vulnerabilities on the device
Network discoveryInterfaces with their link state and speed, the VLANs the switch has defined, SVIs and the subnets they address, and the routing table of every VRF
Host discoveryThe connected endpoints: the learned MAC address table, ARP in every VRF, and CDP and LLDP neighbors

Every sync also reports the switch itself, with model, serial number and software version. Devices appear under Attack Surface > Network Devices. What the switch reports is kept as its own record, alongside hosts and subnets rather than written into them.

A VLAN with an SVI is reported as the subnet the SVI addresses, named after the VLAN. A VLAN without one is still reported, as a network with no address, so the segments a switch carries are visible even where nothing routes them.

Enable NX-API and create a read-only account​

NX-API is off by default. Enable it over HTTPS and create a local user in the network-operator role, which can run show commands and nothing else:

feature nxapi
nxapi https port 443
username inventory password <password> role network-operator

The integration sends the username and password with every request, over HTTPS only. It never uses the HTTP port.

Connect it​

  1. Under Integrations, add Cisco NX-OS with the switch's management address (hostname or IP), the username and the password.
  2. In the integration's settings, assign the Integrator that can reach the management address on port 443.
  3. Enable the syncs you want.

Each switch is its own integration.

Certificates​

A Nexus ships with a self-signed management certificate. The first connection accepts it and records its fingerprint on the integration; every later connection must present the same certificate. If you replace the certificate, clear the pinned fingerprint in the integration's settings so the new one is recorded. A certificate issued by a trusted CA is verified normally and never pinned.

A wrong password fails the sync with an error. It does not report an empty device.