Cisco

Cisco Smart Net Total Care (SNTC) is a network management platform that provides device inventory, hardware and software details, security advisories, and end-of-life (EoL) tracking for Cisco network infrastructure. You can bring device, hardware, software, security advisory, and end-of-life data from Cisco into Brinqa to construct a unified view of your network asset landscape and strengthen your cybersecurity posture.

This document details the information you must provide for the connector to authenticate with Cisco and how to obtain that information from Cisco. See create a data integration for step-by-step instructions on setting up the integration.

Required connection settings

When setting up a data integration, select Cisco from the Connector dropdown. If you cannot find the connector in the dropdown, make sure that you have installed it first. You must provide the following information to authenticate Cisco with Brinqa:

• Server URL: The Cisco CX Cloud API base URL. The default URL is https://apx.cisco.com.

• Login URL: The OAuth 2.0 token endpoint URL used to obtain an access token. The default URL is https://cloudsso.cisco.com/as/token.oauth2.

• Client ID: The OAuth 2.0 client ID for authenticating with the Cisco CX Cloud API.

• Client Secret: The OAuth 2.0 client secret for authenticating with the Cisco CX Cloud API.

• Customer ID: The Cisco customer ID used to scope the SNTC data retrieved from the API.

Obtain Cisco CX Cloud API credentials

For the connector to use the Cisco CX Cloud API, you must provide an OAuth 2.0 client ID and client secret. To obtain these credentials, follow these steps:

1. Log in to the Cisco API Console.

2. Navigate to My Apps & Keys.

3. Click Register a New App.

4. Enter a name and description for the application.

5. Under OAuth 2.0 Credentials, select Client Credentials as the grant type.

6. Select the required API scopes for Smart Net Total Care access.

7. Click Register.

   Your client ID and client secret display. Copy and save them to a secure location.

note

If you do not have the permissions to create API credentials, contact your Cisco administrator. For additional information, see Cisco Developer documentation.

Additional settings

The Cisco connector contains additional options for configuration:

• Page size: The maximum number of records to get per API request. The default setting is 100.

• Parallel requests: The number of concurrent API requests the connector can make. The default setting is the lesser of 4 or the number of available processors.

Types of data to retrieve

The Cisco connector can retrieve the following types of data from the Cisco CX Cloud API:

Table 1: Data retrieved from Cisco

Connector Object	Required	Maps to Data Model
Device	Yes	Host
Hardware	Yes	Host
Software	Yes	Package
Software Install	Yes	Installed Package
Security Alert	Yes	Vulnerability
Security Bulletin	Yes	Vulnerability Definition
Hardware EoL	Yes	Hardware EoL
Hardware EoL Bulletin	Yes	EoL Advisory
Software EoL	Yes	Software EoL
Software EoL Bulletin	Yes	EoL Advisory

info

The Cisco connector does not support operation options for the types of data it retrieves.

For detailed steps on how to view the data retrieved from Cisco in the Brinqa Platform, see How to view your data.

Attribute mappings

Expand the sections below to view the mappings between the source and the Brinqa data model attributes.

Device

Table 2: Device attribute mappings

Source Field Name	SDM Attribute
NetworkDevice.neInstanceId	UID
NetworkDevice.neInstanceId	INSTANCE_ID
NetworkDevice.hostname	HOSTNAMES
NetworkDevice.sysDescr	DESCRIPTION
NetworkDevice.ipAddress	IP_ADDRESSES
NetworkDevice.macAddress	MAC_ADDRESSES
NetworkDevice.createDate	SOURCE_CREATED_DATE
NetworkDevice.managementAddress	MANAGEMENT_ADDRESS
NetworkDevice.swType	SW_TYPE
NetworkDevice.swVersion	SW_VERSION
NetworkDevice.productId	PRODUCT_ID
NetworkDevice.productFamily	PRODUCT_FAMILY
NetworkDevice.productType	PRODUCT_TYPE
NetworkDevice.reachabilityStatus	REACHABLE_STATUS
NetworkDevice.imageName	IMAGE_NAME
NetworkDevice.sysLocation	LOCATION
NetworkDevice.bootstrapVersion	BOOTSTRAP_VERSION
NetworkDevice.inventoryName	INVENTORY
NetworkDevice.resetReason	RESET_REASON
NetworkDevice.lastReset	LAST_RESET
NetworkDevice.inventoryCollectionDate	COLLECTION_DATE

Hardware

Table 3: Hardware attribute mappings

Source Field Name	SDM Attribute
HardwareDevice.hwInstanceId	UID
HardwareDevice.hwName	NAME
HardwareDevice.neInstanceId	INSTANCE_ID
HardwareDevice.serialNumber	SERIAL_NUMBER
HardwareDevice.collectedSerialNumber	COLLECTED_SN
HardwareDevice.productId	PRODUCT_ID
HardwareDevice.productName	PRODUCT_NAME
HardwareDevice.productDescription	PRODUCT_DESC
HardwareDevice.productFamily	PRODUCT_FAMILY
HardwareDevice.productType	PRODUCT_TYPE
HardwareDevice.productSubtype	PRODUCT_SUBTYPE
HardwareDevice.hwType	HARDWARE_TYPE
HardwareDevice.swVersion	SW_VERSION
HardwareDevice.inventoryName	INVENTORY

Software

Table 4: Software attribute mappings

Source Field Name	SDM Attribute
Generated (MD5 of inventoryName, swType, swVersion, swMajorVersion, swCategory, swName)	UID
Software.swName	NAME
Software.swCategory	CATEGORIES
Software.swType	SOFTWARE_TYPE
Software.swVersion	SOFTWARE_VERSION
Software.swMajorVersion	MAJOR_VERSION
Software.inventoryName	INVENTORY

Software Install

Table 5: Software Install attribute mappings

Source Field Name	SDM Attribute
Generated (MD5 of customerId, managedNeInstanceId, inventoryName, swType, swVersion, swMajorVersion, swCategory, swName)	UID
Generated (MD5 of inventoryName, swType, swVersion, swMajorVersion, swCategory, swName)	TYPE
Software.managedNeInstanceId	TARGETS
Software.swStatus	STATUS

Security Alert

Table 6: Security Alert attribute mappings

Source Field Name	SDM Attribute
Generated (MD5 of neInstanceId, managedNeInstanceId, hwInstanceId, securityAdvisoryInstanceId)	UID
SecurityAdvisory.neInstanceId	TARGETS
SecurityAdvisory.vulnerabilityStatus	STATUS
Derived from STATUS	STATUS_CATEGORY
SecurityAdvisory.vulnerabilityStatus	SOURCE_STATUS
SecurityAdvisory.securityAdvisoryInstanceId	BULLETIN_ID
SecurityAdvisory.neInstanceId	DEVICE_ID
SecurityAdvisory.hwInstanceId	HARDWARE_ID
SecurityAdvisory.vulnerabilityReason	REASON

Security Bulletin

Table 7: Security Bulletin attribute mappings

Source Field Name	SDM Attribute
SecurityAdvisoryBulletin.securityAdvisoryInstanceId	UID
SecurityAdvisoryBulletin.bulletinTitle	DESCRIPTION
SecurityAdvisoryBulletin.bulletinSummary	SUMMARY
SecurityAdvisoryBulletin.cveId	CVE_IDS
SecurityAdvisoryBulletin.cveId	CVE_RECORDS
SecurityAdvisoryBulletin.bulletinFirstPublished	PUBLISHED_DATE
SecurityAdvisoryBulletin.bulletinLastUpdated	SOURCE_LAST_MODIFIED
SecurityAdvisoryBulletin.url	URL
SecurityAdvisoryBulletin.cvssBaseScore	CVSS_V2_BASE_SCORE
SecurityAdvisoryBulletin.cvssTemporalScore	CVSS_V2_TEMPORAL_SCORE
SecurityAdvisoryBulletin.advisoryId	ADVISORY_ID
SecurityAdvisoryBulletin.bulletinVersion	BULLETIN_VERSION
SecurityAdvisoryBulletin.securityImpactRating	RATING
SecurityAdvisoryBulletin.alertAutomationCaveat	AUTOMATION_CAVEAT
SecurityAdvisoryBulletin.ciscoBugIds	CISCO_BUG_ID

Hardware EoL

Table 8: Hardware EoL attribute mappings

Source Field Name	SDM Attribute
Generated (MD5 of neInstanceId, managedNeInstanceId, hwInstanceId, productId, hwEolInstanceId)	UID
HwEoL.hostname	HOSTNAMES
HwEoL.neInstanceId	INSTANCE_ID
HwEoL.inventoryName	INVENTORY_NAME
HwEoL.hwEolInstanceId	BULLETIN_ID
HwEoL.hwInstanceId	HARDWARE_ID
HwEoL.hwType	HARDWARE_TYPE
HwEoL.productId	PRODUCT_ID
HwEoL.currentHwEolMilestone	CURRENT_EOL_MILESTONE
HwEoL.currentHwEolMilestoneDate	CURRENT_EOL_MILESTONE_DATE
HwEoL.nextHwEolMilestone	NEXT_EOL_MILESTONE
HwEoL.nextHwEolMilestoneDate	NEXT_EOL_MILESTONE_DATE

Hardware EoL Bulletin

Table 9: Hardware EoL Bulletin attribute mappings

Source Field Name	SDM Attribute
HwEoLBulletin.hwEolInstanceId	UID
HwEoLBulletin.url	URL
HwEoLBulletin.bulletinProductId	PRODUCT_ID
HwEoLBulletin.bulletinNumber	BULLETIN_ID
HwEoLBulletin.bulletinTitle	BULLETIN_TITLE
HwEoLBulletin.eoLifeAnnouncementDate	EOL_ANNOUNCEMENT_DATE
HwEoLBulletin.eoSaleDate	EOS_DATE
HwEoLBulletin.lastShipDate	LAST_SHIP_DATED
HwEoLBulletin.eoSwMaintenanceReleasesDate	EO_SW_MAINTENANCE_RELEASES_DATE
HwEoLBulletin.eoRoutineFailureAnalysisDate	EO_ROUTINE_FAILURE_ANALYSIS_DATE
HwEoLBulletin.eoNewServiceAttachmentDate	EO_NEW_SERVICE_ATTACHMENT_DATE
HwEoLBulletin.lastDateOfSupport	LAST_DATE_OF_SUPPORT
HwEoLBulletin.eoVulnerabilitySecuritySupport	EO_VULNERABILITY_SECURITY_SUPPORT

Software EoL

Table 10: Software EoL attribute mappings

Source Field Name	SDM Attribute
Generated (MD5 of neInstanceId, managedNeInstanceId, swType, swVersion, swEolInstanceId)	UID
SwEoL.hostname	HOSTNAMES
SwEoL.inventoryName	INVENTORY_NAME
SwEoL.swEolInstanceId	BULLETIN_ID
SwEoL.neInstanceId	INSTANCE_ID
SwEoL.swType	SOFTWARE_TYPE
SwEoL.swVersion	SOFTWARE_VERSION
SwEoL.currentSwEolMilestone	CURRENT_EOL_MILESTONE
SwEoL.nextSwEolMilestone	NEXT_EOL_MILESTONE
SwEoL.currentSwEolMilestoneDate	CURRENT_EOL_MILESTONE_DATE
SwEoL.nextSwEolMilestoneDate	NEXT_EOL_MILESTONE_DATE

Software EoL Bulletin

Table 11: Software EoL Bulletin attribute mappings

Source Field Name	SDM Attribute
SwEoLBulletin.swEolInstanceId	UID
SwEoLBulletin.url	URL
SwEoLBulletin.swType	SOFTWARE_TYPE
SwEoLBulletin.swMajorVersion	SW_VERSION
SwEoLBulletin.swMaintenanceVersion	SW_MAINTENANCE_VERSION
SwEoLBulletin.swTrain	SOFTWARE_TRAIN
SwEoLBulletin.bulletinNumber	BULLETIN_NUMBER
SwEoLBulletin.bulletinTitle	BULLETIN_TITLE
SwEoLBulletin.eoLifeAnnouncementDate	EOL_ANNOUNCEMENT_DATE
SwEoLBulletin.eoSaleDate	EOS_DATE
SwEoLBulletin.eoSwMaintenanceReleasesDate	EO_SW_MAINTENANCE_RELEASES_DATE
SwEoLBulletin.lastDateOfSupport	LAST_DATE_OF_SUPPORT
SwEoLBulletin.eoVulnerabilitySecuritySupport	EO_VULNERABILITY_SECURITY_SUPPORT
SwEoLBulletin.inventoryName	INVENTORY

APIs

The Cisco connector uses the Cisco CX Cloud REST API. Specifically, it uses the following endpoints:

Table 12: Cisco CX Cloud API Endpoints

Connector Object	API Endpoint
Device	GET /cs/api/v1/inventory/network-elements
Hardware	GET /cs/api/v1/inventory/hardware
Software	GET /cs/api/v1/inventory/software
Software Install	GET /cs/api/v1/inventory/software
Security Alert	GET /cs/api/v1/product-alerts/security-advisories
Security Bulletin	GET /cs/api/v1/product-alerts/security-advisory-bulletins
Hardware EoL	GET /cs/api/v1/product-alerts/hardware-eol
Hardware EoL Bulletin	GET /cs/api/v1/product-alerts/hardware-eol-bulletins
Software EoL	GET /cs/api/v1/product-alerts/software-eol
Software EoL Bulletin	GET /cs/api/v1/product-alerts/software-eol-bulletins

Changelog

The Cisco connector has undergone the following changes:

Table 13: Cisco connector changelog

Version	Description	Date Published
3.0.1	Improvements - Connector-sourced attribute values now take precedence over non-connector data channels (manual edits, bulk imports, UI input) when the platform consolidates records, so Cisco data is no longer overridden by lower-priority sources. - Attribute values are now written through the platform's shared, type-validating attribute helper, so values are validated against the declared schema type at write time instead of being stored with the wrong type. Bug Fixes - Corrected the End-of-Life date attributes to be stored as proper timestamps. The Hardware and Software EoL and EoL Bulletin models were storing these dates as numbers (epoch milliseconds) instead of timestamps. Affected attributes: "Current EoL milestone date", "Next EoL milestone date", "EoL announcement date", "EoS date", "Last ship date", "End of SW maintenance releases date", "End of routine failure analysis date", "End of new service attachment date", "Last date of support", and "End of vulnerability/security support". Migration Required - Hardware EoL, Software EoL, Hardware EoL Bulletin, and Software EoL Bulletin: the date attributes listed above changed from numbers to timestamps. Re-sync the Cisco connector to repopulate these records with the corrected type.	June 9th, 2026
3.0.0	Initial Integration+ release.	June 9th, 2026