Skip to main content

Cisco

The Cisco integration reads ASA firewalls over SSH. It runs on an Integrator inside your network. The platform is identified from show version when the Integrator connects: an IOS or IOS-XE device is refused with an error naming the Cisco IOS / IOS-XE integration, and a Nexus switch one naming Cisco NX-OS, both under Network.

It is read-only: the Integrator runs show commands 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; ACLs and the interfaces they are applied to
Configuration reviewEvery configuration backup and NAT sync is reviewed against the configuration review checks, and what they find is raised as vulnerabilities on the device
Network discoveryInterfaces (address, nameif, link state, speed), the networks they are addressed into, and the routing table
Host discoveryARP
Exposure correlationNAT: object and twice NAT

What the device reports is kept as its own record, alongside hosts and subnets rather than written into them.

Create a read-only account​

The account needs to run show commands, including show running-config: a user at privilege 15, or a lower privilege with an enable password in the integration.

SSH must be enabled on the management interface for the Integrator's address.

Connect it​

  1. Under Integrations, add Cisco with the device's management hostname, the SSH port if it is not 22, the username and password, and the enable password if the account needs one.
  2. In the integration's settings, assign the Integrator that can reach the device.
  3. Enable the syncs you want.

Host keys and algorithms​

The first connection records the device's SSH host key; every later connection must present the same key. If you replace or re-key the device, clear the pinned host key in the integration's settings so the new one is recorded.

Only modern SSH algorithms are offered. An older device that supports nothing else can be allowed legacy algorithms in the integration's settings; that change is recorded in the audit log.